International Reach
UIDDA → § 1782 → Hague, routed honestlyEvidence across a border needs the right vehicle: UIDDA moves subpoenas between US states, 28 U.S.C. § 1782 brings US discovery power to bear for a foreign proceeding, and the Hague Evidence Convention carries a US case's request into a foreign state. Pick the geometry; the router does the rest — and says plainly what it can't promise.
Hague Evidence Convention letter of request (with the Aérospatiale comity fork for parties)
The US court issues a letter of request to the destination state's central authority, which executes it under local law. For a PARTY subject to US jurisdiction, direct discovery under the ordinary rules may still be available — Aérospatiale makes the Convention non-exclusive, with comity deciding the channel.
Hague Evidence Convention (registry); 28 USC 1781 posture [registry]
⚠ Article 23 reservations: many contracting states refuse or restrict PRETRIAL DOCUMENT discovery letters — check the destination state's declarations before drafting.
⚠ Execution runs months, not weeks; translation into the destination language is usually required.
⚠ Non-contracting destination: letters rogatory through diplomatic channels — slower still; plan the case schedule around it.
The Hague channel
The target is a NONPARTY abroad — US subpoena power does not reach them, and the Convention (or letters rogatory) is the channel. Draft to the destination state's declarations.
- 1. Confirm the destination state's status — Contracting state → Convention channel. Non-contracting → letters rogatory via diplomatic channels (slower). Check the current status table and the state's declarations.
- 2. Check the Article 23 reservation FIRST — Many contracting states declared they will not execute letters of request for PRETRIAL DISCOVERY OF DOCUMENTS, or restrict them to enumerated documents. If the destination made that declaration, a broad document request is dead on arrival — draft to the declaration.
- 3. Draft the letter of request — Specific evidence, specific persons, the questions to be put (many states execute by their OWN judge examining the witness), the proceeding's nature, and the requesting court's issuance — this is a court document, not party paper.
- 4. Translate — Into the destination state's language per its declarations — certified translation, both the letter and attachments.
- 5. Transmit to the central authority and calendar reality — The requesting court sends to the destination's central authority; execution runs on local procedure and local timelines — months. Build the case schedule around it and tell the court early.
⚠ This platform does not state any foreign country's current law — destination-state declarations, privilege rules, and data-protection constraints get verified against the current status table and foreign counsel.
⚠ Evidence obtained abroad still has to be ADMISSIBLE here — plan the authentication path (certification, § 1746(1) declarations, testimony) at drafting time, not after execution.
Foreign blocking / privacy law — the categorical checklist
This platform never states a foreign country's current law. These are the categories to clear with qualified foreign counsel, and the practical sequence for each.
| Data-protection regimes | General personal-data laws (GDPR-style) that condition transfer of personal data abroad. | Narrow to what the case needs → pseudonymize/redact where possible → protective order limiting use and dissemination → documented lawful-basis analysis from counsel qualified in that regime. |
| Blocking statutes | Laws that criminalize gathering evidence in-country for foreign proceedings except through approved channels. | Take the Convention/letters-rogatory channel seriously — it exists precisely to thread these; a US order compelling violation invites a comity fight and puts the producing party in a vise the court must weigh. |
| Bank / professional secrecy | Sector secrecy laws (banking, telecom, health) with their own consent and process exceptions. | Consent from the data subject is often the cleanest key; otherwise the sector law's own disclosure process, through foreign counsel. |
| State-secrecy / export-control overlays | National-security-flavored restrictions that can attach to technical data. | Screen the request BEFORE serving it — narrow away from controlled categories; this is a stop-and-verify lane, never a push-through lane. |
Declarations from abroad: 1746(1) — An out-of-country declarant uses the § 1746(1) formula — the declaration under penalty of perjury 'under the laws of the United States of America,' dated and signed. The corpus carries the statute verbatim; the forms arsenal generates the block.
Doctrine anchors (verify before citing)
- Intel Corp. v. Advanced Micro Devices, Inc., 542 U.S. 241 (2004) — The four discretionary § 1782 factors — participant status, the foreign tribunal's receptivity, circumvention of foreign proof restrictions, and undue burden. Every application argues these.
- ZF Automotive US, Inc. v. Luxshare, Ltd., 596 U.S. 619 (2022) — § 1782's 'foreign or international tribunal' means a GOVERNMENTAL or intergovernmental adjudicator — private commercial arbitration abroad does not qualify. The threshold kill-check for any application.
- Société Nationale Industrielle Aérospatiale v. U.S. District Court, 482 U.S. 522 (1987) — The Hague Evidence Convention is not the exclusive route against a foreign PARTY subject to U.S. jurisdiction — comity analysis decides between direct discovery and the Convention channel.
TrialVector is software, not a law firm — legal information, not legal advice; nothing you enter leaves your browser. § 1782 and Hague outputs are counsel-review lanes for self-represented users. Interstate practice lives in the Discovery Plan Builder (UIDDA weapon); the aggression governor is the Escalation Zone.