1. What changed with the Schrems II ruling
With the Schrems II ruling, the Court of Justice of the European Union annulled the adequacy decision that allowed transfers to the United States under the earlier Privacy Shield scheme. The Court made clear that the tool used to transfer data must, in substance, offer a level of protection equivalent to the European one, taking into account the law of the destination country.
In practice, the controller cannot simply sign a standard clause and consider the matter closed. It must assess whether the law of the destination country, and in particular access by public authorities, allows the data to be protected. This assessment is often called a transfer impact assessment and is documented in writing. It is not a one-off task: it must be reviewed when providers, sub-processors, services or the regulatory framework change.
2. The tools for transferring data outside the EU
The right tool depends on the destination country, the recipient and the nature of the processing. The first step is to understand which tool supports each flow, because the most common error is to use just one for everything. The table below describes the most commonly used tools and what to verify for each. Write the chosen tool next to each flow, so that the decision is traceable.
The Data Privacy Framework has been the subject of legal challenges. Do not assume it will remain valid over time: check its current status when the contract is signed and plan an alternative that can be activated if the framework falls away. The same applies to any adequacy decision, which should be checked in its latest version before relying on it for an ongoing transfer.
| Tool | When it is used | What to verify |
|---|---|---|
| Adequacy decision | Where the European Commission has recognised the level of protection of a country or sector | That the recipient falls exactly within the decision and that it is still in force |
| Data Privacy Framework | Transfers to US companies that have joined and are certified | That the recipient is certified for the type of data and the current status of the scheme |
| Standard contractual clauses | Transfers to recipients in countries without an adequacy decision | The transfer assessment and any supplementary measures, documented |
| Derogations | Exceptional, non-repetitive cases | They cannot become the ordinary basis for ongoing transfers |
3. How to carry out the transfer assessment
The assessment starts from the flow: which personal data, from which system, to which recipient, in which country and for what purpose. It includes remote access. A support technician in a third country who can see the data has access to transferred data, even if the servers remain in Europe. Many real flows arise precisely from these support activities, which nobody considers a transfer because no copy is made.
Then assess the framework of the destination country: laws on access by public authorities, the presence of independent oversight, and the possibility for the data subject to obtain redress. If the framework is weak, look for supplementary measures. Encryption with keys controlled by the exporter, pseudonymisation of data and strict limits on access reduce the risk, but they must be verified in each specific case. Record the conclusions in a clear form: if the risk is acceptable, write down why.
4. The United Kingdom, Switzerland and other countries: they are not all the same
For the United Kingdom and Switzerland, the European Commission has adequacy decisions. This simplifies many transfers, but it does not remove the need to verify that your case falls within the scope of the decision and that the decision is still in force at the time of the transfer. Treating these countries as automatically safe, without checking, is a frequent mistake.
For other non-EU countries the position varies case by case. Not all have an adequacy recognition, and in many cases a standard clause accompanied by a transfer assessment is needed. A provider that uses data centres in several countries, or foreign sub-processors, adds rows to this map. Each row must be treated as a separate flow, with its own tool and its own assessment.
5. Checklist for mapping and documenting transfers
The transfer map is the document the data protection officer or privacy adviser will check first in the event of an inspection. It must be complete, up to date and linked to the actual contracts, not to a generic description of the services. Each item in the list below must have a documented answer, verifiable by a document rather than an oral statement.
Keep the map together with the record of processing activities, and review it whenever a provider changes, a new module is activated or a service is used by a new department. A flow that does not appear in the map, however small, is an uncontrolled flow. A map that exists only in the head of the person who built it is no use for verification.
- List of all providers and services that process personal data.
- Country of storage, country of access and country where backup media are located.
- Sub-processors based or accessible outside the EU.
- Transfer tool used for each flow.
- Written transfer assessment for flows to countries without adequacy.
- Technical measures applied: encryption, access control and logging.
- Up-to-date data processing agreement with the provider.
- Corresponding entry in the record of processing activities.
6. Common mistakes that expose the business
The first mistake is to believe that the provider 'is certified' and close the matter. Certification relates to the recipient for the type of data covered by the scheme; it does not automatically cover sub-processors or services added after signing. The second is to forget remote access: support from abroad, even occasional, is a transfer to be documented with the same seriousness as sending a file.
The third is to use standard clauses as a form to sign without adapting them and without a transfer assessment: on their own they are not enough to demonstrate compliance. The fourth is to draw up the map just once. Every new SaaS tool, every new module and every change of provider can create a transfer that does not appear in the map, and which only comes to light when someone asks.
7. How to start: the flow map
The first concrete step is to ask the IT and administration departments for a list of services that receive personal data, including email apps, collaboration platforms, payment systems and remote support. For each one, note the country of storage and the country of access, although these are details the provider must confirm in writing and not data you can verify yourself.
With the map, rank the flows by risk: first those to countries without adequacy and those involving sensitive data. For these, ask the provider for the documentation on the transfer tool and the assessment. The minimum result is an up-to-date table that the data protection officer or privacy adviser can check without having to rebuild everything from scratch.
Frequently Asked Questions
Is the Data Privacy Framework enough to transfer data to a US provider?
It can be a valid tool if the provider is certified for the type of data you handle and the scheme is valid at the time of the transfer. However, it does not close the matter: you must check that the certification covers the service you buy, review sub-processors and follow the evolution of the scheme, which has been the subject of legal challenges.
Are standard contractual clauses still useful?
Yes, they are the most widely used tool for transfers to countries without adequacy. However, they must be accompanied by the transfer assessment and, where needed, by supplementary measures. A clause signed without analysis only proves that a contract exists, not that the transfer is appropriate to the risk.
Is a support technician in a third country a transfer?
Yes, when they can access personal data from abroad, even if the data remains stored in Europe. The transfer must be documented and covered by the appropriate tool. Ask the provider how it limits access, who authorises it and whether support sessions are recorded.
What is the risk if I do not document transfers?
The risk is a breach of GDPR obligations, with possible requests from the Garante, the Italian data protection authority, and reputational damage, as well as difficulty in responding to a customer or an audit. The size of the exposure depends on the specific case and cannot be estimated in the abstract. The most practical way to reduce it is a simple, up-to-date map supported by written assessments.
Does the data subject's consent always allow the transfer?
No. Consent is a derogation provided for specific and informed cases, and it cannot become the ordinary basis for ongoing transfers, for example to a service provider. For recurring flows, the tools provided for by the GDPR are needed, documented in the contract and in the transfer assessment.