Cookie consent that holds up to the DPC.
Most banners are built to nudge people into "Accept all." Cookies.ie is built the other way: equal-prominence Reject, nothing non-essential fires before consent, and a tamper-proof log that proves it — all from one line of code.
- EU-hosted
- Equal-prominence Reject, by design
- Nothing fires before consent
- GPC honoured
- SRI-pinned snippet
No card to start · English & Irish · Not legal advice
You can pass the checker. Or you can install the fix.
Run a site through our banner checker and the usual report comes back: no real Reject button, Google Analytics firing before anyone consents, five trackers loading on page one. You know what's wrong. The hard part is building a banner that fixes all of it — and keeps fixing it after the next plugin, the next marketing tag, the next redesign.
That's what the Cookies.ie banner is. Paste one line before </head> and
the checks you just failed become the defaults you can't switch off.
Three steps, about ten minutes
1. Paste one line
A single async <script> tag, served from cdn.cookies.ie
and pinned with an integrity hash. It loads after your page is interactive, so it
never costs you a Lighthouse point.
2. Make it yours
Set your copy, categories, colours and position in the dashboard — bottom or top, floating card or full-width bar. Preview it live, then publish a versioned revision.
3. Ship it
Visitors get a clear Accept / Reject / Manage choice. Non-essential scripts stay blocked until they choose. Every decision lands in your consent log.
What you're actually installing
A banner that can't go dark
Accept all and Reject all are the same size, the same weight, the same one click — and that's locked at the code level. You couldn't build a "Reject" buried three menus deep if you wanted to. Which means no accidental dark pattern, and nothing for the DPC to object to.
Real script-blocking
Analytics, pixels and marketing tags are held until the visitor opts in — not loaded and "honoured later." The single biggest reason sites fail a cookie audit is scripts firing before consent. This stops it at the source.
A preference centre
Strictly necessary, functional, analytics and marketing — each one explained, none pre-ticked. Visitors pick exactly what they allow and change it any time, which is precisely what "freely given, specific" consent is supposed to mean.
A tamper-proof consent log
Every choice is written to an append-only, hash-chained log — so if a regulator or a customer ever asks "prove they consented," you export the record as CSV or JSON instead of shrugging. You can't quietly edit it, and neither can we.
GPC, honoured automatically
Browsers sending a Global Privacy Control signal are treated as a default reject for analytics and marketing — the legally-recognised opt-out, handled for you, with no extra setup.
Built for Ireland, in two languages
Scored against Irish DPC guidance, hosted in the EU, and shipped in English and Irish (Gaeilge) from day one — so a Gaeltacht visitor and a Dublin visitor each get a banner in their language.
Fast, and tamper-evident, on purpose
Enterprise consent tools are notorious for tanking page speed — a heavy blocking script that arrives before your content does. The Cookies.ie snippet loads after your page is interactive, so the banner never sits on your critical path.
And because the file is pinned with a Subresource Integrity hash, if anything ever tampers with it in transit, the browser simply refuses to run it. The banner that protects your visitors is itself protected from being swapped out underneath you.
Start free. Upgrade when you grow.
One site and 10,000 consent decisions a month, free forever — no card. Move to Starter for €19/mo when you need more sites, more volume, or your branding off the banner.
Hit your cap? We pause logging — never your billing.