Back to the sub-processor register
Sub-processor records
The formal record for every sub-processor in the register: the purpose, data category and region that our Data Processing Agreement incorporates by reference, grouped by the job each company does for you.
Distronode Corporation • Last Updated: October 10, 2026
On this page
What this page is: A sub-processor is another company we bring in to do part of the work, one that handles some customer data while doing it. Every product like District AI relies on companies like these; we name every one of them.
How to read it: Each entry opens with a plain-language sentence, a chip for its region, chips for the data it can see, and a label where something is optional, off by default, admin-only or touches no customer data. The formal record, which our Data Processing Agreement incorporates by reference, sits below it.
What to take from it: To see who hears your calls, use the call-data path on the register; a typical call touches only a handful of these companies. For a formal vendor review, the purpose, data category and region fields are written for your checklist, and legal@distronode.com answers anything else.
Connects your calls & texts
Twilio
Carries your calls and texts. European calls connect through Twilio's Dublin edge in Ireland, and Asia-Pacific calls through its Singapore edge.
- Purpose
- Voice (SIP), SMS/MMS, caller-ID and carrier lookup, and number registration
- Data category
- Phone numbers, call audio, message content, caller metadata, and the registration documents you submit, including identity documents where a regulator requires them
- Region
United States for messaging, registration documents, and calls on a United States workspace's numbers or a customer's own Twilio account. A Canadian workspace's calls run on our Montreal equipment and meet Twilio in the United States, at Ashburn for numbers we issue it.
European numbers we issue, the United States numbers we issue a European workspace and European outbound calls pass through Twilio's Dublin edge in Ireland to our Frankfurt equipment. In Europe, a number in Estonia needs no paperwork from you; other countries open once your workspace's own local registration is approved. An Asia-Pacific workspace's calls pass through Twilio's Singapore edge to and from our Singapore equipment, both the calls it places and calls on the United States numbers we issue it. Twilio has not yet confirmed its processing location in writing, so we do not claim a region for what happens past that handoff
Sinch
Sends and receives SMS messages, and carries some calls.
- Purpose
- SMS messaging and voice
- Data category
- Phone numbers, message content, and call audio
- Region
- United States (parent company in Sweden). Sinch's messaging service keeps a copy of message content for 180 days after delivery, its default retention, then deletes it.
Telnyx
An additional carrier for calls and texts.
- Purpose
- SIP voice and SMS/MMS
- Data category
- Phone numbers, call audio, and message content
- Region
Telnyx's call, message and conference records are stored in Canada. The exception is European outbound calls: since October 2026, their records are stored in Germany.
Processing: United States for messaging, including texts on Canadian numbers. European outbound calls are handed to Telnyx in Frankfurt, and Canadian calls on Telnyx numbers we issue, both directions, in Montreal. Telnyx treats processing location as a preference, not a guarantee, so we claim no processing region beyond our handoff
Runs the platform
Google Cloud Platform (Google LLC)
Runs our United States hosting, most AI, and live call event buses.
- Purpose
- Databases, compute, call media, AI and embeddings (Vertex AI), live call event buses (Pub/Sub: one in the United States, one in Frankfurt and one in Montreal), document storage, encryption keys, secrets, Android push (Firebase Cloud Messaging) and logging
- Data category
- Contacts, transcripts, CRM records, account data, AI-processed content, and live call audio. Call events carry the caller's name and numbers, plus the transcript and summary for phone calls. Push notifications carry identifiers only
- Region
United States (us-east4): United States workspaces with AI, call media and sign-in, rollback copies of other regions' sign-in and routing, and calls on a customer's own carrier account. United States and Asia-Pacific events ride a message bus in the United States.
Canada: AI, credential key and Canadian message bus in Montreal (northamerica-northeast1). Asia-Pacific: AI and credential key in Singapore (asia-southeast1). In both, the realtime engine runs in us-east4. Europe: AI in the EU (europe-west4); credential key and European message bus in Frankfurt (europe-west3).
A call answered in the United States creates its event there first. Registration documents stay in-region and are deleted 30 days after release. No call is recorded. Global: secrets, push delivery and the United States credential key
Apple (Apple Inc.)
Delivers the notifications that ring the District AI iPhone app for a call and tell it a new message has arrived.
- Purpose
- Push notification delivery to the District AI app on iPhone through the Apple Push Notification service: the notification that rings the app for an incoming call, and the one that tells it a new message has arrived. Notifications to Android devices are delivered by Firebase Cloud Messaging, listed under Google Cloud
- Data category
- The device's push token, the workspace, call and message identifiers, and the kind of notification. Never the message text, a phone number or a caller's name: the words on the lock screen come from the app itself, and the app fetches the call or message afterwards under its own credential
- Region
- Apple does not publish where it processes a notification, and does not let a sender choose a region, so a notification to an iPhone leaves the workspace's region for every workspace, European and Canadian ones included. It carries identifiers only, as described above
Amazon Web Services (Amazon Web Services, Inc.)
Hosts the website, dashboard and database for Canada, Europe and Asia-Pacific, and those regions' call media.
- Purpose
- Website, dashboard and workspace database hosting; call media and telephone equipment for Canadian, European and Asia-Pacific workspaces; speech-to-text (Amazon Transcribe) and text-to-speech (Amazon Polly) on the voice engine new Canadian and Asia-Pacific workspaces start on
- Data category
- For those regions' workspaces: contacts, CRM records, transcripts, messages, account data and web requests. Live call audio for Canadian, European and Asia-Pacific calls, processed and not stored
- Region
- Canada (ca-central-1, Montreal), Germany (eu-central-1, Frankfurt) and Singapore (ap-southeast-1), each region on its own encrypted machine. Each region handles the calls its workspaces place and the calls on the numbers we issue them: Montreal for Canada, Frankfurt for Europe and Singapore for Asia-Pacific. Montreal also handles calls on any Canadian number we issue through Telnyx, and Frankfurt calls on any European number we issue. Twilio publishes no Canadian point of presence, so a Canadian workspace's Twilio calls reach Montreal through Twilio in the United States. Other calls, on numbers held by United States workspaces or on a customer's own carrier account, are handled in the United States
Cloudflare, Inc.
Protects and speeds up our websites, and holds our encrypted backups.
- Purpose
- CDN, DNS, edge routing, bot protection (Turnstile), encrypted backups (R2) and admin-only media generation (Workers AI)
- Data category
- Web traffic metadata and IP addresses; encrypted database backups
- Region
- Global: a visit is handled at the nearest Cloudflare location, which may be outside Canada, since we don't buy Cloudflare's country-restriction add-on. European backups sit in Cloudflare's EU jurisdiction; United States, Canadian and Asia-Pacific backups in its default jurisdiction. Each backup is encrypted in its own region, with the key held outside Cloudflare
Redis Ltd. (Redis Cloud)
Holds the short-lived operational state that keeps the service running.
- Purpose
- Seven managed databases: shared operational state for each region's website (rate limits, caches, webhook claims, job locks, short-lived sign-in codes), call-signaling buses for our Canadian and European media nodes, and a retired United States signaling bus kept for rollback
- Data category
- Counters, cached values, claims and locks keyed to account, workspace, call or IP identifiers, with emails, phone numbers and IP addresses hashed in key names. Live-call room state and trunk configuration. No call audio
- Region
- Shared state in each region, used only by that region: United States (us-east4), Montreal (ca-central-1), Frankfurt (eu-central-1) and Singapore (ap-southeast-1). Signaling buses in Montreal and Frankfurt, and the retired one in us-east4. Our United States and Asia-Pacific media buses run on our own hosts
Turns speech into text — and back
Deepgram
Turns caller speech into text, and our replies into a voice. It is the engine a new workspace starts on everywhere except Canada and Asia-Pacific. European workspaces use its European endpoint.
- Purpose
- Speech-to-text transcription and text-to-speech (the starting engine outside Canada and Asia-Pacific)
- Data category
- Call audio and transcripts
- Region
- United States by default (api.deepgram.com). For a European workspace, both speech-to-text and speech synthesis run on Deepgram's European endpoint (api.eu.deepgram.com), which Deepgram commits to keeping inside the EU without naming a country. A Canadian workspace reaches Deepgram only if it has chosen an engine that uses it, and is then processed in the United States, because Deepgram publishes no Canadian endpoint; since September 2026 a new Canadian workspace starts on Amazon Transcribe and Amazon Polly in Montreal instead. An Asia-Pacific workspace is treated the same way, because Deepgram publishes no endpoint in Singapore; since September 2026 a new one starts on Amazon Transcribe and Amazon Polly in Singapore instead
ElevenLabs
An optional voice for the assistant.
- Purpose
- Text-to-speech voice synthesis (optional voice engine)
- Data category
- Agent text and synthesized audio
- Region
- United States
Cartesia
An optional voice for the assistant, on Cartesia's Sonic model.
- Purpose
- Text-to-speech voice synthesis (optional voice engine)
- Data category
- Agent text and synthesized audio
- Region
United States (api.cartesia.ai), for every workspace that chooses this engine.
Cartesia offers European, British, Indian and Australian endpoints only on its Enterprise tier, which we do not hold, and publishes no Canadian one. So a European or Canadian workspace that selects this engine has its speech synthesis in the United States, and the engine picker says so before the choice is made.
AssemblyAI
An optional speech-to-text engine. European workspaces use its EU data zone.
- Purpose
- Speech-to-text transcription (optional voice engine)
- Data category
- Call audio and transcripts
- Region
- United States, on AssemblyAI's US data zone (streaming.us.assemblyai.com). For a European workspace, transcription runs on its EU data zone (streaming.eu.assemblyai.com), which AssemblyAI states keeps the data inside the EU. Canadian and Asia-Pacific workspaces are processed in the United States, because AssemblyAI offers no data zone in either region
Inworld
An experimental voice engine, not yet generally available.
- Purpose
- Speech-to-text and text-to-speech (optional voice engine; experimental)
- Data category
- Call audio, agent text, and synthesized audio
- Region
- United States
Tavus
Optional video avatar for face-to-face calls — off unless you turn it on.
- Purpose
- Real-time video avatar rendering (optional; off by default, enabled per workspace)
- Data category
- Video and audio streams for avatar sessions
- Region
- United States
Payments & email
Stripe
Processes your payments. Never sees call data.
- Purpose
- Payment processing, billing, tax calculation, and metered usage
- Data category
- Name, email, billing address, payment method, and tax identifiers
- Region
- United States
Postmark
Delivers our emails to you.
- Purpose
- Transactional email delivery
- Data category
- Email address, name, and message content
- Region
- United States
When you contact support
Atlassian (Atlassian Pty Ltd)
Runs our support desk: one site in Canada for all four regions.
- Purpose
- Support ticketing (Jira Service Management) and, only where a workspace chooses the linked knowledge base, answering questions asked of the assistant
- Data category
- Your name, email address, the text of your request and our replies; with the linked knowledge base, each question asked. Never your IP address, browser details or workspace identifier
- Region
- Canada, for every workspace. A European, United States or Asia-Pacific workspace's support requests are held in Canada, outside its own region
Website analytics
Stape
First-party gateway for our website analytics, hosted in Canada.
- Purpose
- First-party server-side Google Tag Manager container (sst.distronode.com) that forwards consented analytics events to Google Analytics and, where your advertising choice allows it, checkout starts to Google Ads
- Data category
- Web analytics events and IP addresses
- Region
- Canada (Toronto)
Google Analytics & Google Ads (Google LLC)
Measures sign-ups, demos and purchases, only with your consent.
- Purpose
- Server-side conversion and analytics measurement (GA4 Measurement Protocol and Google Ads Data Manager) for consented sign-ups and purchases, and for live demos started after a visit from one of our ads
- Data category
- Consented web and conversion events, including hashed billing email addresses, purchase amounts and Google Ads click identifiers
- Region
- United States
LinkedIn (LinkedIn Corporation)
Measures which of our LinkedIn ads led to a sign-up — only with your consent.
- Purpose
- Advertising measurement for our own LinkedIn campaigns: the LinkedIn Insight Tag records consented website events, and the LinkedIn Conversions API receives consented conversion events sent from our servers
- Data category
- Consented web and conversion events, including SHA-256 hashed email addresses and LinkedIn's first-party advertising cookie identifier. We do not send plaintext email addresses, IP addresses or mobile advertising identifiers
- Region
- United States
Mixpanel (Mixpanel, Inc.)
Shows us how the signed-in dashboard and our public website are actually used, held in the EU. Never your calls, messages or contacts.
- Purpose
- Product analytics for the signed-in District dashboard and our public website, by two paths. First, a consent-gated analytics SDK in your browser, in the dashboard and on our public pages, which stores its identifiers in browser storage (localStorage) rather than in cookies. Public-page visits are anonymous, linked to your account only if you later sign in on the same browser. Second, cookieless lifecycle events sent from our own servers when an account or workspace is created, a subscription is purchased, a workflow run completes, or a call is handled. Not used for advertising
- Data category
- Product usage events keyed to a one-way SHA-256 hashed account identifier, the account email address on the user profile, and the workspace identifier, region, and plan tier. On public pages, anonymously: pages viewed, sign-up, checkout and demo link clicks, demos started, forms sent (form name and inquiry type only), campaign parameters, referring site. We do not send call audio, transcripts, message content, contact records, phone numbers, or IP addresses, and IP geolocation is switched off, so no location is derived from your connection
- Region
- European Union (Mixpanel EU data residency, api-eu.mixpanel.com)
Keeps the service reliable
Sentry
Tells us when something breaks, held in the EU.
- Purpose
- Error tracking and application monitoring
- Data category
- Diagnostic data, which may include IP addresses and user identifiers
- Region
- Germany, for all four of our regions rather than one provider region for each of ours. A Canadian workspace's error diagnostics are therefore held in Germany rather than in Canada, because Sentry operates no Canadian region
New Relic
Watches uptime and performance, held in the EU.
- Purpose
- Infrastructure metrics, logs, and alerting
- Data category
- Operational telemetry and scoped application logs
- Region
- European Union (New Relic EU region), for all four of our regions rather than one provider region for each of ours. A Canadian workspace's infrastructure telemetry and logs are therefore held in the European Union rather than in Canada, because New Relic operates no Canadian region
Optional: business-contact enrichment
People Data Labs
Looks up business details for your contacts — only if you turn enrichment on.
- Purpose
- B2B company and person enrichment (primary source)
- Data category
- Business domains and firmographic data, and professional contact details (name, role, business email); phone numbers are used as lookup keys
- Region
- United States
Apollo.io
Backup source for business-contact lookups — only if enrichment is on.
- Purpose
- B2B company and person enrichment (fallback source)
- Data category
- Business domains and firmographic data, and professional contact details (name, role, business email)
- Region
- United States
SerpAPI
Web search used during enrichment — only if it's on.
- Purpose
- Web search used to locate public business information during enrichment
- Data category
- Business names, contact names, and in some cases phone numbers submitted as web-search queries
- Region
- United States
Our own marketing
Bluesky (Bluesky Social, PBC)
Receives our own Bluesky posts directly. No customer data.
- Purpose
- Publishing to Distronode's own Bluesky account directly, rather than through a publishing tool
- Data category
- Distronode's own marketing content only; no customer personal data
- Region
- Not applicable (Distronode content only)
Zernio
The publishing tool that posts our own X and Reddit updates for us. No customer data.
- Purpose
- Relaying Distronode's own marketing posts to Distronode's own X and Reddit accounts, where we publish through a tool rather than through the platform's own interface
- Data category
- Distronode's own marketing content only, together with the credentials for Distronode's own social accounts; no customer personal data
- Region
- Not applicable (Distronode content only)
Clarifications
LiveKit is self-hosted, not a sub-processor. Our real-time voice platform runs LiveKit's open-source software on our own media nodes: Google Cloud in the United States (us-east4) and Amazon Web Services in Frankfurt (eu-central-1), Montreal (ca-central-1) and Singapore (ap-southeast-1). LiveKit, Inc. does not receive or process your data as a third party.
Email runs entirely through Postmark. An earlier email provider (Resend) has been retired and no longer processes customer data.
Retired providers. The legacy enrichment provider Clearbit has been removed and no longer processes any data; People Data Labs and Apollo are the active sources. Two hosting providers have also come off this register: Akamai / Linode, which hosted the Asia-Pacific region until August 13 2026, and Civo, which hosted the European region until August 14 2026. The machines they ran for us were destroyed on those dates and neither company holds anything of ours. Amazon Web Services runs those regions now, in the same cities.
Services you connect are not sub-processors. When you link Google or Microsoft sign-in, calendars, or contact imports, or configure a custom API connector, those providers process data at your direction under your agreements with them, not as our sub-processors.
Questions about a specific sub-processor, or how one fits your own vendor review? Contact us at legal@distronode.com. See also the data residency map and our Data Processing Agreement.