Know what’s on your site before a plaintiff’s firm does
A free privacy audit shows which cookies, pixels and trackers are running — and which ones commonly appear in privacy claims.
On November 19, 2025, the European Commission proposed the Digital Omnibus, the most significant set of changes to the GDPR since it took effect. One year later, none of those GDPR changes is law. The Council of the EU agreed its negotiating position in October 2026, but the European Parliament has not yet voted in committee, and negotiations between the institutions have not started. For privacy teams, the anniversary is a good moment to separate what is proposed from what is decided, and to build a 2027 plan that works whichever way the talks go.
TL;DR
- The Digital Omnibus (COM(2025) 837, procedure 2025/0360(COD)) is still a proposal, and every GDPR, cookie and incident reporting change in it is draft text.
- The Council adopted its negotiating mandate on October 21, 2026, while Parliament’s joint ITRE-LIBE committees are still working through more than 1,750 amendments to their June 2026 draft report.
- Talk in Brussels has moved toward a Parliament committee vote around spring 2027, so most organizations should not expect changed GDPR obligations to apply before 2028.
Where the file stands, step by step
The Omnibus follows the EU’s ordinary legislative procedure. That means the Commission proposes, the Parliament and the Council each adopt a position, the three institutions negotiate in trilogues, and both co-legislators formally adopt the final text. Here is how far each step has got, based on the European Parliament’s Legislative Observatory file and its Legislative Train summary:
- Proposal (done). The Commission published the proposal and its staff working document on November 19, 2025.
- Parliament committee work (in progress). The file went jointly to the Industry (ITRE) and Civil Liberties (LIBE) committees. Aura Salla (EPP) and Marina Kaljurand (S&D) were named co-rapporteurs on February 25, 2026. Their draft report came out on June 22, 2026, and members tabled more than 1,750 amendments by the July deadline. The Legal Affairs committee adopted its opinion on November 11, 2026. The procedure is listed as “awaiting committee decision.”
- Council mandate (done). Under the Irish Presidency, member state ambassadors agreed the Council’s negotiating mandate on October 21, 2026, two days after the Irish Presidency presented a compromise text.
- Trilogues (not started). The Council has said it will negotiate once Parliament adopts its position.
- Adoption and application (not started). After a political deal, the text still needs legal-linguistic review, formal votes and publication in the Official Journal before any change applies.
The timetable has slipped. An early-2027 date had often been mentioned for Parliament’s position, but an adviser in the Parliament has since suggested that the committee vote may come around Easter 2027, according to MLex. Even with fast trilogues after that, it is hard to see new GDPR obligations applying before 2028.
What the Commission proposed for the GDPR
The GDPR elements of the proposal are the ones privacy teams follow most closely. According to the Parliament’s summary, the Commission proposed to:
- make the definition of personal data relative, so that pseudonymized data would not be personal data for an entity that has no means to re-identify the person;
- confirm that legitimate interest can be a legal basis for using personal data to develop and operate AI systems and models, subject to conditions;
- move the cookie consent rules from the ePrivacy Directive into the GDPR, add more processing purposes that do not need consent, allow one-click refusal remembered for six months, and recognize preferences set in browsers or operating systems;
- streamline data protection impact assessments and breach reporting, and create a single reporting point for cybersecurity and data incidents.
Consent stays the main rule for accessing information on a user’s device. The proposal adjusts how that rule works. It does not abolish it.
Where the Council landed
The Council’s mandate is noticeably more cautious than the Commission’s text. According to the Parliament’s summary and law firm analyses of the mandate, the Council:
- keeps the current definition of personal data, while adding a narrower provision under which pseudonymized data is not personal data for a recipient that cannot identify the people concerned. We looked at the politics of that change in our analysis of the Council’s deletion of the Commission’s personal data wording;
- keeps cookie rules in the ePrivacy Directive but adds more purposes that do not need consent, such as audience measurement and device security, which should mean fewer banners;
- backs a longer breach notification deadline, reported as 96 hours, plus common notification templates and a single EU list of high-risk processing operations;
- replaces the single EU entry point for incident reporting with a national entry point in each member state and an EU-level information point;
- adds safeguards for processing sensitive data in AI and biometric verification, and a principle-based definition of scientific research.
Where Parliament may go
The co-rapporteurs’ draft report did not propose key amendments on the most contested GDPR points, such as the personal data definition and cookies. It left those for committee negotiations. It did propose that one-to-one biometric identity checks must be necessary and proportionate and use the least intrusive method; that controllers must offer meaningful human review of automated decisions on request; and that the EDPB must draw up DPIA lists within nine months of entry into force. With more than 1,750 amendments on the table, the committee position could still move in several directions. That uncertainty is the main reason for the delay.
The Commission has framed the package as simplification and legal certainty, not as a rollback of data protection. Data protection authorities have accepted parts of it but strongly opposed changing the personal data definition. On that point, the Council has so far sided with the regulators.
What is already law, and what is not
The confusion is understandable, because a separate and smaller package did make it through. The “Digital Omnibus on AI,” which adjusts the timing of the EU AI Act’s high-risk obligations, was adopted in 2026 as Regulation (EU) 2026/1744 and is in force. The data and GDPR omnibus discussed here is a different procedure and is still a proposal. Ten years after it was adopted, the GDPR still applies exactly as written, and supervisory authorities enforce it that way.
How to plan for 2027
A good plan does not bet on the outcome. It keeps today’s programme compliant and makes future changes cheap to adopt.
- Do not relax anything early. Keep 72-hour breach notification, current DPIA triggers and current cookie consent practice. No regulator will accept a draft regulation as a defense.
- Document your pseudonymization. Whatever version of the personal data rule passes, it will turn on whether a recipient can re-identify individuals. Record who holds keys and what contractual and technical controls stop re-identification.
- Write down your AI legitimate interest assessments now. Even under current law, a documented balancing test is the basis for using legitimate interest for AI development. If the Omnibus confirms that basis, the work is already done.
- Keep records that can be reused. Well-kept records of processing activities will make it easier to adapt to new DPIA lists and simpler information duties.
- Treat cookies as a governance task. Whether the rules move into the GDPR or stay in ePrivacy, the expected changes reward organizations that know what each tag does. A sound cookie governance process lets you remove banners for newly exempt purposes quickly and safely.
- Map your incident reporting duties. List every regime that may require notice of the same incident, including GDPR, NIS2 and DORA. Whether reporting ends up going through national entry points or one EU point, that map will be the starting point.
- Use smaller-business relief carefully. If you are an SME, the final text may reduce some obligations. Until then, practical tools such as the Dutch regulator’s free GDPR templates for smaller businesses reduce the burden without waiting for Brussels.
Frequently asked questions
Is the February 2027 date a legal deadline?
No. Dates mentioned for the Omnibus are political targets. Nothing in the procedure requires agreement by a certain date, and none of the institutions has published a binding timetable.
Could the GDPR changes be split from the rest of the package?
That is possible in principle, but nothing official suggests it. The proposal also covers the Data Act, data sharing rules and incident reporting, and negotiators may want to trade points across topics, which tends to keep a package together.
If the Council keeps the current personal data definition, is the question closed?
No. Parliament has not decided, and the final text will come out of trilogues. Recent case law from the Court of Justice on pseudonymized data will also shape how any new wording is read.
Will cookie banners disappear in 2027?
Very unlikely. Even after adoption, the changes would need to apply and, for some features such as browser signals, be supported by technical standards. Plan for banners through 2027.
The bottom line
A year in, the Omnibus has become a normal EU negotiation: slower, more contested and more balanced than its supporters hoped. That is good news for planning. The rules you comply with today will still apply through 2027, and the direction of change is clear enough to prepare for without guessing the final wording.
Put this into practice
Turn privacy guidance into working controls.
Captain Compliance helps teams discover tracking technologies, enforce consent, manage privacy requests and document the evidence behind every decision.