Sovereign cloud: what it means, the CLOUD Act, GDPR and how to choose
A sovereign cloud keeps your data and the services that process it under the control and the legal jurisdiction you choose, in practice the European Union. The term is used loosely, so it helps to split it into three questions: where is the data, who operates the service, and whose laws can reach it. This guide explains what sovereign cloud means, why an EU data region alone does not settle the question, what the GDPR and the EU Data Act say, and how a small or mid-sized company can choose hosting that fits its risk.
Legal texts were read on 12 November 2026: Regulation (EU) 2016/679 (GDPR), Regulation (EU) 2023/2854 (Data Act), Commission Implementing Decision (EU) 2023/1795 (EU-US Data Privacy Framework) and 18 U.S. Code section 2713 (the US CLOUD Act provision). This guide is general information, not legal advice.
Three levels of sovereignty
| Level | Question | What it takes |
|---|---|---|
| Data location | Where is the data stored and processed? | Data centres in the EU, including backups and logs, with no processing outside the chosen region. |
| Operational control | Who runs the service and can see the data? | Operations and support staff in the EU, customer-held encryption keys, access logged and limited. |
| Jurisdiction | Whose courts and authorities can order access? | A provider established in the EU and not controlled by a company subject to non-EU disclosure laws. |
Most "EU cloud" offers deliver the first level. Hyperscalers increasingly offer the second level through separate sovereign offerings with EU-only operations. The third level is a matter of ownership and law, and is what European providers point to. None of the levels is right for everyone; the right one follows from the data you hold.
Why location is not enough: the CLOUD Act
The US CLOUD Act of 23 March 2018 added section 2713 to Title 18 of the US Code. It states that a provider of electronic communication service or remote computing service shall comply with obligations to preserve, back up or disclose the contents of communications and other records pertaining to a customer within its possession, custody or control, regardless of whether the information is located within or outside the United States. A US provider's EU data centre is therefore within reach of a valid US order addressed to that provider.
EU law answers from the other side. Article 48 GDPR says that a judgment or decision of a third-country court or authority requiring a controller or processor to transfer or disclose personal data may only be recognised or enforced if it is based on an international agreement, such as a mutual legal assistance treaty, without prejudice to other grounds for transfer. Article 32 of the Data Act requires cloud providers to take adequate technical, organisational and legal measures to prevent third-country governmental access to non-personal data held in the EU where that would conflict with EU or national law. A provider can be caught between the two. For most companies that is a theoretical risk; for some (defence suppliers, health data, critical infrastructure, trade secrets in a sensitive field) it is the deciding factor.
GDPR transfers: what the law actually requires
Under Article 44 GDPR, any transfer of personal data to a third country may only take place if the conditions of Chapter V are met, including for onward transfers. The main routes are an adequacy decision by the Commission, or appropriate safeguards such as standard contractual clauses under Article 46.
For the United States, the Commission adopted an adequacy decision for the EU-US Data Privacy Framework on 10 July 2023 (Implementing Decision (EU) 2023/1795). It covers transfers to US companies that have certified under the framework. Its recitals recall that the Court of Justice, in its judgment of 16 July 2020 in Case C-311/18 (Schrems II), invalidated the previous decision on the Privacy Shield. Companies that relied on that earlier framework had to change their transfer basis overnight. The lesson most data protection officers draw: a transfer basis can disappear, so know which of your systems depend on one, and keep a plan for moving them.
Even with no transfer at all, your privacy notice must say whether you intend to transfer personal data outside the EU (Article 13 GDPR), and your records of processing must list such transfers (Article 30). Our data processing agreement guide covers what the contract with each cloud provider must contain.
Sovereign cloud vs private cloud vs public cloud
- Public cloud: shared infrastructure run by a provider, rented by the hour. Can be sovereign or not, depending on the provider and region.
- Private cloud: infrastructure dedicated to one organisation, in its own data centre or hosted. Sovereign only if the operator and jurisdiction are.
- Sovereign cloud: a description of control and jurisdiction, which can be delivered as public or private cloud.
- Hybrid: sensitive data in a sovereign environment, less sensitive workloads in a global public cloud. Common and often the most practical answer.
European cloud providers and sovereign offerings
A company that wants jurisdiction under EU law can choose among European providers of virtual servers, managed databases, object storage and Kubernetes, many of them based in Germany, France, Finland and the Nordics. US hyperscalers have answered with EU sovereign regions or partner-operated offerings with EU operations staff, and some Member States run national qualification schemes for trusted cloud, France's SecNumCloud being the best known. When comparing, look beyond the marketing word "sovereign" and ask the three questions from the table above, plus: which services are available, what the support hours are, and how easy it is to leave.
Switching providers: the Data Act helps
Sovereignty also means being able to leave. Chapter VI of the Data Act, applicable since 12 September 2025, gives cloud customers concrete rights:
- No obstacles to switching. Article 23 obliges providers to remove commercial, technical, contractual and organisational obstacles that prevent customers from terminating, switching to another provider or porting their exportable data and digital assets to their own infrastructure.
- A written switching clause. Article 25 requires the contract to allow switching or porting without undue delay, and in any event within a mandatory maximum transitional period of 30 calendar days, with reasonable assistance and continuity of service.
- Switching charges phased out. Under Article 29, from 12 January 2027 providers may not impose any switching charges; until then, reduced charges may not exceed the costs directly linked to the switch.
The law opens the door; your architecture decides how heavy the move is. Software built on open, portable building blocks (containers, PostgreSQL or another standard database, object storage with a standard interface, infrastructure as code) can move between providers in days. Software built deep into one provider's proprietary services cannot. Our EU Data Act guide covers the rest of the Regulation.
How to choose: a short decision path
- Classify your data. Personal data, special categories (health, biometrics), trade secrets, data covered by sector rules, public data.
- Check customer and sector requirements. Public sector tenders, health, finance and defence often specify hosting conditions in the contract.
- Decide the level you need for each class: location only, plus operational control, or full EU jurisdiction.
- Check the services you need exist at the provider that meets that level.
- Design for portability so the decision can be revisited when the law, the provider or your business changes.
- Document it in your records of processing and, for higher risk processing, in a DPIA.
How we host our clients' software
Every system we build runs in an EU region by default, in a cloud account in the client's company name, with backups in the EU and every subprocessor listed in the data processing agreement. For clients who need full EU jurisdiction we deploy to a European provider; for others we use the EU regions of a global provider where its managed services are worth it. Either way the software is built on portable components and the infrastructure is defined as code, so moving later is a planned project rather than a rewrite. See cloud migration consulting for moves between providers, and our guide to SaaS for what to check before you subscribe to someone else's software.
Questions people ask
What does sovereign cloud mean?
A sovereign cloud is cloud computing where the customer's data and the service stay under the control and legal jurisdiction the customer chooses, usually the EU or one Member State. In practice it combines three things: data stored and processed in the EU, operations run by staff in the EU, and a provider that is not subject to foreign laws that could force it to hand over data.
Is data in an EU region of a US cloud provider sovereign?
It is stored in the EU, which solves data location. It is still held by a company subject to US law, and the US CLOUD Act requires US providers to disclose data in their possession, custody or control regardless of where it is stored. Whether that matters depends on your data and your risk assessment. Providers offer additional controls, such as customer-held encryption keys and EU-based operations, to reduce the gap.
Sovereign cloud vs private cloud: what is the difference?
A private cloud is about who shares the infrastructure: it is dedicated to one organisation. A sovereign cloud is about control and jurisdiction: who can access the data and whose laws apply. A private cloud run by a foreign company can be less sovereign than a public cloud run by an EU company.
Does the GDPR require a sovereign cloud?
No. The GDPR allows transfers of personal data outside the EU under its Chapter V rules, for example under an adequacy decision or standard contractual clauses. It requires you to assess and document those transfers. A sovereign cloud is one way to avoid transfer questions altogether, not a legal requirement for every company.
Can we move from a US cloud to a European one later?
Yes, and the EU Data Act makes it easier: cloud providers must remove obstacles to switching, support a transitional period of at most 30 days, and may not charge switching fees from 12 January 2027. Software built on portable technology (containers, standard databases, infrastructure as code) moves with far less work.
Sources
- 18 U.S. Code section 2713, Required preservation and disclosure of communications and records (added by Pub. L. 115-141, 23 March 2018) (read 12 November 2026)
- Regulation (EU) 2016/679 (GDPR), Articles 13, 30, 44, 46 and 48 (read 12 November 2026)
- Commission Implementing Decision (EU) 2023/1795 of 10 July 2023, EU-US Data Privacy Framework (read 12 November 2026)
- Regulation (EU) 2023/2854 (Data Act), Articles 23, 25, 29, 32 and 50 (read 12 November 2026)