+150 XP

SaaS · Cross-border data transfers and the rules that keep breaking

On October 6, 2015, the Court of Justice of the European Union (CJEU) struck down Safe Harbor, the fifteen-year-old framework that let thousands of companies move European personal data to US servers. Overnight, every SaaS company relying on it, from small analytics startups to Facebook, was operating on legally shaky ground. Five years later, the CJEU killed its replacement too. If you build a data residency map for your SaaS product and file it away, it will be obsolete before your next board meeting.

This lesson traces why that keeps happening, and what it means for how you architect and contract around data flows today.

Why cross-border transfers are a legal problem at all

The EU's General Data Protection Regulation (GDPR), in force since 2018, restricts moving personal data of EU residents outside the European Economic Area (EEA) unless the destination country offers "adequate" protection or specific safeguards are in place.

The US has no comparable federal privacy law. More importantly, it has broad government surveillance powers (under laws like FISA Section 702) that let intelligence agencies compel US companies to hand over foreign users' data. That clash, EU rights versus US surveillance law, is the root of every transfer mechanism collapse you're about to read.

Act one: safe harbor (2000-2015)

Safe Harbor was a self-certification scheme. US companies pledged to follow EU-equivalent privacy principles and registered with the US Department of Commerce. They could then freely import EU personal data.

Austrian law student Max Schrems filed a complaint against Facebook. He argued that US surveillance programs (revealed by Edward Snowden in 2013) made EU data unsafe once it hit US soil, regardless of Facebook's contractual promises. The CJEU agreed in *Schrems I* and invalidated Safe Harbor entirely.

Practical effect for SaaS: any company using US cloud infrastructure for EU customer data lost its legal basis overnight. Companies scrambled to add interim contractual fixes.

Act two: privacy shield (2016-2020)

The EU-US Privacy Shield replaced Safe Harbor with stronger commitments. These included an ombudsperson for EU complaints, more oversight by the US Federal Trade Commission (FTC), and annual reviews.

Schrems sued again. In July 2020, the CJEU issued *Schrems II* and struck down Privacy Shield too, for the same underlying reason. US surveillance law still let agencies access EU data without EU-style redress, and no amount of contractual promising fixed that.

Practical effect for SaaS: Privacy Shield had over 5,000 certified companies at the time (a widely cited figure from the US Department of Commerce list, as of 2020). All of them needed a new legal basis, immediately, for transfers already in motion.

Act three: standard contractual clauses, under pressure

While frameworks rose and fell, most SaaS companies actually relied on Standard Contractual Clauses (SCCs). These are pre-approved contract templates issued by the European Commission. They bind the data importer and exporter to GDPR-level protections regardless of destination country.

*Schrems II* didn't kill SCCs, but it added a requirement. Companies must conduct a Transfer Impact Assessment (TIA), which evaluates whether the destination country's laws actually let the importer honor those contractual promises in practice. For transfers to the US, that meant confronting the surveillance problem directly. No contract clause can override a government's legal authority to compel data access.

This is where most SaaS compliance teams still spend real time. They document TIAs, add encryption and access controls as "supplementary measures," and keep SCCs as the fallback mechanism even after newer frameworks exist.

Act four: the EU-US data privacy framework (2023, present)

In July 2023, the European Commission adopted an adequacy decision for the EU-US Data Privacy Framework (DPF). This time it tries to fix the actual legal problem. A 2022 US Executive Order (14086) created binding limits on signals intelligence collection. It also set up a new Data Protection Review Court (DPRC) where EU individuals can seek redress against US surveillance overreach.

Companies self-certify with the US Department of Commerce, similar to the old mechanisms. The difference is that the DPF is backed by these structural changes to US law rather than just corporate pledges.

The first court test. French MP Philippe Latombe asked the EU General Court to annul the DPF. He argued that the DPRC isn't independent enough and that US bulk data collection still goes too far. On 3 September 2025 the General Court dismissed his case (*Latombe v Commission*, T-553/23) and held that the US offered adequate protection when the decision was adopted. Latombe has appealed to the CJEU, the same court that decided *Schrems I* and *II*. A separate, broader challenge from Schrems's organisation noyb has long been expected.

Critics also point to events in Washington. In early 2025 the US administration removed Democratic members of the Privacy and Civil Liberties Oversight Board (PCLOB), one of the oversight bodies the Commission cited when it found the DPF adequate. Because the DPRC rests on an executive order, a future president could also change it without Congress.

Status as of late 2026 (subject to change): the DPF is active and widely used, and it survived its first court challenge. The final word belongs to the CJEU on appeal, so most compliance teams keep SCCs in place as a backup. You can check whether a vendor is certified at the official Data Privacy Framework registry.

What this means for your data residency map

A "data residency map" documents where a SaaS company's customer data physically lives and travels, across regions, cloud providers, and subprocessors. A few practical constraints follow from this history:

  1. No single mechanism is permanent. Legal teams now assume any US transfer mechanism could be invalidated within a product's lifetime, not just at launch.
  2. Regional hosting is now a real product feature. AWS, Microsoft Azure and Google Cloud all offer EU-region data centers so SaaS companies can promise EU customers "data stays in the EU" in the contract. That sidesteps the transfer question for the core dataset, even if metadata or support tickets still cross borders.
  3. Subprocessor chains multiply the risk. Say your product uses a US-based analytics tool, a US-based support platform, and a US-based payment processor. Each one is a separate transfer path needing its own legal basis. GDPR's accountability principle makes mapping these mandatory.
  4. Check vendor DPF status yourself. A vendor's DPF claim only counts if the vendor appears as active in the registry. Certifications lapse when companies miss their annual recertification.

A simplified compliance decision path

EU personal data needs to leave the EEA?
 ├─ Is destination covered by an EU adequacy decision? (e.g., UK, Japan, South Korea, US via DPF for certified companies)
 │    └─ Yes → transfer permitted under that decision
 ├─ No adequacy decision →
 │    └─ Use SCCs + complete a Transfer Impact Assessment
 │         └─ Add supplementary measures if TIA flags risk (encryption, access limits)
 └─ Still unresolved → consider EU-only data residency architecture

This isn't legal advice, but it reflects the general logic compliance teams apply. It's also why "just pick a transfer mechanism once" is not how this works in SaaS.

Knowledge check

1. What is the fundamental legal conflict that keeps causing EU-US data transfer mechanisms to be struck down?

2. Why was Facebook's compliance with Safe Harbor's self-certification principles not enough to protect it in Schrems I?

3. A SaaS company builds a data residency map showing exactly which countries it's legally permitted to transfer EU personal data to, based on today's approved transfer mechanisms. What is the key risk this lesson highlights about relying on that map long-term?

MULTIPLE CHOICE

4. Select ALL correct answers about why the US lacks an easy path to GDPR 'adequacy' status.

Select all the correct answers.

MULTIPLE CHOICE

5. Select ALL correct answers describing what made Safe Harbor legally vulnerable to challenge.

Select all the correct answers.

The regulators and bodies to know

  • European Data Protection Board (EDPB): coordinates GDPR enforcement guidance across EU member state authorities.
  • National Data Protection Authorities (DPAs): enforce GDPR domestically. Ireland's DPC handles many major tech cases because companies like Meta and Google have their EU headquarters there. In 2023 it fined Meta €1.2 billion for US transfers made under SCCs.
  • US Department of Commerce: administers DPF self-certification.
  • US FTC: enforces DPF compliance commitments as a matter of US law. A false certification counts as an unfair or deceptive trade practice.
  • CJEU: the court that has twice ended transfer frameworks. It now has the appeal in *Latombe* before it.
  • EU General Court: the lower EU court that upheld the DPF in September 2025.

This list matters because a SaaS company's exposure goes beyond "GDPR compliance." It faces whichever of these bodies has jurisdiction over a specific data flow.

🎬 [VIDEO: "GDPR and International Data Transfers Explained" - https://www.youtube.com/results?search_query=gdpr+international+data+transfers+explained - a plain-language walkthrough of why cross-border transfer rules exist and how SCCs and adequacy decisions function in practice]

Key Takeaways

  • Cross-border transfer law has failed twice (Safe Harbor in 2015, Privacy Shield in 2020) for the same reason: US surveillance law conflicts with EU data protection rights.
  • The current DPF (2023) survived its first challenge when the EU General Court dismissed *Latombe* in September 2025, but an appeal is pending at the CJEU.
  • Standard Contractual Clauses plus a documented Transfer Impact Assessment are the durable fallback. SaaS companies keep them in place whichever framework is active.
  • EU-only hosting from AWS, Azure or Google Cloud is increasingly a product requirement for SaaS companies selling to EU enterprise customers.
  • Every subprocessor in your stack is a separate transfer risk that needs its own legal basis. Verify vendor DPF certifications in the registry instead of trusting a sales deck.
  • Treat your data residency map as a living document. The underlying legal mechanism has changed roughly every five years since 2015.