Cookie preferences & banner alignment
Align your public cookie banner and CMP with ePrivacy expectations: granular categories, equal prominence for accept and reject (or “decline non-essential”), and documentation of choices. Use the sections below to configure categories in this hub and track your implementation checklist.
Equal prominence for accept & reject
Regulators expect that refusing non-essential cookies is as easy as accepting them—no dark patterns, no buried “reject” link.
Good practice
- Two primary actions side by side: e.g. Decline non-essential and Accept all with similar size and contrast.
- Optional: a third neutral action Manage preferences opening granular toggles.
- No pre-ticked non-essential categories in “manage” screens.
Avoid
- Single “OK” or “Accept” with reject only via a tiny footer link or multiple clicks.
- Reject styled as a text link while accept is a solid button.
- Bundling unrelated purposes into one vague “accept”.
This app’s demo banner is implemented in frontend/cookie-banner.js—adjust copy and button order
there to match your policy before go-live.
ePrivacy & transparency checklist
Track your own review (saved in this browser only).
Consent categories (banner & CMP)
These categories drive what you disclose and what you log. They should mirror the toggles on your live site.
| Name | Code | Required | Legal basis | Retention | Records |
|---|
Document choices (evidence)
Article 7 GDPR requires you to demonstrate consent. Wire your production banner to your consent capture endpoint, then use the consent register to show what was accepted, when, and with which policy version—supporting audits and DPIAs.