Which AI providers keep your data in the EU

13 providers, read line by line against their own documentation. Where inference runs, where data rests, what is retained, and the exceptions each vendor writes down and almost nobody reads.

Sources checked weekly, last on  ·  content last changed  ·  13 providers  ·  6 EU owned, 6 US owned

The short answer

Sources checked 12 October 2026

Three answers exist, and vendors rarely separate them for you.

  1. 1 EU inference with no geography caveat. Scaleway, OVHcloud, IONOS, STACKIT and Aleph Alpha, all EU owned. The OpenAI API with a project set to Europe, Vertex AI on a regional endpoint, and Bedrock in an EU region also qualify, under US ownership.
  2. 2 Conditional. Microsoft Copilot and Azure sit inside the EU Data Boundary, and Microsoft documents the circumstances in which data still leaves it.
  3. 3 No EU option. The first-party Claude API offers "us" and "global" for inference and US only for storage. Claude with EU residency exists, through Bedrock or Vertex, not through Anthropic.

Hosting location is one input among several. A processing agreement, a sub-processor list, a retention setting and a training exclusion decide as much as the map does.

The comparison

Every cell comes from the vendor's own documentation, linked in the last column with the date it was read. Where a vendor does not publish an answer, the row says so.

Provider Owner HQ EU inference EU storage Training on your content Retention default Source
Microsoft Copilot (Microsoft 365) Microsoft United States US owned Conditional Conditional No. Prompts, responses and data accessed through Microsoft Graph are not used to train the foundation models. Prompts and responses are stored as Copilot activity history and governed by your Microsoft 365 retention policies. Microsoft Learn, Data, Privacy and Security for Microsoft Copilot Checked 2026-09-06
Azure (EU Data Boundary services) Microsoft United States US owned Conditional Conditional Microsoft states customer data is not used to train its foundation models. Set by the service you deploy and your own configuration. Microsoft Learn, What is the EU Data Boundary? Checked 2026-09-06
OpenAI API (Platform) OpenAI United States US owned Yes Yes API inputs and outputs are not used to train models by default. Abuse monitoring logs retained up to 30 days unless you are approved for ZDR. OpenAI API docs, Your data Checked 2026-10-12
Claude API (first party) Anthropic United States US owned No No Commercial API inputs and outputs are not used to train models by default. Governed by the workspace and by Zero Data Retention where it applies. Claude Platform docs, Data residency Checked 2026-10-12
Gemini Enterprise Agent Platform (formerly Vertex AI) Google United States US owned Yes Yes Google states customer data is not used to train its models without permission. Set by the service configuration and your project settings. Google Cloud docs, Data residency (Gemini Enterprise Agent Platform, formerly Vertex AI) Checked 2026-09-21
Amazon Bedrock AWS United States US owned Yes Yes Model providers have no access to customer prompts and completions. Governed by your account configuration and the abuse detection documentation. AWS docs, Data protection in Amazon Bedrock Checked 2026-10-12
La Plateforme Mistral AI France EU owned Conditional Conditional Opt out available. Check the terms for the tier you are on. 30 rolling days by default, zero with ZDR on supported endpoints. Mistral Help Center and Privacy Policy Checked 2026-10-12
Generative APIs Scaleway (Iliad) France EU owned Yes Yes Not used for training, retraining or improving the base models, and not accessible to the model creators. Prompt content is not stored unless the service requires it, as with batch processing. Scaleway docs, Generative APIs privacy policy Checked 2026-10-12
AI Endpoints OVHcloud France EU owned Yes Yes Your data is never used to train our models. Zero data retention. Only data required for billing is kept. OVHcloud, AI Endpoints Checked 2026-10-12
AI Model Hub IONOS Germany EU owned Yes Yes Data is not used for training, fine-tuning, or otherwise improving any AI models. Data sent via the API is processed only to provide the service. IONOS docs, AI Model Hub governance and compliance Checked 2026-10-05
AI Model Serving STACKIT (Schwarz Digits) Germany EU owned Yes Yes Vendor states customer data stays under customer control. Set by the service configuration. STACKIT, AI Model Serving Checked 2026-09-06
PhariaAI Aleph Alpha Germany EU owned Yes Yes Runs on infrastructure you select, so the answer is yours to set. Yours to configure. Aleph Alpha docs, PhariaAI deployment options Checked 2026-10-12
Open weight models on your own server No vendor Wherever you put it You decide You decide Nobody trains on your data, because nobody else sees it. Whatever you configure. No vendor documentation applies Checked 2026-09-06

Conditional means the vendor offers EU processing and also documents circumstances in which data moves outside it. Read the exceptions below before treating conditional as a yes.

What each vendor writes down and buyers miss

The residency claim on a pricing page is usually true. The detail that decides whether it holds for your firm sits three clicks deeper.

Microsoft · Microsoft Copilot (Microsoft 365) Conditional

An EU Data Boundary service for tenants with an EU or EFTA sign-up location. Microsoft states that EU traffic stays inside the boundary.

The catch Anthropic models offered inside Copilot sit outside the EU Data Boundary. Tenants that bought Multi-Geo are out of scope even with an EU address. LLM calls route to the nearest data centre and can go to other regions when capacity is tight.

Microsoft · Azure (EU Data Boundary services) Conditional

Regional Azure services you deploy into an EU Data Boundary region are in scope for the boundary. Non-regional services have to be configured separately.

The catch The commitment covers customer data and pseudonymised personal data, and Microsoft documents limited circumstances in which data still moves outside the boundary. Read that transfer list before you rely on it.

OpenAI · OpenAI API (Platform) Yes

Data residency is configured per project. Europe (EEA and Switzerland) supports regional storage and regional processing.

The catch Abuse monitoring logs are generated for all API usage and kept up to 30 days by default. You need approval for Zero Data Retention or Modified Abuse Monitoring to change that.

Anthropic · Claude API (first party) No

Two settings govern geography. Inference geo controls where the model runs, workspace geo controls where data sits at rest.

The catch Neither setting offers Europe. EU residency for Claude models exists only through AWS Bedrock or Google Gemini Enterprise Agent Platform (formerly Vertex) EU endpoints, so the answer depends on which door you come through.

Google · Gemini Enterprise Agent Platform (formerly Vertex AI) Yes

Regional endpoints such as europe-west4 keep processing in that region. The EU multi-region endpoint keeps processing inside EU locations.

The catch The global endpoint does not support data residency. If the region is left out of the call, the guarantee goes with it. ML processing commitments now reach well beyond the US and EU, into Brazil, Canada, the UK, Australia, India, Japan, Singapore and South Korea, so check the model's own location table rather than assuming it stops at Europe.

AWS · Amazon Bedrock Yes

Bedrock runs in EU regions, and each region holds its own model deployment accounts operated by the Bedrock service team.

The catch Cross-region inference profiles move traffic between regions inside a geography. Check the profile you are actually calling is an EU one, because the model choice does not decide this for you.

Mistral AI · La Plateforme Conditional

Mistral states data is hosted in the European Union by default. Depending on the feature, it can be temporarily transferred to sub-processors outside the EU, under Article 46 GDPR safeguards.

The catch Inputs and outputs are kept for 30 rolling days for abuse monitoring unless Zero Data Retention is switched on, and ZDR is not available for the stateful products such as chat, agents, libraries and batch files.

Scaleway (Iliad) · Generative APIs Yes

Serverless models are hosted in a data centre in Paris operated by OPCORE. Personal data may be stored in the Paris region.

The catch Aggregated and anonymised usage data is kept up to 6 months, and request content can be stored temporarily when traffic causes errors or security issues.

OVHcloud · AI Endpoints Yes

OVHcloud states the service is hosted and run in the European Union.

The catch The model catalogue is open weight models. If you need a frontier proprietary model, this route does not carry one.

IONOS · AI Model Hub Yes

Inference endpoints and managed vector databases run in ISO 27001 certified IONOS data centres in Germany.

The catch Open weight models only, and IONOS positions itself as the AI system provider while model documentation obligations stay with the model developer.

STACKIT (Schwarz Digits) · AI Model Serving Yes

Data is stored and processed exclusively in Europe. STACKIT belongs to the Schwarz Group and states it is independent of external investors.

The catch A smaller model catalogue than the hyperscalers, so check the specific models you need are on it before you plan around this.

Aleph Alpha · PhariaAI Yes

Installs into an environment you choose using Helm and Kubernetes: on premises, or on a cloud provider you pick, including StackIT, AWS, Google Cloud, or Azure.

The catch Aleph Alpha does not offer PhariaAI as a SaaS product themselves. This is a stack to deploy rather than an endpoint to call, so the real cost is the operations around it.

No vendor · Open weight models on your own server You decide

Llama, Mistral, Qwen and the other open weight families run on a European VPS or on hardware in your office. Nothing leaves the machine you rent or own.

The catch There is no vendor to hold to a commitment and no support line. You own the updates, the evaluation and the uptime, and quality sits below the frontier models.

In the vendors' own words

Quoted verbatim, with the source and the date it was read. These are the sentences worth putting in front of whoever signs the contract.

Models provided by Anthropic as a subprocessor are currently excluded from the EU Data Boundary.
Microsoft Learn, Data, Privacy and Security for Microsoft Copilot Read 2026-09-06
These commitments are subject to limited circumstances where Customer Data, personal data, and Professional Services Data will continue to be transferred outside the EU Data Boundary.
Microsoft Learn, What is the EU Data Boundary? Read 2026-09-06
your customer content (as defined in your services agreement) for that project will be stored at rest in the selected region to the extent the endpoint requires data persistence
OpenAI API docs, Your data Read 2026-10-12
Workspace geo: Only "us" is currently available.
Claude Platform docs, Data residency Read 2026-10-12
Because the model providers don't have access to those accounts, they don't have access to Amazon Bedrock logs or to customer prompts and completions.
AWS docs, Data protection in Amazon Bedrock Read 2026-10-12
Zero data retention: We keep only the data required for billing purposes.
OVHcloud, AI Endpoints Read 2026-10-12
data is not used for training, fine-tuning, or otherwise improving any AI models
IONOS docs, AI Model Hub governance and compliance Read 2026-10-05

Six questions to put to any AI vendor

Ask for the answers in writing and note the date you got them. Every one of these terms has moved at least once in the past year.

  1. Where does inference physically run? Ask for the region, not the continent.
  2. Where does data sit at rest? This is a separate setting from inference at three of the providers above.
  3. What happens when your capacity is tight? Capacity routing is where documented residency quietly becomes conditional.
  4. Which sub-processors touch our content? Ask for the current list and how you are told when it changes.
  5. How long are prompts and outputs retained, and can that be set to zero? Abuse-monitoring retention is the default almost everywhere.
  6. Is our content excluded from training by contract? A policy statement and a contractual commitment are different instruments.

This page is documentation research, not legal advice. Terms change, and the answer that matters is the one in your own contract on the day you sign it.

Who maintains this

EVY is a free AI workspace for small teams, built in Tallinn by Helix Studio OÜ. Teams ask where their AI processes data before they move company knowledge anywhere, and the honest answer needed a table nobody had built. What EVY itself does with your data is on the trust page.

So we built it, and we keep it current whether or not it leads anywhere near us. Where a provider's own documentation contradicts our positioning, the documentation wins and the row says so.

Frequently asked

Which AI providers keep your data in the EU?

As of 12 October 2026, EU inference is available without a geography caveat from Scaleway Generative APIs (Paris), OVHcloud AI Endpoints, IONOS AI Model Hub (Germany), STACKIT AI Model Serving (Germany), Aleph Alpha PhariaAI, the OpenAI API with a project set to the Europe region, Google's Gemini Enterprise Agent Platform (the renamed Vertex AI) on a regional or EU multi-region endpoint, and Amazon Bedrock in an EU region. Microsoft Copilot and Azure are conditional, because the EU Data Boundary carries documented exceptions. The first-party Claude API has no EU option at all.

Does Microsoft 365 Copilot keep data in the EU?

For tenants with an EU or EFTA sign-up location, Copilot is an EU Data Boundary service and Microsoft states that EU traffic stays within the boundary. Three documented exceptions matter. Anthropic models offered inside Copilot are currently excluded from the EU Data Boundary. Tenants that purchased Multi-Geo Capabilities are out of scope even with an EU address. Microsoft also documents that Copilot calls to the model route to the closest data centres and can call into other regions where capacity is available during high utilisation periods.

Does Claude have EU data residency?

Not through Anthropic directly. Anthropic's data residency documentation states that the inference_geo parameter accepts only "us" and "global", and that workspace geo, which governs where data sits at rest, is currently US only. EU residency for Claude models is available by running them through AWS Bedrock or Google's Gemini Enterprise Agent Platform (formerly Vertex AI) on EU endpoints, where the region is set by the platform rather than by Anthropic.

Is an AI tool GDPR compliant just because it is hosted in the EU?

No. Hosting location is one input. A data processing agreement, a current list of sub-processors, a retention policy you can point at, a statement that your content is not used for training, and a record of processing activities all sit alongside it. EU hosting with no processing agreement leaves you in the same place you started, and a US provider with a signed agreement and documented safeguards may be the more defensible choice depending on what you process.

What is the CLOUD Act concern with US AI providers?

The US CLOUD Act allows US authorities to compel US-headquartered providers to produce data they control, including data stored outside the United States. This is why the ownership column on this page is separate from the hosting column. It is a factor to weigh and document rather than an automatic disqualification, and how much weight it carries depends on what your firm processes and what your professional body expects of you.

What should a firm ask an AI vendor before signing?

Six questions cover most of it. Where does inference physically run, and can you name the region? Where does data sit at rest? What happens when your capacity is tight, does traffic move? Which sub-processors touch our content, and are any of them outside the EU? How long are prompts and outputs retained, and can that be set to zero? Is our content excluded from training by contract rather than by policy? Ask for the answers in writing, and note the date, because these terms change.

How often is this comparison updated?

Every source page is re-fetched weekly by an automated check that compares the residency, retention, sub-processor and training language against the version we last read. Anything that moved gets read by hand and the row is updated with a new date. Rows nobody has touched in 45 days are re-read anyway, so a vendor that quietly starts blocking us cannot leave a stale answer standing. Where a fact cannot be verified from a primary source, the row says so rather than guessing.

How this is maintained