privacydeep-divesecurity

The US CLOUD Act and Your Personal Files on American Servers

Storing files with Google, Dropbox, or Microsoft? Even if you're in Europe, the US CLOUD Act allows American courts to demand your data from US cloud providers anywhere in the world.

Most people who care about data privacy know that storing files on a platform based in a country with strong privacy laws is generally better than storing them with a platform that has weaker protections. This is partly why EU regulators have pushed for data localization: the idea that European users’ data should be stored on European servers, governed by European law.

The problem is that data localization is not the same as legal protection from foreign governments. And understanding why requires knowing about a piece of US legislation that rarely appears in consumer privacy conversations but affects hundreds of millions of people worldwide: the CLOUD Act.

What the CLOUD Act Actually Says

The Clarifying Lawful Overseas Use of Data Act, passed by the US Congress in 2018, gives US law enforcement — including federal agencies — the authority to compel US-based companies to produce data stored anywhere in the world, regardless of where that data is physically located.

Read that again: regardless of where the data is physically located.

If you store personal files with Google Drive, your data might be on servers in Ireland or Belgium. But Google LLC is a US company. Under the CLOUD Act, a US court can issue a warrant or a subpoena requiring Google to hand over your files from those European servers. The data being stored in the EU does not create a legal barrier to US government access.

The same applies to:

  • Microsoft (OneDrive, SharePoint)
  • Apple (iCloud)
  • Dropbox
  • Amazon (Amazon Photos, Amazon Drive)
  • Meta (WhatsApp backups stored on Facebook infrastructure)

These are all US corporations. Their users worldwide — regardless of nationality or where the data is stored — are potentially subject to CLOUD Act demands.

Why Doesn’t GDPR Protect EU Users?

This is the question EU privacy regulators have been wrestling with publicly. The answer is that GDPR and the CLOUD Act create a genuine conflict, and there is no clean resolution.

GDPR prohibits companies from transferring personal data outside the EU without appropriate safeguards. But the CLOUD Act operates as a US legal mandate, not a data transfer in the traditional sense. When a US court orders a US company to produce data, the company is responding to a domestic legal order — it is not, in the strict legal sense, “transferring” data.

A February 2026 white paper from CMS Law, a major European law firm, described the conflict directly: “No provision of GDPR or EU law prevents a CLOUD Act demand from being issued to a US-based provider.”

In practice, this creates a situation where a US company receives a CLOUD Act demand, faces competing legal obligations (EU law vs. US law), and typically complies with the US demand — because non-compliance with a US court order means contempt of court in the company’s home jurisdiction.

What This Means for Personal Files

If you are an EU resident who stores personal photos, documents, financial records, or communications with a US-based cloud provider, those files could in principle be accessed by US law enforcement through a CLOUD Act demand — without your knowledge, without any notification requirement, and without the EU having any say in the matter.

For most people, this is a theoretical rather than practical risk. CLOUD Act demands are typically targeted at specific individuals under active investigation. The US government is not trawling through random Europeans’ holiday photos.

But “theoretical” is not the same as “impossible,” and understanding the legal structure matters for making informed choices about where personal data lives.

Consider categories of personal files that might attract legal interest:

  • Financial records (tax documents, asset records)
  • Business communications
  • Medical records
  • Legal documents
  • Communications with journalists, lawyers, or political figures

For people in sensitive situations — journalists protecting sources, lawyers protecting client confidentiality, activists in politically contentious environments, business people involved in cross-border disputes — the CLOUD Act creates a meaningful risk calculation.

The Data Residency Illusion

Cloud marketing frequently emphasizes data residency: “Your data is stored in European data centers.” For EU enterprise customers, data residency requirements are often a contractual term.

Data residency is a real and meaningful feature. It affects which legal jurisdiction’s law enforcement has the most direct path to your data, it affects latency, and it ensures compliance with EU regulations that require certain data to remain within the EU.

But data residency does not equal protection from CLOUD Act demands when the provider is a US company. The data can be on a server in Frankfurt, governed by German law at the infrastructure level, and still be subject to a valid CLOUD Act order issued to the US parent company.

This distinction — data residency vs. legal jurisdiction over the company — is one of the least-understood aspects of cloud privacy, and service providers have little incentive to make it clear.

What the EU Has Done and Not Done

The EU has been aware of this problem since before the CLOUD Act was passed. The EU-US Privacy Shield, which governed data transfers between the EU and the US, was struck down by the Court of Justice of the EU in 2020 (the Schrems II decision), in part because of concerns about US government surveillance capabilities.

Its replacement, the EU-US Data Privacy Framework, was put in place in 2023. But it primarily governs commercial data transfers and data protection standards, not law enforcement access through mechanisms like the CLOUD Act. Privacy advocates have raised legal challenges to the framework on essentially the same grounds.

The EU eIDAS regulation, the EU AI Act, and the General Data Protection Regulation all create frameworks for data governance within the EU. None of them contain a provision that effectively blocks CLOUD Act demands on US companies operating in Europe.

Some EU member states are exploring requiring public sector entities to use EU-based cloud providers specifically to avoid this problem. Several national governments have moved toward European cloud sovereignty as a policy goal. But these measures apply to government data, not individual consumers’ personal files.

What Actually Changes Your Risk Profile

If you are concerned about CLOUD Act exposure for personal files, the practical options are:

Use a provider not subject to US jurisdiction. Non-US cloud providers — companies incorporated and headquartered outside the United States — are not subject to CLOUD Act demands in the same way. A company based in Switzerland, Germany, or Canada is subject to its home country’s legal processes, not US ones. This is a genuine differentiator. Proton (Switzerland) and Tresorit (Hungary, now Switzerland) are frequently cited in this context.

Use zero-knowledge encryption. If your files are encrypted client-side with keys the provider doesn’t hold, a CLOUD Act demand produces encrypted blobs that are unreadable without the keys. The demand can be complied with, but the data delivered is useless to the requester. Zero-knowledge encryption effectively neutralizes the practical risk of CLOUD Act exposure for file contents, though metadata (who communicated with whom, file sizes, access times) may still be available.

Understand server-side encryption’s limits. Most major cloud providers offer encryption at rest — AES-256 is standard. This protects your data from raw storage access. But server-side encryption does not protect from CLOUD Act demands because the provider holds the keys. They can decrypt and produce your files.

Minimize what goes to cloud storage. Sensitive documents that don’t need cloud access don’t need to be in cloud storage at all. Local encrypted storage (using tools like VeraCrypt or an encrypted drive) puts the data outside the reach of cloud-directed demands.

Calibrating the Risk

This post is not an argument that everyone should avoid all American cloud services. For most people, in most situations, the CLOUD Act is not a live threat. American cloud companies are not routinely producing personal files to law enforcement on speculative or broad demands.

But understanding the legal structure allows you to make informed choices. The marketing language around “your data is stored in Europe” or “European data centers” is not wrong, but it omits something important. Data location and legal jurisdiction over the company holding it are different things.

If you store files that could be sensitive — legally, professionally, or personally — knowing that your cloud provider’s corporate structure determines the legal pathway to your data is relevant information that most privacy guides don’t include.

The CLOUD Act is one of the best arguments for choosing a provider that is genuinely outside US jurisdiction, or for using zero-knowledge encryption that makes the question of jurisdiction less important because the data is unreadable without your keys regardless of who demands it.

daftei is incorporated outside the US and stores files with AES-256 encryption at rest and TLS 1.3 in transit. It is GDPR and CCPA compliant, never sells user data, and never trains third-party AI models on user content. For users outside the US who want a private home for personal files, understanding the legal structure behind your provider is a starting point — not an afterthought.

Your memories deserve better than an ad platform.

Try daftei free →
← All posts