Cross-border digital evidence exchange between courts used to move at the speed of paper and diplomacy. A request went through central authorities, was translated, was executed under a foreign legal framework, and came back months later if it came back at all.
That is changing in the European Union, and the change is operational rather than doctrinal. Regulation (EU) 2023/1543, the E-Evidence Regulation, entered into force in 2023 and applies from 18 August 2026, with the accompanying Directive having applied from 18 February 2026. Alongside it, Regulation (EU) 2022/850 established e-CODEX as a decentralized infrastructure for secure cross-border exchange of judicial data, and Regulation (EU) 2023/2844 makes electronic communication the default in cross-border civil, commercial, and criminal matters.
For a court, cross-border digital evidence exchange has moved from a treaty abstraction to something arriving in an inbox. This article covers what that means in practice. It assumes familiarity with the guide to court digital evidence management.
One distinction worth drawing at the outset, because the two are frequently discussed as one thing. Cross-border evidence sharing between investigating agencies is a cooperation and logistics problem: getting material from one agency to another intact and admissible. What follows is about judicial instruments, where a court issues or receives an order that has legal effect in another state, on a deadline, whether or not anyone finds it convenient.
What the E-Evidence Regulation actually introduces
Two instruments matter most to a court.
The European Production Order compels a service provider to produce specified electronic evidence. The European Preservation Order compels it to preserve that evidence pending a production request. Both can be issued by a judicial authority in one member state and take effect on a provider established or represented in another.
The scope of who receives these is broad: electronic communications service providers, domain name and IP address registration services, and information society services including social media, cloud, hosting, and marketplaces. Non-EU providers offering services to users in the Union are within scope where they have a designated representative.
The practical consequence for a court is that orders it issues now have direct effect abroad without a central authority acting as intermediary, and orders issued elsewhere may require it to act. Both directions create work.
Receiving and acting on an incoming request
The operational questions are unglamorous and specific.
Verification comes first. Who confirms that an incoming order is genuine, properly issued, and within scope. That is a role rather than a step, and courts that have not assigned it will assign it in a hurry the first time.
Timelines are next. These instruments carry deadlines, and a court whose internal routing takes a week has consumed a meaningful share of the available time before anyone looks at the substance.
Then execution and record. What the court does, when, and how that is evidenced. Cross-border activity attracts scrutiny, and the audit trail needs to show the full sequence rather than the outcome.
None of this is technically hard. All of it fails when it has not been assigned to anyone before the first request arrives.
e-CODEX and what decentralized exchange means for your systems
e-CODEX is not a central database. It is infrastructure allowing national systems to exchange documents, legal forms, and evidence securely with each other, which is a deliberate design choice: member states keep their data in their own systems.
For a court's own architecture, the implication is that the exchange happens at a defined interface rather than by giving a foreign authority access to your platform. Evidence stays where it is until it is transmitted, and transmission is a recorded event.
That design also means the burden falls on national systems being able to package and receive evidence in the expected form. A court whose evidence lives in a system with no clean export path will find cross-border cooperation harder than one whose export is routine, which connects this directly to portability.
Format, language, and metadata across a border
Evidence that crosses a jurisdiction encounters three predictable problems.
Format, because a proprietary CCTV wrapper that opens fine domestically may not open at the receiving end. Transmitting in widely supported formats, or including the means to open what you send, avoids an exchange that technically succeeded and practically failed.
Language, because metadata, file names, and any accompanying description may be in a language the receiving court does not work in. Machine translation handles the description; it does not handle a naming convention that encodes meaning in an abbreviation only your registry understands.
Metadata, because what a receiving court needs to know about provenance may not be what your system records. The chain of custody has to survive the crossing, which means the audit trail travels with the evidence rather than remaining in the originating platform.
Where this collides with national rules
Cross-border cooperation does not suspend domestic obligations, and the interactions are where courts get caught.
Retention rules still apply to material received from abroad, and they may differ from the retention applied where it originated. Data protection obligations apply to personal data in transmitted evidence, which for European courts means the General Data Protection Regulation (GDPR) analysis has to be done rather than assumed. Sealing and protective orders made domestically have no automatic effect abroad, and vice versa.
For courts publishing decisions that reference cross-border material, the anonymization duty applies to the published version regardless of where the underlying evidence came from, which is covered in anonymizing judgments before publication.
Where the record may lawfully reside is a related and larger question, addressed in data sovereignty and deployment choices for national judiciaries.
How VIDIZMO DEMS supports cross-border work
Nothing in a product removes the legal analysis. What a system can do is make the mechanics reliable.
The relevant capabilities are broad format support at ingestion, including proprietary CCTV wrappers, so material received from a foreign system opens rather than requiring a specialist; hash-based integrity verification, so a receiving authority can confirm nothing changed in transit; exportable tamper-resistant audit logs, so the custody record travels with the evidence; and time-limited, monitored access links for controlled transmission rather than sending copies that then exist indefinitely elsewhere.
Deployment inside national infrastructure, including air-gapped configurations, matters here because cross-border cooperation frequently coexists with a prohibition on the underlying record leaving the country.
Connecting the platform to the national access point
e-CODEX moves judicial forms and evidence between authorised access points. Under Regulation (EU) 2022/850 those are operated by Union bodies or by authorised member state entities, so the court or ministry holds that role and no vendor can hold it on their behalf. What a vendor can do is build and run everything behind it.
That integration is buildable. AI Intelligence Hub workflows are graphs with trigger and integration nodes over REST and webhook interfaces, so a court's access point can hand an incoming message straight into an automated intake: verify the submission, hash and scan what arrived, check format and completeness, translate the accompanying description, index it for retrieval, and route it to the person who decides what happens next. Outbound, the same mechanism assembles the requested material, confirms integrity, attaches the audit record, and hands a package to the access point for transmission. It is the intake pattern described in automated court docketing, pointed at a foreign order rather than a domestic filing.
Two things make this workable in Europe specifically. Because e-CODEX is decentralized, the record never leaves national control, and the platform holding it can be deployed in a permitted cloud region, in a national private cloud, on-premises, or fully air-gapped. And the workflow prepares rather than decides: every gate requiring a legal judgment stays with a person, which is what keeps an assisting system outside the high-risk classification the EU AI Act applies to systems used by a judicial authority, or on their behalf, to interpret facts and law.
What to do before the first order arrives
Assign the verification role. Map the internal routing and time it. Test that your evidence exports in a form another jurisdiction can open, including the audit trail. And decide, in advance, how received foreign material is retained and under what rule.
The application date has arrived. The courts that will handle these instruments well are the ones that treated the preparation as operational rather than legal.
Explore DEMS to review export, integrity verification, and controlled transmission against your cooperation requirements.
August 18, 2026
