Digital Omnibus: What Applies to GDPR and Cookies and What Is Only a Draft
The EU Council has set its Digital Omnibus position, but it is not law. What still applies today to GDPR, cookies and data breaches.
Inhalt

On 21 October 2026, the Council of the EU adopted its negotiating mandate on the data part of the Digital Omnibus. That is not a law. Until an amending act enters into force, the GDPR and the ePrivacy rules apply unchanged, including the 72 hours for data breaches and your existing cookie banner. This guide puts the interim status into context (as of 30 October 2026) and shows what you should and should not do now.
Where the procedure stands
The European Commission presented the Digital Omnibus on 19 November 2025 in two separate proposals. The part on artificial intelligence has since been concluded separately. The data part, which concerns the GDPR, the ePrivacy Directive and the Data Act, continues in the ordinary legislative procedure.
The Committee of Permanent Representatives set the Council's position on 21 October 2026. The negotiating mandate is public. According to media reports, Germany voted against. Next, the European Parliament has to set its position, and only then do the trilogue negotiations begin. The law firm Osborne Clarke expects that not before February 2027. Entry into force this year is therefore ruled out, and the content can still change during the negotiations.
What the Council proposes
The overview below compares current law with the Council's proposal. The right-hand column is a negotiating position, not a rule.
| Topic | Current law | Council proposal |
|---|---|---|
| Reporting a data breach | Art. 33 GDPR: within 72 hours, unless a risk is unlikely | Only where a high risk is likely, within 96 hours, via a national reporting point |
| Where cookie rules sit | Art. 5(3) of the ePrivacy Directive | They stay there (the Commission wanted to move parts into the GDPR) |
| Purposes without consent | Only transmission and strictly necessary access | Catalogue is extended, including anonymous audience measurement |
| Waiting time after a refusal | No fixed period in the legal text | At least four months before asking again for the same purpose |
| Browser signals against banners | No obligation | Deleted from the Commission proposal |
| AI training | Legitimate interest under Art. 6(1)(f) GDPR, assessed case by case | Clarification that point (f) is possible, case-by-case assessment remains |
| Personal data | Definition in Art. 4(1) GDPR | Definition stays, new special rule for third parties without means of identification |
The summary of the Council position relies on the analysis by Osborne Clarke, which reviewed the mandate text. The original text is in the linked Council document.
Until an amending act is published and its transition periods have expired, current law applies. A draft is no reason to remove cookie banners or loosen breach processes.
What you should do now
This is an assessment from a software development perspective. Legally binding advice comes from data protection officers and lawyers.
- Leave the cookie banner and consent management unchanged. Neither the four-month waiting time nor the extended exceptions are in force.
- Keep the data breach reporting chain at 72 hours. If you maintain software, keep the deadline and the risk threshold as parameters in your process description, so that a later change can be adopted without a rebuild.
- Document the legal basis for AI features. Even under the Council proposal, legitimate interest remains a case-by-case assessment.
- Integrate tracking cleanly. Scripts that require consent only load after the user agrees. This is a typical topic in web applications.
- Keep reporting obligations in view. In parallel, the Cyber Resilience Act brings its own reporting duties for software. Both regimes should feed into a shared reporting chain.
- Watch the developments. The next visible step is the Parliament's position.
If you want to prioritize these measures, you can clarify them as part of IT consulting.
Conclusion
The Digital Omnibus can change the GDPR and cookie rules noticeably, but today it is a negotiating position. Plan flexibly, change nothing on suspicion and reassess once Parliament has set its position. The exact overview of what applies and what is only proposed is in the table above.
Frequently asked questions
Author of this article
This article is for general information only and does not replace individual legal, tax, or business advice. Prices, timelines, and assessments are non-binding estimates provided without guarantee.
Keep reading
View all articles →
Data Act: No More Switching Fees With Your Cloud Provider From 2027

Digital personnel files in 2027: what is really mandatory

Replacing Excel Lists: When a Custom Solution Pays Off

Ubuntu kernel and Node.js: two critical updates to check this week

AI Chatbot on Your Website: What Article 50 Requires Since 2 August 2026

AI Search: How Your Company Website Gets Named in AI Answers

Accessible Websites under the BFSG: What Market Surveillance Checks
