Fill in these first
- Website and owner: [site name, company, contact email]
- Cookies and tags in use: [paste a scan, or list each with provider type, purpose and expiry]
- Visitors' main countries: [e.g. India, EU, UK, US]
- Consent tool, if any: [e.g. a consent management platform, or none yet]
- Privacy policy URL: [URL]
Task
Group every cookie correctly, explain each in plain words, and give visitors a real choice before anything non-essential is set.
Output format
- | Cookie or tag | Set by: first or third party | Category | Purpose in plain words | Expiry |
- Banner: a heading under 40 characters, body under 200 characters, and three buttons of equal weight: Accept all, Reject all, Manage choices.
- Settings panel: one toggle per category with a one-line description; necessary cookies shown as always on, every other toggle off by default.
- The cookie policy in Markdown: what cookies are, categories used, the full table, how to change choices later, how long choices are kept, contact for questions, last updated date.
- A setup checklist for the developer: no analytics or ad tag fires before consent, the choice is saved, a link in the footer reopens the settings.
Rules
- Necessary means the site cannot work without it; analytics is never necessary.
- Reject must be as easy as accept, on the first layer of the banner.
- No pre-ticked boxes and no consent implied by scrolling.
- Do not name a cookie's provider when the input does not; write [provider].
- Add one line that the text should be reviewed against the laws of the visitors' countries.






