Data Sovereignty / Source date:

2026 Data Sovereignty Reckoning: US CLOUD Act vs EU Laws

How the US CLOUD Act and EU law interact, what the EU Data Act's cloud switching rules change from 12 January 2027, and a cloud exit-readiness checklist. Updated 27 October 2026. Not legal advice.

Illustration of a server enclosure and separate key safe beside a data-access dossier.

Updated 27 October 2026 to add the EU Data Act's cloud switching rules and its limits on third-country access. This is not legal advice. Confirm your position with counsel for your data, providers and jurisdictions.

The conflict between US access powers and EU data law is not new. What changed in 2025 is that the EU Data Act began to apply, adding two things buyers can use: rules that make it cheaper and more predictable to leave a cloud provider, and limits on how providers respond to non-EU government requests for non-personal data. This article covers the US side, what the usual answers do and do not fix, and what the Data Act now changes.

Assess provider jurisdiction, possession, custody or control alongside storage location

18 USC 2713, added by the CLOUD Act, requires a covered provider to preserve or disclose data in its possession, custody or control regardless of whether the records are located within or outside the United States. Ownership alone does not settle jurisdiction, control or the validity of a particular demand. Assess the applicable EU processing and transfer duties with counsel. A subsidiary structure or a storage region is not an automatic answer.

Why the usual answers do not close it

Local data centres address residency, not jurisdiction. Where data sits and which law can reach the provider are separate questions.

Contractual commitments to resist requests are commitments to challenge, not to refuse. They have value, and they are not a guarantee.

Transparency reports cover the requests a provider is permitted to disclose. Read them as a partial picture.

A European subsidiary structure helps only if control genuinely sits with the subsidiary. That is an operational question as much as a corporate one.

What each control addressesA qualitative comparison of the controls described in the source article, not legal advice or verified compliance guidance.
ControlAddressesDoes not establish
Local data centreStorage locationIndependence from provider jurisdiction
Resistance commitmentA promise to challenge a requestA guarantee that disclosure is impossible
European subsidiaryA potential control boundaryThat operational control is genuinely local
Customer-held keysWhat the provider can decryptCompatibility with every processing service

Qualitative summary of this article's source text, not a measured outcome or performance estimate.

What independent key control can and cannot change

Strong encryption and genuinely independent key control may limit readable disclosure, but they do not erase legal obligations. The EDPB's supplementary-measures recommendations (version 2.0, adopted 18 June 2021) set conditions and distinguish storage from processing that needs readable data. Assess implementation, key access, metadata, support access and the specific transfer. Customer-managed keys alone are not a universal guarantee.

Independent key control is also demanding to run, and some services cannot process data they cannot read. Check each service you rely on before you make it a design requirement.

What the EU Data Act changes (as of 27 October 2026)

The Data Act, Regulation (EU) 2023/2854, has applied since 12 September 2025 (Article 50). Its Chapter VI sets rules for switching between data processing services, which include cloud and edge services. It covers providers offering those services to customers in the EU, wherever the provider is established (Article 1(3)).

Switching charges

  • From 12 January 2027, providers "shall not impose any switching charges on the customer for the switching process" (Article 29(1)).
  • Until then, providers may charge reduced switching charges that do not exceed the costs directly linked to the switching process (Article 29(2) and (3)).
  • Switching charges include data egress charges. They exclude standard service fees and early termination penalties (Article 2(36)), which can still apply (recital 89). Providers must tell you about those fees and penalties before you sign (Article 29(4)).
  • If you run two providers in parallel instead of switching, a provider may still charge egress fees, limited to its costs (Article 34(2)).

Exit terms in your contract

Article 25 requires cloud contracts to include, among other terms:

  • A maximum notice period of two months to start a switch (Article 25(2)(d)).
  • A transitional period of no more than 30 calendar days after the notice period, during which the provider keeps the service running and assists with the switch (Article 25(2)(a)).
  • An exhaustive list of the data and digital assets you can port (Article 25(2)(e)).
  • At least 30 calendar days to retrieve your data (Article 25(2)(g)).

If 30 days is technically unfeasible, the provider must tell you within 14 working days, justify it and set an alternative period of no more than seven months (Article 25(4)). You can also extend the transitional period once (Article 25(5)).

Some obligations, including the charge rules, do not apply where most main features of a service are custom-built for one customer (Article 31(1)). Chapter VI also does not apply to time-limited, non-production test versions (Article 31(2)).

What this does not mean

  • Leaving does not become free. Standard fees for the remaining contract term, early termination penalties, your own migration effort, parallel running and outside help can all still cost money.
  • A switch is not guaranteed in 30 days. A provider can justify up to seven months, and you can extend the period.
  • The rules do not do the migration for you. They govern providers' charges, contract terms and assistance.

Third-country government access

The Data Act also speaks directly to the CLOUD Act question, for non-personal data:

  • Providers must publish the jurisdiction their infrastructure is subject to, and the measures they take to prevent international governmental access to non-personal data held in the EU that would conflict with EU or national law (Article 28(1)).
  • A non-EU court or authority decision requiring access to non-personal data held in the EU is recognised or enforceable only if based on an international agreement (Article 32(2)). Without one, the provider may comply only if set conditions are met (Article 32(3)).
  • The provider must inform the customer before complying with such a request, except where the request serves law enforcement purposes and only for as long as needed (Article 32(5)).

Personal data remains governed by the GDPR and its transfer rules.

Proposed changes

The Commission proposed the Digital Omnibus, COM(2025) 837, on 19 November 2025. It would amend the Data Act among other laws. The Council agreed its negotiating mandate on 21 October 2026, and negotiations with the European Parliament begin once Parliament adopts its own position. The Omnibus is a proposal, not law. Until it is adopted, the current Data Act text applies.

Exit-readiness checklist

  • Find your switching clauses: notice period, transitional period, data retrieval period and the list of portable data. Compare them with Article 25.
  • List every charge that could apply on exit: egress, switching support, standard fees for the remaining term, early termination penalties and parallel running. Ask the provider which ones it treats as switching charges, now and after 12 January 2027.
  • Check whether any service could count as custom-built under Article 31.
  • Confirm export formats and tools, and ask for the provider's published information on data structures, formats and interfaces (Article 26).
  • Map dependencies with no direct equivalent elsewhere: identity, keys, logging, backups, integrations, managed databases and AI services.
  • Estimate your own migration effort and the destination provider's onboarding costs. These sit outside the switching-charge rules.
  • Ask for the provider's jurisdiction and access-measure statement under Article 28, and how it will notify you of a non-EU government request (Article 32(5)).
  • Write an exit plan with named owners, and test a partial export before you need it.

Practical guidance for third-country access

  • Assess provider jurisdiction and control, not only data location.
  • Hold your own keys where the workload allows it.
  • Read resistance commitments as undertakings to challenge, not to refuse.
  • Classify the workloads where third-country access would matter most.
  • Build portability into contracts using the Data Act terms above.
  • Document the residual risk you accept, explicitly.
  • Check whether control actually sits with the European entity.
  • Revisit when corporate structure changes, including acquisitions.

Outside the EU

The Data Act's switching rules apply to providers serving customers in the EU, so organisations elsewhere can feel them through their EU operations and customers. If you also have obligations in the GCC, North America or APAC, assess each workload against every regime that applies. A design built for EU concerns about US access may not satisfy a different local requirement. OPS works with operators through hubs in Toronto (North America), Dubai (GCC), Geneva (UK/EU) and Singapore (APAC).

The objection worth taking seriously

The strongest objection is that this risk gets more attention than its likely frequency justifies, while mitigations such as key management, provider restriction and architectural separation carry real cost and capability penalties every day. This article does not measure how often such demands occur.

The objection is fair about cost. The better response is to classify workloads and protect the ones where third-country access would matter most, rather than designing the whole estate around a rare event. Weigh mitigation cost against your documented requirements and each workload's actual risk.

Common questions

Does a European data centre solve this?

Not by itself. Storage location matters, but also assess the provider's legal jurisdiction and its possession, custody or control of the data. Geography and ownership alone do not determine the answer.

Is customer-held encryption practical?

Verify the actual service, processing and key architecture. Independent keys may limit disclosure under the conditions in the EDPB recommendations, but a storage label does not establish compatibility or lawful transfers.

Should we avoid American providers entirely?

Assess each workload's applicable duties, recipients, access and safeguards. Provider nationality alone is not a sufficient rule for every organisation.

Does the Data Act make leaving a cloud provider free?

No. From 12 January 2027, providers cannot impose switching charges, including data egress. Standard service fees, early termination penalties and your own migration costs can still apply.

Is the Digital Omnibus law?

No. It is a Commission proposal from 19 November 2025. The Council agreed its negotiating position on 21 October 2026, and the European Parliament has not yet adopted its own.

Sources

Checked 27 October 2026. This is not legal advice.

Talk to OPS

Start with the operating problem.