On 10 September 2026, a coalition of 19 civil society organisations, businesses and academics sent an open letter to the European Parliament, the Council and the Commission with one demand: keep Article 88b in the Digital Omnibus and use it to "kill the cookie banner". Article 88b would let people set their privacy choice once, in the browser, and oblige websites to respect that automated browser privacy signal instead of asking again on every site. The letter, published by noyb and backed by groups including BEUC and EDRi, points to Global Privacy Control in the US and to European alternatives such as ADPC as proof that the technology exists.
Why it matters now: the Council's working text has already dropped Article 88b, and the coalition says that followed lobbying "spearheaded by Google". Whether the cookie banner ends up replaced by a browser setting depends on what the European Parliament does next. This article explains what Global Privacy Control and similar signals are, what the Commission proposed, and what a website owner can sensibly do today.
Not legal advice. This article describes proposals that are still being negotiated and US rules that may not apply to you. Check with your DPO or a lawyer before changing how you handle consent.
What the "Kill the cookie banner" letter asks for
The coalition runs under the name Kill the cookie banner. Its joint letter is addressed to the Parliament's co-rapporteurs Marina Kaljurand and Aura Salla, to the Council's Irish presidency and to Commissioners Virkkunen and McGrath. It makes four main points:
- Automated signals are the only part of the Omnibus that simplifies life for people, not just for businesses. BEUC's Cláudio Teixeira calls them the only proposal "aimed at actually simplifying".
- Signals should cover more than refusal. The letter wants Article 88b to cover giving consent, refusing or withdrawing it, and objecting to processing, per controller and per purpose, so you could trust a local newspaper and refuse a large platform.
- Refusals should stick. A refusal sent by the browser should take precedence over later consent requests and should not lead to degraded access.
- Dominant browser makers should not control the signal. Big browsers and mobile operating systems should have to let users send their preference, without "gatekeeper interference".
The letter asks the Irish presidency to put Article 88b back into its next compromise text, and notes that "many constructive amendments" to keep and improve it have been tabled in the Parliament committees. noyb's announcement also cites a Commission estimate that automated signals would save people hundreds of millions of hours a year on consent banners.
What Article 88b of the Digital Omnibus would do
The European Commission published the Digital Omnibus on 19 November 2025 (COM(2025) 837). For cookies it proposed two new GDPR articles:
- Article 88a would require consent for storing or reading personal data on a person's device, with a short list of exemptions, including aggregated audience measurement by a site for its own use. Refusing would have to be possible with a single click, and after a refusal the site could not ask again for six months.
- Article 88b would require websites to let people give consent, refuse it and object to processing "through automated and machine-readable means", and to respect those choices. European standardisation bodies would draft the technical standard.
| Article 88b element | Commission proposal |
|---|---|
| Who must accept signals | Controllers' online interfaces (websites, apps) |
| What the signal can say | Give consent, refuse consent, object under Art. 21(2) GDPR |
| Exemption | Media service providers when providing a media service |
| Technical standard | Requested from European standardisation organisations |
| Browser obligation | Web browser providers that are not SMEs must provide the means |
| Applies to websites | 24 months after entry into force |
| Applies to browsers | 48 months after entry into force |
The Council has not finished its position. According to noyb and the coalition, the Council presidency's compromise texts no longer contain Article 88b, and several member states oppose it. The Parliament has not voted on its position yet. Until both institutions agree a final text, none of this is law.
Global Privacy Control, ADPC and navigator.consent
Three technical approaches come up in the debate. They differ in what they can express.
Global Privacy Control (GPC)
Global Privacy Control is the best-known browser privacy signal. When a user switches it on, the browser sends the HTTP header Sec-GPC: 1 with every request and sets the JavaScript property navigator.globalPrivacyControl to true, as described in the GPC specification. A site can also publish a /.well-known/gpc.json file to say it supports the signal. GPC became an official work item of the W3C Privacy Working Group in November 2024.
GPC is a one-way opt-out: "do not sell or share my data". Brave and DuckDuckGo send it by default, Firefox offers it as a setting, and extensions such as Privacy Badger add it to other browsers. The GPC project says that under the GDPR the signal can be read as a general request to limit the sale or sharing of personal data, referring to Articles 7 and 21. No EU regulator has made honouring it mandatory.
ADPC (Advanced Data Protection Control)
ADPC is a European proposal, developed according to the coalition letter by the Vienna University of Economics and civil society groups including noyb. It goes further than GPC: the user can consent, refuse, withdraw or object per purpose and per controller, and the website confirms what it received. That two-way design is what a GDPR-grade consent signal needs.
navigator.consent
navigator.consent is a proposed browser API stewarded by the European CMP Association. Rather than replacing consent management platforms, it gives browsers, CMPs and "consent assistants" a shared channel to exchange choices. It describes itself as complementary to GPC.
| GPC | ADPC | navigator.consent | |
|---|---|---|---|
| What it can say | Opt out of sale/sharing | Consent, refuse, withdraw, object | Structured consent choices |
| Granularity | One global signal | Per purpose, per controller | Per vendor, per purpose |
| How | Sec-GPC header, JS property |
HTTP request and response headers | Browser API with CMPs |
| Legal status | Required in California and other US states | None yet | None yet |
California already requires it
The coalition's strongest argument is that this already works elsewhere. Under the California Consumer Privacy Act regulations (section 7025), a business that sells or shares personal data must treat an opt-out preference signal such as GPC as a valid request to opt out, and the GPC project lists the CCPA as a law that requires support for it. California went a step further in October 2025 with the Opt Me Out Act (AB 566), which requires browsers to offer a setting that sends an opt-out preference signal. It takes effect on 1 January 2027.
So a European site with Californian visitors may already have a duty to honour GPC today, if it sells or shares their data in the CCPA sense.
What websites should do now
Nothing in the EU obliges you to honour browser signals yet. But a few steps make sense regardless of how the Omnibus ends.
- Check whether you are already bound. If you sell or share personal data of California residents, make sure your consent setup reads
Sec-GPCornavigator.globalPrivacyControland treats it as an opt-out. Most consent management platforms have a setting for this. - Consider honouring GPC voluntarily. Treating a GPC signal as a refusal of advertising and cross-site tracking is a few lines of code. It respects a choice the visitor has already made and saves them a banner interaction.
- Do not let the banner become a dark pattern in the meantime. Regulators are already acting on banners that make refusing harder than accepting; see our article on the 1,741-partner consent banner.
- Count what the banner costs you. Every consent wall loses visitors and data, as described in Cookie Consent Banners Are Killing Your Conversion Rate. Google's Consent Mode V2 does not change that; it only changes what Google models when consent is missing.
- Separate what needs consent from what does not. A browser signal only answers a consent question. If a tool never stores or reads anything on the device, there is no question to answer.
Why consent-free analytics sidesteps the debate
Article 88b, GPC and ADPC all deal with the same problem: tools that need permission to access the visitor's device. If your analytics does not access the device at all, a browser signal changes nothing for it. The Commission's own Article 88a also listed aggregated, first-party audience measurement among the exemptions, which shows where EU lawmakers see measurement heading.
Where ClearAnalytics fits
ClearAnalytics sets no cookies and stores nothing on the visitor's device, so there is no consent request for a banner or a browser signal to answer. It counts unique visitors with a daily-rotating hash of IP address, user agent and a daily salt, without storing the IP (how that works), and it keeps all data in the EU. It is designed so that consent should not be needed, whatever happens to Article 88b.