Europe's cookie rules are being renegotiated. In November 2025 the European Commission proposed a package called the Digital Omnibus, which among many other things would move the rules on cookies and similar technologies out of the ePrivacy Directive and into the GDPR itself, with new provisions on how consent is asked for and honored. As of this autumn the proposal is in three-way negotiation between the Commission, the Parliament and the Council, the Council's text drops some of the cookie provisions, and the realistic timeline puts any change into 2027 at the earliest. Nothing has changed yet. But the direction is worth understanding, because it affects what a consent layer should be able to do, and because it turns out to reward the approach we already take.
What the proposal would change
Four ideas in the Commission's text matter for websites.
A single legal home. Cookie consent would be governed by new GDPR articles rather than by the ePrivacy Directive and its national transpositions. For businesses operating in several countries, that would mean one set of rules instead of a patchwork.
Simpler consent, and a rest period. Consent could be given or refused with a single action, and a site that has been refused would not be allowed to ask again for six months. The banner that reappears on every visit would no longer be permitted.
Browser signals with legal force. A preference expressed once in the browser or the operating system, such as a general refusal of tracking, would be binding on every site the person visits. Sites would have to read and honor it automatically.
A longer breach window. Separately, the deadline for notifying a data breach would move from 72 to 96 hours.
The Council's current position removes the cookie-specific articles, so the final shape is genuinely uncertain. Optimistic readings expect adoption late in 2026 with application in 2027; the history of EU digital files suggests slippage.
What it means for a website today
Practically, nothing changes yet. The current rules apply: consent before non-essential cookies, granular choices, easy withdrawal, records of what was consented to. What the proposal does is describe where things are heading, and it points at a set of capabilities a consent layer should have regardless of the final text.
It should be able to honor a signal from the browser, because that is the direction of both regulation and browser makers. It should remember a refusal for a long period and not re-prompt, because that is already good practice and would become law. It should record consent in a form that can be shown later. And it should be adjustable quickly, because when the rules do change, the sites that adapt in a week will be the ones whose consent layer is under their own control.
Why owning the consent layer matters here
We wrote earlier this year about why we ship our own consent component on every Drupal project rather than embedding a third-party banner. The proposal is a good illustration of the reasoning. When the consent layer is a component in your own site, honoring a new browser signal is a change to one component, tested and deployed like any other. A new re-prompt rule is a setting. A new record format is a field. The change lands on every site we run in one release, and it lands when the rule takes effect rather than when a vendor gets around to it.
It also means the consent layer is designed together with everything it governs. Analytics, embedded media, the AI assistant, marketing tags: each loads only when the relevant consent exists, and the logic is in one place. That is the property a regulator, or a customer's compliance team, wants to see, and it is also the property that makes future changes cheap.
Needing less consent in the first place
The quietest way to prepare for stricter consent rules is to depend on consent less. Every year we move more of what a site needs into the category that requires no banner at all. Cookieless analytics measures traffic without identifying anyone. Fonts, scripts and media served from your own infrastructure rather than third parties set no cookies and share no data. Forms, search and personalization built on the site's own session rather than tracking identifiers work for every visitor regardless of their choice. A site built this way asks for consent only for the few things that genuinely need it, which means fewer visitors see a banner, more of those who do say yes, and a change in the rules affects a small surface rather than the whole site.
What we would do when the rules change
If the proposal passes in something like its current form, the work for a site on our platform would be modest and would follow a familiar sequence. Update the consent component to read the machine-readable browser signal and treat it as a decision. Set the re-prompt interval to the legal minimum. Review the consent record to make sure it captures what the new articles require. Update the privacy policy. Test on staging, release, and confirm on every site. We would expect that to be a matter of days from the publication of the final text, with the sites themselves changing behavior on the day the rules apply.
Until then
Follow the negotiations if you find them interesting, but do not redesign anything on the strength of a proposal. Do make sure that your consent layer is something you control, that it already remembers refusals, and that your site depends on consent for as little as possible. Those three things are good practice under today's rules, and they are what will make tomorrow's a small adjustment. If you would like a review of how your site handles consent now, and how ready it would be for the direction things are heading, we are happy to take a look.
