On 16 October 2026 the Dutch Data Protection Authority, the Autoriteit Persoonsgegevens (AP), announced that it has started investigations into two organisations that keep using a misleading cookie banner, despite an explanation and a warning from the regulator. Their banners have no directly visible button to refuse tracking cookies, which nudges visitors into accepting them.
The two cases are small in number but big in signal. For two years the AP mostly sent warning letters. Now organisations that ignore a warning face a formal investigation and, according to the AP, possibly a fine. If your site serves Dutch visitors, this is a good moment to check your banner against the AP's own rules.
Not legal advice. This article summarises public statements and guidance from the Dutch DPA. Check your own situation with your DPO or a lawyer.
What the Dutch DPA announced about cookie banners
The AP's announcement makes four points:
- Two investigations. The AP is investigating two organisations whose cookie banner still has no directly visible reject button after being warned. It does not name them.
- About 100 warnings. In recent months the AP warned around 100 organisations about cookie banners that do not meet the requirements, among them organisations in the media sector, healthcare and welfare, and insurance.
- About 70% fixed it. The majority, around 70 percent, adjusted their banner after the warning. Those that do not, the AP says, "can expect an investigation and possibly a fine" (our translation).
- The core rule. Refusing tracking cookies must be as easy as accepting them, so a cookie banner needs a directly visible reject button next to the accept button.
The AP also notes that it has been checking more often since 2024 whether organisations ask for consent for tracking cookies correctly.
From warnings to investigations: the AP's cookie banner timeline
The October announcement is the latest step in a campaign that has been building for a while:
| Date | What the AP did |
|---|---|
| 15 April 2025 | Warned 50 organisations about misleading cookie banners |
| April 2025 | Started structural checks on whether Dutch websites ask for tracking-cookie consent correctly |
| 11 November 2025 | Said it had warned more than 200 websites, about three-quarters had fixed their banner, and it was taking enforcement steps against those that had not |
| 16 October 2026 | Announced investigations into two organisations after a new round of about 100 warnings, of which about 70% were followed |
The pattern is consistent: warn first, help with guidance, then investigate the organisations that do nothing. In November 2025 AP vice-chair Monique Verdier added that the simplest way to respect visitors' choices is not to use tracking software at all, because then no cookie banner is needed.
What the AP expects from a cookie banner
The AP publishes nine rules of thumb on its page about clear cookie banners. Here they are as a checklist, with the typical mistake each one targets.
| AP rule of thumb | What it means in practice | Typical mistake |
|---|---|---|
| Explain what data you process and why | Name the purposes and the (kinds of) personal data before the visitor chooses; say in the first layer if you share data with third parties and with how many | Vague purposes such as "social media" without saying what happens to the data |
| Don't pre-tick boxes | The visitor ticks options themselves, on every layer; sliders must clearly show on or off | Marketing and analytics toggles switched on by default |
| Use clear wording | Buttons say "accept" or "reject", so it is clear consent is given | "OK" or "Got it" that only seems to confirm reading the text |
| Put choices on one layer | Reject sits on the same layer as accept | "Accept all" up front, "Reject" only in a settings screen |
| Don't hide choices | The reject button is clearly visible and readable | A reject button that barely contrasts with the banner background, or that requires scrolling |
| No extra clicks to refuse | Refusing takes no more clicks than accepting | A "Are you sure?" confirmation after clicking reject |
| No inconspicuous link | Refusing is as visible as accepting | "Continue without accepting" hidden as a text link |
| Withdrawing is as easy as giving | Explain before the choice how to withdraw, and keep that option easy to reach, for example with a floating button | Consent settings buried in a footer link on one page |
| Don't confuse consent with legitimate interest | Tracking cookies need consent; functional and limited analytical cookies may rely on legitimate interest, with a documented balancing test and an easy way to object | Tracking cookies switched on under "legitimate interest" |
The two organisations under investigation fail on the most basic of these: the reject all button is not directly visible. That is also the most common problem the AP has flagged since its first round of warnings.
Colour and contrast count too
The AP is explicit that a reject button that "barely differs from the background" of the banner, making it unreadable for almost any user, counts as hiding a choice. You do not need a giant red button, but the reject option has to be as easy to see as the accept option. Design tricks that steer visitors towards "accept" are exactly what the AP means by a misleading cookie banner.
Cookie banner rules in the Netherlands: what this means for analytics
Not every cookie needs a banner. The AP's guidance on cookies and your organisation says functional cookies and limited analytical cookies with little or no privacy impact may be placed without consent. Tracking cookies, the kind that follow people across sites and build profiles, always need consent.
The same AP page goes a step further. If you stop collecting personal data from your visitors, you no longer need to ask for consent and can remove the cookie banner. It also points to alternatives for "intrusive analytical applications": services that keep statistics without following visitors across the internet or building detailed profiles.
That is a notable position for a regulator. A banner is not a compliance goal in itself; it is the cost of processing personal data for tracking. Every tracking tag you remove is one less thing that needs consent, and one less thing the AP can find wrong with your banner. We looked at the business side of this in how cookie consent banners are killing your conversion rate.
What to do now
- Open your site in a private window on desktop and mobile. Is there a reject button on the first layer, as visible as accept?
- Count the clicks. If "accept all" takes one click, "reject all" must take one click too.
- Check the defaults in every layer of your consent tool. Nothing pre-ticked.
- Test what actually happens after "reject". A banner that looks right but still loads tracking scripts after a refusal is a separate and bigger problem.
- Audit your tags. List every script that needs consent and ask whether you still use the data. The AP's guidance invites exactly this question.
- Keep an eye on enforcement. For background on how the AP makes its sanctions public, see our earlier piece on the Dutch DPA publishing GDPR fines.
Where ClearAnalytics fits
ClearAnalytics sets no cookies and stores nothing on the visitor's device. It counts unique visitors with a daily-rotating hash, does not store IP addresses, keeps data in the EU and never shares visitor data with third parties or uses it for advertising. It is designed to fit the profile the AP describes for analytics that does not follow people around the web, so your analytics does not have to be one of the things your cookie banner asks about. Read more in why your website needs cookie-free analytics in 2026.