Consent that keeps your data honest — and your site fast.
Bold Consent is a cookie consent manager built on Consent Mode v2: zero scripts before consent, analytics in a Web Worker, and a banner that looks like part of your brand — not a court order. It runs in production on letsgobold.com.
Live on letsgobold.com0 cookies before consentAnalytics in a Web Worker
The typical banner does more harm than good
Off-the-shelf CMPs solve the legal problem by creating three new ones.
- A heavy CMP script on the main thread (200–400 KB)TBT ↑
- Consent Mode implemented “roughly” or not at allV2: MISSING
- Marketing scripts firing BEFORE consentRISK
- A wall-of-text banner with dark patternsUX ↓
- Rejected consent = blind analytics−DATA
The result: a slower site, leaky data and legal risk — all at once
How it works
One consent bridge owns the whole lifecycle — before, during and after the decision.
Before consent
The page loads no marketing scripts and Consent Mode reports default “denied”. Zero cookies, zero third-party requests.
The decision
The visitor chooses in the banner — no dark patterns, two clicks, their language. The decision is stored with the policy version.
After consent
A single consent bridge fires the Consent Mode update and loads exactly what was allowed — in a Web Worker, off the main thread.
What's inside
A consent architecture we proved on our own site — before it became a product.
Consent Mode v2 with a single source of truth
Consent state has exactly one writer: default before any other command, update the moment a decision is made. No duplicated logic, no races between scripts.
Analytics in a Web Worker
GA4, Clarity and ad pixels run off the main thread (Partytown). Adding analytics changes neither TBT nor CLS — neither does the banner.
Zero cookies before consent
Rejecting consent genuinely disables the scripts — no hidden tracking. An auditor sees a clean Network tab until the decision is made.
A banner in your brand
Sharp typography, design tokens, full copy control — the banner reads as part of your site, not a bolted-on popup. PL/EN as standard; more languages are configuration.
A decision register
Every consent is stored with a timestamp and policy version — accountability for audits, without shipping personal data to a third party.
The banner on letsgobold.com is this product — open it and click around.
Open letsgobold.comLaunch pricing
Two plans, no surprises. Numbers land with the launch — not before.
Site
One domain
- Consent Mode v2, wired correctly
- Analytics in a Web Worker
- Banner in your brand (design tokens)
- Decision register with policy versions
- PL/EN out of the box
Pricing announced at launch
Talk to salesAgency
Unlimited client domains
- Everything in Site, per client
- Unlimited client domains
- Shared brand presets across projects
- One register, per-client accountability
- Priority support
Pricing announced at launch
Talk to salesLaunching when it's ready — no early-access sales.
Questions & answers
The four things everyone asks first.
Will Bold Consent slow my site down?
No — that's its reason to exist. The banner itself is a fraction of a typical CMP's weight, and analytics scripts run in a Web Worker off the main thread. Your PageSpeed score stays yours.
What happens when a visitor rejects consent?
Nothing loads. Marketing scripts never start, and Consent Mode reports “denied” signals — Google can model conversions without cookies, and you track no one without permission.
Can I match it to my brand?
Yes — colors, typography and copy are configurable via design tokens. The banner is meant to look like part of your site.
Do you support TCF?
We're starting with Consent Mode v2 — it covers the vast majority of sites. TCF support is on the roadmap.
See the banner that pays for itself in milliseconds.
Book a demo, or open letsgobold.com — the consent banner there is the product, running in production.