Understanding the EPOC and EPOC-PR request types is essential for operators subject to the EU e-Evidence Regulation. The EU e-Evidence Regulation (Regulation 2023/1543) represents one of the most significant developments in cross-border digital evidence gathering within the European Union. At its core, the regulation introduces two new orders, the European Production Order and the European Preservation Order, which reach the provider as standardised certificates (EPOC and EPOC-PR) and enable judicial authorities in one EU member state to order data directly from the designated establishment or legal representative of a provider in another Member State, wherever the provider is headquartered. For telecommunications operators and other service providers, understanding the distinction between these two instruments is essential for building compliant response processes.
This article provides a detailed examination of EPOC and EPOC-PR, explaining what each instrument does, who can issue them, what they require from service providers, how they differ from each other, and how they relate to existing lawful interception obligations.
Understanding EPOC and EPOC-PR
The EPOC is an order requiring a service provider to produce specific electronic evidence to the issuing authority. It is the more consequential of the two instruments, as it compels the actual disclosure of data. EPOCs can be issued for subscriber data, for data requested for the sole purpose of identifying the user (such as an IP address with source port and timestamp), for traffic data, and for content data. The authorisation requirements depend on the category. In this article, ‘EPOC’ and ‘EPOC-PR’ are used as shorthand for the orders they transmit.
For subscriber data and user-identification data — which include basic registration information and IP addresses with source port and timestamp — an EPOC can be issued by a judge, a court, an investigating judge, or a prosecutor (or by another competent investigating authority, subject to validation). For traffic data and content data — which include communication metadata such as connection logs and the actual content of communications — an EPOC must be issued or validated by a judge, a court or an investigating judge, reflecting the higher privacy impact of these data categories. For these categories the issuing authority usually notifies the enforcing authority at the same time; outside emergencies, the provider then transmits at the end of the 10-day period unless a ground for refusal is raised.
When a service provider receives an EPOC, it must produce the requested data within ten days, or within eight hours in emergency cases. Any problem with an order (an incomplete form, manifest errors, de facto impossibility, immunities or privileges) is reported on the Annex III form to the issuing authority and, where it was notified, to the enforcing authority of the Member State where the provider’s designated establishment or legal representative is located. Potential conflicts with the law of a third (non-EU) country are raised by the provider through a reasoned objection within 10 days (Article 17). However, the provider cannot simply refuse to comply; the regulation obliges the addressee to execute the order within the deadline unless one of these specific procedures applies.
The EPOC represents a significant departure from traditional Mutual Legal Assistance (MLA) procedures, which require requests to be routed through central authorities and can take months or even years to process. By allowing judicial authorities to address orders directly to service providers, the e-Evidence Regulation dramatically reduces the time required to obtain cross-border digital evidence. For service providers, this means they must be prepared to receive, validate, and respond to EPOCs within tight timescales.
The European Preservation Order (EPOC-PR)
The EPOC-PR is a less intrusive instrument that requires a service provider to preserve specific electronic evidence pending a subsequent production request. Unlike the EPOC, the EPOC-PR does not require the provider to disclose any data — it simply requires the provider to ensure that the specified data is not deleted, altered, or otherwise made unavailable. The EPOC-PR serves as a holding measure that prevents the loss of evidence while the issuing authority prepares a production order or other legal process to obtain the data.
Prosecutors can issue an EPOC-PR for any data category, whereas EPOCs for traffic or content data require a judge, a court or an investigating judge. This broader issuing authority reflects the lower privacy impact of preservation (the data is retained but not disclosed) compared to production (the data is actually disclosed to the requesting authority).
When a service provider receives an EPOC-PR, it must take immediate steps to preserve the specified data. The preservation obligation ends after 60 days. Within that period the issuing authority can extend it once by 30 days if it needs more time to issue a production request. If it confirms (Annex V) that a production request has been issued, the provider must keep preserving the data until it is produced. Without either, the obligation lapses, and the data fall back under the provider’s normal retention rules.
The EPOC-PR is particularly useful in situations where evidence may be at risk of deletion — for example, when a suspect is aware of an investigation and may attempt to destroy evidence, or when the data is subject to automatic deletion under the service provider’s retention policies. By securing the preservation of data quickly, the EPOC-PR prevents the loss of evidence while allowing time for the more rigorous authorisation process required for a production order.
Key Differences Between EPOC and EPOC-PR
The differences between EPOC and EPOC-PR are fundamental and span several dimensions. Purpose is the most basic distinction: an EPOC compels the production (disclosure) of data, while an EPOC-PR compels only the preservation (retention) of data. The privacy impact of an EPOC is significantly higher than that of an EPOC-PR, which is reflected in the different authorisation requirements and procedural safeguards.
Issuing authority requirements differ between the two instruments. EPOCs for traffic and content data must be issued or validated by a judge, a court or an investigating judge, while EPOC-PRs can be issued by prosecutors without judicial validation. This difference reflects the proportionality principle — the more invasive the measure, the higher the level of judicial oversight required.
Response timescales also differ. EPOCs require production within ten days (or eight hours in emergencies), while EPOC-PRs require immediate preservation with the obligation lasting 60 days (extendable by a further 30 days, and until the data is produced once the authority confirms that a production request has been issued). The EPOC-PR is designed to be a rapid, temporary measure, while the EPOC is a definitive order requiring substantive compliance.
The grounds for refusal differ between the two instruments. For EPOCs that require notification, the enforcing authority can refuse on limited grounds (immunities and privileges, a manifest breach of fundamental rights, ne bis in idem, dual criminality). The provider itself can flag immunities or privileges on the Annex III form, file a reasoned objection on third-country law, and object to enforcement only on the grounds in Article 16(4), points (a) to (f). For EPOC-PRs there is no notification and no ground for refusal by the enforcing authority, and no third-country objection procedure. The provider can report problems on the Annex III form and, if enforcement is sought, object on the grounds in Article 16(5).
Implications for Telecommunications Operators
Telecommunications operators are among the most likely recipients of both EPOCs and EPOC-PRs, given the volume of subscriber data, traffic data, and content data they hold. Operators must build processes and systems to handle both types of orders, including the ability to receive and validate incoming orders, identify the relevant data in their systems, preserve data in response to EPOC-PRs, produce data in response to EPOCs, track the status and timelines of each order, and maintain documentation and audit trails for regulatory compliance.
The ten-day response time for EPOCs (and eight hours for emergencies) is particularly demanding. Operators must have processes in place that enable rapid identification and extraction of the requested data, review by qualified legal and compliance personnel, and secure delivery to the requesting authority. Manual processes that rely on individual action may not be sufficient to meet these timescales consistently, and operators should consider investing in automated or semi-automated systems for handling e-Evidence requests.
Relationship to Lawful Interception
It is important to distinguish e-Evidence orders from lawful interception. Lawful interception involves the real-time capture and delivery of communications as they occur. E-Evidence orders, by contrast, relate to stored data — data that has already been generated and is retained by the service provider. An EPOC may request historical traffic data, subscriber records, or stored content, but it does not authorise real-time interception.
However, the two frameworks are complementary. Law enforcement may use e-Evidence orders to obtain historical data about a target’s communications patterns and then use lawful interception to monitor the target’s ongoing communications. Operators must be capable of supporting both frameworks, with appropriate systems and processes for each. The data retention policies of the operator are also relevant, as the availability of historical data depends on how long the operator retains different data categories.
Preparing for e-Evidence Compliance
Operators should begin preparing for e-Evidence compliance by designating a designated establishment (if established in the EU) or appointing a legal representative in a Member State where they offer services (if not) to receive and handle e-Evidence orders. This was due by 18 August 2026. They should map which data they actually hold and for how long under existing law and business need, so they can find it quickly. The e-Evidence Regulation does not require them to keep data longer than they already do. They should also develop internal procedures for receiving, validating, and responding to both EPOCs and EPOC-PRs, train relevant staff on the requirements and timescales, and implement technical systems to support the rapid identification, preservation, and extraction of requested data.
Conclusion
The EPOC and EPOC-PR are the two pillars of the EU e-Evidence framework, each serving a distinct purpose in the cross-border evidence-gathering process. The EPOC compels the production of specified data, while the EPOC-PR requires its preservation. Together, they provide law enforcement with a faster, more direct mechanism for obtaining digital evidence across EU borders, complementing the slower EIO and MLA channels, which remain available. For telecommunications operators, compliance with both instruments requires investment in processes, systems, and trained personnel — but providers that set this up properly gain smoother compliance, reduced regulatory risk, and a constructive relationship with the law enforcement authorities that rely on operator cooperation.
The e-Evidence Regulation also introduces requirements for the establishment of a decentralised IT system to facilitate the transmission of e-Evidence orders between member states and service providers. Since 18 August 2026, orders and responses must go through the EU’s decentralised IT system (built on e-CODEX), where the Member State concerned has connected it. Providers access it through their Member State’s national system, either through the web-based interface or an API based on ETSI TS 104 144. Where the national components are not yet live, orders arrive by secure alternative means, and providers must handle both. The IT system provides a secure, standardised channel for the exchange of orders and responses, and aligning internal processes with its technical requirements avoids compliance challenges as more Member States connect.
Now that the EU e-Evidence Regulation applies, the volume of EPOC and EPOC-PR requests will increase significantly. Operators must ensure their processes can handle EPOC and EPOC-PR requests within the mandated timelines.
Related Articles
For further reading on related topics, explore these articles:
- How e-Evidence and Lawful Interception Differ — and Where They Overlap
- EU E-Evidence Regulation: What Service Providers Must Do Now
- Legal Holds in Telecom: What Operators Must Preserve and for How Long
External Resources
The following external resources provide additional context and official documentation:
