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
Delivery of WhatsApp, Instagram and Messenger messages for a business's own connected account.
Data scope: Message content and media, sender channel identifiers, delivery and read status, and conversation metadata for the connected business account only.
Status: Used when a Meta channel is connected
Language, speech, analysis, image understanding, 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
Region-scoped hosting of the language and vision models that generate agent replies.
Data scope: Conversation content and media submitted for a reply, and the generated output.
Status: Used where a deployment is configured for Azure
Converting speech in calls and voice notes into text so an agent can respond.
Data scope: Call audio and voice-note audio, and the transcripts produced from them.
Status: Used for live call and voice-note transcription
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
Calendar access and meeting attendance for the meeting agent.
Data scope: Meeting title, agenda, invitee names and email addresses, and the meeting transcript.
Status: Used only when a business connects Google Calendar or Meet
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