Subprocessors
Who else
hears it.
An AI receptionist is a chain of companies, not one of them. This page names every link in that chain, what it does, and what your callers' words look like by the time they reach it.
Last updated 19 September 2026
The short version
- Five companies are in the path of every single call — the carrier, the speech recogniser, the router, the language model and the voice — and your callers' own mobile network carries the last leg. There is no version of the service without them.
- We have no negotiated agreement with any of them. Each is used on its own published terms. They may use what passes through, and they may sell it — §2 is the honest version.
- Two more are standby only and receive nothing unless the one above them fails mid-call.
- One of them may train on what it is sent: Google, on the dashboard assistant. It runs on a free tier where that is a condition rather than a setting. It never touches a phone call, and nothing else in the product needs it — §4.
- Stripe takes the payments and holds the card. It is typed into Stripe's own frame, so it reaches them rather than us.
- No analytics, advertising or tracking, on this site or in your portal. There are no tags to list because there are none.
- We update this page before a new one starts, and if you object to it you can leave with the rest of your month refunded.
This summary is for orientation only. It is not part of the agreement, and where it differs from the numbered sections below, the numbered sections are what applies.
The register
Everyone who touches it.
On every call
These are the call itself. A telephone call cannot be answered, understood, thought about or spoken back without each of them, so there is no version of the service where your callers' words do not pass through all of them.
Telnyx
United States
Carries the calls and the text messages, and issues the telephone numbers.
Sees The caller's number, your number, the live audio of the call, and the content of every text.
AssemblyAI
United States
Turns what the caller said into text, while they are still saying it.
Sees The live audio of the call.
OpenRouter
United States
Routes each turn of the conversation to the language model that composes the reply.
Sees The conversation so far, as text, and the business profile the receptionist is working from.
OpenAI
United States
The language model itself, reached through OpenRouter above.
Sees The same conversation text OpenRouter passes on.
Fish Audio
United States
Speaks the reply in your receptionist's voice.
Sees The words the receptionist is about to say. Never the caller's audio.
Your callers' mobile networks
United States
Carry the call and deliver the texts on the last leg to the handset.
Sees The content of every text, both numbers, and the routing and delivery record.
They do not contract with us and never will. Delivery is what a phone network is; there is no version of sending a text that does not hand it to one.
Standby, and only on a failure
Nothing reaches these unless the provider above has stopped answering mid-call. They are listed because a register that only describes the good day is not a register — but on an ordinary day they receive nothing at all.
Deepgram
United States
Speech recognition, if AssemblyAI is unavailable.
Sees The live audio of the call, for as long as the failover lasts.
DeepSeek
China
The last language model in the chain, if OpenRouter and OpenAI have both failed.
Sees The conversation text, for as long as the failover lasts.
The portal assistant, and only it
Aven — the helper inside your own dashboard that answers questions about your account. It is a separate chain from the phone, deliberately, and this is the one row on the page where the answer to “might this be used to train an AI?” is yes.
Google, for the Gemini model
United States
Answers what you type into the assistant in your dashboard. It is never used for phone calls, and it is deliberately left out of the call path's failover chain so a call transcript cannot fall through to it.
Sees The questions you type, and the account data the assistant looks up to answer them — which can include your own customers' names, phone numbers and booking details.
We run this on Google's free tier, and on that tier what is sent may be used to improve Google's products. That is not a switch we have left off — it is a condition of the tier, and it is not ours to disable while we are on it. Nothing else in the product depends on the assistant: if you would rather send Google nothing, do not use it.
Running the platform
Where the service, and everything it has stored, actually live.
Railway
United States
Hosts the platform and the database behind your portal.
Sees Everything the service holds, at rest — bookings, customers, transcripts, recordings, settings.
Vercel
United States
Hosts this website.
Sees Requests to those sites. No portal data and no call data passes through it.
Google, for email delivery
United States
Sends the confirmations, alerts and receipts the service emails on your behalf.
Sees The recipient's address and the content of the message — which for a booking confirmation means your customer's name and their appointment.
Stripe
United States
Takes the subscription payments and holds the card.
Sees Your billing contact details, and the card or bank details themselves — typed into Stripe's own frame on the checkout page, so they reach Stripe rather than us.
Amazon Web Services
United States
Stores video-meeting recordings and the encrypted backups (S3), transcribes meeting audio (Transcribe), and summarises meeting transcripts (Bedrock).
Sees Meeting video and audio, meeting transcripts, and encrypted backup snapshots of everything else.
Video meetings only. A business that never opens one sends AWS nothing but its share of the encrypted backup.
Resend
United States
Delivers customer-facing email for businesses on Business Max+ — confirmations, reminders, follow-ups, review requests.
Sees Recipient address, subject, message content, and your business name.
Business Max+ only. On every other plan this provider is not engaged at all, and platform email never goes through it on any plan.
Sentry
United States
Records a crash so we can find out what broke, where error monitoring is switched on.
Sees The technical detail of a failure and the request that caused it, which can incidentally include personal data that was in that request.
Around the edges
These touch your business's own information rather than your callers'. They are here because the line between the two is exactly the thing a register is for.
The Campaign Registry, through Telnyx
United States
Registers your business to send text messages under 10DLC, as US carriers require.
Sees Your business registration details — the legal name, address, tax number and contact you gave us. No message content, no caller data.
Outscraper, SerpAPI and Google Maps
United States
Read public review and listing data about your business and the competitors near you.
Sees Public search and listing data. Nothing of yours goes out beyond the business name and location being looked up.
Only if you connect them
These are reached on your behalf when you switch a feature on, and not before. Connect nothing and none of them receives anything. Revoke the access and the feature stops the same day.
Google Workspace APIs
United States
Calendar for booking into a connected calendar, Gmail for sending from a mailbox you connect, Sheets for logging bookings to a spreadsheet, Business Profile for pulling reviews and posting replies, Places and Maps for addresses and service areas.
Sees Whichever of those the feature needs — appointment details, message content, booking records, review text, addresses.
Microsoft Graph
United States
Booking and email from a connected Outlook or Microsoft 365 account.
Sees Appointment details, recipient addresses, message content.
Calendly
United States
Booking against a connected Calendly account.
Sees Invitee name, email, phone and the appointment itself.
Sendblue
United States
iMessage delivery, where you turn it on.
Sees Message content, both numbers, delivery metadata.
Relay servers for video meetings
United States
Establish the connection, and carry the picture and sound where a direct one cannot be made.
Sees Meeting audio and video in transit, and the network addresses at each end.
What this page is
A subprocessor is a company we use to deliver the Services that ends up handling personal information you or your callers gave us. The register above names every one of them, what it does, and what it can see.
It exists because the alternative is asking you to take our word for it. An AI receptionist is not one company answering your phone — it is a carrier, a speech recogniser, a language model and a voice, in a chain. A business deciding whether to put its customers through that chain is entitled to know who is in it before it signs, not after.
This page is the list our Data Processing Addendum means when it says "our subprocessors", and §5 is the notice promise that Addendum relies on.
The part most lists leave out
We have no negotiated data-processing agreement with any company in that register. We use each of them on their own published terms, as an ordinary paying customer — the same relationship you have with us.
A subprocessor list is normally read as proof that such agreements exist: that each provider has been bound to process data only on instruction, not to train on it, and not to sell it. In our case it does not prove that. It proves who is in the chain. What each of them may then do with what passes through is governed by their terms, not by ours.
They may use it, and they may sell it. We do not know that they do not, and we will not tell you otherwise. This is the single most important limitation on everything else we publish. It is stated the same way in our Privacy Policy and in the Addendum, and it is stated here rather than left for you to infer from a document that reads as though it were covered.
If your compliance file needs a signed agreement standing behind every provider, this service cannot give you one today — and that is worth knowing before you sign up rather than at your first audit.
Who is deliberately not on it
No analytics, advertising or tracking company, on this website or in your portal. There are no tags to list because there are none, and on this site your browser is now instructed to refuse them.
Wherever you told us to send things. Your own CRM, your webhook endpoint, a spreadsheet you pointed us at — those are destinations you chose, not companies we appointed. Once a booking lands there it is in your system under your agreement with whoever runs it, and we have no control over that copy and no way to delete it for you. Your connected Google and Microsoft accounts are a different case and they are on the list, under Only if you connect them in the register above: you own the account, but we are the ones calling the API.
An earlier version of this page also said "no payment processor". That was true when it was written and is not true now — Stripe takes the payments and holds the card, and it is named in the register above. The claim is recorded here rather than quietly deleted, because anyone who read this page before 19 September 2026 read something that had stopped being correct.
The one that may train on what it sees
Ask of any AI company "might what I send be used to make your model better?" and the answer decides whether a business can use it at all. For every provider above we take the setting or the term that excludes our data where one is offered. For one of them there is no such setting, and we are not going to bury that.
The dashboard assistant runs on Google's free Gemini tier, and on that tier what is sent may be used to improve Google's products. That is not a switch we have left on by accident — it is a condition of the tier, and it is not ours to turn off while we are on it. What reaches it is what you type into the assistant, plus the account data it looks up to answer you, which can include your own customers' names, numbers and bookings.
It does not reach your phone calls. The call path's failover chain deliberately excludes this provider, so a call transcript cannot fall through to it because something else was down. The assistant is a separate chain, on purpose.
Nothing else in the product depends on it. Every other feature works with the assistant untouched, so a business that would rather send Google nothing can simply not use it. We chose the free tier because it costs nothing and needs no card, with this trade-off understood — and moving it to a paid tier removes this, which is a change of one setting on our side.
When this list changes
We will update this page before a new subprocessor starts handling customer data, and the date at the top is when it last changed. Email Flowonnco@gmail.com with "Subprocessors" in the subject and we will tell you in advance, each time.
If you object to a new one, tell us and you may close your account without penalty, with the unused part of your month refunded. We are not going to pretend that one small business can veto our speech provider. What we can honestly offer is notice, and the ability to leave before it takes effect rather than after.
Ask
Anything here unclear?
If you need to know exactly what one of these receives, or you want telling in advance when the list changes, email us and say so. If a provider on it is one your own rules will not allow, tell us before you sign up rather than after.
Flowonnco@gmail.comAt a glance
- In every call
- 5 providers, plus the carrier
- Standby only
- 2 providers
- Only if you connect
- 5 more
- Processing region
- United States, except DeepSeek
- Negotiated DPAs
- None with any of them
- May train on it
- Google, dashboard assistant only
- Payment processor
- Stripe
- Notice of a change
- Before it takes effect
- Last updated
- 19 September 2026
Read alongside our Data Processing Addendum and Privacy Policy.