Cookie consent that actually blocks trackers.
Most banners just ask — the trackers run anyway. CookieCrumb enforces the choice: it scans your site, shows a clear banner in your visitor's language, and holds every non-essential script you tag until someone opts in. Each decision lands in an audit-ready consent log.
- Lightweight loader
- <20KB
- Banner languages
- 12
- Privacy laws covered
- 3
The whole consent lifecycle, behind one script.
Discovery, choice, enforcement, proof — CookieCrumb covers each step of cookie compliance so the banner you show matches what your site actually does.
True prior-blocking
Scripts you tag as analytics, marketing, or preferences — Google Analytics, Meta Pixel, anything else — are held before they execute and released only for the categories your visitor accepts. The loader fails closed, not open.
Deep browser scanning
An optional browser engine loads your pages in headless Chromium like a real visitor, so it catches JavaScript-set cookies that header-only crawlers never see.
Audit-ready consent log
Every decision is recorded with a pseudonymous ID, timestamp, banner version, and the exact categories chosen — the proof GDPR Article 7(1) expects when a regulator asks.
Multilingual by default
Editable translations for every language you serve, with optional auto-detection of the visitor's browser language. One site, every audience.
Your brand, not ours
Box, bar, or modal; your colors, your wording. The banner renders in Shadow DOM, so your site's CSS and the banner never fight.
Global Privacy Control
Switch on GPC support and browsers sending the signal are opted out of optional tracking automatically — required in California, appreciated everywhere.
Scan any domain you have verified, whenever you like.
Install in less than three minutes.
Add a single line of script to your website header and let CookieCrumb do the heavy lifting.
- 01
Add your domain
Sign up, add your site and prove you own it. CookieCrumb then crawls it and builds your cookie inventory — known cookies categorized, unknown ones listed for review.
- 02
Paste one script tag
Copy the generated snippet into your site's <head>, above your analytics tags, and tag the scripts that need consent. Works on any stack — plain HTML, Next.js, WordPress, Shopify.
- 03
Go live and prove it
Style the banner — it is live as soon as the snippet is on your pages. From then on every visitor choice is enforced and recorded in your consent log.
index.html<!-- Paste before </head> -->
<script
src="https://cookie-api.trishchuk.com/cdn/YOUR_SITE_ID/loader.js"
defer
></script>Works with any stack — plain HTML, WordPress, Next.js, or a tag manager.
Full installation guideFrequently Asked Questions
Everything else you might be wondering before you install.
Do I need a cookie banner on my website?
If you use any non-essential cookies — analytics, ads, embedded video, chat widgets — and have visitors from the EU, UK, or Brazil, yes: those laws require consent before tracking starts. California works on an opt-out basis instead. Sites using only strictly necessary cookies are the rare exception.
What is prior-blocking and why does it matter?
Under the GDPR and the ePrivacy rules, non-essential cookies may only be set after the visitor agrees. A banner that lets Google Analytics or the Meta Pixel run on page load is asking for a permission it has already taken. Prior-blocking holds those scripts until consent is explicitly granted — it's the difference between looking compliant and being compliant.
How does the cookie scanner work?
CookieCrumb offers two engines. The default crawler inspects your pages and response headers; the optional deep engine loads pages in headless Chromium, runs their JavaScript, and captures cookies set dynamically by scripts — the ones header-only scanners miss. Detected cookies are matched against a built-in list of known services and categorized automatically; the rest are listed as uncategorized.
Will CookieCrumb slow down my site?
No. The loader is around 18 KB — several times smaller than most consent scripts — and it blocks trackers rather than adding them, which frequently makes first paint faster, not slower.
Where is the consent data stored?
Consent records are stored on our servers with a pseudonymous consent ID; IP addresses are masked by default, so the log remains valid legal proof without hoarding personal data. You can export it as CSV at any time, or pull it over the API.
Ready to automate compliance?
Scan, banner, blocking, and proof — the whole consent stack in one script. Free for your first domain, live in minutes.