On this page
- The two proposals
- COM(2025) 836 — AI Act track (ADOPTED)
- COM(2025) 837 — Data/Privacy track (in negotiation)
- Relationship to the ePrivacy Regulation withdrawal
- Cookie consent: proposed Articles 88a and 88b
- Article 88a (as originally proposed)
- Article 88b (as originally proposed)
- Application timelines (as originally proposed)
- Impact on ecommerce operators
- Cookie and analytics tools
- P2B Regulation repeal
- Enforcement harmonisation
- Industry and civil society positions
- Relationship to the Digital Fairness Act
- Key terms
Digital Omnibus
Digital Omnibus
The Digital Omnibus is an EU Commission package of two legislative proposals published on 19 November 2025, designed to simplify and consolidate overlapping EU digital law — with the Commission projecting savings of up to EUR 5 billion by 2029 (Usercentrics, citing Commission materials). The package was framed as a competitiveness initiative in line with the Draghi report on EU competitiveness, and was listed among the EU institutions' 13 legislative priorities for 2026 (IAPP, early 2026).
The two proposals
The Digital Omnibus comprises two legally distinct proposals with separate legislative tracks (MediaLaws.eu tracker, updated 2026-07-24):
| Proposal | Short name | Primary subjects |
|---|---|---|
| COM(2025) 836 | Digital Omnibus on AI | AI Act amendments — high-risk deployment timelines |
| COM(2025) 837 | Digital Omnibus (Data/Privacy) | GDPR, ePrivacy Directive, Data Act, NIS2, CER Directive, Data Governance Act (repeal), P2B Regulation (repeal) |
COM(2025) 836 — AI Act track (ADOPTED)
The AI Act omnibus proposal completed the full legislative cycle and was published in the EU Official Journal on 24 July 2026 as Regulation (EU) 2026/1744 (MediaLaws.eu, 2026-07-24). Key changes (as-of 2026-07-24):
- Annex III stand-alone high-risk AI systems: application date deferred to 2 December 2027
- AI embedded in regulated products: deferred to 2 August 2028
The EU AI Act index entry in this vault noted the Digital Omnibus proposed deferral "not yet law" as of the 2026-06-28 harvest. The MediaLaws.eu tracker (2026-07-24) records Regulation (EU) 2026/1744 as already in force. The AI Act deferrals are now enacted — the vault entry requires updating.
COM(2025) 837 — Data/Privacy track (in negotiation)
The broader proposal, sometimes called the "Data Omnibus," was still in negotiation as of the tracker's July 2026 update. As of that date the published legislative documents were limited to a draft JURI opinion (5 June 2026) and draft Parliament rapporteur reports by Aurora Salla and Marina Kaljurand; no final adoption date has been set (MediaLaws.eu, 2026-07-24).
The EDPB and EDPS issued Joint Opinion 2/2026 on 11 February 2026, welcoming the AI proposal while warning that it may weaken data protection standards for high-risk AI (MediaLaws.eu, 2026-07-24).
Council and Parliament negotiating positions as of July 2026; the status of the Data/Privacy track in October 2026 is unconfirmed from primary sources. Cookie provisions were already removed from the Council's June 2026 compromise text (see below).
Relationship to the ePrivacy Regulation withdrawal
The ePrivacy Regulation (COM/2017/10/FINAL) was formally withdrawn on 6 October 2025 after eight years of Council deadlock (SecurePrivacy, confirmed by OJ). COM(2025) 837 responds to that withdrawal by migrating cookie and device-access consent rules from the ePrivacy Directive into the GDPR as proposed Articles 88a and 88b, rather than creating a new standalone regulation (Taylor Wessing, 2026):
- Under the proposal, a new boundary sentence would be inserted into the Directive to delineate where ePrivacy Directive obligations end and GDPR obligations begin, leaving a potential transitional overlap between national Directive implementations and the new GDPR-based framework (SecurePrivacy, undated-2026)
- The ePrivacy Directive is not formally repealed under the proposal
EDRi describes the ePrivacy Regulation withdrawal as part of a broader deregulatory trend, and argues that the Omnibus replaces it with device-access rules moved into the GDPR that include broad exceptions allowing businesses to read device data without consent (EDRi, undated-2026).
Cookie consent: proposed Articles 88a and 88b
The provisions described below reflect the Commission's November 2025 proposal. The Council's June 2026 compromise text removed the equal-prominence reject button, the six-month moratorium on re-requesting consent, and the cookie consent relocation provisions (Usercentrics). Secondary analysis sources (SecurePrivacy, Taylor Wessing) describe the original proposal terms, not the Council's amended position. Trilogue negotiations had not opened as of July 2026.
Article 88a (as originally proposed)
Proposed Article 88a would move device-access consent rules into the GDPR and permit access without consent for a closed list of four purposes only (Taylor Wessing, 2026):
- Transmitting communications
- Delivering a user-requested service
- Aggregated audience measurement (strictly first-party, internal use only — third-party and cross-service tools likely excluded)
- Security
For all other tracking purposes, consent remains the default (Taylor Wessing, 2026).
Original proposal also included (SecurePrivacy, undated-2026; removed in Council's June 2026 draft per Usercentrics):
- Equal-prominence accept and reject buttons
- Six-month ban on re-requesting consent after a refusal, requiring logged refusals with timestamps and per-purpose suppression
- Browser or OS-level consent signals that controllers would be required to respect
Enforcement would shift to GDPR Data Protection Authorities, with fines up to €20 million or 4% of global annual turnover (SecurePrivacy, undated-2026) — up from current ePrivacy Directive national enforcement (which varies widely by Member State).
Article 88b (as originally proposed)
Proposed Article 88b would make browser-level consent signals (including Global Privacy Control (GPC)) binding on controllers, with a 24-month delay from entry into force. Taylor Wessing expects cookie banners will persist regardless, because Article 13 notice and consent-withdrawal rights would still apply (Taylor Wessing, 2026).
Application timelines (as originally proposed)
| Article | Entry into force delay |
|---|---|
| Article 88a | 6 months |
| Article 88b | 24 months |
Impact on ecommerce operators
Cookie and analytics tools
The audience-measurement exemption under proposed Article 88a appears to exclude cross-service and cross-platform analytics tools — meaning the majority of third-party analytics and advertising tools would still require consent (Taylor Wessing, 2026). Only strictly first-party audience measurement used internally may fall within the exemption (SecurePrivacy, undated-2026).
Cross-site and cross-service behavioural advertising tracking would remain consent-based under proposed Article 88a, offering limited relief for the performance marketing stack that most ecommerce operators depend on (Taylor Wessing, 2026).
These implications are based on analysis of the November 2025 Commission proposal. The Council's June 2026 position removed the cookie provisions; if the final text reinstates them in an amended form, the impact on ecommerce analytics will differ.
P2B Regulation repeal
COM(2025) 837 includes the repeal of the Platform-to-Business Regulation (Regulation (EU) 2019/1150). No source fetched this run analysed the marketplace-seller implications of this repeal; it is a gap for a future research pass.
Enforcement harmonisation
The GDPR Procedural Regulation entered into force on 1 January 2026, harmonising complaint admissibility and setting a 15-month case timeframe, applicable from 2 April 2027. This parallel development applies to ecommerce operators regardless of the Digital Omnibus outcome (IAPP, early 2026).
Industry and civil society positions
| Actor | Position |
|---|---|
| EuroCommerce | June 2026 position paper: frames Omnibus as necessary competitiveness correction |
| BEUC | February 2026 position paper: "Protecting EU data and privacy rights in the Digital Omnibus" — opposed to GDPR relaxations |
| noyb (Max Schrems) | "Digital Omnibus Report V3" — critical analysis of GDPR and ePrivacy proposals |
| EDRi | Characterises Omnibus as "a major rollback of EU digital protections"; warns of broad exceptions and narrowed personal-data definition (EDRi, undated-2026) |
Relationship to the Digital Fairness Act
The Digital Fairness Act (DFA) is a distinct proposal from the Digital Omnibus, covering B2C consumer protection gaps (dark patterns, addictive design, unfair personalisation). Commissioner Michael McGrath announced at the PL&B Dublin conference that he would propose the DFA before the end of 2026 (Privacy Laws & Business, 2026-05-15). There is no formal legislative link between the DFA and the Digital Omnibus, though both are part of the Commission's simplification agenda (Privacy Laws & Business, 2026-05-15). EDRi warned that the deregulatory climate around the Omnibus may spill over into the DFA (EDRi, undated-2026).
Key terms
| Term | Meaning |
|---|---|
| Article 88a | Proposed new GDPR article: moves cookie/device consent from ePrivacy Directive into GDPR with a narrow list of no-consent exemptions |
| Article 88b | Proposed new GDPR article: makes browser-level consent signals binding on controllers after a 24-month grace period |
| COM(2025) 836 | Digital Omnibus on AI — enacted as Regulation (EU) 2026/1744 (as-of 2026-07-24) |
| COM(2025) 837 | The broader Data/Privacy Omnibus — in negotiation as of July 2026 |
| Audience-measurement exemption | The Article 88a carve-out for analytics; appears to exclude cross-service and third-party tools |
| P2B Regulation | Regulation (EU) 2019/1150 on platform-to-business relations — proposed for repeal under COM(2025) 837 |
| Trilogue | Negotiation between Parliament, Council, and Commission; not yet opened for COM(2025) 837 as of July 2026 |
| GDPR Procedural Regulation | Entered into force 1 Jan 2026; harmonises cross-border DPA complaint handling from 2 April 2027 |