Set up in an afternoon
Add one line to your site, then build the banner, set your rules and publish — all point-and-click. Changes go live as versioned deployments you can roll back, so consent works as smoothly as the rest of your site.
Why ConsentCook
Plenty of tools will show a banner. ConsentCook shows the right one, records what was chosen, and keeps the proof — without making you fight the plumbing to get there.
Every reason below comes back to this one record
Consent receipt
Signedsha256 4f9c2a1d8b…e2d1
signed 2026-06-26T09:41:22Z · cfg v8 · pol v3
The reasons
Each one earns its place by doing real work — setting up faster, proving more, and asking less of you afterwards.
Add one line to your site, then build the banner, set your rules and publish — all point-and-click. Changes go live as versioned deployments you can roll back, so consent works as smoothly as the rest of your site.
Every choice is a signed, tamper-evident receipt that records the exact banner and policy version a visitor saw. When someone asks you to prove consent, you can.
Visitors see the rules that apply where they are — UK, the EEA, California and more — all driven from one policy. No duplicate set-ups, no guesswork.
Anonymous subject keys, never raw identifiers, and no full IP addresses by default. You set the retention window, and deletion actually runs when it expires.
Consent Mode v2 signals update the instant a visitor chooses. No extra tags, no glue code, no analytics quietly ignoring a refusal.
ConsentCook runs on ConsentCook. The banner on this very site is ours, served from the same signed pipeline you'd put in front of your visitors.
The short version
Get consent right, prove it later, and never think about the plumbing. Here's the whole journey — four steps, one afternoon, ending in proof.
Name the site and it gets its own key straight away. Paid plans also get a staging environment to rehearse changes in.
Drop in a DNS record or a hosted file. Once it's verified, every receipt carries weight.
Build it, set the rules, add one line to your site. Changes go live as a versioned deployment.
A visitor chooses, and the signed record is written the instant it happens. You're on the record.
One site, signed receipts, every region pack. No card required.