GUIDE EUROPE · DIGITAL SOVEREIGNTY

Data sovereignty in Europe: the legal limits of American cloud services and sovereign alternatives

Keeping data on servers in Frankfurt or Milan, but run by subsidiaries of US companies, exposes businesses to the CLOUD Act, which allows US federal authorities to demand access to data without an international letter rogatory. Here is what real digital sovereignty means for European businesses.

Updated october 2026
8 min read
Altovar Technical Editorial Team

1. Where the data sits and who can ask for it are different questions

Many companies believe that a server located in Frankfurt or Milan guarantees data sovereignty by itself. This is an incomplete assessment. Physical location answers the question 'where is the disk?'. Sovereignty concerns who controls the provider, who can access the data and under which legal instruments. These are two separate questions, and the first does not resolve the second.

This is why the US CLOUD Act matters even for data stored in Europe. The law allows US authorities to require providers subject to their jurisdiction to hand over data in their possession, custody or control, wherever that data is stored. This is not an abstract issue: it depends on the provider's corporate and contractual structure, and it must be verified case by case.

2. Corporate control and the supply chain

Check who controls the company providing the service, its parent company and the companies taking part in the supply chain. If a controlling entity is subject to a non-EU jurisdiction, the risk of access requests can exist even if the service is delivered by a European subsidiary. This should not be assumed either way: ask for it in writing and document it in your risk analysis.

Look at sub-processors too. A European provider may use third-party software, remote support or backup services, which may be based or accessible outside the Union. Every sub-processor with access to data is part of the assessment. The sub-processor register should be kept up to date, communicated to the customer and accompanied by a commitment to report changes before they take effect. Perfect control over every sub-processor is not required: what matters is knowing who they are, where they operate and what they can see.

3. Comparing service models

No model is sovereign by definition. The comparison is there to put the right questions next to each option, so that the choice rests on verified information rather than slogans. The table below describes four common models and the checks to carry out for each. The table columns are the questions to put to the provider: who controls it, where the data is, who can access it.

The choice depends on the data you handle and on your dependencies. A company that only uses standard tools may have a very different risk profile from one handling health, industrial or strategic data. The right model is one in which the level of risk accepted for each type of data has been decided, documented and signed off by the accountable manager. Write the decision in a sentence the manager can sign.

ModelWhere the data isWho controls the providerWhat to verify
Global public cloud in a European regionIn Europe, by configuration choiceGroup headquartered or controlled outside the EULegal access, key management, support from third countries
European provider with its own infrastructureIn Europe, as set out in the contractCompany under European controlSub-processors, backups and remote support
Dedicated private cloud at a providerIn the data centres named in the contractDepends on the corporate structureIsolation of the environment, administrators and access
On-premises or colocation infrastructureOn company premises or at an operator of your choiceThe company itselfIn-house skills, continuity and physical security

4. What the GDPR says about transfers and access from abroad

The GDPR governs transfers of personal data to third countries. Remote access from a non-EU country, even just for technical support, is a transfer to be considered, even if the data remains stored in Europe. The controller must know not only where the data is stored, but also where it can be read and modified from, and by whom.

Not all jurisdictions are the same. The European Commission may recognise that a country provides an adequate level of protection; for some countries this decision exists, for others it does not. For the United States there are specific instruments that must be checked in each case. Encryption with keys managed only by the customer reduces the risk of access in clear text, but does not solve everything: if the provider processes the data to deliver the service, the issue remains. Document the assessment in writing.

5. Checklist for evaluating a cloud provider

Before signing, ask in writing for the information that determines the real risk. The answers should be assessed with your legal adviser and your data protection officer, not only by the IT department, because the matter concerns the contract and not just the technology. Information the provider refuses to put in writing is information you cannot rely on in the assessment.

A transparent provider answers with detail, even when the answers are uncomfortable. A provider that refers everything to generic statements of compliance is telling you something, and that is a fact to include in the assessment. When the provider gives you a precise document, such as an up-to-date sub-processor register, attach it to the contract. The document should be dated and signed by the provider.

  • Complete corporate structure, up to the ultimate parent company.
  • List of sub-processors with access to data, with the location and role of each.
  • The provider's procedure for requests for access from a foreign authority, with any notification commitments where the law allows.
  • Where backups are stored and who can access them.
  • Who manages the encryption keys and how.
  • Access by support staff from third countries, and how it is logged.
  • Contractual clauses on the processing of personal data and related documentation.
  • Exit options: data format, timescales and migration costs.

6. Common mistakes in the assessment

The first mistake is to stop at the location of the data centre: the contract says 'Europe' and the matter seems closed. The second is to think that a security certification resolves the legal question. A certification such as ISO/IEC 27001 attests to an information security management system, not to the jurisdiction that applies to the provider or to who can request the data. Every generic claim should be requested in a verifiable form.

The third is to forget ancillary services: email, collaboration tools, monitoring and remote assistance. They are often the point where data leaves the intended perimeter. The fourth is to treat sovereignty as an absolute goal. It is better to set the acceptable level of risk for each type of data, justify it and review it when providers or regulations change. Choosing to do nothing is also a decision, and it must be documented.

7. How to start: a map of data and dependencies

The first concrete step is a map: which personal or strategic data you use, in which systems, where it is stored and who accesses it from Italy and abroad. The map should also include services you do not consider cloud, such as productivity apps, support portals or payment systems. The most sensitive data often sits precisely in these smaller tools.

With the map, classify the data by sensitivity and operational dependence. For the most sensitive data, ask the provider for a written assessment of the transfer and of legal access. For the rest, verify that the level of risk has been accepted by the accountable manager. The first useful result is a written decision, even a small one, because it is the basis on which everything else is built.

Frequently Asked Questions

Is a US provider with data centres in Europe the wrong choice?

Not automatically, but it must be assessed. Data location does not exclude the possibility that the parent company is subject to access requests from non-EU authorities. A risk analysis with your legal adviser is needed, covering the contract, corporate control, encryption and support access. The outcome may be acceptable for some data and not for others.

Does encryption solve the problem?

It reduces the risk if the keys are controlled by the party that holds the data rather than by the provider. It does not solve everything: if the provider processes the data in clear text to deliver the service, it can still be subject to requests. Ask who manages the keys, where they are kept and who can use them, and have the answer checked by an independent technical expert.

Do I have to move everything out of the public cloud?

No. The most reasonable path is classification: better protect, or move, the sensitive data, and keep standard services where the risk is accepted. A full migration is an expensive choice that must be justified by real requirements, not by an abstract principle.

Is the GDPR enough to guarantee data sovereignty?

The GDPR sets rules on processing and transfers, but it does not require data to remain in Europe, nor does it prevent every access from third countries. It obliges you to assess risks and document the safeguards adopted. It is therefore a tool of control and accountability, not an absolute guarantee of sovereignty.

How do I ask the provider what happens if a request arrives from a foreign authority?

Ask for the written procedure: how it assesses the request, whether it can legally inform the customer, what controls it applies to the requested scope and how it documents the response. Also check the contract clauses and the references to the applicable rules. A reputable provider can explain the procedure without going into confidential operational detail.

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 →