AI Provider Trust Registry evidence verified as of 2026-08-19

Registry / Residency

Which AI providers offer EU data residency?

As of 19 August 2026, of 16 AI model offerings tracked, 8 have clear public evidence, 6 are conditional or gated, and 2 have no public evidence.

  • Clear public evidence: Azure OpenAI Service, Claude via AWS Bedrock, Claude via Google Vertex AI, Gemini via Vertex AI, AWS Bedrock (platform), Mistral La Plateforme, Mistral via Azure AI, Llama via AWS Bedrock
  • Conditional, sales-gated, or partial: OpenAI API, Anthropic API, Cohere via AWS Bedrock, Llama via Azure AI, xAI API, DeepSeek via Fireworks AI
  • No public evidence: Cohere API, DeepSeek API (first-party)

Region-pinning and EU residency options across major AI model offerings. The cell answers: Can data be pinned to a region (especially the EU)? Statuses below are evidence grades, not endorsements, “no public evidence” means we could not verify it from public sources, not that the answer is no.

OpenAI API first-party API
Yes, sales-gated confidence: high · verified 2026-08-15

The OpenAI API data residency feature is documented on OpenAI's own site but is gated: only Enterprise Customers approved for advanced data controls (requires sales contact and prior approval) can use it, making it yes_sales_gated, not publicly self-serve.

source · full cell

Azure OpenAI Service OpenAI model, served by Microsoft Azure
Yes, public confidence: high · verified 2026-08-19

Microsoft’s own Azure OpenAI deployment documentation explicitly states that data can be pinned to a single Azure geography (e.g., an EU region) via Standard or Regional Provisioned deployments.

source · full cell

Anthropic API first-party API
Partial confidence: high · verified 2026-08-19

Anthropic's official data residency docs confirm self‑serve region pinning exists but is limited to US only, so EU pinning is not possible, matching a partial answer.

source · full cell

Claude via AWS Bedrock Anthropic model, served by AWS Bedrock
Yes, public confidence: high · verified 2026-08-17

AWS Bedrock model card explicitly states the EU geo inference ID keeps data within EU regions, confirming data can be pinned to an EU region.

source · full cell

Claude via Google Vertex AI Anthropic model, served by Google Cloud Vertex AI
Yes, public confidence: high · verified 2026-08-16

Google Cloud's own blog documents self-serve EU multi-region endpoints for Claude on Vertex AI (now generally available), confirming public, non-gated EU data-residency pinning.

source · full cell

Gemini via Vertex AI Google model, served by Google Cloud Vertex AI
Yes, public confidence: high · verified 2026-08-15

Google Cloud’s Vertex AI documentation publicly states that using EU jurisdictional multi‑region or EU locational endpoints pins ML processing to the EU, confirming data residency capability for Gemini.

source · full cell

AWS Bedrock (platform) platform row
Yes, public confidence: high · verified 2026-08-15

The official AWS Bedrock documentation publicly describes an In-Region inference option that guarantees data stays within the chosen AWS Region, confirming region pinning including EU regions.

source · full cell

Mistral La Plateforme first-party API
Yes, public confidence: high · verified 2026-08-19

Mistral's own docs provide self-serve EU regional endpoints; the recorded quote is verbatim and the value is accurate.

source · full cell

Mistral via Azure AI Mistral AI model, served by Microsoft Azure
Yes, public confidence: high · verified 2026-08-15

Microsoft's official region-availability page lists Mistral-Large-3 and mistral-medium-3-5 (models sold by Azure) with checkmarks in the Data Zone Standard tables, confirming EU data-zone processing is supported. The GitHub discussion #176 is an unanswered user feedback post that is not authoritativ

source · full cell

Cohere API Cohere model, served by Cohere (first-party)
?Unclear confidence: medium · verified 2026-08-14

Verified the verbatim quote on Cohere's own docs page; the value "unclear" is a defensible judgment since the page indicates region pinning exists but leaves available regions (and EU availability in particular) to a sales contact rather than settling it publicly.

source · full cell

Cohere via AWS Bedrock Cohere model, served by AWS Bedrock
Partial confidence: medium · verified 2026-08-17

The value partial is defensible: AWS Bedrock documents self-serve In-Region pinning, and some current Cohere models are EU-available, but the flagshiip Command R+ remains available only in us-east-1/us-west-2 (its official model card lists no EU regions and Geo/Global 'Not supported'), so a material

source · full cell

Llama via AWS Bedrock Meta model, served by AWS Bedrock
Yes, public confidence: high · verified 2026-08-15

The recorded quote is present on the authoritative AWS docs page, but the value 'partial' understates the evidence: the page documents a self-serve In-Region option that "keeps requests within a single Region" and shows it is available for eu-central-1, eu-west-1, and eu-west-3, meaning data can be

source · full cell

Llama via Azure AI Meta model, served by Microsoft Azure (Azure AI Foundry / Models-as-a-Service)
Partial confidence: high · verified 2026-08-15

The recorded source describes general Azure AI Foundry platform capabilities, not Llama-specific support. Multiple sources confirm Llama models lack Data Zone Standard and Standard (single region) deployment types: Microsoft Q&A confirms users cannot select Data Zone Standard for Llama, only Global

source · full cell

xAI API xAI model, served by xAI (first-party)
Yes, sales-gated confidence: high · verified 2026-08-16

Verified on x.ai's own pricing page that Data residency is listed under the Enterprise tier alongside "Talk to our sales team," and x.ai/api also lists "Data residency options" under its sales-oriented enterprise section, with no self-serve regional pinning documented in the docs.

source · full cell

DeepSeek API (first-party) first-party API
No public evidence confidence: medium · verified 2026-08-18

DeepSeek's authoritative privacy policy (cdn.deepseek.com) states data is directly collected, processed and stored in the PRC and no regional data-pinning feature is documented for the first-party API, so no_public_evidence stands; the recorded source chat-deep.ai is a third-party aggregator and was

source · full cell

DeepSeek via Fireworks AI DeepSeek model, served by Fireworks AI
Partial confidence: high · verified 2026-08-14

Verified on Fireworks' own docs: self-serve --region pinning to listed EU single regions exists, but single-region quota is only granted at the GLOBAL multi-region level by default and requires contacting Fireworks, so the capability is partially self-serve and partially gated. Quote is verbatim on

source · full cell