Data Protection GDPR

Transferring Customer Data Outside the EU? What Spanish Businesses Need to Know in 2026

EV

Elena Vasquez-Moretti

Spanish business data transfer guide showing international customer data transfers, GDPR safeguards, risk assessment, and compliance documentation.

If your business uses a US-based CRM, sends customer data to a supplier in India, or relies on cloud software hosted outside the European Economic Area, you are almost certainly making international data transfers under GDPR — and you may not have the legal safeguards in place to do it lawfully.

This is one of the most commonly misunderstood areas of GDPR compliance, and it is also one of the most actively enforced. Spain's data protection authority, the AEPD, has already fined companies for unlawful data transfers — including a €10 million penalty against Google for precisely this type of violation.

The rules have also shifted significantly in 2025 and early 2026, with new adequacy decisions for Brazil and the United Kingdom, ongoing uncertainty around the EU–US Data Privacy Framework, and fresh guidance from EU regulators on how to document your transfers properly.

This guide explains what international data transfers are under GDPR, which legal mechanisms Spanish businesses can use, what has changed recently, and what you need to do right now to stay compliant.

What Counts as an International Data Transfer Under GDPR?

An international data transfer occurs when personal data is moved from a controller or processor inside the European Economic Area (EEA) to a recipient located outside it.

The EEA covers all 27 EU member states plus Iceland, Liechtenstein, and Norway. Sending data to any other country — including the United States, the United Kingdom (which now has its own separate adequacy status), India, Brazil, Canada, or anywhere else — constitutes an international transfer that requires a legal basis under GDPR Chapter V.

The definition is broader than most businesses expect. It includes:

  • Uploading customer data to a US-based cloud platform such as Salesforce, HubSpot, or Microsoft 365
  • Using a marketing tool hosted on servers outside the EU
  • Sharing customer records with an overseas supplier, outsourcing partner, or parent company
  • Allowing remote access to EU personal data by staff or contractors based outside the EEA
  • Sending emails containing personal data to recipients outside the EEA

Even allowing access to EU personal data from a third country can constitute a transfer. If a customer support agent in the Philippines can log in to your customer database, that is a transfer under GDPR, regardless of where the servers are physically located.

Examples of international data transfers from Spain and the EU to non-EEA providers and recipients.

⚠️  Important: Using a cloud provider that stores data in EU-based data centres is not automatically compliant. If the provider is a US-incorporated company subject to laws like the US CLOUD Act — which can compel companies to hand over data regardless of where it is stored — you must still have an appropriate transfer mechanism in place.

The Three-Step Test Before Any Transfer

Before sending personal data outside the EEA, GDPR requires you to work through a three-step process in order.

Step 1 — Check for an adequacy decision

The European Commission periodically assesses countries outside the EEA and formally decides whether their data protection framework provides an essentially equivalent level of protection to GDPR. If the country you are transferring to has an adequacy decision, the transfer can go ahead without additional safeguards.

As of April 2026, countries with full or partial adequacy decisions include: Andorra, Argentina, Canada (commercial organisations under PIPEDA only), Faroe Islands, Guernsey, Isle of Man, Israel, Japan, Jersey, New Zealand, South Korea, Switzerland, Uruguay, the United Kingdom, and the United States (limited to organisations certified under the EU–US Data Privacy Framework).

Two significant updates have occurred recently. Brazil received a formal adequacy decision in January 2026 — the most recent addition to the list and a significant development for Spanish businesses with Latin American operations. The UK’s adequacy decision, which was set to expire in June 2025, was renewed in December 2025 and now runs until December 2031.

Adequacy decisions are not permanent. They are reviewed periodically and can be revoked if a country’s data protection standards deteriorate. Always verify the current status of the destination country before relying on adequacy as your transfer basis.

Step 2 — If no adequacy decision exists, implement appropriate safeguards

For countries not on the adequacy list — which includes most of the world — GDPR requires you to put “appropriate safeguards” in place before any transfer can go ahead. These safeguards ensure that the data continues to receive GDPR-equivalent protection once it leaves the EEA.

The main options are covered in the next section.

Step 3 — If no safeguard is available, check for narrow derogations

GDPR Article 49 contains a limited list of exceptional circumstances under which a transfer may be permitted even without an adequacy decision or safeguards. These include explicit consent from the data subject, necessity for the performance of a contract, and important public interest reasons.

Three-step GDPR transfer test for Spanish businesses sending personal data outside the EEA.

These derogations are narrow and intended for occasional, one-off transfers — not routine business operations. The AEPD has been clear that relying on Article 49 as a regular basis for commercial data transfers is not compliant.

The Legal Mechanisms Spanish Businesses Use Most

Standard Contractual Clauses (SCCs)

Standard Contractual Clauses are the most widely used transfer mechanism globally. They are pre-approved model contract terms issued by the European Commission that create legally binding data protection obligations between the EU data exporter and the non-EU data importer.

The current version of the SCCs was adopted on 4 June 2021. They replaced the previous three sets of older SCCs and introduced a modular structure with four modules covering different transfer scenarios: controller to controller, controller to processor, processor to processor, and processor to controller.

SCCs can be implemented relatively quickly. Unlike Binding Corporate Rules (see below), they do not require prior approval from a data protection authority. However, signing SCCs is no longer sufficient on its own.

⚠️  Since the Schrems II ruling in 2020, organisations relying on SCCs must also conduct a Transfer Impact Assessment (TIA) — a documented risk analysis of whether the laws in the destination country undermine the protections the SCCs are supposed to provide. Without a TIA, your SCCs are not legally valid.

Transfer Impact Assessments (TIAs)

A Transfer Impact Assessment is a structured evaluation of whether the legal and regulatory environment of the destination country is compatible with GDPR standards. It focuses particularly on government surveillance powers, whether authorities can access data without judicial oversight, and what legal remedies are available to EU data subjects in that country.

The French data protection authority CNIL published finalised TIA guidance in January 2025, which provides a practical step-by-step methodology. While this is French guidance, it closely follows the European Data Protection Board’s recommendations and represents the clearest practical framework currently available to EU businesses.

If your TIA reveals that the destination country’s laws undermine the protections in your SCCs, you must implement supplementary technical measures — such as end-to-end encryption — before proceeding. If no supplementary measure can adequately close the gap, the transfer must not take place.

SCCs, transfer impact assessments, and supplementary measures required for GDPR data transfers.

Binding Corporate Rules (BCRs)

Binding Corporate Rules are internal policies that allow multinational corporate groups to transfer personal data between entities within the group, even to countries without adequacy decisions. They create GDPR-level standards across all group entities globally.

BCRs must be approved by a competent EU data protection authority before use — a process that typically takes one to two years and involves significant legal resources. For this reason, BCRs are mainly used by large multinational corporations rather than SMEs.

If your business is a subsidiary or division of a larger international group that already has approved BCRs, you may be able to rely on those for intra-group transfers. Check with your group’s DPO or legal team.

The EU–US Data Privacy Framework (DPF)

The EU–US Data Privacy Framework was adopted by the European Commission in July 2023 as the successor to the invalidated Privacy Shield mechanism. It allows US companies that have self-certified compliance with the DPF to receive personal data from the EU without needing SCCs or a TIA.

If you transfer data to a US-based service provider, the first thing to check is whether that provider is certified under the DPF. You can verify certification at the official DPF website (dataprivacyframework.gov). Many major cloud and technology providers are certified.

However, the DPF’s long-term stability is not guaranteed. A legal challenge brought before the Court of Justice of the EU remains pending as of publication. Additionally, political developments in the US — including the dismissal of members of the oversight body in January 2025 — have raised questions about whether the DPF’s redress mechanism remains fully operational. Privacy advocates, including the group noyb, have argued the framework could be challenged again.

The practical advice for Spanish businesses: use the DPF for US transfers where it is available, but maintain SCCs with your key US providers as a backup mechanism. That way, if the DPF is invalidated, your transfers do not become unlawful overnight.

 

Checklist for Spanish businesses using US providers, including DPF certification, SCCs, and documentation.

What the AEPD Has Said and Done

Spain’s data protection authority has demonstrated it will actively enforce the international transfer rules. The AEPD fined Google €10 million for unlawful transfers of personal data — one of the clearest signals that the authority treats this area with the same seriousness as it treats consent violations or security failures.

More broadly, the AEPD’s enforcement trend is unmistakable. Total fines in 2024 reached a record €35.5 million — a 19% increase on the previous year. The authority has shifted its focus from high-volume, low-value sanctions to targeted, high-impact cases with substantially larger penalties. International transfers, biometric data, and AI-related processing are all within its current enforcement priorities.

 

Compliance dashboard showing international transfer risks, missing SCCs, TIA gaps, and penalty warnings.

The AEPD follows GDPR Chapter V without adding significant national-level restrictions beyond the standard framework. This means Spanish businesses rely on the same transfer mechanisms available across the EU — but they must be properly implemented, documented, and regularly reviewed.

📌  Spain leads all EU member states in total GDPR enforcement actions, with 1,033 fines totalling over €123 million since GDPR came into force. Treating international data transfers as a low-priority compliance area is not a risk worth taking.

Common Scenarios Spanish Businesses Get Wrong

Using US software without checking the DPF or implementing SCCs

If your business uses US tools like Google Workspace, Salesforce, HubSpot, Mailchimp, or Zoom, you are almost certainly transferring personal data to the US. Many of these providers are DPF-certified or offer SCCs as part of their data processing agreements. But you need to actively confirm this — and keep a record that you did.

Assuming data residency solves the problem

Choosing a cloud provider that stores data in Frankfurt or Dublin does not necessarily mean your transfer obligations are met. If the provider is a US-incorporated company subject to the US CLOUD Act, the risk of government access to data persists regardless of server location. You still need SCCs or another transfer mechanism.

Not reviewing third-party processors

If you use a data processor — a third party that processes personal data on your behalf — you are responsible for ensuring that processor has appropriate transfer safeguards in place, including for any sub-processors they use. Under GDPR Article 28, your Data Processing Agreement with that provider must address international transfers. Simply signing a DPA is not enough if it does not cover onward transfers and sub-processors.

Relying on outdated SCCs

The 2021 SCCs replaced all previous sets. If your business signed SCCs before December 2022 and never updated them, you may be operating under clauses that are no longer compliant. Check all your data processing agreements now.

No TIA documentation

Many businesses use SCCs but have no documented Transfer Impact Assessment to accompany them. Following the Schrems II ruling, a TIA is not optional — it is a legal requirement when relying on SCCs. Without documentation, you have no accountability evidence and no defence in an investigation.

A Practical Compliance Checklist for International Transfers

Use this checklist to assess and improve your current position.

  • Map all outbound data flows. Identify every transfer of personal data outside the EEA — including data shared with software providers, cloud services, outsourcing partners, and group entities.
  • Check adequacy status for each destination country. Verify whether the country has a current adequacy decision before assuming you can transfer freely.
  • Verify DPF certification for US recipients. For US-based providers, check dataprivacyframework.gov to confirm their certification status.
  • Implement SCCs with non-adequate country providers. Use the 2021 SCCs and select the correct module for your transfer scenario.
  • Conduct and document a TIA for each SCC-based transfer. Assess the destination country’s legal framework and document your conclusions. If supplementary measures are needed, implement and record them.
  • Review Data Processing Agreements. Ensure every DPA with a third-party processor covers international transfers and sub-processor obligations.
  • Keep your transfer records in your Record of Processing Activities (RoPA). Your RoPA should record not just what data you process but where it goes and what transfer mechanism you rely on.
  • Set a review schedule. Adequacy decisions can be revoked. The DPF may be challenged. Transfer mechanisms should be reviewed at least annually or when material changes occur.
International data transfer compliance checklist covering data flows, adequacy, DPF, SCCs, TIAs, and reviews.

How This Connects to the Rest of Your GDPR Compliance Programme

International data transfers do not exist in isolation. They intersect with several other areas of GDPR compliance that are covered in more depth across our content cluster:

Build the Knowledge to Get International Transfers Right

Understanding the rules for international data transfers is one thing. Building the documentation, conducting proper TIAs, reviewing your supplier agreements, and keeping everything updated as the regulatory landscape evolves is a sustained compliance programme.

The EU GDPR Compliance and Data Protection for Businesses course from the Spanish Compliance Institute is designed to give you exactly that — a complete, structured programme built for the Spanish and EU regulatory environment your business operates in.

Across five modules, you will cover everything from the foundational principles of GDPR to advanced topics including risk assessment, third-party processor management, and the data protection implications of emerging technologies. The course includes 18 downloadable templates, among them the tools you need to document your international transfers, assess destination country risks, and maintain compliant supplier agreements.

Whether you are a business owner getting compliant for the first time or a compliance professional building a formal programme, the course provides the structure and practical tools to get it done properly.


 

Frequently Asked Questions

01 Does GDPR apply to data transfers from Spain to other EU countries? +

No. Transfers between countries within the EEA — all EU member states plus Iceland, Liechtenstein, and Norway — are not subject to the international transfer restrictions in GDPR Chapter V. The rules apply only when data crosses outside the EEA.

02 Can I transfer customer data to the UK after Brexit? +

Yes. The European Commission renewed its adequacy decision for the UK in December 2025, extending it until December 2031. This means personal data can flow freely from Spain (and the EU) to the UK without additional transfer mechanisms. However, this decision is subject to ongoing monitoring and could be revoked if UK data protection standards diverge significantly from EU standards.

03 Is it safe to use US cloud providers like Google, Microsoft, or Salesforce for EU customer data? +

Many major US cloud providers are certified under the EU–US Data Privacy Framework or offer SCCs as part of their standard data processing agreements. However, you must actively verify this — do not assume compliance. Check each provider’s DPF certification or confirm that their SCCs are the current 2021 version. Given ongoing uncertainty around the DPF, maintaining SCCs as a backup mechanism is advisable.

04 What is a Transfer Impact Assessment and do I really need one? +

A Transfer Impact Assessment is a documented analysis of whether the legal environment in the destination country provides adequate protection for EU personal data, particularly in relation to government surveillance. Since the Schrems II ruling in 2020, a TIA is legally required whenever you transfer data using Standard Contractual Clauses. Without one, your SCCs are not legally valid. The CNIL published practical TIA guidance in January 2025, which provides a clear methodology.

05 What happens if I transfer data to a country without an adequacy decision and no SCCs in place? +

That transfer is unlawful under GDPR. The AEPD can investigate, issue formal warnings, order the transfer to stop, and impose fines of up to €20 million or 4% of global annual turnover, whichever is higher, for the most serious violations. The AEPD has already fined a major company €10 million for exactly this type of violation.

06 Does Brazil’s new adequacy decision affect Spanish businesses? +

Yes, if you transfer personal data to Brazilian recipients. Brazil received a formal EU adequacy decision in January 2026, meaning data can now flow freely from Spain to Brazil without the need for SCCs or a TIA. This is particularly relevant for Spanish businesses with Latin American operations or Brazilian suppliers.

07 Can I use Article 49 derogations for routine transfers to countries without adequacy decisions? +

No. The derogations under GDPR Article 49 are intended for occasional, one-off transfers in specific exceptional circumstances — such as when a transfer is strictly necessary to perform a contract with an individual who requested it. Relying on Article 49 as a routine basis for commercial data transfers is not compliant and has been explicitly criticised by EU regulators.

08 What should I do if a sub-processor or supplier transfers data on my behalf to a non-adequate country? +

You are responsible for ensuring any third party processing data on your behalf maintains appropriate transfer safeguards. Your Data Processing Agreement must cover international transfers. Review your DPAs for all suppliers, and ask providers to confirm which transfer mechanism they rely on for any non-EEA processing.

This article is for informational purposes only and does not constitute legal advice. For guidance specific to your organisation’s circumstances, consult a qualified data protection professional or legal adviser.