On 21 October 2026 the Council of the EU agreed its negotiating mandate on the GDPR part of the “Digital Omnibus”, the Commission's simplification package of 19 November 2025 (COM(2025) 837). It is a negotiating position, not law. The European Parliament has not adopted its own position, trilogue talks have not started, and the current GDPR applies in full until a final text is adopted. This article is for general information only and is not legal advice.
Do not confuse this file with the Digital Omnibus on AI, Regulation (EU) 2026/1744. That one is already in force, delays parts of the AI Act and does not amend the GDPR. The proposal discussed here covers the GDPR, the ePrivacy Directive (cookies), NIS2 incident reporting and the Data Act. It still matters for AI projects, because it touches the definition of personal data, AI training, breach notification and cookies.
What the Commission proposed and what the Council would keep
The table compares the Commission's proposal with the Council mandate, based on the law-firm and specialist summaries listed at the end. Everything in the right-hand column is still a negotiating position.
| Topic | Commission proposal (Nov 2025) | Council mandate (21 Oct 2026) |
|---|---|---|
| Personal data definition (Art. 4(1)) | Relative test: data is not personal for an entity that cannot identify the person by means reasonably likely to be used | Amended definition deleted; current definition kept. A new Art. 25a says pseudonymised data is not personal for a third party that cannot identify the person, but a processor still treats it as personal |
| AI and legitimate interest | Explicit rule that AI development and operation may rely on legitimate interest (Art. 88c) | GDPR amendment removed. A recital says developing or operating an AI system is not in itself a legitimate interest and must be assessed case by case |
| Special-category data in AI | New derogation for AI development and operation | Limited to incidental, residual data, and only where erasure is technically impossible or needs disproportionate effort |
| Access requests (Art. 12(5)) | Refuse or charge where the request is for purposes other than data protection | Only where the controller can demonstrate abusive intention |
| Breach notification (Art. 33) | Notify only high-risk breaches, within 96 hours, through a single EU entry point | High-risk threshold kept; EDPB to draw up lists of likely and unlikely high-risk cases; national entry points instead of one EU point. One source reports 96 hours kept |
| Cookies | Moved into the GDPR with machine-readable consent signals | Back in the ePrivacy Directive; closed list of consent exemptions; browser-signal duty dropped; one-click refusal; re-ask allowed after four months, not six |
| Automated decisions (Art. 22) | Reframed as a rule on when automated decisions are permitted | Right not to be subject to them reinstated, with extra safeguards; special-category data only with explicit consent or substantial public interest |
Sources describe some details differently, notably the AI provision (earlier Council drafts used an “Article 88 bis”) and the breach deadline. Confirm against the Council text before acting on any single detail.
Where the process stands and the criticism
The road to the mandate was bumpy. The Irish Presidency, in office since 1 July 2026, circulated two compromise texts between July and September. Coreper, the committee of national ambassadors, could not agree on 7 and 11 October, mainly over trade-secret safeguards in the Data Act, and settled on 21 October.
In Parliament, the ITRE and LIBE committees tabled a draft report on 22 June 2026 and amendments followed on 27 July. No position has been adopted. Trilogues begin only afterwards, and one law-firm briefing does not expect them before March 2027. The “One Europe, One Market” roadmap of 24 April 2026 aims to conclude the simplification packages by the end of 2027.
The EDPB and the EDPS, in Joint Opinion 2/2026 of 10 February 2026, firmly objected to changing the definition of personal data and said legitimate interest for AI was superfluous after EDPB Opinion 28/2024. The Council mandate follows their line on the definition and keeps the Article 22 right, but is looser on cookies and offers no browser-signal duty. Where objections concentrate, the final text is least likely to match the proposal. That is our judgment, not a forecast.
What businesses should do while the text is uncertain
Nothing in the mandate changes the law today, so the best preparation is to strengthen practices that would hold up under any version. These suggestions are our own reading, not legal advice.
- Keep the 72-hour breach procedure. A longer deadline and a high-risk-only duty are proposals, not law. Keep logging every incident internally.
- Write a legitimate-interest assessment for each AI tool that handles personal data. The Council's recital says AI is not automatically a legitimate interest. Current law already allows Article 6(1)(f) and EDPB Opinion 28/2024 describes the test, so a written assessment helps under any outcome.
- Check for special-category data in training and input sets. Have filtering or erasure steps ready, because even the Council's narrow derogation expects residual data to be erased where possible.
- Map pseudonymised data shared with vendors. The proposed Article 25a would turn on who can re-identify the data, so know who holds the keys.
- Do not rebuild cookie banners or privacy notices yet. The cookie text is the part most likely to move. See our cookie banner guide for what already applies.
- Keep your access-request procedure. Record the reasons for any refusal or fee. The Council would allow them only where abuse is demonstrated.
- Watch the calendar. The next milestone is Parliament's position, expected in 2027.
The bottom line
The GDPR is being adjusted, not replaced. Lawfulness, accountability and data subject control remain, and organisations with documented assessments and clear data maps will adapt to whichever text emerges at the least cost. For how the AI debate got here, read our earlier article on AI and legitimate interest. Book a free consultation with GDPRGard → and we will help you map your AI data flows before the rules settle.
Sources
- Addleshaw Goddard: EU Digital Omnibus, the European Council adopts its position (26 Oct 2026)
- IAPP: EU member states finalize Digital Omnibus negotiating stance (22 Oct 2026)
- NicFab Blog: Digital Omnibus, the Council adopts its position
Pages used for this article as of 11 November 2026. All are secondary: a law-firm briefing, a trade-press report and a specialist blog. The Commission proposal, the Council text itself and the EDPB-EDPS opinion were not read directly. Check the status on the Legislative Observatory before relying on this article.
Also read:
- The GDPR Is Being Rewritten for AI: What the Digital Omnibus Means for Your Business
- Inside the EU's Digital Omnibus: what's actually changing for GDPR, and what just stalled
- Is Your “Anonymous” Data Really Anonymous? The EDPB's New Draft Changes the Test