Loading
Subprocessor register
A public register of the systems that may support Hanasand delivery. Exact provider names and regions are confirmed in the DPA/order form for the target deployment.
Default posture
Hanasand-operated container services and database storage for the core product.
External processors
Limited to hosting/runtime, mail, billing, alert processing, and customer-selected integrations where configured.
Customer control
Webhook, SIEM/SOAR, ticketing, and chat destinations are customer-selected.
Provider details
Named providers and regions are confirmed for each contracted deployment.
The product can run with a mostly self-hosted stack. Some customers may use invoice-only billing, customer-managed deployments, or their own downstream integrations. Because provider use can change by deployment, the signed packet should identify the exact providers and regions for that customer.
When a customer configures webhooks, email, SIEM, SOAR, ticketing, Slack/Teams-style destinations, or internal tools, those systems receive the alert payloads the customer chooses to route.
Review table
Next steps