A cookie table for your cookie policy.
Pick the tools your site uses, or enter an address and we tick the ones we find. Add your own cookies, and copy a table grouped by category as HTML or Markdown. Every vendor row comes from that vendor’s own documentation.
Tick what your site uses
Each vendor comes with the cookies it documents. Some only appear with a certain setting, so they start unticked: open “Choose cookies” to check.
Your cookie table
Grouped by category, as HTML or Markdown. Vendor details as each vendor documents them, checked on 28 October 2026.
Preview
Pick a tool above or add a cookie of your own, and the table appears here.
HTML
No classes or styles, so it takes on your site’s look. Paste it into your cookie or privacy page.
<!-- Pick a tool or add a cookie of your own, and the table appears here. -->Markdown
For a static site, a docs page or anything else that reads Markdown tables.
<!-- Pick a tool or add a cookie of your own, and the table appears here. -->What a cookie table needs to say
A cookie declaration, often a table on your cookie policy page, tells visitors what your site stores on their device and who receives the data. The ePrivacy Directive ties consent to clear information about the purposes. In Planet49 (2019), the EU’s Court of Justice added that visitors must be told how long cookies stay active and whether third parties can access them. That’s why each row here has a name, a provider with a link to its privacy page, a purpose and a retention period.
Start with what your site loads. Enter an address and we check one page the way the cookie banner checker does: we fetch its HTML, read which tools it loads and which cookies its server sets, and tick what we recognise. Then go through the list yourself. A tag manager can load tools that aren’t in the HTML, and other pages can load different ones.
Open “Choose cookies” under a vendor to see what that vendor documents. Cookies that only appear with a certain setting, such as Cloudflare’s bot protection or HubSpot’s chat, start unticked. Then add the cookies your own site sets, such as a login, a cart or a language choice, with a purpose in plain words.
The table groups everything into necessary, preferences, statistics and marketing, the groups most banners use. The category is a starting point. Where a vendor names one, we follow it, and we put players and pixels from other companies under statistics or marketing. If your banner groups things differently, move the rows after you copy.
Copy the HTML into your cookie page, or the Markdown into a static site. The HTML has no classes or styles, so it takes on your site’s look, and it doesn’t link to gatelamp.com. The guide What to put in a cookie policy covers the rest of the page, with a template.
Every vendor row comes from that vendor’s own documentation, checked on 28 October 2026, with the sources below. Where a vendor doesn’t state a lifetime, the table says so. Vendors change names and lifetimes, so a table written once goes out of date. Gatelamp’scookie declaration will build it from what its scanner finds and keep it current.
Where each row comes from
Only the vendors’ own pages, read on . A vendor whose cookies we couldn’t source isn’t in the list.
| Vendor | Documentation | Privacy page in the table |
|---|---|---|
| Google Analytics 4 | ||
| Microsoft Clarity | Microsoft | |
| Hotjar | Hotjar (Contentsquare) | |
| Google Ads | ||
| Meta Pixel | Meta | |
| LinkedIn Insight Tag | ||
| TikTok Pixel | TikTok | |
| Microsoft Advertising (UET) | Microsoft | |
| YouTube embeds | Google (YouTube) | |
| Vimeo embeds | Vimeo | |
| HubSpot | HubSpot | |
| Stripe | Stripe | |
| Cloudflare | Cloudflare |
Cookie declarations: common questions
- What should a cookie declaration list?
- For each cookie or similar item: its name, who sets it, what it’s for, how long it stays and which category of your banner it falls under, with a link to the provider’s privacy page. The guide on cookie policies on this site explains where those points come from. This is general information, not legal advice.
- Where does the vendor data come from?
- From each vendor’s own documentation, such as Google’s cookie pages, Microsoft Learn and HubSpot’s knowledge base. The page lists the sources for every vendor and the date we checked them. Where a vendor doesn’t state a lifetime, the table says so instead of guessing.
- Is the table complete for my site?
- Not on its own. It lists what vendors document, vendors change cookie names and lifetimes, and your setup can add cookies or leave some out. Check your live site: the cookie banner checker on this site reads one page, and your browser’s developer tools show every cookie a page sets.
- Do I need a cookie declaration without a banner?
- It helps. A site that needs no consent still stores or loads something, and France’s regulator, the CNIL, recommends telling visitors about cookies that don’t need consent too. A short table with the necessary ones is enough.
- What happens to the address I scan?
- Our server fetches that one page and sends the result to your browser, which ticks the tools it found. We don’t store the address or the result, and we don’t log them. To stop abuse, Cloudflare counts how many checks come from one IP address per minute.
General information about the rules, not legal advice. A row that’s out of date? Tell us.
Read and use next
Where Gatelamp helps
Switch on early.
Join the waitlist for Gatelamp. We invite people in small groups, and waitlist members get the early price.
The form didn’t load. You can also join on our waitlist page.