Design a cookie banner. Check it before you build it.
Configure layout, theme, consent granularity and copy — and see both the visitor experience and the compliance consequence, checked against India's DPDP Act as you edit.
Runs entirely in your browser. No sign-up, no cookies set, nothing sent anywhere.
Configuration
Where the first layer sits on the page.
Notice and consent
We process personal data for the itemised purposes below. You can give or withdraw consent for each purpose, and request details in your preferred language.
48 cookies across 4 purposes · India
Evaluated live against DPDP Act.
- 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
- · Notice must itemise the personal data and the specific purpose — not a category summary.
- · The notice must be available in English and the scheduled Indian languages.
- · Withdrawal must be as easy as giving consent, and routes to the Data Protection Board must be shown.
Built around the DPDP Act
Opt-in by default, itemised purposes, and a decline that carries the same weight as consent — the defaults are the ones the Act actually asks for.
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 a real banner?+
It is the same experience model — layouts, granularity, DPDP 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 declining carry the same weight as consenting?+
Because the DPDP Act treats consent as valid only where it is freely given, and withdrawal has to be as easy as giving it. A decline buried in a text link beside a full-width accept button is precisely the pattern an audit picks up.
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 anyone writes the implementation ticket.
Does a compliant banner make my site DPDP compliant?+
No. The banner is the consent surface. The Act also expects an itemised notice covering the personal data and the specific purpose, a standing route to withdraw, an answer to data principal requests, and the notice available in the scheduled Indian languages. The free audit on this site checks what a visitor can see of all that.