Home Blog The EU Digital Omnibus Explained: GDPR, Cookies and Data Rules

GDPR

The EU Digital Omnibus Explained: GDPR, Cookies and Data Rules

Posted by Kevin Yun|December 13, 2025

The EU Digital Omnibus Explained: GDPR, Cookies and Data Rules

Last updated: 6 November 2026. We update this page as the proposal moves through the EU institutions.

The Digital Omnibus is a European Commission proposal to simplify the EU's digital rulebook in one go. Published on 19 November 2025 as COM(2025) 837, it would amend the GDPR, change the cookie rules in the ePrivacy Directive, merge several data laws into the Data Act and create a common route for reporting cyber and data incidents.

It is not law yet. EU governments agreed the Council's negotiating position on 21 October 2026. The European Parliament has not adopted its position, so the final negotiations between the two have not started. Until a final text is adopted and published, the GDPR and today's cookie rules apply exactly as before.

The AI part of the package was split off, fast-tracked and is already law as Regulation (EU) 2026/1744. Our guide to AI Act amendments covers it. This page covers the rest: what the Commission proposed, how the Council has changed it and what to do in the meantime.

The main changes at a glance

Area Rule today Commission proposal Council position (21 Oct 2026)
Definition of personal data Data is personal if anyone can reasonably identify the person Personal only for an organisation that can identify the person itself Keeps today's definition. Adds a separate rule on pseudonymised data
Breach notification Notify the regulator within 72 hours unless the breach is unlikely to be a risk Notify only high-risk breaches, within 96 hours, through a single EU reporting point High-risk only, 96 hours "where feasible", through national entry points
AI and legitimate interest No specific rule Developing and running AI can rely on legitimate interest, with safeguards Same idea, assessed case by case, with the normal right to object
Abusive access requests Can refuse requests that are "manifestly unfounded or excessive" Can refuse or charge for requests that abuse the right for other purposes Abusive intent counts as excessive, but the controller must prove it
DPIAs Each country has its own list One EU list of when a DPIA is and is not needed, plus a template Kept
Cookies ePrivacy Directive: consent for non-essential cookies Moved into the GDPR. New exemptions, one-click refusal, no re-asking for 6 months, browser signals Stays in the ePrivacy Directive. New exemptions, one-click refusal, no re-asking for 4 months, no browser-signal rule
Incident reporting Separate reports under the GDPR, NIS2, DORA and other laws One EU reporting point run by ENISA National entry points in each country, with an EU-level information point

What the Digital Omnibus would change in the GDPR

The definition of personal data

This is the most contested part of the package. The Commission proposed writing a "relative" approach into Article 4(1): information would only be personal data for an organisation that can identify the person behind it with means it is reasonably likely to use. It builds on the Court of Justice's September 2025 ruling in EDPS v SRB, which held that pseudonymised data shared with a recipient who cannot re-identify anyone may not be personal data for that recipient.

Critics, including the European Data Protection Board (EDPB), the European Data Protection Supervisor (EDPS) and privacy groups, warned that this would take large amounts of tracking and data-broker data outside the GDPR. The Council dropped the change. It keeps the current definition and adds a narrower rule instead: pseudonymised data is not personal data for a third party that cannot identify the person, but it becomes personal data again if passed to someone who can, and it always remains personal data for a processor.

Breach notification

Both the Commission and the Council would cut the number of breach reports. Organisations would only have to notify the regulator of breaches likely to result in a high risk, the same threshold that already applies to telling the people affected. The deadline would move from 72 to 96 hours. The Council adds that late notifications must explain the delay, that every breach must still be documented internally, and that the EDPB should publish lists of when a breach is and is not likely to be high-risk. Our guide to breach notification requirements covers the rules that apply today.

AI training and legitimate interest

The proposal confirms that developing and operating an AI system can rely on legitimate interest as a legal basis, provided the usual balancing test is met and safeguards are in place. The Council keeps this, with a case-by-case assessment and the general right to object under Article 21. Both texts also allow incidental processing of sensitive data that turns up in AI training data, as long as it is removed once found or protected if removal is impossible. The Council's text also includes an exception for biometric identity checks where the person keeps sole control of their biometric data. See our guide to AI training data governance.

Access requests

Organisations would get a clearer basis for dealing with access requests made for purposes other than data protection, such as fishing for evidence in a dispute. The Council's version treats abusive intent as a reason a request can be excessive, but puts the burden of proof on the controller and says repeated requests are not automatically excessive.

Impact assessments and other changes

  • DPIAs: one EU-wide list of processing that does and does not need a DPIA, plus a common template and method, replacing 27 national lists.

  • Automated decisions: the Commission proposed clarifying when decisions based solely on automated processing are allowed under Article 22.

  • Scientific research: a common definition of scientific research, with some exemptions subject to safeguards.

  • Data protection by design: the Council would extend Article 25 duties to processors, not just controllers.

What would change for cookies

The Commission proposed moving the cookie consent rule for personal data out of the ePrivacy Directive and into the GDPR, as new Articles 88a and 88b. The aim is fewer banners and less consent fatigue. Its proposal would:

  • add consent exemptions for low-risk purposes, such as aggregated audience measurement by the site itself and security,

  • require a single-click option to refuse,

  • stop sites asking again for the same purpose for six months after a refusal, and

  • make browsers and other software send machine-readable consent signals that sites must respect.

The Council takes a different route. It keeps the rules in the ePrivacy Directive, which means each country has to write them into national law (the Council text allows 24 months). It keeps the new exemptions and adds one for measuring contextual advertising without profiling. It keeps the single-click refusal but shortens the waiting period before asking again to four months, and it drops the browser-signal requirement.

Either way, nothing changes until the final text is adopted and, under the Council approach, transposed nationally. A compliant cookie consent banner is still required today.

What would change for data laws and incident reporting

  • The data acquis: the Commission proposed repealing the Data Governance Act, the Open Data Directive and the Free Flow of Non-Personal Data Regulation, and moving their useful parts into the Data Act, so there is one main data law instead of four. The Council's position adds stronger protection for trade secrets under the Data Act, after Germany and France pushed for it.

  • Platform-to-business rules: parts of the P2B Regulation would be repealed.

  • Incident reporting: the Commission wants one EU-wide reporting point, built by the EU cybersecurity agency ENISA, for incidents that must be reported under NIS2, DORA, the CER Directive, eIDAS and the GDPR. The Council prefers a national entry point in each country, supported by an EU-level information point.

Where the Digital Omnibus stands

Date Step
19 November 2025 Commission publishes the Digital Omnibus (COM(2025) 837) and the separate Digital Omnibus on AI
10 February 2026 EDPB and EDPS publish a joint opinion: support for parts of the package, serious concerns about the personal data definition
22 June 2026 Parliament co-rapporteurs Aura Salla and Marina Kaljurand present their draft report to the ITRE and LIBE committees
July 2026 MEPs table well over 1,000 amendments. The AI part becomes law as Regulation (EU) 2026/1744
21 October 2026 Council agrees its negotiating position
Next Parliament committee vote and plenary position, then negotiations between Parliament and Council (trilogues)

As of late October 2026, the Parliament's committees had not voted. EU leaders have asked for the simplification packages to be agreed quickly, but because Parliament's position is still open and the GDPR changes are contested, the final text could differ substantially from both the Commission's and the Council's versions. A realistic expectation is that nothing applies before 2027, and the cookie changes later still if they stay in a directive.

Who supports it and who opposes it

Business groups and several member states, Germany in particular, have pushed for simplification and in some cases wanted it to go further. The Commission presents the package as cutting administrative costs while keeping protection standards.

The EDPB and EDPS support parts of the package, such as the higher breach-reporting threshold, but opposed the narrower personal data definition. Privacy groups such as noyb and EDRi argue that several changes, especially on personal data and AI training, weaken the GDPR and mainly benefit large tech companies. The Council's decision to keep the current definition of personal data reflects some of that criticism.

What to do now

  1. Keep complying with the GDPR as it is. The 72-hour breach deadline, the current definition of personal data and today's cookie rules all still apply.

  2. Don't remove cookie banners or consent tools. Even the exemptions will take time to apply, especially if the rules stay in a directive that each country must transpose.

  3. Document your legitimate interest assessments for any AI training or analytics. Under every version of the proposal, a written balancing test is what lets you rely on that basis.

  4. Log unusual access requests. If the abusive-intent test is adopted, you will need evidence to rely on it.

  5. Keep internal breach records for every incident. Both versions keep that duty, even for breaches you no longer have to report.

  6. Follow the separate SME changes. The record-keeping relief for smaller companies is in a different law, Omnibus IV, which is further along. See our guide to GDPR simplification for small businesses.

ComplyDog keeps your cookie consent, records of processing and data subject requests in one place, so you can adapt quickly whichever version of the rules is adopted. For every GDPR-related change in one view, see our overview of GDPR changes and updates.

FAQ

Is the Digital Omnibus law yet?

No. The Council agreed its position on 21 October 2026, but the European Parliament has not, and the two still have to negotiate a final text. Only the separate AI part, Regulation (EU) 2026/1744, has been adopted.

Will the Digital Omnibus get rid of cookie banners?

Not entirely. It would remove the need for consent for some low-risk cookies, such as basic audience measurement and security, and make refusing easier. Consent would still be needed for advertising and tracking cookies.

Does the Digital Omnibus change the 72-hour breach deadline?

Both the Commission and the Council propose 96 hours, for high-risk breaches only. Until the change is adopted, the 72-hour deadline applies.

What is the difference between the Digital Omnibus and Omnibus IV?

They are separate laws. Omnibus IV deals with GDPR record-keeping relief for SMEs and small mid-caps and reached a provisional agreement in June 2026. The Digital Omnibus covers the wider GDPR, cookie, data and incident reporting changes on this page.

When will the Digital Omnibus apply?

There is no date yet. After the Parliament and the Council agree a final text, most GDPR changes would apply directly once it is published and in force, while cookie changes in a directive would need national transposition first.