
EU-Hosted vs. Sovereign AI: What CLOUD Act Exposure Really Means for AI?
Data residency tells you where your data sleeps. It says nothing about who can wake it up. Every security questionnaire I receive from an enterprise customer has some version of the same question: "Where is the data hosted?" The usual answer is a location: Frankfurt, Dublin, Paris, an EU region. It's a good question, but it's only half of one.
Faraz Jafri
The question that actually matters is: who can be legally compelled to hand that data over, and under which country's law? Depending on how a provider is structured, the answer can involve US law, regardless of where the servers are.
That gap between EU-hosted and sovereign is what this post is about. As part of the security team at DeepMask, I work through this question regularly, with customers and with our own suppliers. Here's how we think about it.
The CLOUD Act in one paragraph
The Clarifying Lawful Overseas Use of Data Act was passed in 2018, largely as a response to United States v. Microsoft Corp., the case where Microsoft refused to hand over emails stored in Ireland. Congress settled the argument by changing the law. The CLOUD Act requires US providers to disclose data within their "possession, custody, or control", regardless of whether that data is located inside or outside the United States.
Read that phrase again. The test is not location. The test is control.
A few things follow from this that people tend to miss:
It follows the corporate tree, not the server. If the parent company is American, a European subsidiary running the infrastructure doesn't automatically put the data out of reach. Whether a US court treats the parent as having "control" is a legal question, and it hasn't been tested for most of the new sovereign structures.
The built-in objection is narrow. The Act lets a provider challenge an order on comity grounds, but that mechanism is tied to countries that have signed an executive agreement with the US. The UK and Australia have one. The EU, as of today, does not.
Notification is not guaranteed. Orders can come with non-disclosure requirements. Your provider may not be allowed to tell you.
It's not the only instrument. FISA Section 702 is a separate surveillance authority with its own reach over US electronic communication service providers. When Europeans talk about "the CLOUD Act problem," they often mean both.
None of this means US authorities are routinely pulling European data. It means the possibility exists by law, and no contract between you and your vendor can override a statute your vendor is subject to.
Why this came into focus in 2025
In June 2025 the topic got a very public airing. During a French Senate inquiry into public procurement and digital sovereignty, a senior legal representative of a major US cloud provider was questioned under oath.
The question was simple: could the provider guarantee that French citizens' data would never be handed to US authorities without the French government's consent?
The answer was candid: no such absolute guarantee could be given, although it was noted that this had never happened in practice.
Credit where it's due — that was a straight answer, because it clarifies something that often gets blurred. The same provider described strong contractual commitments to keep European customer data inside the EU, at rest, in transit and during processing. Those commitments are real and valuable. They simply answer a different question: where data is stored, rather than which legal orders a company must respond to.
This isn't specific to any one company. It applies to any provider whose parent falls under US jurisdiction, and the large providers have generally been open about it.
Why AI makes this worse, not better
With a traditional SaaS app, the sensitive data mostly lives in one database. You can encrypt it, hold the keys yourself, and reason about it fairly cleanly.
An AI inference pipeline is messier. A single user prompt to an enterprise LLM product can touch:
The prompt and the completion, which in regulated industries often contain exactly the data customers are most nervous about: contracts, patient notes, transaction details.
Embeddings and vector stores used for retrieval. They feel abstract, but they're derived from customer documents and can reveal more than people assume.
Logs, traces and evaluation sets. Observability tooling can retain prompts longer than expected, for debugging or quality review.
The model provider itself, if the model is served through someone else's API.
Support and on-call access, meaning the humans who can get into production when something breaks, and which company employs them.
Key management, because customer-managed keys only help if the keys are held somewhere a US order can't reach.
There's also a hard technical truth here: to run inference, the model needs the data in plaintext in memory. Encryption at rest and in transit doesn't change that. Confidential computing can narrow the window, but it's not a legal shield.
So when an AI vendor says "EU-hosted," the follow-up should always be: which parts? Often the compute is in Europe while some supporting services sit elsewhere. Seeing the full picture is what matters.
Sovereign by contract vs. sovereign by law
The market has responded. Several large US providers now offer dedicated European sovereign clouds: separate partitions, EU-incorporated operating entities, EU-resident staff and significant local investment. Others have partnered with European companies that operate the platform locally under licence.
These are genuine improvements. But it helps to be precise about what kind of sovereignty you're buying, because there are really three distinct models on the market and they offer very different things.
The first is the standard EU region of a US hyperscaler. Your data sits in the EU, but operations and staff are global, with contractual commitments to limit access. The ultimate parent is American. CLOUD Act exposure is straightforward — it exists. What protects you is a contract.
The second is a sovereign offering from a US hyperscaler. Data is still in the EU, but now operations are handled by an EU-incorporated entity with EU-resident staff. The corporate structure is designed to put distance between the EU operation and the US parent. CLOUD Act exposure is reduced by design, but legally untested — no court has ruled on whether these structures hold up against a US order directed at the parent. What protects you is a contract plus a corporate structure that hasn't faced its first real test.
The third is an EU-owned provider. Data is in the EU, operations are in the EU, and — critically — the ultimate parent is an EU company. There's no US entity in the corporate tree for a CLOUD Act order to land on. What protects you isn't a contract or a clever structure. It's jurisdiction itself.
I'd call the second model sovereignty by contract: the provider promises, and structures itself, to make US access very difficult. The third is sovereignty by law: there's no US parent for an order to reach in the first place.
One caveat on that third model: "EU-owned" only holds if the whole chain is EU-owned. An EU provider that quietly runs its logging on a US SaaS can reintroduce exposure through a dependency. Which brings me to the questions I actually ask.
Five questions your questionnaire is missing
If you're buying an AI product, or selling one, these are the questions worth putting in the questionnaire instead of "where is it hosted?"
Who is the ultimate parent company, and where is it incorporated? Not the contracting entity. The top of the tree.
Which subprocessors touch prompts, outputs, embeddings or logs, and who owns each of them? Ask for the list, then check the ownership of every name on it. Observability tools and model APIs deserve a closer look.
Who holds the encryption keys, and could the provider be compelled to use them? "Customer-managed" keys stored in the provider's own KMS are a different thing from keys in an HSM you control.
Who can access production, and which company employs them? Support arrangements across time zones are worth understanding.
If you had to leave this provider tomorrow, could you? Sovereignty without an exit path is just a more comfortable form of lock-in. A documented exit plan and portable architecture matter as much as the hosting location.
A vendor who can answer all five clearly, in writing, is usually one who has actually thought about it. If the answers stop at the data centre location, it's worth asking a little further.
How we approach it at DeepMask
We build AI for enterprises in regulated industries, so these questions come up early in almost every conversation. We'd rather answer them clearly than leave them to a footnote.
That shaped a few decisions for us.
Our primary inference runs on a German-owned cloud. It was a practical choice: it gives our customers a simple, clear answer to the first question above. No US parent means no CLOUD Act exposure at the infrastructure level — and in a conversation with a DPO or a regulator, that's one less thing you have to argue around.
Where we work with other providers, we map which data flows where, keep the most sensitive paths on the sovereign side, and document a transfer assessment for every supplier that needs one.
The bottom line
"EU-hosted" is a statement about geography. "Sovereign" is a statement about jurisdiction. They overlap, but they're not the same thing, and AI workloads, with their prompts, embeddings, logs and model APIs, have more places for the difference to hide.
One last thing worth keeping on your radar. Many organisations take comfort from the fact that the EU-US Data Privacy Framework survived its first challenge at the EU General Court in September 2025. But that ruling is under appeal at the Court of Justice, which struck down the framework's two predecessors in Schrems I and Schrems II. And even a valid DPF governs transfers. It does nothing to switch off the CLOUD Act. If your sovereignty story depends on a transatlantic adequacy decision staying alive, it's worth having a plan B.
Europe now has real options at every level, from hyperscaler sovereign clouds to fully EU-owned stacks. The work is in being honest about which one you've actually chosen, and saying so plainly when the questionnaire arrives.