Data Processors

A data processor is a company that handles some of your data, or your callers’ data, on our instructions so the Service can run. The chart below lists the primary processors by category. It is deliberately not a directory of every vendor we hold an account with: operational categories name the category and the country rather than the company, because the vendor in one of those slots can change while the promise stays the same.

Our servers are in the United States: call recordings, transcripts, and account data sit in US regions. Three nuances. Files you or your callers upload sit in object storage we lock to North America, because that provider commits to the continent rather than to a single country, and we would rather say North America than promise narrower than we can prove. Cloudflare delivers and shields our websites, which we serve only to visitors in the United States and Canada. And for the language-model step we use US-headquartered providers whose terms forbid training on your data, but those providers run datacenters in more than one country and none of them publishes which one handled an individual request, so we do not claim a processing location for that step.

Primary data processors by category

Category	Provider	What they handle
Large language models	OpenRouter · routing Fireworks AI · inference CoreWeave · inference DIDeepInfra · inference PSParasail · inference	The text your assistant reads and writes. OpenRouter routes each request to one of these inference providers, and each of them commits in its own terms not to train on what we send or to keep it beyond serving the request.
Speech to text	American provider(s)	Caller audio during calls, turned into text.
Text to speech	American provider(s)	The receptionist’s voice: our text, spoken aloud.
Telephony	American provider(s)	Calls, text messages, your provisioned phone numbers, E911 registration, and the carrier (10DLC) registration of your business for texting.
Business verification	TINCheck by Sovos	Your legal name, address and EIN, once, during business verification for texting: IRS TIN matching, a federal watch-list (OFAC) screen, and a USPS address check. We never store or log the EIN, in whole or in part. Only the result is kept.
Servers and web services	Amazon Web Services Cloudflare	AWS runs our servers and database in US regions. Uploaded files sit in object storage we lock to North America, as the intro above explains. Cloudflare provides DNS, security, and delivery for our websites.
Payments	Stripe	Subscription payments. Your card number goes to Stripe directly and is never stored on our systems.
Email and sign-in	Google	The support@ and billing@ mailboxes you write to, and the Google sign-in option for your account.
Website analytics	Google Analytics	How the public site is used. Loads only if you accept analytics cookies, with ad personalization disabled.

What is not on this list

Integrations you connect are your accounts, not our processors: calendars, Slack, Microsoft Teams, Discord, Telegram, Signal, Google Chat, and the other destinations you choose for summaries and notifications. We send data there because you connected them, and you can disconnect them at any time. This page covers the systems that deliver the Service; it is not an inventory of every tool our company uses to run itself.

Changes

We update this page when the list changes, and the date above is the version marker. If a category label here ever stops being true, that is a bug in the page, not a footnote: tell us and we will correct it.

Contact

This page works together with our Privacy Policy, our Terms of Service, and the Security page.