The EU's Digital Omnibus would change the cookie rules, but it is still only a proposal. As of mid-October 2026 the Council has not agreed its negotiating position, Parliament is still working through amendments, and trilogue talks have not started. Until a final text is adopted and comes into force, the current ePrivacy Directive (as implemented in each Member State) and the GDPR apply in full. You still need prior consent for non-essential cookies and an easy way to refuse.
This guide tracks what the Commission proposed on Digital Omnibus cookies, how the Council's drafts have changed it, and what, if anything, you should do now. It reflects the position on 18 October 2026 and will change; it is general information, not legal advice.
What is the Digital Omnibus?
On 19 November 2025 the European Commission published a "digital omnibus" package aimed at simplifying EU digital rules. The data part (procedure 2025/0360(COD)) proposes amendments to the GDPR, the ePrivacy Directive, the Data Act and other laws. A separate AI part, amending the AI Act, has moved on its own faster track. You can follow the file on the European Parliament's Legislative Train page.
It is not the old ePrivacy Regulation. That proposal was withdrawn after years of deadlock, which is partly why the Commission tried a different route.
Digital Omnibus cookies: the Commission's proposal
The Commission proposed moving the rules on storing and accessing personal data on users' devices into the GDPR, through new Articles 88a and 88b. The main elements:
- Consent stays the default for storing or reading personal data on a device.
- A short list of consent exemptions: transmitting a communication, providing a service the user explicitly requested, creating aggregated audience measurement for the provider's own service, and maintaining or restoring security.
- One click refusal: users must be able to refuse with a single click, as easily as they accept.
- Re-prompt limits: no repeated requests while consent remains valid, and a six-month wait after a refusal before asking again for the same purpose.
- Browser consent signals (Article 88b): people could express choices through automated, machine-readable signals, for example set in their browser, and sites would have to respect them. Larger browser providers would have to build support. Media service providers would get a carve-out from honouring these signals.
The wider package also proposed GDPR changes that affect webmasters: a narrower, entity-relative definition of personal data, breach notification to regulators only for high-risk breaches with 96 hours instead of 72, a single EU incident-reporting entry point, and recognition of AI development as a possible legitimate interest.
The Council's 2026 drafts: what has changed
Member States have rewritten much of the cookie section across several presidency compromise texts:
| Issue | Commission (Nov 2025) | Irish Presidency text (2 Oct 2026) |
|---|---|---|
| Where the rules sit | Moved into the GDPR (Articles 88a and 88b) | Stay in Article 5(3) of the ePrivacy Directive; Articles 88a and 88b deleted |
| Consent exemptions | Four narrow purposes | Wider list, including first-party audience measurement, media audience measurement, security and limited measurement of contextual advertising |
| One-click refusal | Yes | Yes: a single-click button or equivalent means |
| Re-prompt after refusal | Six months | Four months |
| Browser consent signals | Yes, with obligations on browsers | Dropped |
The 2 October text was meant to become the Council's negotiating mandate. A vote of EU ambassadors (Coreper) planned for 7 October was postponed to 11 October, and did not go ahead then either, reportedly because of unresolved disagreements over other parts of the package such as Data Act trade secrets. As of 15 October the Council had no mandate and no new vote date had been announced.
Where the European Parliament stands
Parliament's joint ITRE and LIBE committees published a draft report on 22 June 2026, and MEPs tabled more than 1,750 amendments by mid-July. The rapporteurs left the most contested GDPR and ePrivacy points, including the cookie provisions and the personal data definition, to committee negotiations. Parliament has not adopted its position. Civil society groups have lobbied hard against several of the GDPR changes, so expect Parliament's text to differ from the Council's.
ePrivacy reform in 2026: realistic timeline
- Council agrees a mandate (not yet done).
- Parliament committees and plenary adopt Parliament's position.
- Trilogue negotiations produce a compromise.
- Formal adoption by both institutions and publication in the Official Journal.
- Entry into force, followed by any application date or transition period in the final text. If the rules stay in the ePrivacy Directive, Member States would also need to transpose them.
Even on an optimistic path, practical changes to cookie banners are unlikely before 2027, and browser-signal obligations, if they survive at all, would take longer because technical standards would need to be developed.
Don't pre-empt the law. Removing consent for analytics or cutting your banner because "the omnibus says so" would breach today's rules. EU regulators continue to enforce the current ePrivacy and GDPR requirements.
What the changes could mean for affiliate and adult sites
For most publishers, the realistic upside is modest. A first-party audience measurement exemption could let you run basic, aggregated analytics without a banner prompt in the EU, as UK sites can already do. One-click refusal and re-prompt limits would make consent rates more predictable but probably lower, which matters if your revenue depends on cookie-based attribution. Nothing in the drafts relaxes the rules for advertising, retargeting or cross-site tracking, and the sensitive nature of adult browsing data (see special category data on adult sites) means regulators are unlikely to treat this sector leniently whatever the final text says.
What webmasters should do now
- Keep complying with current rules. Prior consent for non-essential cookies, equal accept and reject options, no pre-ticked boxes. Our guide to cookie banner requirements in the EU sets out today's standard.
- Make refusal one click now. Most EU regulators already expect a reject option on the first layer, and both the Commission and Council texts point the same way, so this is a no-regret change.
- Separate your analytics. All versions favour first-party, aggregated audience measurement. If your analytics is configured that way, you will be ready to benefit from any exemption.
- Choose a flexible CMP. You may need to change re-prompt intervals or exemption categories at short notice.
- Remember the UK is different. The UK has already changed its rules through the Data (Use and Access) Act 2025, with analytics exemptions in force since February 2026. If you serve both markets, see UK GDPR vs EU GDPR.
Frequently asked questions
Has the Digital Omnibus abolished cookie banners?
No. It is a proposal still under negotiation. Even if adopted, consent would remain the default for most tracking, and banners would still be needed for advertising and cross-site tracking.
Will affiliate tracking become exempt?
None of the published texts includes a general exemption for affiliate or advertising tracking. The exemptions under discussion focus on security, services the user requested and audience measurement. See do affiliate cookies need consent?.
Will the 72-hour breach deadline change?
The proposal would extend it to 96 hours for high-risk breaches, but until adopted the 72-hour rule applies.
Next steps
Bookmark this page; we will update it as the Council and Parliament move. In the meantime, make sure your current set-up meets today's rules using our pillar guide to GDPR and cookie compliance for affiliate websites.