Power map · Updated June 2026

AI data sovereignty: where does your data go?

Before you sign up, know which country your data lands in — and whose laws reach it. This is the single table every business needs, with the self-hosted option that sidesteps the question entirely.

Four jurisdictions, one decision: US (CLOUD Act reach), EU (GDPR-native), China (data stored in China), or your own infrastructure (self-hosted open weights). Match the model's jurisdiction to your data's legal requirements before anything else.

Where each model's data goes

ModelJurisdictionSelf-hostable?Best for
Claude (Anthropic)USNoUS/EU enterprise, regulated with DPA
GPT (OpenAI)USNoGeneral enterprise (EU residency available)
Gemini (Google)USNoGoogle Workspace orgs
Microsoft CopilotUSNoMicrosoft 365 orgs, EU data boundary
MistralEUYesEU sovereignty, regulated industries
Llama 4 (Meta)US (or your infra)YesSelf-hosted privacy
DeepSeek / Qwen / Kimi / GLM / MiniMaxChina (API)Yes (weights)Budget; self-host for compliance

What each jurisdiction means

Match jurisdiction to your data

Your dataSafe choices
EU personal dataMistral, EU-resident enterprise tiers, or self-hosted in EU
US business dataAnthropic, OpenAI, Google, Microsoft
Regulated (HIPAA/financial)Compliant enterprise tiers or self-hosted
Non-sensitive / internalAny, including Chinese APIs for cost
Maximum controlSelf-host an open-weight model

On the homepage comparison table, the jurisdiction flag and "self-host" badge appear on every model, and you can filter to EU-safe or self-hostable.

Next steps: run the privacy checklist, weigh the China risk, and read self-host vs API for the deployment trade-off.