AI data residency and sovereignty: what really stays in country

Data residency means your data is stored or processed in a chosen place. Sovereignty goes further and asks who can be legally compelled to hand it over and who operates the system. For AI services, the offer varies by provider, by region and by feature, so read the exact scope before you promise anything to a regulator.

This post explains the terms, then sets out what three kinds of provider say today: model labs, cloud platforms and sovereign clouds. Everything is as of 19 October 2026, drawn from provider documentation, regulator pages and court releases, and these pages change often. It is general information, not legal advice.

Key numbers at a glance

• GDPR maximum fine, tier one: up to 10 million euros or 2 percent of worldwide annual turnover, whichever is higher (Article 83(4)). Source: text of the regulation as published on gdpr-info.eu.
• GDPR maximum fine, tier two: up to 20 million euros or 4 percent of worldwide annual turnover, whichever is higher (Article 83(5)). Same source.
• EU-US Data Privacy Framework: adopted 10 July 2023 (Commission Implementing Decision 2023/1795), an adequacy decision for participating US companies. European Commission page, as of 19 October 2026.
• Claude API inference options: "global" (default) and "us" only. Anthropic documentation, as of 19 October 2026.
• Claude US-only inference price: 1.1 times the standard rate for Claude 4.6 and later models. Same source.
• Claude workspace geo (storage at rest): "us" is the only value. Same source.
• OpenAI API data residency regions: United States, Europe (EEA and Switzerland), United Arab Emirates, plus Australia, Canada, Japan, India, Singapore, South Korea and the UK for storage. OpenAI developer documentation, as of 19 October 2026.
• OpenAI residency price uplift: 10 percent for eligible models released on or after 5 March 2026. Same source.
• Microsoft EU Data Boundary: described as complete in April 2025; European datacentre capacity to grow 40 percent over two years across 16 countries. Microsoft, 30 April 2025.
• AWS European Sovereign Cloud: general availability announced 15 January 2026, first region in Brandenburg, more than 7.8 billion euros planned in Germany, more than 90 services at launch. Amazon press release.
• EU AI Factories: 19 sites plus 13 antennas across 16 countries hosting sites. European Commission, as of 19 October 2026.
• Privacy Shield struck down: 16 July 2020, Court of Justice judgment in Case C-311/18 (Schrems II); standard contractual clauses survived. Court of Justice press release 91/20.
• Data Privacy Framework upheld: 3 September 2025, the EU General Court dismissed a challenge brought by Philippe Latombe. IAPP report, 3 September 2025.
• Adequacy review cycle: at least every four years, under GDPR Article 45(3). Text of the regulation.

Three terms that get mixed up

Data residency is where data sits. If a contract says "EU residency", it normally means the data is stored in, and sometimes processed in, EU data centres.

Data localisation is a legal rule that data must stay inside a country. It is something a government imposes, not a feature a vendor sells.

Data sovereignty is about control and legal reach. A service can run in a German data centre and still be run by a company subject to another country's laws. Sovereign offerings try to cut that link through local ownership, local staff and local legal structures.

Our earlier post on residency, sovereignty and localisation covers the definitions in more depth. This one looks at how they apply to AI services specifically, because AI adds a wrinkle. A prompt is processed (inference) at one place, stored (logs, files, memory) at another, and may be used for abuse monitoring at a third.

Why the rules exist: the GDPR transfer chapter

The European Union's General Data Protection Regulation (GDPR) does not say personal data must stay in Europe. Chapter V says personal data may leave only on a recognised basis. The chapter's headings are: general principle for transfers (Article 44), transfers on the basis of an adequacy decision (45), transfers subject to appropriate safeguards (46), binding corporate rules (47), transfers not authorised by Union law (48), and derogations for specific situations (49).

The three main routes work like a ladder.

Adequacy (Article 45). The Commission looks at a country's rule of law, its legislation, and in particular "the access of public authorities to personal data", along with whether independent supervisory authorities exist and function, and the country's international commitments. Each adequacy decision must carry a periodic review "at least every four years". Once a country is found adequate, data can flow to it without any further paperwork.

Appropriate safeguards (Article 46). Without adequacy, the exporter needs a safeguard, and the most common are standard contractual clauses adopted by the Commission and binding corporate rules approved for a corporate group. Codes of conduct and certification mechanisms also qualify if the recipient makes binding commitments. Every one of these comes with a condition in Article 46(1): transfers are allowed only if "enforceable data subject rights and effective legal remedies for data subjects are available".

Derogations (Article 49). These are narrow exits for when neither of the first two applies: explicit consent after the person has been told the risks, transfers necessary for a contract with the person, important public interest, legal claims, and vital interests. There is a last resort for a transfer that is "not repetitive", concerns a "limited number of data subjects" and serves compelling legitimate interests, but the controller must then tell the supervisory authority and the person. An AI service that processes every customer prompt abroad cannot run on derogations; it is the definition of repetitive.

An adequacy decision is the European Commission formally finding that a country offers suitable protection. The EU-US Data Privacy Framework is one for the commercial sector: it lets personal data flow to US companies that participate. The Commission says it also limits US intelligence access to what is necessary and proportionate and gives EU individuals a way to seek redress. The Commission page does not describe litigation, so the court record matters.

The court history behind every AI residency question

European buyers ask hard residency questions about AI partly because two earlier transfer frameworks did not survive the courts.

On 16 July 2020, in Case C-311/18 (known as Schrems II), the Court of Justice declared the EU-US Privacy Shield adequacy decision invalid. Its press release says the Court found that the Privacy Shield decision gave US national security, public interest and law enforcement requirements "primacy", and that the limits on US public authority access to data were not equivalent to EU standards. An earlier framework, Safe Harbour, had already been struck down in October 2015 in the first Schrems case.

The same judgment kept standard contractual clauses alive, with a catch. The Court said people whose data is transferred under the clauses must get a level of protection "essentially equivalent" to that in the EU, and that the assessment must look both at the contract and at the legal system of the destination country, including public authority access. The exporter and the recipient must verify, before any transfer, whether that level of protection is respected, and the exporter must suspend the transfer or end the contract if the recipient cannot comply. This is the origin of the transfer impact assessments that appear in procurement for AI services.

The Data Privacy Framework, adopted in July 2023, is the third attempt. On 3 September 2025, the EU General Court dismissed an action by French member of parliament Philippe Latombe that sought to annul it, rejecting arguments that the new Data Protection Review Court lacked independence and that bulk collection by US intelligence agencies lacked safeguards, according to IAPP's report of the ruling. The court assessed validity as at the 2023 decision, the ruling can be appealed to the Court of Justice, and IAPP reported that the privacy group noyb said it was reviewing its options for a separate challenge. The Commission must also keep monitoring US law and can suspend, amend or repeal the decision.

For an AI buyer this history explains a common pattern: many European customers ask for both a framework certification and standard contractual clauses, so that a transfer still has a legal basis if one route falls.

Why do companies care? Fines. The ceilings in Article 83 are 20 million euros or 4 percent of worldwide annual turnover for the most serious infringements, and 10 million euros or 2 percent for the lower tier, in each case whichever is higher. Those are maximums, not typical fines.

What model labs offer today

Labs differ, and the details matter.

Anthropic. The company's documentation separates two settings. Inference geo controls where model inference runs, per request. Workspace geo controls where data is stored at rest and where some endpoint processing (such as image transcoding and code execution) happens. As of 19 October 2026, inference geo accepts "global", the default, or "us", and workspace geo accepts only "us". There is no EU value. US-only inference costs 1.1 times the standard rate on Claude 4.6 and later models, and older models return an error if you send the parameter. Rate limits are shared across geos. The documentation also says that on Amazon Bedrock and Google Cloud, the region is set by the endpoint or inference profile, so the parameter does not apply there.

That last point is the practical route for many European and Asian buyers. In its Singapore announcement of 14 October 2026, Anthropic noted that regulated organisations can run Claude with in-region inference on Amazon Bedrock to meet strict data processing requirements. The route is the cloud partner's regional offering, not a first-party regional setting.

OpenAI. The developer documentation lists regional storage and processing options. The United States and Europe (EEA plus Switzerland) support both regional storage and regional processing. The United Arab Emirates supports storage and limited processing and requires extra approval through sales. Australia, Canada, Japan, India, Singapore, South Korea and the UK support regional storage but not regional processing, which means OpenAI may process and temporarily store content outside the selected region.

The same page lists conditions worth knowing. Eligibility requires contacting sales. Europe requires a zero data retention or modified abuse monitoring arrangement. Residency covers customer content at rest where an endpoint needs persistence, and it does not cover account, metadata, usage, billing or support data. Residency endpoints carry a 10 percent uplift for eligible models released on or after 5 March 2026. Some features, such as realtime tracing, are noted as not compliant with EU residency.

Put the two side by side and the lesson is clear: "we offer data residency" is not one thing. One provider offers one region for inference and storage, another offers several regions with different rules for storage and processing.

What cloud platforms and sovereign clouds add

Cloud platforms sell the same models inside their own regions. The customer gets the cloud's regional controls, contracts and audit trail, and the model provider's model.

Sovereign clouds add a legal and operational layer. Two examples from company statements:

• Microsoft said in April 2025 that its EU Data Boundary was complete, meaning core cloud services store and process data and personal identifiers within the EU and EFTA for European customers. It also committed to a European-only board overseeing European datacentre operations, a legally binding commitment to contest government orders to suspend European cloud operations, and partnerships on sovereign clouds in France and Germany.
• AWS announced general availability of its European Sovereign Cloud on 15 January 2026. The company says the first region is in Brandenburg, Germany, operated exclusively by EU residents through German subsidiaries led by EU citizens, physically and logically separate from other AWS regions, with customer metadata able to stay in the EU, and that it holds a third-party audited sovereignty framework. These are company statements, and the third-party report is the thing to ask for.

On the public side, the European Commission describes AI Factories (19 sites and 13 antennas across 16 countries that host them, built on EuroHPC supercomputers) and plans up to seven AI gigafactories. These are publicly funded compute, aimed at European research and industry. They are not a statement that private AI services must be hosted there.

Where the gaps usually are

Five gaps appear again and again in questionnaires and contracts.

• Storage is not processing. Data may sit in a region while the model runs elsewhere. Ask where inference runs.
• Content is not metadata. Account, billing, usage and support data often fall outside the residency promise.
• Features differ. A residency promise may exclude newer or experimental features. OpenAI's page says so for several endpoints.
• Support access. Remote support staff may be in another country. Sovereign offerings address this, ordinary regions often do not.
• Sub-processors. A model hosted by a cloud, with a vendor in front, has several parties in the chain.

For more, see our posts on answering data residency questions and on LLM API calls and EU customers.

A simple checklist before you commit

• Write down which data is personal, which is regulated, and which is neither.
• Ask the provider for inference location, storage location and support access in writing.
• Ask what is excluded: metadata, logs, abuse monitoring, newer features.
• Check whether the setting is per request, per workspace or per contract.
• Ask for the third-party audit, not just the marketing page.
• Note the date. These offers changed several times in the past year.

What is firm and what is uncertain

Firm: the GDPR fine ceilings and transfer routes, the Schrems II outcome, the adoption date of the Data Privacy Framework and the September 2025 General Court ruling, and the documentation statements from Anthropic and OpenAI as of 19 October 2026.

Uncertain: whether regions will be added (Anthropic's page lists only "us" today), whether the General Court ruling is appealed or a fresh challenge to the Data Privacy Framework is filed, and how sovereign cloud claims hold up under audit. Rules outside the EU, such as India's, are not covered here and need their own check.

What to watch next

• New inference geographies from model labs.
• New regions and services in sovereign clouds.
• Any appeal of the September 2025 General Court ruling to the Court of Justice, or a new challenge to the Data Privacy Framework.
• The Commission's periodic reviews of the Data Privacy Framework.
• Further regional processing for features that are storage-only today.

Safeguard's SBOM and dependency scanning, including a free scan at https://gold.safeguard.sh/scan, shows which AI SDKs your code uses.

Quick check

Sources

• GDPR Article 83, gdpr-info.eu, text of the regulation.
• GDPR Chapter 5, gdpr-info.eu, chapter contents.
• GDPR Article 45, gdpr-info.eu, text of the regulation.
• GDPR Article 46, gdpr-info.eu, text of the regulation.
• GDPR Article 49, gdpr-info.eu, text of the regulation.
• Press release 91/20, Judgment in Case C-311/18, Court of Justice of the European Union, 16 July 2020.
• European General Court dismisses Latombe challenge, IAPP, 3 September 2025.
• EU-US data transfers, European Commission, as of 19 October 2026.
• Data residency, Anthropic documentation, as of 19 October 2026.
• Anthropic opens Singapore office and signs MOU, Anthropic, 14 October 2026.
• Your data: data residency controls, OpenAI developer documentation, as of 19 October 2026.
• European digital commitments, Microsoft, 30 April 2025.
• AWS launches AWS European Sovereign Cloud, Amazon, 15 January 2026.
• AI Factories, European Commission, as of 19 October 2026.

Last reviewed: 19 October 2026.