Cookie Consent Beta

Name: Cookie Consent
Availability: InStock

A cookie consent banner that matches your site, plus the switch every other site app obeys: nothing that needs consent is stored until the visitor allows it. Ask everywhere or only in the EU/UK/Switzerland, keep proof of consent, show a cookie table built from your apps, and connect your own banner or consent tool.

Freev0.6.2Cloudflare free plan

Beta

Cookie Consent is in beta: it works, but things may still break. Tell us if something does: open an issue.

Get Cookie Consent

Free

Free for every site you own or build for clients.

You'll log in first. New here? That creates your account: no password, no card.

Ask your AI agent to install this

Paste this into your AI agent (Claude Code, Codex, Cursor or another), opened in your site's project. It tells you what the app needs and costs before it changes anything.

Install the Cookie Consent app (id: consent) from the Sundogs site apps store on this site.
First read https://sundo.gs/apps/consent.md and tell me what it needs and what it costs.
It's free: get_download claims it for me if I don't have it yet.
Then download it with get_download for this site's domain. Follow the install guide (site-apps/INSTALL.md in the download, also at https://sundo.gs/install-guide.md).
Check it with the install guide's step 6 (the public status, then the self-test once you can sign in to the admin) and tell me what's next.
(Not connected to the store yet? See https://sundo.gs/agents.)

Connect your agent

What it needs

Cloudflare plan: Cloudflare free plan
Works on: Cloudflare Workers, Cloudflare Pages
Version: 0.6.2 (site layer 0.22.0 or later)
Price: Free

All the details

Runs on the Cloudflare free plan, in the same D1 database as your other site apps. No third-party script, no outside requests, no account elsewhere.
Once installed, visitors in the EU, EEA, UK and Switzerland see a cookie banner and tags that need consent wait for their answer. Everyone else sees no banner and every app and tag works as before. Change who is asked in Settings, When to ask.
Consent records are stored in your D1 database: a random id, the choices, the policy version, the time and the visitor's country. No IP address, no browser details. One small write per choice made (not per page view).
The banner is added to pages as they are served, so page views run through the site apps (as with link tagging and forms). It is not legal advice: whether and where you must ask depends on your site and your visitors.
Cost per visit: no writes on a page view; one small write each time a visitor makes a choice, and an old-records cleanup at most every 6 hours. Consent choices are always saved (not part of the logging budget); if the Cloudflare free database limit is reached, new choices cannot be recorded until midnight UTC.

Site on another host? Start here checks what you have.

Works with

Cloudflare Workers
Cloudflare Pages
Astro
Next.js
Vite
Hugo
HTML
Vanilla JS
Cookiebot
OneTrust
CookieYes
Termly
Google Consent Mode

Works with your other apps

Connects with no setup, in any install order:

Analytics Tag Manager Popups

Included

Site admin dashboard (installed with your first app, no extra cost)
Updates for as long as the app is free (you keep it if that ever changes)
An agent skill and install guide
Free License: any number of sites

What's new

Cookie Consent 0.6.2 · Nov 6, 2026

Marked as beta: it works, but things may still break. The admin shows where to report a problem.

Show full history

Cookie Consent 0.6.1 · Nov 5, 2026

Small wording updates in the admin and in the instructions for your AI agent. Nothing else changes.

Cookie Consent 0.6.0 · Nov 4, 2026

Finding your privacy page no longer trusts a redirect to a page that isn't there: on a site without a privacy page (common on Next.js) the banner linked to a 404 and the self-test said the page was found. A page found earlier is checked again once a day.
Notices are now clean tinted cards in their status color, with no side edge.

Cookie Consent 0.5.0 · Nov 4, 2026

Deleting old consent records explains that they are your proof of consent, points to the CSV download first, and asks you to tick "I understand" and type DELETE. Your AI agent must ask you and send DELETE too (consent_records_prune).

Cookie Consent 0.4.5

With no policy link set, the banner links to the site's own privacy page when there is one (/privacy, /legal/privacy or /privacy-policy, looked for once); the self-test fails only when none is found.
The banner follows the site's light and dark accents.

Cookie Consent 0.4.4 · Nov 2, 2026

The banner passes the page's landing source (ad tags, referring site, page) to the site only after a visitor accepts analytics on that same page, so a conversion from an EU ad click can still be credited. Nothing is stored or sent before they accept.
The missing privacy policy link check is shared with Tag Manager, so both say the same thing.
Turning consent off (mode never) while ad or analytics tags are live needs confirm:true and says "Every tag will run for every visitor without asking, including in the EU/UK. Not legal advice."; the answer carries the same as a warning.
With your own banner (banner off, source own) the page is now marked as waiting for an answer, so popups and notices hold back until your banner calls siteConsent.set(). The check "visitors can answer" is a warning that says what to check, and turns green once a choice has been recorded in the last 30 days.
The skill tells agents never to edit site-apps/ and links to agent-scenarios.md.
Saved choices are only accepted from your own pages, at most 120 an hour per visitor network, and are written within the daily logging budget so a flood can't use up the free database limit. Choices stay anonymous.
Deleting old consent records now asks you to confirm first.
Empty screens link to Settings ("Choose when to ask"), the Google Consent Mode text says what it does in plain words first, and times use one format.
For agents: the consent_settings_save ownRows field now says it takes JSON text (not lines separated by |) and which category and storage values it accepts.
For agents: the consent_settings_save description now says how to show the app's banner (source "own" with banner: true) and how to reopen it (#cookie-settings or siteConsent.open()); source only accepts the values that work.

Cookie Consent 0.4.0 · Nov 1, 2026

AI agents: consent_settings_save's dry run now returns the same warnings as a real save and the complete settings after the save; failing health checks name the exact fix.

Cookie Consent 0.3.0 · Oct 31, 2026

"Only these countries" is now the recommended choice and the default for new installs: the picker says who sees the banner and who doesn't, and the status line reads "Live for everyone outside the EU/UK; asks visitors in the EU, EEA, UK and Switzerland". Your saved choice hasn't changed; sites that ask everyone or nobody get a one-click suggestion.
Your AI agent sees the same suggestions as the settings page (consent_settings recommendations), each with the tool that applies it once you agree.
New US opt-out link: "Do Not Sell or Share My Personal Information", added at the end of every page for US visitors or placed by you in your footer. One click opts the visitor out; ad tags that honour opt-outs stop selling or sharing their data. Shared with Tag Manager.

Cookie Consent 0.2.3 · Oct 31, 2026

Phone admin: the records and cookie tables read as compact list rows.

Cookie Consent 0.2.2 · Oct 31, 2026

Admin pages work like a phone app: a menu drawer instead of a tab strip, 44px tap targets, fields that bring up the right keyboard, save buttons that stay in reach on long forms, and no sideways scrolling at any phone or tablet width. The cookie, record and country tables stack into cards on phones.

Cookie Consent 0.2.1 · Oct 31, 2026

Agents: self-test fixes name consent_settings_save with the exact fields to send.

Cookie Consent 0.2.0 · Oct 30, 2026

Your AI agent can manage this app through the admin's MCP connection (Settings, Connect an agent), signed in with Cloudflare Access like you. Deletes ask for a second confirmation; personal data is left out unless asked for.

Cookie Consent 0.1.2 · Oct 30, 2026

States its cost per visit (requests and database writes) before you install, and can be turned off in an emergency from Settings, Apps.

Cookie Consent 0.1.1 · Oct 30, 2026

Settings and Health warn when your banner's signal can never allow "preferences", explain what that means for popups and timers, and show the one-line mapping if your banner covers both.

Cookie Consent 0.1.0 · Oct 30, 2026

First release: a cookie banner with equal Accept all and Reject all buttons and a per-category choice, a cookie table built from every installed app, consent records with CSV export, and Google Consent Mode v2.
Works three ways: our banner, your own banner (one line tells the apps the choice), or a consent tool you already use (Cookiebot, OneTrust, CookieYes, Termly, or any cookie you describe).
Every other app obeys the choice: no preferences, analytics or marketing cookie is set before it is allowed, wherever you ask for consent.

Questions

Do I need to write code?

No. Your AI coding agent installs it into your site's project and deploys it with your own Cloudflare account. You approve the changes.

Does it send my site's data anywhere?

No. It runs in your own Cloudflare account. The store never sees your visitors, your form entries or your settings.

What if it stops being free?

You keep it. Apps you claimed stay yours, with updates for as long as the app is free.

Can I use it on client sites?

Yes: free apps work on any number of sites, yours or your clients'.

What does it need from Cloudflare?

Cloudflare free plan, on Cloudflare Workers, Cloudflare Pages.

Guides for this job

The decisions, rules and setup around it, and where the app fits.

How to vibecode an affiliate site on Next.js (and host it free on Cloudflare)Build a whole affiliate site with an AI coding agent, start to finish: pick a niche you can win, plan the pages that earn (best-of lists, comparisons, reviews), set up Next.js as a static export, write content Google rewards, get the SEO basics right, deploy on the Cloudflare free plan, then monetise with affiliate links and an email list, and measure which pages make money. With prompts you can give your agent at each step.