Subprocessor register

Current service-provider and integration categories.

A public category-level inventory of systems that may support Hanasand delivery. It is not a complete named subprocessor register.

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 must be supplied and approved for each production deployment.

Why the register is scoped

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. This page does not substitute for a named provider, legal entity, processing location, and transfer-mechanism list for the production deployment.

Customer-selected destinations

When a customer configures a webhook or API consumer for SIEM, SOAR, ticketing, chat, or an internal tool, that customer-owned system receives the alert payloads the customer chooses to route.

Review table

What a reviewer can check.

CategoryPurposeCurrent disclosure

Hosting/runtimeApplication, API, worker, processing, Tor/onion session, and scheduled-job infrastructureHanasand-managed deployment; named infrastructure provider and region are not published here

Database/storageAccount, organization, watchlist, alert, audit, and operational statePostgreSQL-backed storage in the deployment environment

MailAccount recovery, commercial requests, support, and operational messagesHanasand mail stack or configured mail provider by deployment; monitoring alerts use webhook, case, and API paths

Alert processingStructure source records into safer alert fields when enabledHanasand-controlled model endpoint or explicitly approved provider

Billing/paymentSubscriptions, invoices, and plan administrationOnly used when the customer is not handled by invoice/order form

Customer integrationsWebhook/API delivery to customer toolsCustomer-selected destination receives customer-approved alert payloads

Next steps

Require the named provider, legal entity, hosting region, and transfer details for the target deployment.
List any prohibited subprocessors before procurement approval.
Confirm whether you need customer-managed deployment, invoice-only billing, or restricted integration routing.

Request review docs

Why the register is scoped