Why a foreign production order doesn't settle the GDPR question
Your client's European subsidiary has received a discovery request, disclosure order or document demand in an arbitration from a court outside the EU. The other side wants custodian email, Teams chats and shared drives, and expects production in about 60 days. Your task is to comply without putting the EU entity in breach of the GDPR, a national blocking statute or local employment law. GDPR fines can reach 4% of global annual turnover or €20 million, whichever is higher, and producing too little carries its own sanctions risk.
eDiscovery GDPR work is hard because neither legal system gives way to the other. Article 48 GDPR says a judgment or order from a non-EU court or authority doesn't, on its own, justify a transfer unless it rests on an international agreement such as a mutual legal assistance treaty. Foreign courts, particularly in the US, often take the view that a party controlling data must produce it wherever it sits. So you build a defensible record on the EU side: a lawful basis, proportionate processing, a valid transfer route and documented consultation. Then you take that record to the foreign court as the basis for a narrower, staged production.
This guide follows the steps roughly in the order they bite. It also gives typical 2026 cost ranges and a timeline you can show a litigation partner who's planning around short domestic deadlines.
Looking to streamline vendor RFP selection?
Access pre-negotiated tier discounts through our independent institutional network.
Picking a lawful basis that survives scrutiny
Start with roles. The EU entity holding the data is usually the controller for collection and review. Outside counsel and the parent company may be separate controllers. The eDiscovery vendor is a processor and needs an Article 28 data processing agreement that names the hosting region and sub-processors.
For the processing itself, the realistic options are narrow:
- Legal obligation (Article 6(1)(c)) usually doesn't work. Article 6(3) requires the obligation to come from EU or member state law. A foreign discovery rule doesn't qualify.
- Legitimate interests (Article 6(1)(f)) is the standard basis. The interest is defending or pursuing the claim. You need a written legitimate interests assessment that weighs it against custodians' and third parties' rights, and shows how scoping and redaction reduce the impact.
- Consent is a poor fit for employees. The power imbalance makes it hard to show consent was freely given, and it can't cover third parties who appear in the mail.
Expect special-category data (health, union membership, religion) in any large email set. Article 9(2)(f) permits processing necessary to establish, exercise or defend legal claims, but only for what's actually needed. Criminal-offense data under Article 10 depends on national law, so fraud or misconduct investigations need local advice. For large-scale employee review, carry out a data protection impact assessment. Many supervisory authorities treat systematic employee monitoring as high-risk, and the DPIA is the document a regulator will ask for first.
Data minimization: the staged filtering model
European regulators have long expected a staged approach to pre-trial discovery, and foreign courts will often accept it if you raise it early. Cull as much as possible inside the EU, then transfer only the narrowest set the proceeding needs.
- Preserve in place. A legal hold within Microsoft 365 or Google Workspace limits copying and keeps data in its existing region.
- Target custodians and date ranges. Negotiate them with the other side and record the reasons. Ten well-chosen custodians are easier to defend than forty.
- Process and search in the EU. Run deduplication, email threading, search terms and technology-assisted review (TAR) on an EU-hosted instance.
- Review in the EU. Use EU-based reviewers, or remote reviewers working on EU infrastructure under access controls, for first-pass relevance.
- Redact or pseudonymize. Before export, strip irrelevant personal data such as names of uninvolved employees, private messages and HR material. Keep the key in the EU in case the court later needs identities.
- Produce under protection. Ask for a protective order covering confidentiality tiers, filing under seal and return or destruction at the end of the case.
Proportionality-based rules, such as US Federal Rule 26(b)(1), disclosure practice in England and Wales, and the document-production standards common in international arbitration, all give you room to argue for this sequence. Raise it at the first scheduling conference. A court has little patience for the argument once you've missed a deadline.
Transfer mechanisms for sending EU data to a foreign court or counsel
Once the set is culled, each recipient needs a valid transfer route. A production may go to several places, and each gets its own analysis.
- Adequacy. Recipients in countries with an EU adequacy decision, such as the UK, Switzerland, Japan, South Korea, Israel and Canada (commercial organizations only), can receive data without a further mechanism. Check the Commission's current list, since decisions are reviewed and can change.
- EU-US Data Privacy Framework (DPF). It covers only certified US organizations, and many law firms, vendors and courts aren't certified. It has withstood its first court challenge but remains contested, so keep a fallback in place.
- Standard contractual clauses (SCCs). These suit your own US counsel and vendors, paired with a transfer impact assessment. Opposing counsel rarely signs them.
- Article 49(1)(e) derogation. It allows transfers necessary for legal claims. EDPB guidance reads it as covering occasional, necessary transfers, not wholesale exports. It supports a culled production, not a bulk upload of forty custodians' mailboxes.
For most cross-border matters, the workable combination is SCCs or the DPF for your own team and vendors, and Article 49(1)(e) plus a protective order for the production to the court and the other side. Write down which mechanism covers each recipient. That one-page transfer map is what regulators and works councils ask to see.
Looking to streamline vendor RFP selection?
Access pre-negotiated tier discounts through our independent institutional network.
Blocking statutes and the Hague Evidence Convention
Blocking statutes are separate from the GDPR and can apply even to fully anonymized business documents. The best known is France's 1968 law, as amended. It makes it an offense to request or disclose economic, commercial or technical information for use as evidence in foreign proceedings outside treaty channels. French guidance since 2022 expects entities that receive such requests to notify the government's economic security service (SISSE), which can advise and help route the request.
Other regimes to check:
- Switzerland: Articles 271 and 273 of the Criminal Code restrict acts on behalf of foreign authorities and disclosure of business secrets.
- China: The Data Security Law and PIPL require government approval before data is provided to foreign judicial bodies. This matters when the custodian group spans EU and Chinese affiliates.
- Canada: Ontario and Quebec have business records protection statutes.
The formal alternative is a letter of request under the Hague Evidence Convention. Many EU states have made Article 23 reservations limiting pre-trial document discovery, and the process commonly takes many months. US courts generally weigh comity and don't treat the Convention as mandatory, so they often order production despite a blocking statute. Treat the statute as a reason to narrow and sequence the production, not as a shield. Get a written opinion from local counsel to file with the court.
Works councils and employee notice
Litigation teams most often underestimate this step. In Germany, Section 87(1) no. 6 of the Works Constitution Act gives the works council co-determination rights over technical systems capable of monitoring employees. Introducing an eDiscovery platform or searching custodian mailboxes can trigger those rights unless an existing IT framework agreement already covers it. If the company allows private email use, telecommunications secrecy raises further questions. France requires information and consultation of the CSE before tools that process employee data are introduced. The Netherlands and Austria have their own consent and consultation rules.
Look for an existing works agreement first. One with an investigations or litigation clause can cut weeks from the timeline. If there isn't one, offer a matter-specific agreement covering scope, keyword lists, who sees results, a review protocol for private content and deletion dates. That usually moves faster than arguing about whether co-determination applies.
Custodians and affected third parties are also entitled to transparency under Articles 13 and 14. A custodian notice is standard. Article 14(5)(b) allows delaying notice to third parties where it would seriously impair the purpose, but record that decision rather than assuming it.
What EU-hosted eDiscovery typically costs
RelativityOne, Everlaw, Reveal and Microsoft Purview eDiscovery generally offer EU regions, but confirm the specific data center, the support model and where sub-processors sit. "EU hosting" sometimes still means support staff outside the EU can reach the data. In-region work costs more, mostly because of local-language review and privacy counsel rather than hosting.
| Cost line | Typical 2026 range (USD) | What drives it |
|---|---|---|
| Forensic collection | $500-$2,500 per custodian | Remote vs. on-site, mobile devices, chat platforms |
| Processing | $15-$75 per GB ingested | Bundled vs. line-item pricing, OCR, language ID |
| EU hosting | $8-$25 per GB per month | Region, user seats, analytics; often priced at a premium to other regions |
| First-pass review, EU language reviewers | $55-$110 per hour | German, French and Nordic languages cost more than English |
| Redaction and pseudonymization | $0.10-$0.60 per page, or hourly | Automated PII detection vs. manual QC |
| Local privacy and employment counsel | $10,000-$50,000 per matter | LIA, DPIA, transfer assessment, works council negotiation |
These are typical market ranges and vary widely by contract, volume commitments and country. Local pricing differs, so confirm with vendors and get quotes from at least two. Ask whether hosting is billed on ingested or post-culling volume. That one term can swing the budget by five figures.
A realistic timeline, with a worked example
Litigators used to 30- or 60-day production windows need to reset expectations early. Several workstreams can run in parallel, but some can't be compressed.
| Phase | Typical duration | Runs in parallel with |
|---|---|---|
| Scoping, roles, LIA and DPIA | 2-4 weeks | Legal hold, vendor selection |
| Works council consultation | 2-12 weeks | Scoping; collection may wait for it |
| Collection and processing in the EU | 2-4 weeks | Search-term negotiation |
| EU-side review, TAR and redaction | 4-10 weeks | Blocking-statute steps, transfer documentation |
| Protective order and rolling production | 2-6 weeks | Final review batches |
End to end, plan on roughly 10 to 20 weeks. A Hague letter of request takes longer.
Hypothetical example: Say a group's German and French subsidiaries must produce documents in a commercial dispute abroad, from 25 custodians with 1.2 TB collected. Processing at $25/GB comes to about $30,000. Culling brings hosted volume to around 180 GB, and six months of EU hosting at $15/GB per month is about $16,000. Say TAR leaves roughly 1,600 reviewer hours at $80, or $128,000. Add $30,000 for local counsel and $20,000 for collection and redaction. The total is about $225,000 over roughly 16 weeks. In this scenario the works council and the French SISSE notification set the schedule, not the review.
Red flags and a decision rule before you agree to a deadline
Stop and escalate if you see any of these:
- Opposing counsel or your own team proposes exporting full mailboxes to a US or offshore review center "to save time."
- The vendor's EU region still routes support or sub-processing outside the EU, and the contract doesn't say so.
- Nobody has checked for a works agreement in Germany, Austria or the Netherlands.
- The transfer plan relies only on Article 49 for your own vendors and counsel, where SCCs or the DPF should apply.
- A French entity is about to answer a document request without considering the blocking statute.
- The protective order has no return-or-destroy clause or sealing provision.
The decision rule: don't agree to a production date for EU custodians until you've confirmed the lawful basis, the works council position and the transfer route. That should take about two weeks. Then propose a staged schedule to the court with EU-side culling built in. These are general principles, not advice on a specific matter. Have qualified data protection and employment counsel in each affected country sign off before collection starts.