Build Cookiebot

KINDAreplaces $8/mosaves $96/yrback to the verdict

0%0 of 15 items done

Saved on this device only. Tick prerequisites first, then work the phases in order · do not start one until the checks above it pass.

A consent manager for your own site: an inventory of every script you load, gating so nothing non-essential runs before consent, an accessible banner with equal-weight accept and reject, withdrawal, Consent Mode signals and an optional consent log. First question: do you load anything non-essential at all? If not, the right build is no banner.

estimated effort one sittingthe files for this build are in the project pack

BannerVanilla JS under 8 KB, self-hostedLogA tiny optional endpoint

Before step 1

Everything below is assumed from the first step. Tick each one when you actually have it, not when you plan to.

installfree
Why Every step below is a command you type or a file you edit.
Get it VS Code (code.visualstudio.com), Cursor or Zed. Open a folder for the project and use the editor's built-in terminal. open ↗
Verify You can open a folder and run a command in its terminal
installfree
Why History for your code, and the way most hosts deploy.
Get it Install from git-scm.com or with your package manager, then run git init in the project folder once it exists. open ↗
Verify git --version prints a version
have readyfree
Why Phase 1 gates them by category. You cannot gate what you have not listed.
Get it Open DevTools > Network on a cold load and write down every third-party host and what it does.
decidefree
Why Cookieless analytics and no ad or social scripts means no banner is the correct build.
Get it Answer honestly from the inventory.
accountfree
Why Phase 4 sends Consent Mode v2 signals if you use Google tags.
Get it Your existing container id.

Environment variables

These go in a .env file the app reads at startup. The pack's .env.example is this table as a file · copy it, never commit the filled-in version.

Variable	Needed	Example	Where the value comes from
`CONSENT_LOG_ENDPOINT`	optional	`https://forms.yourdomain.com/consent`	Optional endpoint for consent records. Empty disables logging.

The build, in order

1
Inventory
scripts.json and every non-essential tag inert before consent.
1. Files scripts.json
done when · tick each as it passes
next phase
2
The banner
Accept all, Reject all, Preferences with equal weight; stored with a version and timestamp.
done when · tick each as it passes
next phase
3
Preferences and withdrawal
Reopen, re-ask on change, stop and clear on withdrawal.
done when · tick each as it passes
next phase
4
Consent Mode and the log
Google signals and an optional record without IPs.
done when · tick each as it passes
next phase
5
Verify
A checklist someone else can run.
2. Files README.md
done when · tick each as it passes
next phase
6
Keep it honestproduct builder
Catch the tag someone adds next Tuesday.
done when · tick each as it passes

what this build does not replace

Scanning for cookies you do not know about, jurisdiction-specific legal text, a regulator-familiar audit trail.
automatic scanning that finds cookies you did not know about
the consent log a regulator will accept
legal text kept current across jurisdictions
Google-certified Consent Mode integration

after v1, if you want it

A per-region default (no banner where none is required)

Need the files? The project pack on the verdict page hands your agent the whole brief · more legal.