Cookie policy
The page listing every cookie and tracker you set: its name, who set it, what it does, how long it lasts, and how to switch it off.
See it
What it is
Three things get confused constantly. The banner is the mechanism that asks. The privacy policy is the whole story of personal data. The cookie policy is the itemized receipt: every cookie, pixel, local storage key, and SDK you set, with the name, who set it, what it does, how long it lives, and whether it is first or third party.
In practice it is a table grouped by purpose category: strictly necessary, functional, analytics, marketing. Rows read like '_ga, Google Analytics, distinguishes users, 2 years, third party'. Around the table sit a plain explanation of what cookies are, how to change your choices (linking back to the banner), and how to clear them in the browser. Many teams publish it as a section inside the privacy policy, which is fine as long as the banner links straight to it.
Gotcha: it is stale the day marketing adds a pixel. Automated scanners help, but they only report what fired during their crawl, so anything behind login, checkout, or a specific country's geo rules is invisible to them and quietly missing from your table. Re-scan on a schedule and add 'update the cookie policy' to the checklist for shipping any new tag.
Ask AI for it
Write a cookie policy page for this site. Start with two short paragraphs in plain English explaining what cookies and similar technologies (local storage, pixels, SDKs) are and why this site uses them. Then render one table per purpose category (strictly necessary, functional, analytics, marketing) with the columns: cookie name, provider, first or third party, purpose in one sentence, and duration. Populate it from the list of tags and vendors below, and mark anything you cannot verify as a bracketed TODO instead of guessing a name or a lifetime. Finish with a section on changing your choices that links to the cookie settings control, a short note on clearing cookies in major browsers, a contact address, and a last-updated date. Make the tables responsive and horizontally scrollable on mobile.