Design a cookie banner. Check it before you build it.
Configure layout, theme, consent granularity and copy across four regulatory regimes — and see both the visitor experience and the compliance consequence in real time.
Runs entirely in your browser. No sign-up, no cookies set, nothing sent anywhere.
Configuration
Jurisdiction — changes defaults, required controls and copy.
We ask before we track
We use cookies to run this site, understand how it is used and personalise what you see. Nothing optional runs until you choose.
48 cookies across 4 purposes · European Union & UK
Evaluated live against GDPR / ePrivacy.
- A one-click reject is present at the first layer.
- Accept and reject share the same visual weight.
- Per-purpose choice is reachable from the first layer.
- Optional categories start off. Nothing non-essential runs before a choice is made.
- A persistent preferences route supports withdrawal after the banner is dismissed.
What this regime expects
- · Consent must be a clear affirmative action — no pre-ticked optional categories.
- · Rejecting must be as easy as accepting, at the same level and visual weight.
- · Consent must be withdrawable at any time, as easily as it was given.
Four regimes, one surface
Switch between GDPR, CCPA, DPDP and LGPD and watch the default state, required controls and copy change with the jurisdiction.
Live compliance feedback
Every configuration is checked as you edit, so a design that would fail an audit tells you before it reaches a sprint.
Real consent records
Interact with the preview and see the exact audit record the interaction would produce — including the case where nothing is recorded at all.
Questions about the playground
Is this the real ConsentCenter banner?+
It is the same experience model — layouts, granularity, regional defaults and the resulting consent record — running entirely in your browser. Nothing you configure here is sent anywhere, and no cookies are set by the preview.
Why does the reject button change when I switch jurisdictions?+
Because the requirement changes. Opt-in regimes such as GDPR and DPDP require refusing to be as easy as accepting, so the reject action is promoted to a full button. CCPA is a notice-and-opt-out regime, where a clear "Do Not Sell or Share" route is what matters.
Can I export what I build here?+
Not from the playground — it keeps nothing, which is the point: no account, no storage, no transmission. It is a place to settle layout, granularity and copy before implementation; the same choices become the configuration ConsentCenter Cookie Consent is initialised with once your property is onboarded.
Does the playground handle the Global Privacy Control signal?+
GPC is handled by the runtime rather than the banner design, because it must be honoured before the banner renders. The playground focuses on the experience layer; GPC support is built into ConsentCenter Cookie Consent itself.
Ship the banner you just designed
ConsentCenter Cookie Consent adds the parts a playground can't show: continuous scanning, real script blocking, GPC handling and an audit trail behind every choice.