GUIDE EUROPE · DIGITAL SOVEREIGNTY

Sovereign cloud versus EU regions of US giants: the technical reality

Residency alone does not make a cloud sovereign. Encryption managed by the provider does not stop the provider from decrypting your data to run the service, and legal exposure depends on where the provider is based, who controls it, who holds the keys and who can access the systems. Here is what separates a genuinely independent European cloud from a European region run by a large provider.

Updated october 2026
8 min read
Altovar Technical Editorial Team

1. Data residency is not the same as sovereignty

When a company hears the term 'sovereign cloud', it often thinks of just one thing: the data is in Europe. That is a necessary condition in many cases, but it is not enough. Data can be stored in a European data centre and still be exposed to non-European laws, if the provider managing it is based, controlled or staffed outside the Union. For this reason it is worth separating three questions: where the data physically is, who holds the keys that make it readable, and who can access the systems and on what legal basis. The answers may differ from one another.

The concrete risk concerns customers, contracts, staff data and technical documents. If a provider receives an access request from a foreign authority, it may be obliged to respond, even when the data is in Europe. This is not a reason to give up on the cloud. It is a factor to assess before signing, with the same weight as cost and performance. Ask the provider how it handles these requests and whether it notifies you before responding, where the law allows.

2. Three levels of control to distinguish

The first level is residency: where data is stored and replicated, including backup copies, logs and test environments. The second is management of encryption keys. If the provider manages the keys, it can decrypt the data to deliver the service, and this holds even when encryption is switched on. The third is administrative access: which provider staff can enter the systems, from which country they operate and with which logged controls.

In standard public cloud, encryption is almost always enabled, but the keys are often managed by the provider. There are options where the keys remain under the customer's control, or in a hardware module the customer can revoke, at greater cost and complexity. No choice is right in absolute terms. It depends on the data, the sector and the risk the business can accept. The useful question is which level of control is needed for which data.

3. What European rules actually require

The GDPR requires that transfers of personal data to third countries take place with adequate safeguards, and that the controller choose providers with sufficient measures. The NIS2 Directive requires the management of supply chain risk, and therefore covers cloud providers too. The DORA Regulation imposes specific oversight of ICT providers for the financial sector. None of these rules says 'use a European cloud'. They require you to assess risks, document them and have a plan for exiting the provider.

Choosing a cloud should therefore be treated as a risk decision, not as a commercial label. A 'sovereign' offering may improve some aspects, for example staff management or key control, but the guarantees must be read in the contracts and in the documents on data processing. For a specific case, the legal adviser is the right person to say whether a combination is adequate.

4. Four models compared

In practice, businesses choose between different models. The table compares the most common ones on three criteria: where the data is stored, who holds the encryption keys and how much exposure there is to non-European laws. The values are indicative and must be verified against the current terms of each offering. The most important differences lie not in the commercial name, but in the details of residency, keys and staff access.

Among the tags of this article are offerings from large providers with names such as AWS Sovereign Cloud or Azure Europe. Do not assume they carry the same guarantees: for each one, check what is provided for residency, keys, personnel and support, and which services are excluded from the guarantee. If a guarantee does not cover backups or logs, the risk remains for that data.

ModelData residencyEncryption keysExposure to non-EU laws
EU region of a large providerIn Europe, in the chosen regionManaged by the provider, with control optionsPresent if the provider is based or controlled outside the Union
Sovereign offering from a large providerIn Europe, with dedicated contractual guaranteesPossibly keys under customer controlTo be assessed case by case in the contracts
European provider with dedicated managementIn Europe, in the data centres named in the contractManaged under explicit agreementDepends on its location and corporate structure
Private infrastructure on premises or in colocationIn the location chosen by the businessUnder direct controlLimited, but with in-house costs and responsibilities

5. What to request in writing from the provider

Verbal answers are not enough. Before signing, ask for precise documents and clauses. Bring this list to the meeting and ask that each point receives a written answer. A reputable provider responds without difficulty, and its answers become part of the risk assessment you will need to document. Keep track of who answered and when, because the assessment must be reconstructible later.

Each answer should then be compared with the contract. A commercial phrase such as 'sovereign data' has no value if the contract says otherwise. If an answer is vague, rephrase it as a written question. Silence or a generic answer on an important point is already useful information for the decision. Do not sign until the answers are consistent with the proposed clauses.

  • Where the main data, replicas and backups are stored, with the list of countries.
  • Who holds the encryption keys and whether the customer can change or revoke them.
  • Which staff and which sub-processors can access the data, and from which countries they operate.
  • How requests for access from authorities are handled, and whether the customer is notified.
  • The up-to-date list of sub-processors and how changes are communicated.
  • Timescales and formats for returning data at the end of the contract.
  • Which independent audits or certifications exist, and what scope they cover.

6. Common mistakes in the choice

The first mistake is to stop at the label. An offering called sovereign may have a structure different from what the team imagines. The second is to look only at the data centre and not at backups, logs and test copies, which often end up in other regions without anyone having really decided so. The third is to forget the exit plan: if the provider changes its terms or prices, how long would it take to move the data elsewhere?

The fourth mistake is to treat sovereignty as a purely technical topic. Deciding where data is stored involves the legal manager, whoever handles privacy and whoever signs the contracts. Involve them before the choice, not after. Remember too that encryption does not replace access control and the management of privileged accounts. Ask the teams to verify these items together before entrusting the project to a provider.

7. How to start: the first concrete step

Start from an inventory of data, not from the price list. List the systems you use, the data they contain, their sensitivity and who uses them. For each, note whether it contains personal data, client information or contract documents, and what damage you would suffer if they became inaccessible or visible to third parties. This exercise shows which data requires higher levels of control and which can stay on standard solutions.

Then prepare a written request with the questions from the list, and ask two or three providers to answer against the same criteria. If your business falls within NIS2 or DORA, take the answers to your compliance adviser before signing. The first step is not choosing a brand, but knowing which data you want to protect and at what level of control.

Frequently Asked Questions

If the data is in a European data centre, is it safe from non-European laws?

Not necessarily. Data residency and the provider's jurisdiction are two different matters. If the provider is based, controlled or staffed in a way that subjects it to the laws of a third country, it may receive access requests even for data stored in Europe. Reducing this risk requires the contract, key management and access controls, not just the location.

Is encryption enough to avoid the problem?

Encryption reduces the risk, but it depends on who holds the keys. If the provider can decrypt the data to deliver the service, it may also be obliged to do so. Ask who generates and stores the keys, where they are kept and whether you can revoke them independently.

Are the sovereign offerings from large providers a guarantee?

They must be assessed case by case. They may offer stronger guarantees on residency, staff and key control, but the conditions change over time and by individual service. Read the contract, the service terms and the data processing documents, and check which functions are actually included in the guarantee.

Does the GDPR prohibit using cloud providers based outside the EU?

No. The GDPR governs transfers of personal data to third countries and requires adequate safeguards. It does not impose an absolute ban. The controller must assess the risk, choose providers with adequate measures and document the decision. For specific situations, a legal opinion is advisable.

How long does it take to change cloud provider?

It depends on the volume of data, the connected applications and their complexity. There is no standard timeframe. For this reason the exit plan should be defined before signing: export formats, responsibilities, return timescales and a restore test in a test environment.

About this content

General informational guide. Regulations and technical requirements change over time: always check the official sources and assess your specific case with a qualified technical or legal advisor.

GET IN TOUCH

Talk to our team.

We'll show how Altovar integrates into your infrastructure. No commitment, no sales pitch. Just a technical conversation.

BOOK A DEMO →