1. Residency and localisation: what we are talking about
When people talk about data residency they mean the physical place where information is stored: servers, disks, databases and backup copies. Localisation is the concrete choice of that place, which the provider may fix for the whole service or leave configurable for some components. It is not the only thing to look at, however, because alongside content there are logs, technical metadata and support data, which often end up in different places from the main data.
For this reason the useful question is not only where my data is, but which copies exist, where they are and for how long they are kept. A serious provider must be able to answer separately for content, backups, logs and support data. A generic answer such as within a European area is not enough to make an assessment, because it says nothing about continuity copies or the flows that are triggered when something goes wrong.
2. Sovereignty: a different question from localisation
Sovereignty is a term used in very different ways. In this guide we take it to mean effective control over data: who can decide how it is handled, who can access it, under what conditions and with what ability to intervene. Where data is stored and who can legally access it are two separate questions. Data kept in a European area may still be subject to access requests from authorities in other countries, if the provider is controlled by companies that fall under those jurisdictions.
For this reason there is no simple label of the type all European, therefore sovereign. The assessment combines several elements: localisation, ownership and corporate structure of the provider, management of encryption keys, staff who can access it for support, and contractual clauses on requests from third parties. Each element must be verified with documents, not accepted on trust from commercial material.
3. Why the question matters for your company
The GDPR (Regulation (EU) 2016/679) governs the processing of personal data and imposes safeguards when data is transferred to third countries. Knowing where the data is located, who processes it and who accesses it therefore becomes part of the risk assessment, not a technical detail to be delegated. The NIS2 Directive (Directive (EU) 2022/2555, transposed in Italy by Legislative Decree 138/2024) also addresses the security of the supply chain, and the cloud provider is part of it. How far this rule applies to you depends on size and sector: check with a consultant.
Even without a specific obligation, residency affects business continuity, recovery times and the ability to change provider. Data whose location you do not know is data you cannot protect or recover precisely. When a restore is needed, discovering that a copy sits in a different perimeter from the one agreed can turn a manageable incident into a legal and operational problem.
4. Who is responsible for what
In a cloud service responsibility is shared. Typically the provider manages the physical infrastructure and part of the platform, while you manage user identities, configuration, content and how you use the service. The contract must describe this division precisely, because grey areas usually emerge during an incident or an audit, when nobody wants to take on a responsibility that is not written down. A good starting point is a table with three columns: service, operational owner and the document that describes it.
When residency is unclear, the role of each party in processing personal data also becomes uncertain: data controller, data processor and any sub-processors. Ask in writing which services process personal data, in which locations they store it and with what supporting documentation. If the provider cannot answer for a service, that service should not be in scope until the answer arrives.
5. The levels to verify
A useful assessment breaks the subject into separate levels, because each requires a different kind of evidence. The table summarises the questions to ask and the document to request for each. Answers should be included in the contract or in signed technical annexes, not given verbally during a sales meeting, because only a document can be verified over time and compared with what actually happens.
Pay attention to the details. A provider may correctly declare the location of the main data and leave out logs, metadata, backup copies or support recordings. Explicitly ask for these elements to be included in the list, because they often contain the most sensitive information about who used the system and when. If the answer does not state where these elements are located, treat them as part of the scope until the provider documents them.
| Level | Question to ask | Document to request |
|---|---|---|
| Where the main data sits | In which locations are content and databases stored? | List of locations per service |
| Where the copies sit | Do backups and replicas stay within the same perimeter? | Scheme of copies and replication rules |
| Who can access it | Which staff can read the data, including for support? | Description of access controls |
| Who controls the keys | Who holds the encryption keys and can revoke them? | Key management model |
| Who sits beneath the provider | Which sub-processors take part in the service? | Up-to-date list with locations |
6. Keys, support and copies: the points that change the risk
Two elements change real risk more than others: who controls the encryption keys and who can enter the systems for support. If the provider manages the keys exclusively, access by third parties or an order from an authority remains technically possible. Models in which the customer keeps or controls the keys reduce this risk, but add operational responsibilities: whoever loses the key risks losing the data too.
Support deserves the same attention. Ask how many people can access, from which countries they operate, under what temporary access arrangements and how sessions are recorded. Backups follow the same logic: if a backup sits in a different perimeter from the main data, its location must be declared and approved in the same way as the original data.
7. Sub-topics to explore further
This guide is an overview. Each of the following topics deserves a separate deep dive. It is best to read them in this order: first data flow mapping, because without an inventory you do not know what to verify. Then key management, the chain of sub-processors and regulated data. Only after that does it make sense to compare cloud models and prepare the questionnaire for the provider. The time to devote to each deep dive depends on the complexity of your organisation.
- Data flow mapping: how to see where information travels
- Who controls the keys: BYOK, HYOK and client-side encryption
- Sub-processors and the cloud supply chain: how to verify them
- Regulated data: where and how to keep health, financial and personal data
- Public, private and hybrid cloud: how to choose the right model
- The questions to ask a cloud provider about control of data
- Data Act: data portability and changing cloud provider
- Qualification of cloud services for public administration
8. Common mistakes
The first mistake is confusing the location stated in the sales presentation with the one written in the contract. The second is accepting a generic answer such as everything in Europe, without a list of services and locations. The third is forgetting backups, logs and support data, which often live in different places from production data and do not appear on any service sheet.
Another mistake is treating residency as a choice made once and for all. New features, additional services and sub-processors can change the picture without anyone noticing. Recheck the list at every renewal and every time the provider announces changes to the service, and keep versions of the documents you receive. A reminder in your diary a few months before renewal helps you avoid arriving unprepared.
9. How to start
This week, prepare a list of the cloud systems you actually use, including those activated by departments without going through IT. For each one note what data it holds, where it is recorded as being stored and who manages it. A perfect inventory is not needed on the first attempt: you need a baseline to start from and to complete with the provider. Even an incomplete list, if it is honest, is already a useful starting point.
Then send the questions from the table to the provider, asking for a written answer within an agreed deadline. If the answers are vague or refer to generic documents, flag it as an issue to discuss with a consultant before renewal. Clear residency cannot be improvised, but it can be obtained with a few precise requests. In this way renewal becomes a moment of verification, not automatic signature.
Frequently Asked Questions
Are data residency and localisation the same thing?
They are closely linked but do not coincide. Residency indicates the place where the provider stores the data, while localisation is the concrete choice of that place, which may be fixed for the whole service or configured for individual components. In practice it is worth asking for both pieces of information, per service and per type of data, because one service may have different rules for content, backups and logs.
If the server is in Europe, is the data sovereign?
Not necessarily. Localisation is only one factor. A provider controlled by entities outside the European territory can be reached by access requests under other jurisdictions, even if the data resides in Europe. Assessing real control requires information about the provider's ownership, key management, support staff and clauses on third-party requests. Have your case assessed by a consultant.
Does the GDPR require data to be kept in Europe?
In general, no. The GDPR regulates transfers of personal data to third countries and requires adequate safeguards when they take place, but it does not directly require every piece of data to remain within European territory. Regulated sectors or specific agreements may, however, introduce tighter constraints. Check with a consultant or your data protection officer which rules apply to your processing.
Which documents should I request from the provider?
Request a document listing the services, the storage locations for each type of data, the scheme of backups and replication, the key management model, an up-to-date list of sub-processors and a description of the controls on support access. Also ask for the clauses on handling access requests from third parties. A signed and up-to-date document is worth more than any sales presentation.
Do backups have to stay within the same perimeter as the original data?
It is not a universal obligation, but it is a choice that must be declared. If backups end up in a different perimeter, the backup copy is itself a processing of data, with the same sensitivity as the original. The risk is that a restore brings the data to a place not foreseen by the contract or by your assessment. Ask where the copies are, how long they are kept and who can access them.
Can I choose the region where my data is stored?
It depends on the provider and the service. Some options are standard, others require a plan or a dedicated configuration, and some features may not be available in every location. Before signing, check which choices are available for the services you need and whether they remain valid over time, including after platform updates or changes of sub-processors.