AI Guide

EU-US Data Privacy Framework: The adequacy basis for US AI vendor transfers

The EU-US Data Privacy Framework (DPF) is the European Commission's adequacy decision that lets companies send personal data to certified US companies, including many AI and cloud vendors, without signing Standard Contractual Clauses or other extra safeguards. It replaced Privacy Shield, struck down by the 2020 Schrems II ruling, and is now facing fresh legal challenges that could end the same way. Learn below what the DPF covers, why it matters for Mittelstand companies using US AI vendors, and what happens if it is invalidated.

Key Facts
  • The EU-US Data Privacy Framework took effect in July 2023 as the Commission's adequacy decision for transfers to certified US companies, replacing Privacy Shield after its 2020 annulment
  • French MEP Philippe Latombe's appeal is pending before the CJEU as Case C-703/25 P, with Microsoft granted leave to intervene and no hearing expected before late 2026
  • The US Supreme Court's June 2026 ruling in Trump v. Slaughter removed the FTC commissioner independence the Commission's adequacy decision cites as a safeguard
  • noyb (Max Schrems) called for an orderly withdrawal from the Framework after that ruling and has signaled a fresh annulment case, often called Schrems III
  • Bitkom's 2026 Cloud Report found 85 percent of German companies consider the country too dependent on US cloud providers, up from 78 percent a year earlier

Definition: EU-US Data Privacy Framework

The EU-US Data Privacy Framework (DPF) is a European Commission adequacy decision letting personal data flow to self-certified US companies without Standard Contractual Clauses or other safeguards.

Core characteristics of the EU-US Data Privacy Framework

The DPF took effect in July 2023 under GDPR Article 45, resting on US commitments limiting intelligence access to EU data.

  • Voluntary self-certification run by the US Department of Commerce
  • An adequacy decision, not a signed transfer contract
  • Covers only companies that actively certify, not every US vendor

EU-US Data Privacy Framework vs. Standard Contractual Clauses

The DPF and SCCs solve the same problem through opposite routes. A certified vendor receives data with no extra contract, since the Commission deems US protections equivalent to GDPR. SCCs are the fallback used once an adequacy decision falls, as happened almost overnight when Privacy Shield fell in the 2020 Schrems II ruling.

Importance of the EU-US Data Privacy Framework in enterprise AI

Many US AI and cloud vendors cite DPF certification as their legal basis for processing EU customer data. Gartner projects over 40 percent of AI-related data breaches will involve improper cross-border AI data use by 2027, a risk that grows whenever the transfer basis itself is disputed.

Methods and procedures for the EU-US Data Privacy Framework

Checking whether the DPF applies, and preparing for if it stops, follows a repeatable sequence.

Verifying a vendor’s certification status

Certification is self-declared and vendor-specific, not industry-wide.

  • Check the vendor’s listing on the Department of Commerce’s DPF registry
  • Confirm certification covers the data and subsidiaries in use
  • Re-check periodically, since certifications can lapse

Running a contingency assessment

A prudent company documents a fallback, typically a Data Processing Agreement with SCCs attached, and estimates how fast it could switch if annulled.

Data protection teams increasingly monitor the CJEU docket and US regulatory developments themselves, since an annulment can take effect fast.

Important KPIs for the EU-US Data Privacy Framework

Tracking DPF exposure works best as a standing compliance metric.

Operational exposure metrics

  • Vendors relying on DPF certification alone: tracked by name
  • Vendors with a documented SCC fallback ready: target 100 percent
  • Time to switch a vendor’s legal basis if annulled: under 30 days

Strategic risk metrics

The practical risk is concentration: many tools resting on one adequacy decision carry more exposure than a mixed approach. IDC notes only 4 percent of European organizations plan to drop global cloud vendors entirely, so most keep this exposure.

A well-run program tracks the open CJEU appeal and US regulatory developments as live risk items.

Risk factors and controls for the EU-US Data Privacy Framework

The DPF carries a structural risk different from an ordinary gap: its legal basis itself can be annulled.

Repeat annulment risk

The DPF is the third adequacy mechanism in this line, after Safe Harbor (2015) and Privacy Shield (2020).

  • CJEU appeal Latombe v. Commission, no hearing before late 2026
  • noyb’s threatened Schrems III challenge after the FTC ruling
  • Microsoft’s intervention for the Commission signals the stakes

US regulatory independence risk

The adequacy decision relies on FTC independence as proof US oversight is GDPR-equivalent. The June 2026 Trump v. Slaughter ruling removed that statutory protection.

Abrupt switching cost if annulled

If a ruling annuls the DPF, as happened to Privacy Shield, every company relying on it needs a new basis fast, often under pressure from auditors.

Practical example

A 140-employee precision tooling manufacturer in Baden-Württemberg had connected support and quality workflows to a US AI copilot, relying solely on its DPF certification. When its external data protection officer flagged the Latombe appeal and the FTC ruling, leadership realized it had no fallback. The firm drafted a standby SCC annex, set a review trigger tied to the CJEU docket, and began evaluating an EU-hosted alternative.

  • Documented fallback legal basis ready before any annulment
  • Vendor certification checked against the current DPF registry
  • Workflow-by-workflow check of which data must leave the EU

Current developments and effects

The DPF’s legal footing has moved markedly since mid-2026, with two challenges running in parallel.

The CJEU appeal

Latombe’s appeal against the General Court’s dismissal is now before the CJEU as Case C-703/25 P.

  • Microsoft granted leave to intervene for the Commission
  • No hearing date set, not expected before late 2026
  • Argument centers on whether US surveillance safeguards meet GDPR standards

The FTC-independence challenge

The Trump v. Slaughter ruling removed the independent-removal protection for FTC commissioners. noyb argues this undermines the adequacy decision’s reasoning and has signaled a separate challenge.

Mittelstand caution despite continued reliance

Most companies are not abandoning US AI tools, but DACH data protection leads now ask vendors for a fallback before signing, tied to broader data sovereignty planning.

Conclusion

The EU-US Data Privacy Framework remains in force, but two predecessor mechanisms already fell and two challenges now run against it in parallel. Privacy Shield’s collapse showed an annulment can arrive with little warning. Building a documented fallback now, rather than after a ruling, is the difference between an orderly switch and a scramble. Companies that would rather not carry this exposure can remove the question through EU-hosted AI deployment.

Frequently Asked Questions

What happens to our data if the Framework is struck down?

Any transfer relying solely on DPF certification needs a new legal basis immediately, typically SCCs plus a Transfer Impact Assessment. Companies without a fallback must pause the data flow under pressure.

Is this risk relevant for a company with under 100 employees?

Yes. GDPR Chapter V applies regardless of size, and smaller companies often have fewer options to switch quickly, which makes early preparation more valuable.

How is the EU-US Data Privacy Framework different from Standard Contractual Clauses?

The DPF is an adequacy decision: certified vendors receive data without an extra contract. SCCs are the fallback used once an adequacy decision applies no longer, as happened after Privacy Shield fell in 2020.

Do we need to act now, or only if the CJEU rules against the Framework?

Acting now means documenting a fallback and knowing which vendors rely solely on the DPF, not switching vendors immediately. That avoids a forced migration later.

Does using an EU-hosted AI vendor avoid this issue entirely?

Yes, for data that stays on EU infrastructure. A vendor processing data within the EU under customer control needs neither the DPF nor SCCs, one reason EU hosting is now a procurement criterion alongside data residency.

What is Schrems III and should we worry about it now?

Schrems III is the informal name for a new annulment challenge noyb has signaled after the Trump v. Slaughter ruling. It has not been decided, so the prudent step today is documentation, not an immediate vendor switch.

Building better software Contact us together