Equal Accept and Reject. Real script blocking. A consent log you can export. Google Consent Mode v2. In Dutch, German and French. No plugin subscription, ever.
The Dutch Autoriteit Persoonsgegevens, the Belgian GBA and the German data protection authorities have all been explicit in recent years: a banner is only valid consent if it meets a short list of conditions. Most sites fail at least one.
| Requirement | What most sites do | What's required |
|---|---|---|
| Reject as easy as Accept | "Accept" button, "Settings" link | Two equal buttons on the first layer |
| Nothing fires before consent | GA4, Meta Pixel, YouTube load on page load | Scripts blocked until the category is accepted |
| Granular choice | All-or-nothing | Per category: necessary / analytics / marketing |
| Withdraw as easily as given | No way to reopen the banner | Persistent link in the footer |
| Proof of consent | Nothing stored | Timestamp, choices, banner version, anonymised ID |
| No pre-ticked boxes | Marketing pre-selected | All optional categories off by default |
| Right language | English banner on a Dutch shop | Banner and policies in the visitor's language |
The fines are real — the AP fined a Dutch retailer in the six figures for a "cookie wall" — but the more common cost is quieter: Google Ads and GA4 now require Consent Mode v2 in the EU, and without it your conversion data degrades and remarketing stops working.
A first layer with short text and three equal-weight buttons — Accept all, Reject all, Choose — over a second layer of per-category toggles in plain language. Every non-essential category is off by default; the choice is stored for 12 months (configurable), with a footer link to change it at any time. Fully keyboard-accessible, screen-reader labelled, with no layout shift when it appears — and styled into your theme, not a floating third-party box.
Third-party scripts are rewritten to a blocked type and only activated when their category is accepted — nothing fires on page load. Embeds show a placeholder with a one-click consent option instead of a blank space.
Every choice is logged with a timestamp, the categories accepted, the banner text version and a hashed identifier — exportable as CSV from the admin. This is the evidence you show a regulator or a complaining customer. It is the part most plugins put behind a paid tier; we include it.
Default consent state set to denied for ad_storage, ad_user_data, ad_personalization and analytics_storage, updated when the visitor chooses. Verified in Tag Assistant. This keeps GA4 modelling and Google Ads conversion tracking working legally in the EU.
Checkout, cart and account pages are excluded from marketing scripts until consent, and order data is never sent to ad platforms without the marketing category. Customer data export and erasure requests run through WooCommerce's built-in privacy tools, configured and tested, with data retention rules set for orders, failed orders and inactive accounts.
Privacy policy, cookie policy and terms structured for NL, BE and DE requirements, including the German Impressum. We prepare them with our legal counsel and hand them to you for confirmation; we also integrate texts your own lawyer supplies. Each page is available in every shop language.
Blocked out of the box until their category is accepted — plus any custom tag you add:
| Complianz / CookieYes / Cookiebot | Our custom layer | |
|---|---|---|
| Annual cost | €50–500 per site per year | €0 after build |
| Consent records | Paid tier | Included |
| Consent Mode v2 | Paid tier on most | Included |
| Design | Generic, limited styling | Part of your theme |
| Page weight | 50–150 KB extra | ~8 KB |
| Auto-scanning for new cookies | Yes | No — we document what you use and update when you add a tool |
| Legal text generator | Yes | Prepared with counsel, or yours |
If you add marketing tools every month and want automated cookie scanning, a plugin is a fair choice and we'll configure Complianz Premium for you. If you want something light, owned, and correctly wired into Consent Mode, build it once — on its own, or as part of a full WooCommerce webshop for the Netherlands and Belgium.
In NL, BE and DE, yes. GA4 sets identifiers and is treated as analytics/tracking requiring consent, and Google itself requires Consent Mode v2 for EU traffic.
Yes. Strictly necessary cookies — session, cart, consent choice itself — don't need consent and stay on.
Yes. The same mechanics — prior consent, equal reject, revocation — satisfy TTDSG §25 alongside the DSGVO.
Yes. We audit what loads on your pages, wire the blocking, and deliver the same layer. Timeline: one to two working days.
Blocking access to the site until the visitor accepts is not valid consent under the AP's guidance. We don't build cookie walls.
Tell us what loads on your site. One fixed price of €300, on any WordPress or WooCommerce site — see how pricing works.
Get compliant →