Sub-processors
The outside companies listed below are the ones that touch your data on our behalf — where your data is processed, whether a written agreement covers it, and what each company's own terms say about training on it.
A connection to an outside tool refuses to start at all unless it has a row on this page. That is a property of how the software is built, not a promise about our intentions — a new outside company cannot be connected without appearing here first.
Three terms are used below. A data processing agreement is the written contract that limits what a company may do with your data; where it is “part of the company's own terms of service”, that contract already applies without a separate signature. Standard contractual clauses are standard promises, written by the European Commission, that a company outside the European Union signs so data can lawfully be sent to it. The EU–US Data Privacy Framework is a scheme under which a company in the United States certifies that it protects European data, and the European Commission accepts certified companies as a lawful destination.
Companies that process your data for us
| Company | What they do for us | Where data is processed | Agreement | Standard contractual clauses | How data leaves the EU | Training on data, and keeping it |
|---|---|---|---|---|---|---|
| Anthropic | Makes the models your agents run on. Today our requests reach its models through OpenRouter, not through an account of our own with Anthropic. | United States | In force. It is part of the company's own terms of service, so it applies automatically. | Signed | Standard Contractual Clauses (Modules 2 and 3), with Anthropic Ireland. Anthropic is not on the EU–US Data Privacy Framework list. | Under its own API terms it does not train on what is sent to it by default. Under its own API terms it deletes inputs and outputs within 30 days. |
| Composio | Holds the connections to some of the tools you link. | United States | Not in force yet. | Not in place | Standard Contractual Clauses, once the agreement is accepted. Composio is not on the EU–US Data Privacy Framework list. | Its data processing agreement has to be accepted in Composio's own dashboard, and we have not accepted it yet. Until we do, no agreement covers this company. |
| Fly.io | Runs the background workers that carry out agent runs. While a run is in progress they hold your workspace's data in memory and connect directly to the database. | Frankfurt, Germany (fra) | Not in force yet. Read the agreement | Not in place | EU–US Data Privacy Framework (certification active). No Standard Contractual Clauses are in place. | Its data processing agreement has to be accepted in Fly.io's own dashboard, and we have not accepted it yet. Until we do, no agreement covers this company. |
| OpenRouter, Inc. | Receives every model request from ZenOS and passes it on to the company that runs the model. | United States (Google Cloud US regions) | In force. It is part of the company's own terms of service, so it applies automatically. | Signed | Standard Contractual Clauses (Module 2). OpenRouter is not on the EU–US Data Privacy Framework list. | It receives the prompts and the responses of every model call routed through it. Each request asks it to use only model companies that do not collect or train on request data. Beyond that, what it keeps follows its own policy. Zero data retention is not switched on yet, and we have not confirmed that every model we use is served with it. Listed here since 26 September 2026. |
| Stripe | Takes payment. | Ireland (Stripe Payments Europe), with processing in the United States | In force. It is part of the company's own terms of service, so it applies automatically. | Signed | EU–US Data Privacy Framework first, then Standard Contractual Clauses. | Acts as our processor and also as a controller in its own right. |
| Supabase | Stores your workspace data. | Frankfurt, Germany (AWS eu-central-1) | In force. It is part of the company's own terms of service, so it applies automatically. Read the agreement | Signed | Standard Contractual Clauses, which are signed by accepting the data processing agreement (clause 12.2). Supabase is not on the EU–US Data Privacy Framework list. Its support staff may reach your data from the United States or Singapore under those clauses. | Your workspace data is deleted within 30 days of cancellation, on our schedule. |
| TypeSafe | Answers typed decision questions for the Decision agent and for decision steps. It runs the JEV model, which we reach through OpenRouter. | United States (TypeSafe's own privacy policy says its services are hosted there; we have not confirmed any processing in the EU) | Not in force yet. | Not in place | No transfer mechanism is in place with TypeSafe. We have no agreement of our own with it, and no Standard Contractual Clauses. Requests reach it through OpenRouter. | It receives the text a decision step sends it: content the run already has. Each request asks OpenRouter to use only companies that do not collect or train on request data. We have not confirmed what TypeSafe itself keeps, and we have no agreement with it. The feature that uses it is switched on, so it receives what is described above. |
| Vercel Inc. | Hosts the website, the dashboard and the console our own staff use; processes web requests and application logs. | Frankfurt, Germany (fra1) for application functions; static files from Vercel's global network; may also process in the United States | In force. It is part of the company's own terms of service, so it applies automatically. | Signed | EU–US Data Privacy Framework (certification active) and Standard Contractual Clauses. | Listed here since 26 September 2026. |
| Voyage AI | Turns your documents into a form we can search by meaning. Our requests reach Voyage AI's model through OpenRouter, not through an account of our own with Voyage AI; a workspace whose older documents have not yet moved to the newer search model may still be searched through Voyage AI directly until that move has finished. | United States (Voyage AI does not publish which region) | In force. It is part of the company's own terms of service, so it applies automatically. | Signed | Standard Contractual Clauses. Voyage AI is also covered by the EU–US Data Privacy Framework certification of MongoDB, Inc. | Its terms allow it to train on the content sent to it unless the account opts out. We have not yet confirmed that our account has opted out, so do not assume it has. |
AI model providers a workspace can choose
A workspace's owner chooses which of these providers its agents use, and can switch on “EU processing only” to allow just those that process inside the European Union. Every request passes through OpenRouter, a routing service in the United States, which sends it on to the provider chosen. EU routing is not switched on for our OpenRouter account, so a request to a provider inside the European Union still passes through the United States on its way.
This list is read from our reviewed model catalogue, so it names only the providers a workspace can choose today. Where a person at ZenOS has not yet checked where a provider processes requests and what it keeps, the list says “Not yet reviewed” instead of a guess, and “Being checked again” where what was recorded did not add up. Which of them is bound by the data processing agreement, and on what terms, follows that agreement; it is being reviewed by a lawyer and nothing in this list changes what the agreement says.
| Provider | Country | Where a request is processed | What it keeps | Models |
|---|---|---|---|---|
| Amazon Bedrock | Being checked again | Being checked again | Being checked again | Anthropic Claude Sonnet 5.5 |
| Anthropic | Not yet reviewed | Not yet reviewed | Not yet reviewed | Anthropic Claude Haiku 4.5, Anthropic Claude Opus 5, Anthropic Claude Sonnet 5 |
| Anthropic | United States | Outside the European Union | Keeps nothing, as the provider states | Anthropic Claude Haiku 5.5 |
Services you connect yourself — they act as independent controllers
When you connect your own account at one of these companies, it holds that account under its own terms with you and answers for its own use of what it holds. It is not working for us, so no data processing agreement applies between us and it.
| Company | The account you connect | Where data is processed | How data leaves the EU | Terms that apply |
|---|---|---|---|---|
| The Google Ads and Gmail accounts you connect yourself. | Global (set by Google, not by us) | EU–US Data Privacy Framework (certification active). | Google's own terms for the service apply between you and Google. They are terms between two controllers, not a data processing agreement. | |
| LinkedIn Corporation | The LinkedIn account you connect yourself. | Global (set by LinkedIn, not by us) | EU–US Data Privacy Framework (certification active). LinkedIn's own data processing terms also include Standard Contractual Clauses. | LinkedIn's own terms for the service apply between you and LinkedIn. They are terms between two controllers, not a data processing agreement. |
| Meta Platforms | The Facebook and Instagram accounts you connect yourself. | Global (set by Meta, not by us) | Meta's certification under the EU–US Data Privacy Framework is under re-certification review. | Meta's own terms for the service apply between you and Meta. They are terms between two controllers, not a data processing agreement. |
Listed but not in use
These companies are listed so the list is complete. Nothing is sent to them today.
| Company | What they would do for us | Where data would be processed | Agreement | How data would leave the EU | Notes |
|---|---|---|---|---|---|
| Better Stack | Receives operational logs from the workers and the web application. Logs never contain credentials or your own API keys. | Germany, only if its data region is set to Germany (not in use today) | In force. It is part of the company's own terms of service, so it applies automatically. | It says it is certified under the EU–US Data Privacy Framework, which we have not confirmed on the official list, with Standard Contractual Clauses as the fallback. | Not in use: no log drain is set up, so nothing is sent to it. |