The EU wrote the rule that kills cookie banners. Then the Council deleted it.
Behind the viral killthecookiebanner.eu site is noyb, one deleted GDPR article, and a Google-commissioned study worth EUR 40 to 50 billion.
A viral site with 1,121 Hacker News points is really a fight over one deleted GDPR article.
A single-purpose website called killthecookiebanner.eu hit 1,121 points on Hacker News on July 27, 2026. It looks like a stunt. It is not: the legal imprint traces to noyb, Max Schrems' Vienna-based privacy group, joined by EDRi, EFF, BEUC, and the Irish Council for Civil Liberties, and its target is one specific act of deletion. On June 18, 2026, the EU Council removed Article 88b, the provision that would have made cookie banners largely obsolete, from the Digital Omnibus package.
The article that would have ended the banner
The European Commission's Digital Omnibus proposal, published November 19, 2025, included a new Article 88b for the GDPR: websites would be legally required to honor an automated, machine-readable consent signal set once in the browser. Decline tracking in one place, and every site has to respect it, no banner needed. Individual sites could still ask, but they could not ignore the signal. The rollout gave everyone 24 months, with 48 months for the biggest browser vendors. It is the idea behind Global Privacy Control, except legally binding across the EU.
How it died
The Council's fifth compromise text, dated June 18, 2026, deleted Article 88b outright, with Germany, France, and Poland backing the removal. A single-click reject requirement and a six-month consent moratorium fell out of the text at the same time. In the background sat a Google-commissioned study from Implement Consulting Group, published in March 2026, estimating that binding browser signals would cost EUR 40 to 50 billion per year in European ad revenue from a 60 to 65% drop in consent rates. noyb calls those figures "completely far-fetched," because they model a universal opt-out the Commission never actually proposed.
What the campaign asks
The site asks EU residents to email the members of the European Parliament's LIBE and ITRE committees, listed country by country, before the Parliament fixes its negotiating position and the file goes into trilogue. It is deliberately manual: no petition counter, no pre-filled mass-mail tool, just a list of addresses and an argument. That argument leans on a familiar pair of numbers: under dark-pattern banner design, up to 90% of visitors click accept, while research the campaign cites puts the share of people who actually want tracking at 3 to 10%.
One honest caveat: every headline number in this fight is an advocacy number. The 90% and the 3 to 10% come from the campaign's side; the EUR 40 to 50 billion comes from a study Google paid for. Treat all of them as arguments with citations, not neutral measurements.
Why a build studio cares
Every client site we ship in or into the EU carries a consent layer, and an entire industry of consent management platforms exists to build, test, and litigate that one banner. Article 88b would have deleted that whole UI layer and replaced it with a browser setting. Whether the Parliament restores it decides if the consent UX we keep building is a permanent fixture of the web or a transition artifact, which makes this the rare Brussels procedural fight with a direct line to our component library.
Next step: read the campaign site, ppc.land's report on the Council deletion, and noyb's statement. If your product needs a consent flow that respects users today, write to hello@gattyworks.com.