Prefer to listen? Click play for AI narration

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.

TopicCommission 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 usedAmended 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 interestExplicit 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 AINew derogation for AI development and operationLimited 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 protectionOnly where the controller can demonstrate abusive intention
Breach notification (Art. 33)Notify only high-risk breaches, within 96 hours, through a single EU entry pointHigh-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
CookiesMoved into the GDPR with machine-readable consent signalsBack 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 permittedRight 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.

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

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.

Share this article

Also read:

⚠️ This article is for informational purposes only and does not constitute legal advice. For complex compliance situations, consult a qualified data protection professional. GDPR and EU AI Act requirements are subject to ongoing regulatory guidance — verify current obligations with your legal adviser.