Cookie declaration table

The cookie declaration is the human-readable list of every cookie your site sets, its purpose, the provider that sets it, and how long it lives — the artifact most privacy regulations expect you to publish (GDPR Art. 13, and effectively required by most DPAs' cookie-banner guidance). Cookie Munch generates and keeps it current for you from scanner results.

Viewing the table

Dashboard → Cookies shows every cookie detected for the active property, grouped into a badge-colored category and sortable/filterable by:

Use the search box to find a cookie by name, domain, provider, or purpose, and the category/provider dropdowns to narrow the list. A Scanned on badge shows when the underlying snapshot was last refreshed.

Publishing it on your site

The declaration is also available as a drop-in embeddable widget — no dashboard access required for whoever maintains your privacy policy page:

<script src="https://YOUR-CMP-DOMAIN/cookie-declaration.js" data-cbid="YOUR_SITE_ID"></script>

Drop that tag anywhere in your privacy policy or cookie policy page. It:

• Finds its own <script> tag and reads data-cbid.

• Fetches the live /api/v1/:cbid/cookies feed for that site.

• Renders a self-contained HTML table, grouped by category, with a "Last updated" timestamp — no CSS or JS dependencies required from the host page.

Note: The embed always reflects the current snapshot. There's nothing to re-publish when cookies change — the widget updates itself on the visitor's next page load.

Keeping it accurate

The declaration is only as good as the underlying scan. If you add a new analytics/marketing script to your site:

1. Run a manual scan (Cookies → Scan now), or wait for the next scheduled crawl.

2. Review any cookies that land in Unclassified and confirm their category — unmatched cookies default to Unclassified until a human (or a future scanner-database update) classifies them.

See also: Cookie scanner · REST consent for the underlying /api/v1/:cbid/cookies feed.