Definition: Schrems II
Schrems II is the Court of Justice of the European Union ruling in Case C-311/18 of 16 July 2020, which invalidated the EU-US Privacy Shield and bound every transfer of personal data to a third country to an individual assessment of whether that country offers protection essentially equivalent to the GDPR.
Core characteristics of Schrems II
The judgment did not forbid transatlantic transfers but shifted the legal burden onto the exporter, which must now prove case by case that recipients abroad meet EU-level protection.
- Immediate invalidation of the EU-US Privacy Shield
- Confirmation that Standard Contractual Clauses remain valid only with safeguards
- Mandatory Transfer Impact Assessment for every third-country export
- Duty for supervisory authorities to suspend non-compliant transfers
Schrems II vs. Schrems I
Schrems I (Case C-362/14, 2015) struck down the Safe Harbor agreement because US surveillance law failed to limit access to personal data. Schrems II went further and ruled that Standard Contractual Clauses alone are insufficient wherever local law, in particular Section 702 FISA and Executive Order 12333, allows disproportionate government access. Schrems I ended one legal basis, while Schrems II restructured the entire transfer regime.
Importance of Schrems II in enterprise AI
Nearly every enterprise AI stack touches a US provider, from foundation models to vector databases. According to the Bitkom KI-Studie 2025, 77 percent of German companies use at least one US-hosted cloud or AI service, which makes Schrems II a board-level issue. A single unlawful transfer can trigger fines of up to four percent of global turnover under Article 83 GDPR.
Methods and procedures for Schrems II compliance
The European Data Protection Board translated Schrems II into a six-step approach in Recommendations 01/2020, finalised on 18 June 2021.
Transfer mapping
Before any assessment, the exporter needs a complete inventory of personal data flows leaving the EEA. Without this map, no Transfer Impact Assessment is defensible.
- Identify all processors, sub-processors, and support channels
- Classify data by category and sensitivity
- Document the Article 46 GDPR transfer tool in use
Transfer Impact Assessment
The exporter evaluates the legal regime of the recipient country against EU fundamental rights. Where US surveillance laws apply, documented supplementary measures are required before the transfer may continue.
Supplementary technical measures
Technical measures carry the most weight. Common patterns are end-to-end encryption with keys held in the EU, pseudonymisation before export, and confidential computing enclaves that keep plaintext inaccessible to the US provider.
Important KPIs for Schrems II
A Mittelstand data protection programme should track a short set of indicators that surface weak spots before an audit does.
Operational compliance metrics
- Third-country transfers with a signed TIA: 100 percent
- Average age of TIA documentation: under 12 months
- Vendor roster covered by EU-US Data Privacy Framework certification: above 80 percent
- Unauthorised transfer incidents per quarter: zero
Strategic business metrics
Leadership should monitor exposure at portfolio level. Bitkom reports that 42 percent of German enterprises have cancelled or postponed a US cloud project since 2023 because of transfer risk, which makes vendor substitutability a strategic KPI.
Audit and documentation metrics
Supervisory authorities expect current records: a dated TIA per active contract, a change log for every safeguard, and evidence that the Data Protection Officer has signed off before go-live.
Risk factors and controls for Schrems II
The post-Schrems II regime concentrates risk on the exporter, which makes a defined control catalogue essential.
Government access risk
Section 702 FISA permits bulk collection from US electronic communication service providers. Mitigation needs technical barriers that render the data meaningless to the recipient.
- Customer-managed encryption keys stored in the EU
- Data minimisation and tokenisation before export
- Contractual duty to challenge disclosure orders
Onward transfer risk
A US vendor often relies on its own US sub-processors. Each hop needs the same safeguards, and the main contract has to flow the obligations down to every tier.
Loss of legal basis
Adequacy decisions can be annulled, as Schrems I and Schrems II showed. Resilience means every transfer has a fallback such as Binding Corporate Rules or an EU-only deployment with controlled data residency.
Practical example
A 180-employee specialty chemicals manufacturer in Baden-Württemberg wanted to roll out a US generative AI assistant for its 60 lab researchers. The initial contract routed formulation data through US servers with standard terms only. After a Transfer Impact Assessment, the Datenschutzbeauftragter and procurement moved the workload to an EU-hosted deployment with customer-held keys. The project went live three months later, without the renegotiation an unaddressed Schrems II finding would have forced.
- Documented data flow for every integration point
- EU-only hosting with customer-managed encryption keys
- Supplementary technical and contractual measures logged in the TIA
- Quarterly review by the Datenschutzbeauftragter
Current developments and effects
The Schrems II framework keeps shifting as courts and regulators refine it.
Confirmation of the Data Privacy Framework
On 3 September 2025 the EU General Court dismissed the annulment action against the DPF in Case T-553/23. Companies that rely on a DPF-certified US recipient now have an expressly confirmed adequacy basis.
- Case T-553/23 Latombe v Commission upheld the Commission’s decision
- A possible second CJEU challenge still looms
- Transfer Impact Assessments remain mandatory for non-DPF recipients
National guidance
On 31 January 2025 the French CNIL published detailed guidance on Transfer Impact Assessments, and the German BfDI continues to issue model clauses. Regulators converge on the EDPB six-step model, so a defensible TIA now follows a near-standard template.
Sovereign alternatives
European providers are positioning around data sovereignty as a direct response. Superkind applies this stance by running every AI agent on EU infrastructure with no training on customer data and an approval workflow that keeps control inside the organisation.
Conclusion
Schrems II is not an abstract legal case but an operating constraint on every cloud and AI decision a German Mittelstand company makes. The EU-US Data Privacy Framework has eased the picture for certified US recipients, yet the exporter still owns the Transfer Impact Assessment. A defensible posture combines current documentation, strong technical controls, and a vendor roster with credible EU-only alternatives. Companies that treat Schrems II as a standing discipline move faster on AI than those that rediscover it project by project.
Frequently Asked Questions
Is Schrems II still relevant now that the Data Privacy Framework exists?
Yes. The Framework provides an adequacy basis only for US companies certified under it. For every other US recipient, Schrems II and its Transfer Impact Assessment requirement continue to apply in full.
Does Schrems II apply to a Mittelstand company with 100 employees?
Yes. The GDPR applies regardless of company size, and supervisory authorities have fined SMEs for unlawful US transfers. A proportionate response is a one-page TIA per vendor, not a legal project of its own.
How much does Schrems II compliance cost for an SME?
For a typical setup with 10 to 20 external data processors, the initial mapping and TIA work costs between 8,000 and 25,000 euros with external support. Ongoing review is roughly a day per quarter for the Datenschutzbeauftragter.
Can we keep using US AI providers after Schrems II?
In most cases yes, but only with documented safeguards. Preferred routes are a DPF-certified provider, an EU-hosted deployment of the same product, or a European provider that keeps data in the EU with customer-held keys.
Do we need our own IT team to stay Schrems II compliant?
No. Vendor selection, contract clauses, and a reviewed TIA template cover most of the work. Internal IT only enforces the encryption and access controls that the Datenschutzbeauftragter and procurement have already specified.
How long does a first Schrems II review take?
A focused review for a 150 to 250-employee company takes four to six weeks: one week of transfer mapping, two weeks of TIA drafting per high-risk vendor, and a final week for sign-off.