Join our Newsletter — 33% off our NHI Course
Home› Guides› CLOUD Act Guide: Cross-Border Law Enforcement Access to…
Guide Regulations & Frameworks

CLOUD Act Guide: Cross-Border Law Enforcement Access to Cloud Data

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 27 October 2026 15 min read
On this page

Choosing an EU region does not, on its own, take your data out of reach of a US warrant, because the CLOUD Act ties disclosure duties to who controls the data, not where it sits. The Clarifying Lawful Overseas Use of Data Act of March 2018 amended the US Stored Communications Act so that providers must preserve and disclose data in their possession, custody or control regardless of location, gave providers a narrow route to challenge orders that conflict with foreign law, and created executive agreements that let trusted foreign governments serve orders directly on US providers. This guide sets out what the Act actually says, how it interacts with the GDPR and the new EU e-Evidence rules, and what security and cloud architecture teams can do about it. It is for CISOs, cloud architects, privacy and procurement teams assessing sovereignty risk. Status: summarised from the US Code, the Act text published by the US Department of Justice and EU official sources, checked 27 October 2026.

Key takeaways

  • Control, not location, decides. 18 U.S.C. 2713 requires providers of electronic communication service and remote computing service to meet SCA preservation, backup and disclosure duties for data in their possession, custody or control, whether it is stored inside or outside the United States.
  • Challenges are narrow. Under 2703(h) a provider can move to modify or quash within 14 days only where the customer is not a US person and does not reside in the US, and disclosure would create a material risk of breaching the law of a "qualifying foreign government".
  • Executive agreements run both ways. 18 U.S.C. 2523 lets the US conclude agreements, so far with the UK and Australia, under which partner governments can serve orders directly on US providers, subject to privacy and civil liberties conditions.
  • European regulators see a conflict. The EDPB and EDPS concluded in July 2019 that a CLOUD Act order is not, by itself, a lawful ground for transfer under GDPR Article 48, and the EU's own e-Evidence Regulation applies from 18 August 2026.
  • Technical controls change exposure, not the law. Who holds encryption keys, which entity contracts with you and what the provider can technically access determine what a provider can be compelled to hand over.

Scope: who and what is covered

The CLOUD Act is Division V of the Consolidated Appropriations Act 2018. It did not create a new search power; it amended existing provisions of the Stored Communications Act (SCA) and Wiretap Act. Its reach therefore follows the SCA's categories. For the underlying warrant, order and subpoena rules see the US Electronic Communications Privacy Act and Stored Communications Act Guide for Security Teams.

ElementWhat the text coversPractical reading
ProvidersProviders of electronic communication service (ECS) and remote computing service (RCS); 2703(h) expressly refers to foreign ECS and RCS providersEmail, messaging, cloud storage, hosting, SaaS and IaaS providers subject to US jurisdiction, including non-US companies with sufficient US presence
DataContents of wire or electronic communications and records or other information pertaining to a customer or subscriberMailbox content, files, chat, logs and account metadata, wherever replicated
TestPossession, custody or control of the provider (2713)If the provider can access and produce it, location is not a defence
Who can compelUS governmental entities using SCA process; qualifying foreign governments under an executive agreementCriminal investigations, not civil litigation discovery
Who is not boundOrganisations that are not ECS or RCS providersAn enterprise customer is not itself a CLOUD Act addressee, but its provider may be

The Act was passed while United States v. Microsoft, about emails stored in Dublin, was before the Supreme Court. On 17 April 2018 the Court vacated the lower court judgment as moot, because the government had obtained a new warrant under the amended statute. The data location question was settled by Congress, not by the Court.

Key obligations

For providers

  • Disclosure regardless of location (2713): comply with SCA preservation, backup and disclosure obligations for communications, records and other information in the provider's possession, custody or control, inside or outside the US.
  • Comity motion (2703(h)(2)): a provider may file a motion to modify or quash within 14 days of service where it reasonably believes the customer is not a US person and does not reside in the US, and that disclosure would create a material risk of violating the laws of a qualifying foreign government. The data must be preserved while the motion is pending.
  • Court analysis (2703(h)(3)): the court weighs factors including US and foreign government interests, penalties the provider faces, the customer's location and nationality, the provider's ties to the US, the importance of the information and whether other means of obtaining it exist. 2703(h) is stated to be the exclusive basis for this type of conflict of law motion.
  • Foreign orders (2511(2)(j) and SCA amendments): providers may disclose content and records in response to an order from a foreign government covered by a certified executive agreement, which would otherwise be barred by US law.

For the US government in executive agreements (2523)

RequirementStatutory condition (2523(b), paraphrased)
Foreign law qualityRobust substantive and procedural privacy and civil liberties protections, including adequate cybercrime law (for example, Budapest Convention membership), rule of law, human rights obligations, oversight and transparency
US person minimisationProcedures to minimise acquisition, retention and dissemination of information about US persons
EncryptionThe agreement must not require providers to be able to decrypt data, nor prevent them from decrypting it
TargetingOrders may not intentionally target US persons or persons in the US, or target others to obtain information about them, or be issued on behalf of the US or a third country
Order qualitySerious crime purpose, a specific identifier, compliance with domestic law, reasonable justification, particularity, review by a court or other independent authority
InterceptionFixed, limited duration, no longer than necessary, only where less intrusive means are not reasonably available
OversightReciprocal access for the US, periodic US compliance reviews, and a US right to declare the agreement inapplicable to an order

The Attorney General's certification is not subject to judicial or administrative review (2523(c)). Congress must be notified within 7 days, and an agreement may enter into force no earlier than 180 days after notification unless a joint resolution of disapproval is enacted (2523(d)). Determinations must be reviewed every 5 years (2523(e)).

Timeline and current status

DateEvent
23 March 2018CLOUD Act enacted as part of the Consolidated Appropriations Act 2018
17 April 2018Supreme Court vacates United States v. Microsoft as moot
10 July 2019EDPB and EDPS publish their assessment of the CLOUD Act's impact on the GDPR
3 October 2019US-UK Agreement on Access to Electronic Data for the Purpose of Countering Serious Crime (UK Command Paper CS USA No.6/2019)
15 December 2021US-Australia agreement concluded
22 March 2022US and Canada announce negotiations
3 March 2023US-EU negotiations on electronic evidence resume
12 July 2023EU adopts Regulation (EU) 2023/1543 on European Production and Preservation Orders, and Directive (EU) 2023/1544 on legal representatives
18 February 2026Directive (EU) 2023/1544 applies
18 August 2026Regulation (EU) 2023/1543 applies
27 October 2026Status check for this guide: the European Commission states that EU-US negotiations are ongoing; the DOJ lists the UK and Australia agreements

The dates for the UK and Australia agreements are the agreement dates the DOJ lists, not their entry into force, which followed the congressional review process. Check the DOJ CLOUD Act resources page for any new agreement before relying on this table.

How it sits beside EU law

  • GDPR Article 48: the EDPB and EDPS consider that a foreign court or authority decision requiring transfer is only recognised where based on an international agreement such as a mutual legal assistance treaty. They found that Article 6(1)(f) legitimate interests and the Article 49 derogations generally cannot justify disclosure in response to a CLOUD Act order, with a narrow exception for vital interests, and recommended that EU companies refer US authorities to the MLAT route until an EU-US agreement exists.
  • EU e-Evidence Regulation: from 18 August 2026, authorities in participating Member States can send European Production Order Certificates directly to a provider's designated establishment or legal representative. Data must be produced within 10 days, or within 8 hours in an emergency (Article 10), preservation lasts up to 60 days with a possible 30-day extension, and penalties can reach 2% of total worldwide annual turnover (Article 15). Europe now has its own provider-directed access regime.

Enforcement and penalties

The CLOUD Act creates no new penalty schedule. Enforcement works through the instruments it amended. A provider that fails to comply with a warrant, 2703(d) order or subpoena faces the court's contempt powers, which is how the Microsoft case reached the Supreme Court. A provider that discloses improperly faces civil liability under 18 U.S.C. 2707 and the good faith defences the SCA provides. On the EU side, a provider that discloses personal data without a lawful basis risks GDPR enforcement, and from August 2026 a provider that ignores a European Production Order risks penalties of up to 2% of worldwide turnover under the e-Evidence Regulation. The real exposure for providers is the conflict between these regimes, which is why the 2703(h) comity motion and executive agreements exist.

RegimeInstrumentConsequence of non-compliance
US SCA as amended by CLOUD ActWarrant, 2703(d) order, subpoena, preservation requestContempt of court; civil claims under 2707 for improper disclosure
Executive agreement partner (for example UK)Partner's domestic order served on a US providerEnforced under the partner's law; the agreement removes the US legal bar to compliance but does not itself compel
GDPRArticle 48 and Chapter V transfer rulesSupervisory authority enforcement and fines under GDPR
EU e-Evidence RegulationEuropean Production and Preservation OrdersPecuniary penalties up to 2% of worldwide annual turnover (Article 15)

What it means for AI agents and non-human identities

  • Agent memory and logs are reachable records: conversation history, tool call logs, vector stores and agent memory hosted by an AI platform provider are communications or customer records in the provider's control. Include AI platforms in your sovereignty assessment alongside email and storage.
  • Keys decide what can be produced: the CLOUD Act does not require providers to decrypt, but if the provider manages the keys it can be ordered to produce readable data. Customer-held keys in an external key manager or HSM, with the provider unable to unwrap them, reduce what a provider can produce. See the BYOK, HYOK and External Key Management Guide.
  • Workload identities show who accessed what: if data is produced under compulsion, service accounts and workload identities used by the provider's own operators should appear in the access logs you receive. Ask whether provider operator access is logged and visible to you, and whether you are told of compelled access where the law permits.
  • Secrets in SaaS are data too: API keys, OAuth client secrets and tokens stored in a US-controlled secrets service are customer data in the provider's control. Rotate credentials after any notified compelled disclosure that touched them. See the Secrets Management Guide.
  • Autonomous data flows multiply jurisdictions: agents calling third-party tools and APIs move data into further providers' control. Each new tool endpoint is another possible addressee of an order; record them in the data flow inventory.

Compliance steps

  1. Map providers to jurisdictions: for each cloud, SaaS and AI provider, record the contracting entity, parent company and whether it is likely to be subject to US jurisdiction, alongside data location. Location alone is the wrong field.
  2. Classify data by compulsion sensitivity: identify data where foreign government access would breach a legal duty or cause serious harm (for example special category personal data, defence, critical infrastructure or legally privileged material).
  3. Choose technical controls by class: for the most sensitive class use client-side encryption or customer-held keys outside the provider's control; for others, provider-managed keys with access transparency may be acceptable. Test that the provider genuinely cannot decrypt.
  4. Negotiate contract terms: notification of government requests where lawful, a commitment to challenge overbroad requests and to use 2703(h) where it applies, transparency reports, and redirection of requests to the customer. See the Data Sovereignty and Residency Guide.
  5. Update transfer impact assessments: record the CLOUD Act and e-Evidence exposure in GDPR transfer assessments and the measures that reduce it, reflecting the EDPB-EDPS position.
  6. Prepare if you are a provider: a law enforcement request procedure that checks the instrument, identifies whether the customer is a non-US person outside the US, flags the 14-day comity window, and, from August 2026, handles European Production Orders within 10 days or 8 hours.
  7. Review annually: check the DOJ list of executive agreements, the status of EU-US negotiations and changes in provider sovereign cloud offerings.

Choosing a sovereignty approach

ApproachEffect on CLOUD Act exposureTrade-offs
EU region with a US-controlled providerLittle change: data remains in provider controlLow cost, full service catalogue; meets residency, not sovereignty
Customer-held keys (external key manager, HSM)Provider can produce only ciphertext for data at rest it cannot decryptServices needing plaintext processing lose features; key availability becomes your risk
Client-side or end-to-end encryptionStrongest reduction for stored contentSearch, AI processing and DLP on the provider side stop working
Provider operated by a separate non-US entityDepends on whether the US parent retains possession, custody or controlHigher cost; legal analysis of the control structure needed
Non-US provider with no US presenceRemoves US compulsion where the provider is outside US jurisdictionNarrower service range; other national access laws still apply

Smaller organisations usually get most value from classifying a small set of crown-jewel data and applying customer-held keys there, rather than moving everything. Large regulated organisations and public bodies often need a documented provider-by-provider assessment that a regulator can review.

Framework mapping

TopicNIST CSF 2.0NIST SP 800-53 Rev 5ISO/IEC 27001:2022 Annex A
Legal requirements and conflicts of lawGV.OC-03PT-25.31 Legal, statutory, regulatory and contractual requirements
Supplier contracts on government accessGV.SC-05SR-65.20 Addressing information security within supplier agreements, 5.23 Information security for use of cloud services
Encryption and key controlPR.DS-01SC-12, SC-288.24 Use of cryptography
Privacy and personal data transfersGV.OC-03PT-35.34 Privacy and protection of PII

Common failure patterns

  • Residency mistaken for sovereignty: a programme selects EU regions and declares the CLOUD Act risk closed, without assessing provider control.
  • Bring your own key that the provider can still use: keys imported into a provider key service remain usable by that service, so the provider can still produce plaintext.
  • Ignoring AI and observability tools: data is protected in core storage but copied in full to a US-controlled logging, analytics or AI service.
  • Contract clauses that promise the impossible: a clause that the provider will "never disclose" data conflicts with US law; aim for notification, challenge and minimisation commitments instead.
  • Missing the provider's 14-day window: a provider unaware that a customer is a non-US person outside the US cannot raise a comity motion in time; customers should make this information available to providers through account records.

Practitioner checklist

  • Every cloud, SaaS and AI provider is recorded with its contracting entity, parent and likely US jurisdiction.
  • Crown-jewel data classes have a documented decision on customer-held keys or client-side encryption.
  • Key management has been tested to confirm the provider cannot decrypt the protected class.
  • Contracts include government request notification, challenge and transparency commitments.
  • GDPR transfer impact assessments reflect the CLOUD Act, the EDPB-EDPS assessment and e-Evidence exposure.
  • Agent memory, AI logs and secrets services are included in the sovereignty inventory.
  • Providers in your group have a request procedure covering 2703(h) and European Production Orders.
  • The list of executive agreements and EU-US negotiation status is reviewed at least annually.

Standards and references

Related NHI Mgmt Group resources: Data Sovereignty and Residency Guide · US Electronic Communications Privacy Act and Stored Communications Act Guide for Security Teams · BYOK, HYOK and External Key Management Guide · Secrets Management Guide. This guide summarises the US CLOUD Act and related EU rules and is not legal advice.

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 27 October 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.