Sub-processors

Purpose: translation of message text into English, classification against your taxonomy, urgency and sentiment scoring, personal-data flagging, and embedding generation.

Data: message body text only. Account data, fingerprints and console activity all stay inside the platform. Contracted to exclude your data from model training.

Region: United States by default, fully relocatable on Dedicated, or replaced entirely with your own contracted keys and region.

Purpose: primary data storage, authentication, scheduled jobs and the deployed intelligence layer.

Data: everything in your tenant.

Region: EU on the shared backend; your choice on isolated and Dedicated deployments.

Purpose: serving the portal and the console.

Data: request routing only, with message content held entirely at the database layer.

Region: global edge, with the origin in the region of the deployment.

Purpose: capturing application exceptions so failures are found before a user reports them.

Data: stack traces and request metadata, with message bodies scrubbed before transmission.

Region: EU.

Purpose: console invitations, password resets, alert emails and daily digests.

Data: console user email addresses and alert content. Alert emails link to messages and carry no message bodies.

Region: EU.

Purpose: serving images and video used on this marketing website only.

Data: visitor address, as a technical necessity of delivering a file. This applies to the marketing site alone. The portal and the console load every asset from your own domain, fonts included.

Region: global edge.

We notify subscribed institutions in writing thirty days before adding a sub-processor. Where an objection stands unresolved, you may terminate the affected service with no penalty.