e-Evidence for Online Marketplaces and Cloud Platforms: What You Need to Know

The EU e-Evidence Regulation (EU) 2023/1543 is often discussed as if it were a problem only for telecoms. It is not. Since 18 August 2026, online marketplaces, SaaS platforms, cloud storage and IaaS providers, hosting companies, social networks and collaboration tools can all be in scope, if they let users communicate with each other or if storing data for users is a defining part of the service. If that describes your platform and you offer services to users in the EU, you must be ready to receive and execute European Production Orders (sent as EPOCs) and European Preservation Orders (transmitted as EPOC-PR certificates) — directly from the issuing authority, on tight regulatory deadlines. For production orders covering traffic or content data, the authority in your addressee’s Member State is usually notified and can raise grounds for refusal within 10 days (96 hours in emergencies).

For platforms that have historically dealt with data requests as an occasional, ad-hoc legal matter, this is a step-change. The German government’s implementing bill estimates around 10,000 affected service providers in Germany alone. This guide explains exactly which platforms are affected, what kinds of orders to expect, what the regulation requires of marketplaces and cloud providers in particular, and how to build a compliant operating model now that the Regulation applies.

Which Online Platforms Are in Scope of e-Evidence?

The Regulation deliberately uses broad, technology-neutral definitions to capture the realities of modern online services. The categories most directly relevant to platform operators include:

• Online marketplaces — where they let buyers and sellers communicate with each other (messaging, Q&A, reviews) or store data on users’ behalf; being a marketplace is not enough on its own (Regulation (EU) 2023/1543, Art. 3(3)(c) and recital 27). This can cover B2C marketplaces, peer-to-peer trading platforms, ticketing platforms, gig and on-demand marketplaces, and rental platforms.
• Cloud computing and storage providers — IaaS, PaaS and SaaS providers, object/file storage services, backup and disaster-recovery providers, and managed database services.
• Hosting providers — managed hosting, dedicated servers, VPS, and CDNs and edge platforms where they store customer data.
• Social networks and online communities — including forums, dating apps, professional networks, gaming platforms with social features and creator/streaming platforms.
• Information society services that store user data — collaboration suites, file-sharing tools, project-management platforms, low-code/no-code platforms and AI products that retain prompts or outputs.
• Internet domain and IP numbering services — registries, registrars, privacy/proxy services and regional internet registries.
• Number-independent interpersonal communications — over-the-top messaging, video conferencing and chat features embedded in larger products.

Crucially, the Regulation applies the “substantial connection” test: you are in scope if users in the EU can use your service and you have a substantial connection to the EU: an establishment there, a significant number of EU users, or activities targeted at EU Member States (language, currency, local app store, ads), regardless of where your corporate entity is registered. Mere accessibility of your website is not enough.

What Kind of Data Will Authorities Request?

The Regulation differentiates between four categories of electronic evidence, each with different thresholds and safeguards:

1. Subscriber data — identity, contact details, billing information, the type of service used and date of registration.
2. Data requested for the sole purpose of identifying the user — IP addresses with, where needed, source port and timestamp, requested only to identify a person.
3. Traffic data (other than identification data) — connection logs, transaction metadata, purchase history, device IDs, timestamps and routing information.
4. Content data — listings, messages, uploaded files, photos, documents and other substantive content.

For production orders, subscriber and identification data may be requested for any criminal offence; traffic and content data are reserved for offences punishable in the issuing State by a maximum sentence of at least three years, or for listed offences: non-cash payment fraud, child sexual abuse and attacks against information systems committed online, and terrorist offences. Preservation orders can cover any data category for any criminal offence. Marketplaces and cloud platforms typically hold all four categories — which is why precise data mapping is a foundational compliance task.

Typical e-Evidence Scenarios on Marketplaces and Cloud Platforms

Online marketplace fraud

An investigator pursuing a fraud ring asks a marketplace operator for the seller’s identity, registration IP, transaction history and message threads with victims. Subscriber data and the registration IP address (identification data) can be ordered for any criminal offence. Transaction metadata, message threads and photos are traffic and content data: they need a judge-issued or judge-validated order for an offence carrying a maximum of at least three years (or a listed offence such as online payment fraud), and the enforcing State is usually notified at the same time.

Ransomware and infrastructure abuse on cloud platforms

A prosecutor investigating a ransomware operation asks a cloud provider for control-plane logs, instance metadata, billing identity and storage access logs for a suspect tenant. Where the attack threatens life or critical infrastructure (e.g. a hospital), these can arrive as emergency orders with an 8-hour deadline; otherwise the 10-day deadline applies.

Online child safety investigations

Investigations into child sexual abuse material on social or content platforms typically combine identification orders with content production and preservation orders. These cases benefit from the Regulation’s specific offence list and, where a child is at imminent risk, the 8-hour emergency regime, but also demand the highest standards of integrity and chain of custody.

Account take-over and large-scale phishing

Authorities may issue European Preservation Orders (sent as EPOC-PRs) early in an investigation to lock down logs and account data while a production order is prepared. Platforms must be able to preserve specific datasets for 60 days, extendable by 30, and for as long as needed once the authority confirms that a production request has been issued, without disturbing normal retention or analytics workflows.

Designated Establishment or Legal Representative: Who Receives Your Orders

Every in-scope provider that is active in more than one Member State, or established outside the EU, must name an addressee for orders: EU-established providers designate one of their EU establishments as the designated establishment; providers without an EU establishment appoint a legal representative in a participating Member State (Directive (EU) 2023/1544, Art. 3). New entrants have six months from launch. This addressee is the address of service for every EPOC and EPOC-PR — and is itself liable for compliance.

• Without a designated establishment or legal representative you breach national law implementing Directive (EU) 2023/1544 (in Germany: fines up to EUR 500,000). Failing to execute orders can cost up to 2% of worldwide turnover.
• The designated entity must be registered with the competent national authority (in Germany, the Bundesamt für Justiz; other Member States have equivalents).
• It must have authority — and the operational capability — to act on orders within the regulatory deadlines.
• It must coordinate seamlessly with your global legal, security and engineering teams, often across time zones.

For non-EU platforms, the most efficient solution is often a legal representative service: an EU-based partner appointed under Directive (EU) 2023/1544, jointly liable with you, that runs the 24/7 intake, validates and triages orders, and escalates to your in-house teams the substantive decisions that require platform-side knowledge. SMEs may share a legal representative with other providers.

Operational Requirements for Marketplaces and Cloud Platforms

Compliance is not just a paperwork exercise. To meet 10-day standard and 8-hour emergency deadlines reliably, platforms typically need:

• Secure intake through the national e-Evidence system of the Member State where your addressee sits, either via the ETSI TS 104 144 API or the web interface, with validation of qualified electronic signatures and seals (Art. 21) and issuing-authority credentials.
• Cross-system data discovery capable of locating subscriber, identification, traffic and content data across legacy and modern data stores.
• Standardised delivery through the same channel, in formats the issuing authority can process, with integrity hashes.
• Encrypted delivery to the issuing authority’s X.509 certificate where one is supplied, with verifiable receipt and audit-grade logging; files over 25 MB go by the most appropriate secure alternative means (Art. 19(5)).
• Tamper-evident audit trails covering every action from receipt to delivery — essential for evidentiary integrity and after-the-fact regulatory review.
• 24/7 on-call legal and engineering responders, with rehearsed runbooks for emergency orders.
• Data minimisation controls ensuring you disclose only what was specifically ordered, in line with GDPR Article 5.
• Optional e-Evidence statistics (Art. 28(4)), coordinated with any DSA transparency reporting you already publish.

Building all of this in-house is feasible for the largest platforms, but most marketplaces and cloud providers benefit from a purpose-built solution. The ICS e-Evidence Compliance Platform covers the full lifecycle — from intake through validation, extraction, review and delivery — and integrates with existing identity, logging and storage systems.

Special Considerations for Cloud Service Providers

Cloud providers face several layered challenges that pure-content platforms do not. Orders should normally go to your business customer as data controller. You will be addressed directly only if the controller cannot be identified or approaching it would jeopardise the investigation, and you must inform the customer unless the authority asks you not to (Art. 5(6)-(7)).

• Multi-tenancy and isolation: production must target a single customer’s data without exposing other tenants — both technically and contractually.
• Customer-controlled encryption: where customers hold their own keys (BYOK/HYOK), the provider may genuinely be unable to produce content data, and that limitation must be documented and communicated.
• Shared responsibility: contracts and data-processing agreements should clearly state which party is responsible for receiving and executing law-enforcement orders for which data.
• Notification of customers: commercial customers — particularly enterprise B2B clients — often have contractual rights to be notified of access requests, subject to confidentiality obligations imposed by the issuing authority.
• Cross-region replication: data may sit in multiple Member States or third countries, raising potential conflicts between EU orders and third-country law (the “Article 17 review”), raised as a reasoned objection within 10 days; the mere fact that data is stored outside the EU is not a valid ground.

Special Considerations for Online Marketplaces

• Seller verification data (KYC, business registration, tax IDs) is frequently the highest-value subscriber data for investigators and must be readily extractable.
• Listings and messages are typically content data and require the higher offence-severity threshold to be produced.
• Payment data held by payment service providers is outside the e-Evidence Regulation (financial services are excluded); authorities obtain it through national procedures.
• Cross-border sellers create overlap with consumer-protection, VAT and DSA obligations; e-Evidence should be integrated with — not duplicated by — those programmes.

Penalties for Non-Compliance

Member States must impose effective, proportionate and dissuasive penalties. Member States must allow pecuniary penalties of up to 2% of total worldwide annual turnover for failing to execute orders or protect their confidentiality. Germany, for example, fines up to EUR 500,000, or up to 2% of turnover for providers above EUR 25 million; for hyperscalers and large marketplaces, the headline figures rapidly become material to financial reporting. Beyond fines, repeated failures can trigger court orders, regulatory action and significant reputational damage with enterprise customers, partners and investors.

A 90-Day Catch-Up Plan for Platforms

1. Days 1–15 — Scope and data mapping. Confirm which entities and services are in scope, map subscriber/identification/traffic/content data across systems, identify gaps.
2. Days 15–30 — Legal foundations. Designate an EU establishment or appoint a legal representative, register with the competent authority, update contracts, DPAs, terms and law-enforcement guidelines.
3. Days 30–60 — Technical build. Connect to the national e-Evidence system of the Member State where your addressee sits (ETSI TS 104 144 API or web interface). As of September 2026 only Germany and Ireland can receive orders this way; elsewhere, agree a secure fallback channel with the authorities. Deploy intake/validation/extraction tooling, harden audit logging.
4. Days 60–80 — Operational readiness. Recruit and train the 24/7 response team, finalise runbooks, run emergency tabletop exercises.
5. Days 80–90 — Assurance. Independent compliance audit, board-level sign-off and a go-live rehearsal.

Frequently Asked Questions

For a longer reference, see our dedicated e-Evidence FAQ.

Does e-Evidence apply to small marketplaces and cloud start-ups?

Yes. There is no general SME exemption. If you offer an in-scope service to users in the EU, you are in scope regardless of headcount or revenue. Smaller platforms can scope their compliance proportionately, but the core obligations — designated establishment or legal representative, intake, response capacity — still apply. The exception: a provider established in one Member State and offering services only there need not designate an addressee (Directive (EU) 2023/1544, Art. 1(5)). SMEs may share a legal representative with other providers.

Can we rely on our existing law-enforcement workflow?

Probably not. Most existing workflows assume manual email/portal intake and weeks of turnaround. The e-Evidence Regulation requires intake through the national e-Evidence system (ETSI TS 104 144 API or web interface), hour-level emergency response and tamper-evident audit logs that legacy workflows usually do not provide.

What if the data is held by a sub-processor or another part of our group?

The provider receiving the order is responsible for executing it. Orders are normally addressed to the data controller; a processor is addressed only if the controller cannot be identified or approaching it would jeopardise the investigation, and must then inform the controller unless told not to (Art. 5(6)-(7)). Internal contracts and data-processing arrangements must be aligned so that you can compel a sub-processor or affiliate to deliver data within the regulatory deadlines.

What about end-to-end encrypted services?

The Regulation does not require providers to weaken encryption. If you genuinely cannot access content data because of customer-held keys or true E2E architecture, that limitation can be communicated, but you must still produce subscriber, identification and metadata you do have access to.

How ICS Helps Platforms Get Ready

ICS provides both the technical compliance platform and a legal representative service (with support for EU providers running their own designated establishment) for platforms of all sizes — from fast-growing SaaS scale-ups to global marketplaces and hyperscale cloud providers. Our combined offering covers intake through the national e-Evidence system (ETSI TS 104 144 API or web interface), automated validation, multi-system data extraction, encrypted delivery, tamper-evident audit logging and 24/7 managed operations, all framed within an integrated e-Evidence compliance programme.

Contact ICS today for an independent e-Evidence readiness assessment for your platform, with a clear plan to close any gaps now that the Regulation applies (since 18 August 2026).