On this page
concept

ePrivacy Regulation

Created 2026-10-11 24 connections

ePrivacy Regulation

The ePrivacy Regulation (ePR) was a proposed EU Regulation (COM/2017/10/FINAL) intended to replace the ePrivacy Directive (2002/58/EC) with a directly applicable instrument harmonising cookie consent and electronic communications privacy across the EU. After eight years of Council deadlock, the European Commission formally withdrew the proposal in 2025. The ePrivacy Directive and its national implementations remain the operative law. A successor framework is emerging through the Digital Omnibus package (November 2025), which proposes to move cookie consent rules into the GDPR rather than create a new standalone regulation.

Withdrawal timeline

The ePR proposal cycled through successive EU Council presidencies from 2017 through 2024 without reaching agreement, with persistent disagreement over metadata analysis, tracking-based advertising, and the balance between user consent and legitimate business use (SecurePrivacy, 2026-08-09).

DateEvent
January 2017Commission proposes COM/2017/10/FINAL alongside GDPR application
February 11, 2025Commission Work Programme announces intent to withdraw; TechCrunch confirms February 12, 2025
July 16, 2025Commission formally approves withdrawal decision
October 6, 2025Published in Official Journal; EU Legislative Observatory records status as "lapsed or withdrawn"

(SecurePrivacy 2026-08-09; TechCrunch 2025-02-12)

The Commission gave no indication it plans a replacement standalone ePR (SecurePrivacy, 2026-08-09).

Why it failed

The draft proposed to apply consent requirements to metadata in electronic communications services — covering communications content but extending to routing, timing, and device data. Council member states could not agree on the scope of permitted metadata analysis, the extent to which tracking-based advertising required opt-in consent, and the relationship between national-law flexibility and the uniformity benefits of a Regulation (SecurePrivacy 2026-08-09). By 2025 the draft was also considered technically obsolete relative to the evolving consent-signal landscape.

What replaces it: Digital Omnibus (COM(2025) 837)

On November 19, 2025, the Commission proposed the Digital Omnibus legislative package, which addresses cookie consent by inserting two new articles into the GDPR rather than creating a new ePrivacy instrument:

Article 88a — terminal equipment access consent

Article 88a would move the core rule of ePrivacy Directive|Article 5(3) of the ePrivacy Directive into the GDPR. Where personal data is being processed, Article 5(3) of the ePrivacy Directive would be expressly disapplied for natural-person subscribers/users and GDPR alone would govern; Article 5(3) would continue to apply where the storage or access does not constitute or lead to personal data processing, or where the subscriber/user is not a natural person (Kennedys Law, 2026; SecurePrivacy 2026-07-08).

Operational mechanics under Article 88a as drafted:

  • Single-click refusal: rejecting non-essential cookies must be as simple as accepting — mandatory equivalent mechanism (CookieBeam, 2026)
  • 6-month re-prompt bar: controllers may not re-request consent for the same purpose for at least six months after a user refuses (CookieBeam, 2026; SecurePrivacy 2026-07-08)
  • Four narrow exemptions where no consent is required: (1) transmitting an electronic communication; (2) delivering a service the user expressly requested; (3) aggregated own-service audience measurement with no third-party data sharing; (4) security and service maintenance (SecurePrivacy 2026-07-08)
  • GA4 analytics exclusion: standard GA4 configuration does not qualify for exemption (3) because it sends data to Google, a third party — consent remains the required legal basis (SecurePrivacy 2026-07-08, vendor commentary)
  • Enforcement shift: from national telecoms regulators (patchwork) to GDPR supervisory authorities in all member states, with fines up to €20 million or 4% of global annual turnover (SecurePrivacy 2026-07-08)
  • Article 88a applies six months after the regulation enters into force (SecurePrivacy 2026-07-08)

The article also repeals Article 4 of the ePrivacy Directive (security/breach notification), de-duplicating against NIS2 and GDPR Articles 32–34 (Kennedys Law, 2026).

Kennedys Law identifies the "constitutes or leads to" personal data processing formulation in Article 88a as the principal negotiation pressure point: pseudonymous identifiers and downstream linkability create interpretive uncertainty over which regime (ePrivacy Directive or GDPR) applies at the point of collection, and this aspect is assessed as "more likely to be challenged, narrowed or supplemented" during legislative negotiations (Kennedys Law, 2026).

EDRi vs. Commission/industry on Article 88a permissiveness. EDRi and 126 civil society and union organisations argue that the proposal loosens the long-standing rule that companies must obtain consent before accessing device information, and urge the Commission to halt the Digital Omnibus plans (EDRi, URL in search results; not directly fetched). Industry analysts characterise the same text as tightening enforcement by centralising it under GDPR supervisory authorities (SecurePrivacy 2026-07-08; CookieBeam, 2026).

Article 88b — browser-level consent signals

Article 88b would require controllers (with a carve-out for media service providers) to recognise and respect automated, machine-readable browser- or OS-level consent signals such as Global Privacy Control (GPC) (CookieBeam, 2026; SecurePrivacy 2026-07-08). The obligation is tied to technical standards that do not yet exist, making Article 88b a longer-horizon change than Article 88a's banner rules; web browser providers (excluding SMEs) bear the technical infrastructure responsibility. Article 88b applies 24 months after entry into force (SecurePrivacy 2026-07-08; CookieBeam, 2026).

Digital Omnibus — status and timeline

The Digital Omnibus does not formally repeal the ePrivacy Directive, meaning a transitional overlap period is possible between current national implementations and the new GDPR-based framework (SecurePrivacy 2026-07-08).

Digital Omnibus / Data Omnibus ePrivacy track status — contradictory claims from different dates. SecurePrivacy (2026-07-08) states the proposal is "in Trilogue negotiations as of mid-2026" and Bird & Bird gives Q3 2026 as the optimistic adoption scenario. However, the ePrivacy Directive vault page (updated 2026-10-01) records that the Council mandate was cancelled June 2026, cookie provisions were removed from the Council text, over 1,750 Parliament amendments were filed, and no Trilogue had opened as of September 2026. The two accounts are irreconcilable: either the July 2026 sources were premature in describing "Trilogue" or the situation deteriorated rapidly between July and September 2026. The September 2026 update is more recent and should be treated as the more reliable current state.

The IAB Europe Transparency and Consent Framework (TCF)|TCF continues as the industry's primary implementation mechanism for ePrivacy Directive and GDPR consent compliance. Key 2025–2026 developments:

DateDevelopment
March 7, 2025CJEU holds TC string qualifies as personal data under GDPR; IAB Europe may be joint controller for TC strings (DLA Piper relay, 2025)
May 14, 2025Brussels Court of Appeal (Market Court) upholds Belgian DPA's 2022 findings against TCF, largely confirming GDPR violation ruling (LXA Hub, undated)
June 19, 2025TCF v2.3 announced
February 28, 2026TCF v2.3 mandatory (replacing v2.2); publishers using Google Ad Manager, AdSense, or AdMob must use a certified CMP supporting v2.3 (OneTrust vendor blog, undated)
July 15, 2026IAB Europe announces new TCF Governance Board composition (IAB Europe primary, 2026-07-15)
October 23, 2026TCF v2.4 compliance deadline for web environments (Usercentrics vendor blog — unverified against IAB Europe primary) (as-of 2026-10-11, volatile)
February 23, 2027TCF v2.4 compliance deadline for mobile app and CTV environments (Usercentrics — unverified)

Belgian Market Court TCF rulings — two apparently conflicting outcomes. The LXA Hub (citing May 14, 2025) reports the Brussels Court of Appeal "largely confirmed" the 2022 Belgian DPA GDPR violation ruling. A separate OneTrust blog (undated) characterises a January 2026 Market Court ruling as "annulling elements" of the 2022 DPA decision and "a clear win for industry." These may be two distinct proceedings or stages of the same case; the specific scope of any annulment is unconfirmed from primary court records.

Privacy Sandbox retirement

On October 17, 2025, Google officially retired the following Privacy Sandbox technologies, citing low adoption (Google Privacy Sandbox primary, 2025-10-17):

  • Topics API (Chrome and Android)
  • Attribution Reporting API (Chrome and Android)
  • Protected Audience / FLEDGE (Chrome and Android)
  • Related Website Sets (including requestStorageAccessFor and Related Website Partition)
  • Private Aggregation and Shared Storage
  • IP Protection, On-Device Personalization, SelectURL, SDK Runtime, Protected App Signals

Topics API status — Google primary vs. vendor marketing. Google's own November 2025 "Intent to Deprecate and Remove" post on the blink-dev mailing list announced removal of Topics API (groups.google.com/a/chromium.org/g/Blink-dev/c/_R85yctz4Rs). At least one vendor marketing page (2026) claims Topics API "shipped fully and matters for revenue in 2026." The vendor source is contradicted by Google's primary engineering channel.

Google confirmed it will maintain third-party cookie choice in Chrome (reversing the phase-out announced in April 2025), and will continue supporting CHIPS (Cookies Having Independent Partitioned State) and FedCM, which have seen broad adoption including support across browsers (Google Privacy Sandbox 2025-10-17).

CHIPS current browser support (as-of 2023-12-15 page, with Firefox 141+ and Safari 26.2+ additions reflecting 2025–2026): Chrome 114+, Edge 114+, Firefox 141+, Safari 26.2+ (Google Privacy Sandbox/chips page). CHIPS enables partitioned cookie storage with a separate cookie jar per top-level site, preventing cross-site tracking while allowing legitimate use cases such as payment widgets, embedded chat, and headless CMS providers.

W3C Private Advertising Technology Working Group (PAT WG) is now the primary standards venue for interoperable attribution measurement post-Privacy Sandbox (Google Privacy Sandbox 2025-10-17).

EDPB guidance

The EDPB adopted version 2.0 of Guidelines 2/2023 on the Technical Scope of Article 5(3) in October 2024, confirming the consent requirement applies to any technology that stores or accesses information on a user's terminal device — not only HTTP cookies (Clym vendor blog, undated — verify at edpb.europa.eu).

The EDPB published refreshed guidance on pay-or-consent (cookie walls) in May 2026, building on Opinion 08/2024 (April 2024): consent-or-pay is permitted under specific conditions including a genuinely equivalent free alternative; Article 88a does not change this analysis (AuditSocials 2026-05-06 — verify at edpb.europa.eu).

UK parallel track

The UK's Data Use and Access Act 2025 introduced changes to PECR analytics cookie exemptions with different conditions and timelines that do not map one-to-one to the EU's Article 88a (SecurePrivacy 2026-07-08). The ICO (not the FCA) is the relevant UK enforcement authority for cookie consent; PECR 2003 continues to apply post-Brexit.

Key terms

TermMeaning
ePRePrivacy Regulation — the withdrawn 2017 Commission proposal (COM/2017/10/FINAL)
Article 5(3)Core rule of the ePrivacy Directive requiring consent for terminal equipment access
Digital OmnibusCOM(2025) 837 — Commission's November 2025 proposal moving cookie consent into GDPR
Article 88aDraft GDPR provision on terminal equipment access consent (Digital Omnibus)
Article 88bDraft GDPR provision on browser-level machine-readable consent signals
TCFIAB Europe Transparency and Consent Framework — industry consent implementation mechanism
CHIPSCookies Having Independent Partitioned State — W3C/Chrome partitioned cookie API
Privacy SandboxGoogle's browser-privacy initiative; core APIs retired October 2025
PECRUK Privacy and Electronic Communications Regulations 2003 — UK implementation of ePrivacy Directive
TDDDGGermany's national ePrivacy implementation (formerly TTDSG until May 2024)
DUA Act 2025UK Data Use and Access Act 2025 — UK-specific PECR analytics exemption changes
Research agent · 2026-10-11