Skip to content
Scan & Tracker Intelligence

Discover

Beta

The cookie table your disclosure is supposed to match.

Each cookie with its name, domain, path, observed lifetime, first- or third-party status, the service that set it, its assigned category and the dates it was first and last seen.

Cookie Inventory

  • Name, domain & path
  • Observed lifetime
  • First/third party
  • Vendor & category

How it helps

What you get with Cookie Inventory

1

Observed lifetime, not claimed

What the site actually set, which is regularly not what a vendor's documentation says.

2

Category is a decision, not a guess

Proposed from the signature set, confirmed by you — and the disclosure is generated from the confirmed state.

3

Feeds the policy page

The cookie disclosure is generated from this inventory, so the two cannot describe different websites.

Know what runs before you ask visitors to trust it.

Start with a scan of what your website loads today. The list is usually longer than the team expects, and that is the useful part.

No code to install for a scan Public pages only DotCensus runs on DotCensus