Sub-processors
Last updated 2026-09-19
What is on this page
A sub-processor is a company we have appointed to help run Botseon, which handles your data on our instructions. This page lists all of them, what each one does, where it runs, which company we actually contract with, and what makes the arrangement lawful. The Data processing addendum is the contract this list belongs to.
At the bottom there is a second list, of places a member of your organisation may choose to connect a bot to. Those are not sub-processors: your member picked them, not us.
Where a cell below cites a provider's own published document, the URL and the date we read it are given in the cell. Where no citation appears, the statement is our own description of the arrangement and has not been re-read against that provider's published document for this version of the page. We say which is which rather than presenting both the same way.
Running the service
| Company we contract with | Where it runs | What it does | Legal instrument | Retention |
|---|---|---|---|---|
| Supabase Pte. Ltd. (Singapore) | AWS eu-central-1, Frankfurt | Database, authentication and file storage | Standard Contractual Clauses, Module Two and Module Three (https://supabase.com/legal/customer-resources/data-processing-addendum, as published on 2026-09-06) | Backups per plan; on project deletion Supabase removes all associated data including backups |
| Vercel Inc. (United States) | fra1, Frankfurt | Hosting for botseon.com and for the web app | Standard Contractual Clauses, Module Two and Module Three, plus an active EU–US Data Privacy Framework certification (https://vercel.com/legal/dpa, as published on 2026-09-06) | Request logs per Vercel's own schedule |
| Fly.io, Inc. (United States) | fra, Frankfurt | The computer each bot works on, and the screen gateway | EU–US Data Privacy Framework, active (https://fly.io/legal/data-privacy-framework/, as published on 2026-09-06). Whether Fly.io's data processing agreement also incorporates Standard Contractual Clauses is not yet confirmed | A volume and its snapshots are deleted when the volume is destroyed; we reclaim an idle bot computer on our own schedule |
| Resend, Inc. (United States) | eu-west-1, Ireland | Transactional e-mail (sign-in codes, receipts, account notices) and delivery and complaint events | Standard Contractual Clauses | The period Resend keeps message bodies and recipient addresses after delivery |
| Stripe Payments Europe, Ltd. (Ireland) | EU | Subscription billing, payment processing and invoicing | Established in the EEA, so no Chapter V transfer arises between us and Stripe; Stripe's own onward transfers run under its Standard Contractual Clauses | As Stripe's terms and financial-records law require |
Language and vision models
Your content is sent to a model provider to produce the answer, and for nothing else. It is not used to train their models. Two of the routes below run in the EU today. The Claude route does not yet, and we say so in its own row rather than at the bottom of the page.
Live routes
| Company we contract with | Where it runs | What it does | Legal instrument | Retention |
|---|---|---|---|---|
| Mistral AI (France) | EU | Mistral's own models, and embeddings | Established in the EU, so no Chapter V transfer arises | Mistral's published position on training and on request retention for its API |
| Microsoft Ireland Operations Limited (Ireland) | Azure AI Foundry, Sweden Central, EU data zone | Mistral Large 3 | Established in the EEA, so no Chapter V transfer arises between us and Microsoft Ireland. Microsoft's onward transfers run under the Microsoft Products and Services Data Protection Addendum and its Standard Contractual Clauses | Microsoft's published position for Azure AI Foundry is that customer inputs and outputs are not used to train foundation models, and that EU data zone processing stays in the EU data zone; abuse-monitoring storage is off where it has been disabled for the deployment |
| Anthropic PBC (United States) | United States | Anthropic's Claude models. This is the primary Claude route today, not a fallback. It is the one route on this page that processes your content outside the EU | Standard Contractual Clauses | Anthropic's published position on training and on request retention for its commercial API |
Being enabled, and not used for customer data until they are
| Company we contract with | Where it runs | What it does | Legal instrument | Retention |
|---|---|---|---|---|
| Google Cloud EMEA Limited (Ireland) | Vertex AI, EU multi-region | Anthropic's Claude models, and embeddings | Established in the EEA, so no Chapter V transfer arises between us and Google Cloud EMEA. Google's onward transfer to Google LLC in the United States, for maintenance and support, runs under Google LLC's EU–US Data Privacy Framework certification with Standard Contractual Clauses, Module Three, as the fallback (https://cloud.google.com/terms/data-processing-addendum, as published on 2026-09-06) | Google will not use customer data to train or fine-tune AI/ML models without the customer's prior permission or instruction (https://cloud.google.com/terms/service-terms, as published on 2026-09-06). Abuse-monitoring logging applies to some models and stays in-region |
| Amazon Web Services EMEA SARL (Luxembourg) | Amazon Bedrock, eu-central-1, Frankfurt | Anthropic's Claude models. Being enabled; not used for customer data until it is | Established in the EEA; onward transfers under AWS's Standard Contractual Clauses | AWS states that Bedrock does not use customer inputs or outputs to train models and does not share them with model providers |
When an EU-resident Claude route is switched on, the Anthropic PBC row comes off this page and we tell the administrators of every organisation before it happens. EU processing for every plan from a date to be announced: we would rather leave the date open than name one we cannot hold.
Each provider's commitment above should be read against its own published terms. The cells that carry a URL and a date were read from the provider's own document on that date; the rest are our description of the arrangement, and we re-read them against the provider's published terms at least once a quarter and whenever a provider announces a change.
Voice calls
Voice is the one part of the product where processing is not in the EU, and we say so rather than leaving it out. The recording, the audio and the turn-by-turn transcript are processed by the provider below while a call is running. Everything we store about the call, the call record, the transcript in our database, the ledger and the meter rows, stays in the same EU database as the rest of your data, under the same isolation, the same encryption and the same retention schedule.
An administrator has to acknowledge this before the first call on an organisation, and until they do, calls are refused. An organisation set to EU-only routing gets the EU provider or nothing.
| Company we contract with | Where it runs | What it does | Legal instrument | Retention |
|---|---|---|---|---|
| ElevenLabs (United States) | Global, or the provider's EU residency environment | Speech to text, speech synthesis and turn-taking | Standard Contractual Clauses. Even on the EU residency environment, support and content moderation are named exceptions to the location guarantee | Per the account's data-use setting; training opt-out to be set on the account |
| Deepgram (United States) | The provider's EU endpoint | Streaming speech to text | Not yet in place. No data processing agreement is published and none is incorporated in the terms; one must be requested and signed before any production call audio is sent | Deepgram's terms license call audio for model training unless each request opts out |
| Google Cloud EMEA Limited (Ireland) | eu-texttospeech.googleapis.com | Speech synthesis | Established in the EEA, so no Chapter V transfer arises | No logging; processing at rest and in use within Europe, contractually backed (https://cloud.google.com/terms/service-terms, as published on 2026-09-06). Whether "Europe" here includes the United Kingdom is open |
Voice is part of the product today, which is why this section is on the page. One thing in it is not settled: the Deepgram row above is the only entry anywhere on this page with no data processing agreement in place. It is listed because the route is configured and reachable, not because the arrangement is finished, and the agreement and the training opt-out are both owed before production call audio is sent to it.
Places you connect a bot to
Beyond the sub-processors above, a member of your organisation may connect a bot to a service of their own choosing. Today that is Gmail, and Slack as an inbound channel. That connection, and whatever it shares, is your member's decision and your organisation's responsibility. We have not appointed those companies and they are not our sub-processors. What a connector may reach is limited by the permissions your member grants it.
Changes to this list
When we add a sub-processor, we notify your organisation's administrators and give you 30 days to object before it goes live. The objection route is in the Data processing addendum.
Contact
Nordio ApS, CVR 46714040, Skansevej 88, 3400 Hillerød, Denmark. Questions about this page: privacy@botseon.com.