What is the CLOUD Act?
DefinitionCLOUD Act
The US CLOUD Act (Clarifying Lawful Overseas Use of Data Act, 2018) lets US authorities require providers subject to US jurisdiction to disclose data in their possession, custody or control, wherever in the world that data is stored.
At PilaePilae answers it with placement. Your apps run on your premises or on dedicated machines run by European datacentre operators in a Swiss or EU region, and every company that processes your data is named in the DPA.
TopicLaw and jurisdiction
On this page (7)
What the CLOUD Act says
The Clarifying Lawful Overseas Use of Data Act was enacted on 23 March 2018 as part of the Consolidated Appropriations Act, 2018. Its core provision, 18 U.S.C. § 2713, confirms that a provider subject to US jurisdiction must answer a valid US warrant or order for data in its possession, custody or control, even when the data is stored outside the United States.
The test is control, not location. If a provider can retrieve the data, the order can reach it, whether the server is in Virginia, Dublin or Zurich.
The court case behind it
The Act was written to settle a dispute. In 2013 US prosecutors served Microsoft with a warrant for the emails of a customer whose mailbox was stored in Dublin. Microsoft refused, arguing that a US warrant stopped at the US border, and in 2016 the Court of Appeals for the Second Circuit agreed. The government took the case to the Supreme Court, which heard it in February 2018.
Congress answered before the judges did. The CLOUD Act passed in March, the government obtained a new warrant under it, and on 17 April 2018 the Supreme Court dismissed United States v. Microsoft as moot. The question of whether US law follows data abroad has had a statutory answer ever since: it follows the provider.
From a mailbox in Dublin to a statute
- 2013: US prosecutors serve Microsoft with a warrant for a customer’s emails stored in Dublin.
- 2016: The Court of Appeals for the Second Circuit agrees with Microsoft that a US warrant stops at the US border.
- February 2018: The Supreme Court hears the government’s appeal.
- 23 March 2018: The CLOUD Act is enacted.
- 17 April 2018: The Supreme Court dismisses United States v. Microsoft as moot.
What it does not do
The Act does not create a new power to demand data. An order still has to meet the usual US standards, such as a warrant based on probable cause for the content of communications. It does not reach a company with no presence in or ties to the United States. And it does not let a foreign government serve orders on US providers, except under an executive agreement.
Executive agreements and the comity challenge
The Act lets the United States sign executive agreements under which each side’s authorities can ask the other’s providers for data directly in serious criminal cases. Two are in force: with the United Kingdom since October 2022 and with Australia since January 2024. Talks with the European Union have been under way since 2019 without an agreement. Switzerland has none.
The agreements also unlock a defence. A provider can ask a US court to modify or quash an order when the customer is not a US person and disclosure would risk breaking the law of a “qualifying foreign government”, meaning one with an executive agreement. For everyone else, including Switzerland, a provider can still argue a conflict of laws before a US court, but the starting point is disclosure.
Where it collides with Swiss and EU law
European law points the other way. Article 48 of the GDPR says a foreign court order to hand over personal data can be recognised only on the basis of an international agreement, such as a mutual legal assistance treaty. A provider that complies with a CLOUD Act order outside such an agreement may be breaking the GDPR by doing so.
Swiss law adds a criminal brake. Article 271 of the Swiss Criminal Code forbids acting on behalf of a foreign state on Swiss territory without authorisation, and the Federal Supreme Court held in 2021 that handing a foreign authority data about third parties outside official channels can fall under it. The route Switzerland recognises is international legal assistance, in which a Swiss authority reviews the request before anything leaves the country.
A provider caught between the two is in a conflict it did not choose, and its customers are the ones exposed.
Which companies in your data path it reaches
The Act follows the company, not the server. A European datacentre operated by a US company, or by a subsidiary of one, can fall within its reach. Whether a non-US company with ties to the United States is covered depends on the facts, so the useful question is: which companies in my data path answer to US courts?
That list is longer than the main vendor. It includes the hosting provider, the content delivery network, the identity provider, error reporting and any AI API your apps call. Many organisations accept some of that exposure; the point is to decide it knowingly. This is one part of data sovereignty.
What it means for a Pilae deployment
Pilae answers it with placement. Your apps run on your premises or on dedicated machines run by European datacentre operators in a Swiss or EU region, and every company that processes your data is named in the DPA. The services in a deployment that still involve a US company, and how to exclude them, are listed on CLOUD Act and your data location.
Talk to an engineer about what the rules mean for the apps you run
Thirty minutes with an engineer, a written plan and a fixed price for the first workload.
- Go deeperJurisdiction and the CLOUD ActA deployment designed so that the data sits where you choose and US-controlled services stay outside your data path.
- CompareWhat is data sovereignty?Data sovereignty is the principle that data is subject to the laws of the country where it is held and of the countries whose laws bind the companies that operate it, and that its owner keeps control over who accesses it, where it goes and how it leaves.
- CheckData residencyYour data stays in the country your contract names, Switzerland, the EU or your premises, with your contract naming each location.
