Skip to main content
v2026.11,986 entries · CC-BY 4.0

Editorial · CASRAI · Compliance and regulatory

EDPB Adopts Statement 3/2026 on Onward Data-Transfer Clauses and Finalizes Processor BCR Rules

The EDPB endorsed alternative model contractual clauses for onward international transfers under GDPR and finalized updated processor BCR recommendations.

Published 21 Nov 2026· 6 minute read
The Berlaymont building, headquarters of the European Commission in Brussels
Photo: Ank Kumar / Wikimedia Commons, CC BY-SA 4.0 (cropped). Source · Licence

The European Data Protection Board adopted Statement 3/2026 on 10 November 2026 in Brussels, endorsing alternative model contractual clauses for onward international data transfers alongside finalized Recommendations 1/2026 on processor binding corporate rules. Published in the EDPB announcement, the decisions give research universities, clinical trial networks, and cloud computing vendors new legal mechanisms for secondary cross-border transfers while preserving European Union privacy standards.

EDPB Endorses Alternative Onward Transfer Clauses and Concludes BCR-P Overhaul

During its 125th plenary meeting on 10 November 2026, the European Data Protection Board (EDPB), chaired by Anu Talus, adopted two key regulatory decisions under GDPR Chapter V. Statement 3/2026 formally endorses European Commission updates recognizing non-EU model contractual clauses for onward transfers of personal data originally exported under EU Standard Contractual Clauses (EU SCCs). Concurrently, the Board finalized Recommendations 1/2026 on Processor Binding Corporate Rules (BCR-P), completing a revision process initiated with public consultations in January 2026.

The dual release resolves critical operational bottlenecks for international research consortia and scientific cloud providers. Previously, when a primary non-EEA data importer transferred personal data onward to regional partner laboratories or external sub-processors, re-executing European contractual templates created jurisdictional friction. Statement 3/2026 establishes that data importers may rely on Model Contractual Clauses (MCCs) developed by the Council of Europe under Convention 108+ or by the Ibero-American Data Protection Network (RIPD).

In parallel, Recommendations 1/2026 modernize requirements under GDPR Article 47 for multinational corporate groups acting as data processors. The finalized guidance officially repeals and replaces legacy Article 29 Working Party documents WP 257 rev.01 and WP 265.

Core Safeguards, Module Compatibility, and Comparative Transfer Mechanisms

Alternative MCCs apply exclusively to secondary onward transfers and cannot replace EU SCCs for the initial export of personal data from the European Economic Area (EEA). Data flows must maintain compliance with European privacy standards across each processing tier, summarized below:

Transfer Mechanism Authorizing Body Permitted Scope Available Modules Key Governance Safeguards
EU Standard Contractual Clauses (Decision 2021/914) European Commission Primary EEA export and secondary onward transfers C2C, C2P, P2P, P2C Transfer impact assessments (TIAs), submission to EU supervisory authorities
Council of Europe Convention 108+ MCCs Council of Europe Consultative Committee Secondary onward transfers from non-EEA importers Module 1 (C2C), Module 2 (C2P), Module 3 (P2P) Convention 108+ principles, Clause 15 onward cascade rules
Ibero-American Data Protection Network (RIPD) MCCs RIPD Plenary Assembly Secondary onward transfers from non-EEA importers C2C and C2P only (no P2P module) Clause 6.9 onward protocols, restriction to authorized processing purposes
Processor Binding Corporate Rules (Recommendations 1/2026) European Data Protection Board Intra-group processor transfers Intra-corporate binding group rules Direct GDPR Article 28(4) satisfaction, mandatory compliance audits

Onward transfers must strictly respect the principle of GDPR Article 5(1)(b) purpose limitation. Scientific data cannot be transferred for objectives incompatible with the original research protocol. Special categories of data, including genetic and health information, require heightened technical safeguards. Furthermore, the initial data importer remains bound by Clause 11(e) and Clause 13(b) of the original EU SCCs, requiring continued cooperation with EU supervisory authorities and adherence to binding court orders.

A crucial technical limitation applies to RIPD clauses: because RIPD currently provides only Controller-to-Controller and Controller-to-Processor modules, non-EEA processors cannot use RIPD clauses for processor-to-processor onward transfers. Council of Europe clauses provide Module 3 for processor-to-processor routing.

Regulatory Background: From Schrems II to Interoperable Data Transfers

Following the Court of Justice of the European Union’s 2020 Schrems II ruling (Case C-311/18), international data transfers faced heightened compliance burdens, requiring rigorous transfer impact assessments. The European Commission modernized its standard contractual clauses in June 2021 under Decision 2021/914, establishing four functional modules for international commerce.

However, cross-border academic research encountered persistent obstacles when international partners in Latin America and Council of Europe member states hesitated to execute European contracts for local activities. Updated European Commission SCC guidance established the necessary legal bridge by acknowledging converging international model clauses.

This recognition supports multilateral data governance initiatives, such as the G7 Data Free Flow with Trust (DFFT) framework and privacy information management standards under ISO/IEC 27701. Concurrently, Recommendations 1/2026 bring Processor BCR standards into alignment with Controller BCR guidelines updated under Recommendations 1/2022.

EDPB Chair Anu Talus stated that the Board welcomes the Commission’s recognition of additional transfer tools and remains ready to engage with international fora to foster future interoperability across model contractual regimes.

Regulatory analysts at TechGDPR observed in their data protection digest that while the recognition creates valuable flexibility, organizations must verify module availability, noting that the absence of a P2P module in RIPD clauses prevents secondary cloud routing between sub-processors.

Legal analysis from Bird & Bird partners Ruth Boardman and Elizabeth Upton in their regulatory analysis welcomed the EDPB’s confirmation that approved BCR-Ps satisfy GDPR Article 28(4) sub-processing requirements without separate agreements. However, they observed that disallowing direct transfers from external EEA controllers to non-EEA group processors maintains administrative overhead compared to UK ICO policy.

Policy monitoring by Digital Policy Alert tracked the formal adoption trajectory across EU member states, confirming unified evidentiary standards for lead supervisory authorities.

Operational Implications for Universities, Clinical Consortia, and Research Offices

For academic research institutions and university technology transfer offices, the EDPB decisions require focused governance reviews across four operational areas:

  • Consortium Agreement Audits: Legal teams managing multi-site clinical trials must review existing data transfer agreements. When non-EEA academic hubs distribute EU clinical cohorts to secondary research centers, incorporating CoE or RIPD clauses can reduce negotiation delays with local ethics boards.
  • Module Alignment: Prior to executing onward transfers under RIPD clauses, university data protection officers must verify that the transfer fits controller-to-controller or controller-to-processor modules. Processor-to-processor transfers must use CoE Module 3 or EU SCCs.
  • Research Cohort Governance: Longitudinal studies utilizing broad consent under GDPR Recital 33 must ensure that secondary recipients maintain explicit purpose limitations, technical access controls, and pseudonymization standards.
  • Cloud Vendor Due Diligence: University procurement teams evaluating research repositories and genomics platforms must confirm whether providers hold approved BCR-Ps, eliminating duplicate sub-processing agreements under Article 28(4).

Implementation Timeline and Next Milestones

The regulatory roadmap sets clear milestones for research compliance teams:

  • 10 November 2026: The EDPB formally adopted Statement 3/2026 and finalized Recommendations 1/2026 (version 2) in Brussels.
  • Immediate Operational Effect: Non-EEA importers may immediately utilize Council of Europe Convention 108+ and RIPD model clauses for qualifying secondary onward transfers.
  • BCR-P Compliance Alignment: Organizations with active or pending Processor BCRs must align documentation with Recommendations 1/2026 during upcoming annual updates or ongoing supervisory reviews.
  • Multilateral Expansion: The EDPB will monitor future international developments, including proposed processor-to-processor modules within the RIPD framework and expanding ratifications of Convention 108+.

Sources

Ask CASRAI · full access

Ask about this story

Full access: large monthly usage, up to 10 source passages behind each answer, and MCP and API access for Claude Code, Codex and other CLIs. Cancel any time.

An AI assistant for research: funder rules, compliance, methods and publishing. It links the sources behind its answers and labels answers that come from a web search.

Answers draw on CASRAI's guides and dictionary plus the federal and funder documents we index: Federal Register, Grants.gov, Regulations.gov and UKRI.

Works on this site and inside Claude, Cursor and the AI tools you already use.

Everything CASRAI publishes — this page, the dictionary, the guides and the news — stays open to read, with no account and no card.

Referenced across the research world

University of Cambridge logoColumbia University logoCrossref logoUniversity of Edinburgh logoHarvard University logoUniversity of Oxford logoPrinceton University logoStanford School of Medicine logoUniversity College London logoORCID logoUniversity of Cambridge logoColumbia University logoCrossref logoUniversity of Edinburgh logoHarvard University logoUniversity of Oxford logoPrinceton University logoStanford School of Medicine logoUniversity College London logoORCID logo
  • University of Cambridge logo
  • Columbia University logo
  • Crossref logo
  • University of Edinburgh logo
  • Harvard University logo
  • University of Oxford logo
  • Princeton University logo
  • Stanford School of Medicine logo
  • University College London logo
  • ORCID logo

View CASRAI adoption →