
Per-category toggles
Each cookie category appears as a row with:- Category name and description — editable in the dashboard, translated per language.
- A toggle — on/off for that category. The Necessary category is always on and shown as locked.
- An expandable cookie list — the cookies mapped to that category from your latest scan, with provider, purpose, and expiry.
Granular consent enforcement
When a visitor saves preferences, the banner script immediately:- Stores the per-category consent state in a first-party cookie.
- Releases any blocked scripts whose category is now allowed.
- Leaves scripts in refused categories blocked — no page reload required for newly granted categories.
Consent is per-category, not per-cookie. Mapping cookies accurately to categories (see Cookie Categories) is what makes granular consent meaningful.
Consent receipts and logging
Every consent decision generates a consent receipt recorded against your organization:| Field | Description |
|---|---|
| Receipt ID | Unique identifier for the consent event |
| Timestamp | UTC time the decision was made |
| Categories | The exact per-category grant/deny state |
| Action | accept_all, reject_all, or save_preferences |
| Banner version | The published banner configuration in force at the time |