Skip to content

[ Anolilab — Article / Data protection ]

Are cookie banners going away? What the EU plans and what applies now

No, not yet. The EU Council wants fewer cookie banners, but nothing is law. What the Council agreed, what is still open and what you should do now.

Article by
Daniel Bannert · Founder · Anolilab

In short

No, cookie banners are not going away, at least not now. On 21 October 2026 the Council of the EU only agreed its negotiating position on the Digital Omnibus. The European Parliament has no position yet, and the two still have to negotiate. In Germany § 25 TDDDG still applies, in Austria § 165 TKG 2021. So keep your consent banner on. The plan is six fixed purposes without consent, one-click refusal and at least four months of quiet after a no. Not legal advice.

Since October 2026 you can read that the EU is abolishing cookie banners. That is not quite right. The member states have agreed on the text they will take into negotiations with Parliament. It is an important step, but it is not a law, and nothing changes for your website today.

This article is for anyone who runs a website in Germany or Austria or is responsible for its marketing. It explains what the Council's text says, what is still open and what you should do in the meantime. The AI rules from the same omnibus have already been adopted and are a different topic; they are covered in the article on the EU AI Act from 2 December 2026.

What the Council agreed on 21 October 2026

The Commission proposed the Digital Omnibus on 19 November 2025. For cookies it wanted fewer banners, one-click consent and privacy preferences stored centrally in the browser. Legally, it wanted to move the rules for cookies involving personal data out of the ePrivacy Directive and into the GDPR, in two new Articles 88a and 88b (proposal COM(2025) 837).

The Council did not follow that path. In its negotiating mandate, Council document 14756/26 of 22 October 2026, Articles 88a and 88b are deleted entirely. Instead it rewrites Article 5(3) of the ePrivacy Directive. The Council press release of 21 October 2026 sums it up: the rules on cookies and other tracking technologies stay in the ePrivacy Directive, but get clearer and additional purposes for which no consent is needed.

PointCommission proposal (Nov 2025)Council mandate (Oct 2026)
Where the rules sitGDPR, new Art. 88a and 88bePrivacy Directive, new Art. 5(3)
Purposes without consentfoursix
Refusalone click or equivalentone click or equivalent
New request after a noafter six months at the earliestafter four months at the earliest
Signals from browser settingsmandatory for websites, later for browsers toodeleted
When it appliessix months after entry into force, directly as part of the GDPRafter transposition into national law, deadline 24 months after adoption

The source for every row is Council document 14756/26. It shows the changes against the Commission proposal: deletions in strikethrough, additions in bold.

Under the Council's text, information may be stored on or read from a device without consent when this serves only these purposes and is strictly necessary for them:

  1. transmitting a communication over an electronic communications network;
  2. providing a service the person explicitly requested, including its functionality;
  3. creating anonymous, aggregated audience figures for your own service, by the provider itself or a processor acting on its behalf. The data must not be used for other purposes, shared with third parties or combined with third-party data;
  4. measuring audiences under Article 24 of the European Media Freedom Act (Regulation (EU) 2024/1083). This concerns media services; the data is pseudonymised, and activity outside the measured service is not tracked;
  5. maintaining or restoring the technical security of the service or the device;
  6. measuring the display and performance of contextual advertising, meaning ads based only on the content of the page being shown or on a single search query. Profiles, history and tracking across websites are excluded.

The Commission had only proposed points 1, 2, 3 and 5. According to a note by the Council secretariat of 2 October 2026, measuring contextual advertising was only added in the final compromise.

In practice: Google Analytics with advertising features, the Meta Pixel or retargeting fall under none of these points. They would still need consent under the Council's text. Point 3 only covers statistics you use yourself and share with nobody.

What the Council requires of the banner itself

For everything that still needs consent, the text sets three rules:

  • Refusing must be easy and intelligible, with a single click or an equivalent means.
  • Once someone has consented, you must not ask again for the same purpose while the consent is valid.
  • Once someone has refused, you may ask again for the same purpose after four months at the earliest.

The central browser setting the Commission wanted is no longer in the text. According to the note of 2 October 2026, the Committee of Permanent Representatives had already discussed this "automated and centralised consent signal" and the missing impact assessment for it in June 2026. Instead, the Commission is to present a report on privacy-enhancing technologies within twelve months of adoption and, where needed, make new proposals.

What is still open and when it could apply

An EU law is made in the ordinary legislative procedure: Parliament and Council each set their position, then negotiate in the so-called trilogue and adopt the joint text. For the Digital Omnibus, Parliament's position is missing. On 20 November 2026, Parliament's procedure file 2025/0360(COD) shows the stage "Awaiting committee decision", so the responsible committee has not voted yet. The Council itself says it will start negotiations once Parliament has adopted its position.

Everything in this article can therefore still change in the negotiations: the number of exemptions, the four months and the browser signals.

There are only two firm reference points for the timeline:

  • According to the note of 2 October 2026, the European Council called in March 2026 for all pending omnibus packages to be agreed by the end of 2026. That is a political goal, not a date.
  • Under the Council's text, member states would have 24 months after adoption to transpose the new Article 5(3) into national law, and are to apply it only from then. In Germany that would require amending § 25 TDDDG.

So even if Parliament and Council agree quickly, under the Council's version today's law stays in force for at least two more years. No official source names a date yet.

What applies in Germany and Austria today

In Germany, § 25 TDDDG governs cookies and similar technologies. Storing or reading information on the device is only allowed with consent. There are exactly two exceptions: transmitting a message, and cases where it is "strictly necessary" to provide a digital service "explicitly requested" by the user. In Austria the same rule is in § 165(3) TKG 2021.

There is no separate exemption for audience measurement today. In their guidance on digital services (version 1.2, November 2024), the German supervisory authorities state explicitly that they make no general statement on whether audience measurement is allowed without consent. Even simply counting visitors is not automatically part of the requested service; it depends on the specific purpose (paras. 87 to 90). As simple forms they name a page counter, log file analysis without personal data or a counting pixel of your own service that collects no further data. Third-party web analytics providers, by contrast, "regularly process (sometimes very extensive) information about users".

Two more points from the same guidance affect almost every banner:

  • § 25 is not only about cookies. Local storage, session storage and reading device properties for a fingerprint count too (paras. 21 to 24). And it does not matter whether the data is personal.
  • Refusing must not take more effort than accepting. If refusal is only possible on a second layer of the banner, the authorities consider consent no longer freely given (para. 58). A "Settings or refuse" button that leads to a second layer is not enough (para. 137).

So in Germany the one-click refusal from the Council's text is already required in most cases today. What would be new are mainly the additional exemptions and the four-month waiting period.

What you should do now

Not legal advice

This article describes the situation on 20 November 2026 and is not legal advice. Whether a specific tool on your website needs consent is something to settle with your data protection officer or a law firm when in doubt.

  1. Keep the banner and consent

    Do not switch off your consent banner because headlines promise otherwise. Until an amended § 25 TDDDG is in force, the current law applies.

  2. Make refusing as easy as accepting

    Check on mobile and desktop that "Reject all" sits on the first layer, is as visible as "Accept all" and is clearly labelled. The supervisory authorities already require this, and the Council's text provides for it too.

  3. Take an inventory of all tools

    List every script, pixel and embedded element that uses cookies, local storage or device information. To do this, open your website in a private window, reject everything and look in the developer tools under "Application" (Chrome) or "Storage" (Firefox) for what is set anyway. Anything that shows up there before consent and is not strictly needed for the page is a finding.

  4. Write down the purpose of each tool

    Note what you need each tool for and who receives the data. You need this list today for your privacy policy, and later to check whether a tool falls under one of the new exemptions.

  5. Consent-free measurement only within narrow limits

    Today you can only measure without consent what stores or reads nothing on the device, such as counts from your own server logs, or what is demonstrably strictly necessary for the requested service. If a tool advertises itself as "cookieless", still check whether it uses local storage or a fingerprint. The GDPR continues to apply to the data itself.

In audits I find three things again and again that load before consent: fonts pulled straight from Google Fonts instead of your own server, embedded YouTube videos and Google Maps that load at once instead of after a click, and an analytics or tag manager snippet hard-coded in the <head> that never checks the banner. With all three, the page sends a request to someone else's server as soon as it opens, with your visitor's IP address. You can host fonts yourself. Videos, maps and the snippet should only load after consent. In c15t, which I also use on anolilab.com, an embed blocker holds back YouTube and Maps until their category is allowed (c15t: Embeds). You register scripts with the consent provider, which loads them only after consent and removes them again when consent is withdrawn (c15t: Scripts).

What you can prepare for

If the Council's text survives in substance, three things change for most websites:

  • Pure statistics would no longer need a prompt: if you collect visitor numbers only for yourself, anonymously and without sharing them, you would no longer need a banner for that. Whether your analytics tool qualifies depends on its configuration. The inventory above is the basis for that check.
  • A lock applies after a no: your consent tool would have to remember a refusal for at least four months. Check how long it stores the choice today and whether you can set the duration.
  • The banner stays for marketing: retargeting, ad pixels and personalisation still need consent. Many websites would keep a smaller banner, but no banner at all would be the exception.

Switching consent tools or analytics solutions just because of the omnibus is not worth it today. The text can still change in the trilogue.

On anolilab.com I use c15t for consent and PostHog for analytics. I chose both because they are open source and PostHog stores the data on servers in the EU (privacy policy). PostHog only loads once you agree to analytics. If you withdraw consent, it deletes its cookie and its local storage entry again, and it hides what you type into forms in session recordings.

When an audit of your website helps

The inventory from step 3 is the part many people put off: which scripts does the site really load, what do they set, and does any of it run before consent? On websites that have grown over years, with a tag manager, several agencies and old plugins, that is hard to keep track of.

[ Anolilab — Blog ]

More hands-on writing on AI, web development and infrastructure.

Related articles.

[ Anolilab — Contact ]

Tell me what you're building. I'll tell you how I can help.

Let's talk.

Quick response.
If you're ready to create and collaborate, I'd love to hear from you.
Clear next steps.
After the consultation, I'll give you a detailed plan.
Alternatively, you can email me directly at hello@anolilab.com