Subprocessor Register
Operational list of infrastructure, AI, telephony, payment, and hosting providers used to deliver the platform.
Provider name, purpose, and high-level data scope
Customer-facing change notice process before material provider changes
Production environment separation from development resources
Provider DPAs and security terms tracked before regulated rollout
Language, speech, analysis, and AI-assisted review capabilities.
Data scope: Workflow prompts, call/session content, analytics evidence, and generated outputs when enabled.
Status: Requires active customer processing terms
Voice call routing, phone number connectivity, and provider callbacks.
Data scope: Call metadata, caller/callee numbers, provider call IDs, recordings when consent and configuration permit.
Status: Provider-specific agreement required
Subscriptions, invoices, payment method handling, and billing portal access.
Data scope: Billing contact, customer identifiers, subscription state, invoice and payment metadata.
Status: Used when billing module is enabled
Secrets, email delivery, object storage, DNS, and related production infrastructure services.
Data scope: Secrets metadata, transactional email metadata, uploaded objects, recordings, and operational artifacts.
Status: Environment-specific configuration
Application containers, backend services, worker services, and runtime networking.
Data scope: Application traffic, logs, runtime metadata, and database/network connectivity.
Status: Confirm final production hosting posture during procurement