Transferring Personal Data Outside the EEA
Transfers of personal data outside the EEA mapped and given a lawful basis under Chapter V GDPR, with adequacy checks, standard contractual clauses and transfer impact assessments.
- By
- By Bart Lieben, Attorney-at-Law
- Published
- Updated
The question
Your CRM is hosted in the United States. Your support desk sits in India. A software supplier in the UK has a subcontractor in Canada. Each of these is a transfer of personal data out of the European Economic Area, and each needs a legal basis. Which one applies, and what paperwork do you need?
Chapter V of the GDPR sets the rules. Article 44 allows a transfer only if the conditions of the chapter are met, also for onward transfers, so that the protection of the GDPR is not undermined. There are three routes, in this order.
The first is an adequacy decision under Article 45. Where the European Commission has decided that a country ensures an adequate level of protection, data can flow there without further safeguards. The Commission's current list includes, among others, Switzerland, the United Kingdom, Japan, the Republic of Korea, Canada (for commercial organisations) and Israel. For the United States, adequacy covers only commercial organisations that participate in the EU-US Data Privacy Framework (Commission Implementing Decision (EU) 2023/1795 of 10 July 2023). That decision is in force today, but it has been challenged in court and a question about it is pending before the Court of Justice, so we check its status at the time of each assessment.
The second route is appropriate safeguards under Article 46, in practice usually the standard contractual clauses adopted by the Commission in Implementing Decision (EU) 2021/914. They come in four modules: controller to controller, controller to processor, processor to processor and processor to controller. Under Clause 14 the parties must assess whether the laws and practices of the destination country prevent the importer from meeting its obligations, document that assessment and make it available to the supervisory authority on request.
The third route is a derogation under Article 49, such as explicit consent or a transfer necessary for a contract with the individual. These apply only where there is no adequacy decision and no appropriate safeguard, and each has its own conditions.
Our approach
We start with a map. From your record of processing and your supplier list, we trace where personal data goes, who receives it, in which role and from which country, including the sub-processors behind your suppliers. Many transfers turn out to sit one level down, in a supplier's own chain.
For each transfer we then pick the route. Is there an adequacy decision for the country? For a US recipient, is it on the Data Privacy Framework list for the right type of data? If not, which module of the standard contractual clauses fits the roles? We draft or complete the clauses and their annexes in our Document Studio, usually alongside the data processing agreement with the same supplier.
Where the clauses are used, we prepare the transfer impact assessment that Clause 14 requires. It looks at the circumstances of the transfer, the law and practice of the destination country on access by public authorities, and the technical, contractual or organisational measures that add protection where needed. For those measures we follow the EDPB's Recommendations 01/2020 on measures that supplement transfer tools. Our Academy article on international data transfers after Schrems II explains the background.
Finally, each transfer and its safeguard are entered in your register, as Article 30 expects (what a record of processing must contain). We use our own technology and our own AI, and a lawyer reviews every assessment and every set of clauses before it is used.
What you get
- A transfer map: recipients, countries, roles and onward transfers.
- Per transfer, the route chosen and why: adequacy, the Data Privacy Framework, standard contractual clauses or a derogation.
- Standard contractual clauses with completed annexes, in the right module.
- A documented transfer impact assessment for each transfer that relies on the clauses, with the supplementary measures recommended.
- Transfers and safeguards recorded in your register, with review dates.
Limits apply. An assessment can conclude that no measure gives enough protection for a given transfer. In that case the honest answer is to change the set-up, for example a supplier or hosting location inside the EEA, and we will say so. Adequacy decisions can also be withdrawn or annulled, which is why we set review dates.
Next step
Send us your list of suppliers and the countries they work from, or your current record of processing. We will tell you which transfers need attention first.
In short
- Every transfer outside the EEA mapped, including onward transfers
- Adequacy and Data Privacy Framework status checked per recipient
- Standard contractual clauses with the right module
- Transfer impact assessments documented under Clause 14
- Transfers recorded in your register
- Reviewed by a lawyer