Onward Transfer Options Keep Proof Burden Intact

Wider Onward Transfer Options Leave the Proof Burden Intact

Every new set of contractual clauses a regulator blesses gives your organization one more way to move personal data, and one more thing to prove when someone asks where that data went.

The European Data Protection Board just handed privacy and security teams exactly that trade. In Statement 3/2026, adopted on November 10, 2026, and announced three days later, the board welcomed the European Commission’s updated FAQs on the EU standard contractual clauses and agreed that two other clause sets may now sit underneath them. The Council of Europe Model Contractual Clauses and the Ibero-American Data Protection Network Model Contractual Clauses may be used for onward transfers of personal data that a company first received under the EU SCCs, provided the conditions in the Commission’s FAQs are met.

Read that as a longer menu, not a loophole. Flexibility is the headline. Accountability is the fine print, and the fine print belongs to the first importer, the company outside the EU that received the data under the SCCs and now wants to pass it along. For a CISO, a chief compliance officer, or a data protection officer, the question after this statement is not “which clauses can we use?” It is “can we show, transfer by transfer, which clauses we used, why they were allowed, and that we still meet our original obligations?” Kiteworks secure data exchange is built around governed, logged exchange, which is where that second question gets answered. This post walks through what the statement says, what it leaves unsaid, and what to do before an auditor asks.

Key Takeaways

  1. The menu got longer. The EDPB says the Council of Europe and Ibero-American model clauses may be used for onward transfers of data received under the EU SCCs, but only under the Commission’s conditions.
  2. The first importer stays on the hook. That company must keep meeting its EU SCC duties, including cooperation with supervisory authorities and courts, and must stay able to meet them toward the next recipient.
  3. The statement leaves real gaps. It does not address adequacy decisions or third-country law, one clause set rests on a convention that is not yet in force, and the other is recognized by a limited number of Latin American countries.
  4. The failure to fear is paper chain compliance. A signed clause set with no transfer-level record of who received what is a contract, not evidence.
  5. Build the record now. A per-transfer register, a mapped vendor chain, and an audit trail that ties each disclosure to a legal instrument are what will hold up when a regulator asks.

What Statement 3/2026 Says

The statement is short, and its structure matters. The board opens by welcoming a change the Commission made to its published questions and answers on the new EU SCCs. Those updated FAQs say that the Council of Europe clauses and the Ibero-American clauses may also be used for onward transfers of personal data received under the EU SCCs. The EDPB endorses that reading and frames it as a way to keep protection strong while easing cross-border data flows, according to the EDPB’s news item of 13 November.

Take the two clause sets in turn. The Council of Europe Model Contractual Clauses, which the board calls CoE MCCs, rest on Convention 108+. The statement covers Modules 1, 2, and 3, adopted in 2023 and 2024. Convention 108+ is not yet in force, and each party to the convention decides for itself whether to approve the clauses as a transfer tool. That is a lot of conditional in one sentence. It means the clause set is real, but its footing depends on national decisions that have not all been made.

The Ibero-American Data Protection Network Model Clauses, the RIPD MCCs, have a different footing. They are recognized by a limited number of Latin American countries. The statement draws the contrast directly with the EU SCCs, which every EU supervisory authority recognizes as legally binding under the GDPR. The EU SCCs themselves date from the Commission’s Implementing Decision (EU) 2021/914, so the comparison is between a clause set with Union-wide standing and two sets whose standing varies by country.

Then come the conditions. The clauses may be used only as the Commission’s FAQs describe, and the board says it will work with other bodies toward more convergence and future interoperability among model clauses. Notice what that last sentence admits. Today the model clauses do not line up neatly with each other. The EDPB expects to spend time making them do so. Until it does, every organization that chooses to use them takes on the job of reconciling the differences itself.

Two Wrong Readings of a Short Statement

Short regulatory statements invite lazy takes, and this one has attracted two.

The first wrong reading treats the statement as a green light. A procurement team sees “other model clauses may be used” and starts swapping clause sets in vendor contracts to match whatever the downstream recipient already signs. That is the fastest way to turn a narrow, conditional permission into a compliance incident. The permission covers onward transfers of data received under the EU SCCs, and it holds only under the Commission’s conditions. A clause set swapped in without checking those conditions is not covered by anything the board said.

The second wrong reading shrugs and moves on. The argument goes that a statement about niche clause sets from Latin America and the Council of Europe cannot matter to a US company. It matters precisely because the statement lands on the party that most US companies occupy in an EU data flow, the importer. If your company receives EU personal data from a customer, a subsidiary, or a research partner under the EU SCCs, you are the first importer. Every downstream disclosure you make sits under the obligations the statement describes.

Block everything and you strangle the vendors your business depends on. Switch clause sets freely and you build exposure faster than you can see it. The resolution is neither. The variable is not which clause set you pick. It is whether you can prove, for any given transfer, which instrument applied, which conditions you checked, and where the data went afterward. Pick the clause set last. Build the proof first.

The First Importer Still Holds the Obligations

The statement focuses on the first importer, and it is specific about what that company keeps. The first importer must continue to comply with its EU SCC obligations, including cooperating with the competent supervisory authority and courts under Clauses 11(e) and 13(b). It must abide by binding decisions under EU or Member State law. And it must remain able to meet those duties in its relationship with the second importer, according to the statement itself.

Say that last duty slowly. Remaining able to meet your obligations toward a recipient you no longer control is not a signature. It is an operational capability. It means that if a supervisory authority asks you to account for a disclosure, you can reach the second importer, you know what they hold, and you can show the authority what happened. A contract clause that promises cooperation is only as good as the facts about who received which records.

The Commission’s own FAQ adds detail. In its answer on onward transfers, the Commission’s FAQ tells importers to pick the module that matches their role under the EU SCCs. The Council of Europe clauses have three modules and the Ibero-American clauses have two. The first importer must still meet every EU SCC safeguard, including purpose limitation, cooperation with the supervisory authority, and compliance with binding decisions. Sensitive data must keep the same level of protection, including the restrictions recorded in Annex I.B of the SCCs.

Here is where it gets uncomfortable for anyone hoping the new clause sets simplify things. The FAQ also addresses further transfers under those clauses. Under Clause 15.1(a) of the Council of Europe clauses and Clause 6.9 of the Ibero-American clauses, further transfers should go only to countries covered by a Commission adequacy decision for that transfer. The Ibero-American clauses add that the second importer must ensure protection equal to both the Ibero-American clauses and the EU SCCs. This is general information, not legal advice, and anyone relying on a specific clause should read the FAQ and the clause text with the data protection officer and Legal. The pattern is still plain. The new flexibility comes with a chain of conditions, and each link needs a record.

Where the Statement Goes Quiet

What a regulatory statement leaves out can matter more than what it includes. This one is explicit about its limits. It does not discuss adequacy decisions, and it does not assess the law of any specific third country or whether that law affects the clauses. The Commission’s FAQ speaks to adequacy for further transfers, as the previous section showed, but the board’s statement does not.

Three gaps follow, and each one lands on the first importer.

The first gap is jurisdictional. A Council of Europe clause set that depends on each party to an unratified convention approving it creates a patchwork. Your counterparty in one country may accept the clauses while a counterparty in another does not. The statement tells you the clauses may be used under the Commission’s conditions. It does not tell you whether the recipient’s own country will honor them.

The second gap is evidentiary. Nothing in the statement tells you how to demonstrate the conditions were met. The board assumes you can. That assumption is the quiet burden. If a supervisory authority asks how you satisfied the conditions for a given onward transfer, “we signed the right clauses” is the start of an answer, not the answer.

The third gap is interoperability. The EDPB says it will work toward more convergence among model clauses. That is a promise of future alignment, and it confirms that alignment is incomplete today. An organization that uses three clause sets across its vendor chain has three sets of definitions, three sets of obligations, and three sets of exit conditions to track.

Regulators are not waiting for tidier rules. DLA Piper’s GDPR fines and data breach survey, published in January 2026, counted roughly 1.2 billion euros in GDPR fines for 2025 and about 7.1 billion euros cumulatively since 2018 through January 10, 2026. Its authors also noted that the Irish Data Protection Commission fined a social media company 530 million euros in April 2025 for breaching the GDPR’s international transfer restrictions, the highest fine of the year. Transfers are not a theoretical corner of the law. They are enforcement territory.

Paper Chain Compliance Is the Failure to Name

I keep coming back to one pattern in how organizations handle transfer compliance, and it has no good name in most programs. Call it paper chain compliance. The contract chain is complete. Every vendor has signed the right clause set. The legal team can produce the agreements on request. And the data chain is a blank, because no one can say which records moved to which recipient on which date through which channel.

Paper chain compliance feels safe because the paperwork is the part lawyers can see. The clause set is a PDF. The vendor list is a spreadsheet. The transfer impact assessment lives in a shared folder. Meanwhile the data moves through email attachments, SFTP drops, shared drives, forms, and APIs that nobody tied back to the register. The first time someone asks “show me what went to the second importer in March,” the legal chain and the operational chain turn out to be two separate documents that were never reconciled.

The statement makes this problem larger in a specific way. A longer menu of clause sets multiplies the number of legal instruments in play. Each instrument carries its own conditions. The more instruments you use, the more the paper chain diverges from the data chain unless something forces them together. That forcing function is not a legal document. It is a system of record for the exchange itself.

Stop asking whether your contracts are in order. Here is the question that matters: for any single onward transfer, can you produce the instrument, the recipient, the data categories, the purpose, and the access record in one sitting? If the answer takes a week and three departments, you have paper chain compliance.

The Vendor in the Middle Already Shows the Stakes

A breach announced in France on November 14, 2026 makes the stakes concrete, even though nothing in the public coverage connects it to international transfers. According to a report by L’Express published by Orange, La Poste announced that Maileva, a subsidiary of its Docaposte unit, suffered a data theft affecting about 22 million people. The attack dates to mid-September, per Le Parisien as cited in that report. The exposed data was first names, last names, and postal addresses of people who received documents that Maileva sent on behalf of business clients.

Look at the structure, not the headline. Maileva is a processor sitting between its clients and their recipients. It says it serves more than 70,000 clients, mainly small and mid-sized companies, and that it notified the affected companies. The French data protection authority, the CNIL, has been informed, a complaint has been filed, and a judicial investigation is ongoing. This is secondary reporting, so treat the details as provisional.

What does a client company do with that notification? It must work out which of its own customers, tenants, patients, or employees were among the 22 million, what each of them was sent, and what it now owes them. That is a chain of custody question. A company that sent documents through a vendor and kept only the contract with that vendor has a very short list of facts. A company that logged what it handed to the vendor, when, and under what authority has a head start.

Notice that this is not an onward transfer story and no one should pretend otherwise. It is a vendor-in-the-middle story, and the vendor in the middle is exactly where first importers end up when they pass data along. The second importer is someone else’s processor, someone else’s cloud, someone else’s mail house. When that party has a bad day, your obligations do not pause. Your evidence either exists or it does not.

What a Regulator or Auditor Will Ask First

Put yourself in the seat of a supervisory authority reviewing an onward transfer by a first importer. The authority is not going to start with your corporate values. It will start with a handful of plain questions, and a prepared team can answer each in minutes.

Which clause set governed the transfer, and which module? The answer should name the instrument, the module that matches the importer’s role, and the version in force at the time of transfer.

Who received the data, in which country, and under which conditions? The record should tie each recipient to the clause set, show where the recipient sits, and show how the conditions in the Commission’s FAQ were checked, including whether the destination is covered by an adequacy decision where the FAQ points to one.

What data categories moved, and did any of them count as sensitive? Under the Commission’s FAQ, sensitive data must keep the same protection, including Annex I.B restrictions. If your register cannot flag sensitive categories, it cannot prove you honored that rule.

What was the purpose, and did it stay within the original purpose? Purpose limitation is one of the safeguards the first importer must keep meeting.

Who accessed the data after it left? Here the answer depends on what the recipient will share, but at minimum you need your own side of the record, showing who sent what and who authorized it.

How will you cooperate if the authority or a court asks? Clauses 11(e) and 13(b) make cooperation a continuing duty. The practical test is whether you can reach the second importer and retrieve the facts within the time the authority sets.

Run a data protection impact assessment alongside new clause choices where your jurisdiction expects one, and attach the record of that assessment to the transfer entry so the file is complete. An audit log that cannot be tied to a specific instrument answers only half of these questions.

How Kiteworks Secure Data Exchange Fits the Evidence Problem

No platform decides which clause set is lawful. That is a legal call, and it belongs to your data protection officer, your general counsel, and the transfer assessments they run. What a platform can do is make the operational chain visible and tie it to the legal one.

Kiteworks secure data exchange governs email, file sharing, managed file transfer, web forms and APIs on one platform, with a single audit log that records who accessed what, when, from where and what they did, instead of a scatter of unrelated tools. That matters here because onward transfers rarely travel through a single channel. A first importer might send a dataset by SFTP, a contract by email, and a customer file through a share link. When those channels live in different tools, the paper chain and the data chain drift apart. When they run through one platform, a single audit trail records who sent what to whom and when.

Access is the second piece. Role-based and attribute-based access controls let an organization limit which users can send which data classes to which recipients, so a sensitive category does not leave through a channel configured for ordinary business files. Content is protected with AES-256 encryption at rest and TLS 1.3 in transit, and geofencing and data residency controls support organizations that need to keep certain data within defined jurisdictions. Customers also hold their own encryption keys, and the audit log feeds security monitoring systems in real time through syslog or Splunk. A built-in GDPR compliance report (an Advanced Reporting license feature) pulls policy settings and monitored operations into one view. These capabilities help demonstrate that the conditions attached to a transfer were applied to data that moves through the platform, though they do not replace the legal analysis and they do not guarantee any regulatory outcome.

The point for a CISO or compliance leader is practical. When the register says “Recipient B, Module 2, adequacy confirmed,” the exchange record should show the files that went to Recipient B, who approved them, and when. That alignment is the difference between a contract chain and a defensible one. It also supports the data sovereignty questions that tend to follow a transfer review, such as where the data sits and who can reach it.

Where to Start This Week

Stop debating what the statement means in the abstract. Start by finding out what you already have.

  1. Inventory your onward transfers. List every recipient that receives EU-origin personal data from you, the country they sit in, and the clause set that covers them. Ask your data protection officer to confirm the list rather than assembling it from vendor contracts alone.
  2. Read the sources with Legal before changing any contract. Pull the statement and the Commission’s FAQ and walk through the conditions with counsel. Do not rewrite a vendor agreement to a new clause set because of a news summary.
  3. Check destinations against the further-transfer language. For each recipient, confirm whether the FAQ’s adequacy language applies to where the data goes next, and record the finding next to the transfer.
  4. Map each recipient to the channel used. Match every entry in the register to the system that moved the data. Retire the side channels, because a transfer through an unlogged channel cannot be proven.
  5. Run an evidence drill. Pick one onward transfer and time how long it takes to produce the clause set, recipient, data categories, and access record. If it takes longer than a working day, your paper chain is ahead of your data chain.
  6. Ask your vendors how they would tell you. Find out how and when each vendor would notify you of a breach, and whether your agreement requires it. You do not want the answer to be your first finding during an incident.

Work through this list with your third-party risk management team and your incident response plan owner in the room. The goal is not a longer binder. It is the ability to answer a regulator in hours, with records that tie each disclosure to the instrument that allowed it. Teams that hold the chain together through supply chain risk management discipline will treat Statement 3/2026 as a useful option. Teams that do not will find that a longer menu mostly gave them more to explain.

To learn more about proving where regulated data went after it left your control, schedule a custom demo today.

Frequently Asked Questions

Yes, but only under the conditions in the European Commission’s FAQs. The EDPB’s Statement 3/2026 says the Council of Europe clauses, along with the Ibero-American clauses, may be used for onward transfers of personal data received under the EU SCCs. The Council of Europe clauses rest on Convention 108+, which is not yet in force, and each party to the convention decides whether to approve them, so your recipient’s country matters. This is general information, not legal advice, so confirm the specifics with your data protection officer and Legal before changing any agreement.

The statement keeps the first importer responsible for continuing to meet its EU SCC obligations. That includes cooperating with the competent supervisory authority and courts under Clauses 11(e) and 13(b), abiding by binding decisions under EU or Member State law, and staying able to meet those duties toward the second importer. Passing data onward under a different clause set does not release the first importer from those duties. Your GDPR compliance program should therefore track each onward transfer as a continuing obligation, not a closed file.

Expect to produce the clause set and module that governed each transfer, the recipient and its country, the data categories and any sensitive data, the purpose, and proof of who accessed the data. The Commission’s FAQ conditions, including purpose limitation and Annex I.B protections for sensitive data, are the safeguards a first importer must keep meeting, so the records should show how each was satisfied. An audit log tied to each transfer lets you supply the access history quickly. Build the register before the request arrives, because retrofitting it under a regulator’s deadline is slow.

The RIPD clauses are recognized by a limited number of Latin American countries, while every EU supervisory authority recognizes the EU SCCs as legally binding under the GDPR. The Commission’s FAQ says importers should pick the module that matches their role, and the Ibero-American clauses have two modules where the Council of Europe clauses have three. For further transfers, the FAQ says the second importer must ensure protection equal to both the RIPD clauses and the EU SCCs. Read the FAQ with Legal, and review the standard contractual clauses basics if your team needs a refresher on how the EU set works.

Start with an inventory of every recipient of EU-origin personal data, the country each sits in, and the clause set that covers it, confirmed by your data protection officer. Then match each recipient to the channel that moves the data, so the register and the exchange record describe the same transfer. Run one evidence drill by timing how long it takes to produce the instrument, the recipient, and the access record for a single transfer. A platform such as Kiteworks secure data exchange can help consolidate the channels and supply the audit trail, while the legal decisions stay with counsel.

Additional Resources

Get started.

It’s easy to start ensuring regulatory compliance and effectively managing risk with Kiteworks. Join the thousands of organizations who are confident in how they exchange private data between people, machines, and systems. Get started today.

Share
Tweet
Share
Explore Kiteworks