Know what’s on your site before a plaintiff’s firm does
A free privacy audit shows which cookies, pixels and trackers are running — and which ones commonly appear in privacy claims.
Every cookie has a name, and most of those names mean nothing to the people who find them. _fbp, IDE, cf_clearance, hubspotutk: they show up in browser tools, scan reports and demand letters, usually with no explanation attached.
The Captain Compliance cookie database explains them in plain language. Look up a cookie by name to see who sets it, what it does, how it fits into the main types of cookies, and whether it needs consent before it runs. Each entry links to a full guide.
Scan My Website for Cookies Read the Types of Cookies Guide
How to Use the Cookie Database
Find the cookie name. Open your browser’s developer tools, go to Application (Chrome) or Storage (Firefox and Safari), and look under Cookies. Or run a cookie scan to list every cookie your site sets.
Look it up below. Cookies are grouped by type. Use your browser’s find feature (Ctrl+F or Cmd+F) to jump straight to a name.
Check the consent rule for its type. The type decides whether a cookie can run on page load or has to wait for the visitor’s choice.
- Strictly Necessary Cookies and Security Examples
- Functional and Preference Cookies
- Analytics Cookies
- Marketing and Advertising Cookies
Strictly Necessary Cookies and Security Examples
Strictly necessary cookies (in the ePrivacy Article 5(3) sense) are usually allowed without consent, but they still belong in your cookie notice. ‘Security’ cookies are exempt only when they are strictly necessary for a service the user requested, not as a separate category. More on this type.
| Cookie | Set by | What it does |
|---|---|---|
PHPSESSID |
PHP | Holds a session ID so the site remembers a visitor from page to page. |
INGRESSCOOKIE |
Kubernetes Ingress NGINX | Keeps a visitor on the same server behind a load balancer. |
cf_clearance |
Cloudflare | Shows Cloudflare that the visitor already passed a bot challenge. |
_abck |
Akamai | Used by Akamai Bot Manager to spot automated traffic. |
pxvid |
HUMAN (PerimeterX) | Bot-detection visitor ID used to block automated attacks. |
_grecaptcha |
Google reCAPTCHA | Helps reCAPTCHA tell real people from bots. |
__stripe_sid |
Stripe | Fraud-prevention session cookie set during Stripe checkout. |
tsrce |
PayPal | PayPal cookie set during PayPal checkout flows. |
nsid |
PayPal | PayPal session cookie that supports secure checkout. |
HSID |
Google account cookie used to protect signed-in users. | |
datr |
Meta | Meta browser identifier used for security and fraud prevention. |
_js_datr |
Meta | JavaScript-set version of datr used for Meta security checks. |
CookieConsent |
Cookiebot | Stores a visitor’s consent choices for a Cookiebot banner. |
Captain |
Captain Compliance | Stores a visitor’s consent choices for a Captain Compliance banner. |
Functional and Preference Cookies
Often need consent in the EU, especially when they come from embedded third-party tools. More on this type.
| Cookie | Set by | What it does |
|---|---|---|
YSC |
YouTube | Session cookie set by embedded YouTube videos. |
lidc |
Routes visitors to the right LinkedIn data center. | |
messagesutk |
HubSpot | Remembers a visitor’s HubSpot chat conversations. |
Analytics Cookies
Need consent in most of the EU and can raise opt-out and wiretapping issues in the US. More on this type.
| Cookie | Set by | What it does |
|---|---|---|
_gid |
Google Analytics | Tells visitors apart for 24 hours in Google Analytics. |
__utma |
Google Analytics (legacy) | Legacy Google Analytics cookie that counts visitors and visits. |
__utmz |
Google Analytics (legacy) | Legacy Google Analytics cookie that records traffic sources. |
_clck |
Microsoft Clarity | Stores a Clarity user ID across visits. |
_clsk |
Microsoft Clarity | Connects page views into one Clarity session recording. |
ANONCHK |
Microsoft | Microsoft cookie used alongside Clarity and Bing. |
_hjAbsoluteSessionInProgress |
Hotjar | Marks a visitor’s first Hotjar session. |
hubspotutk |
HubSpot | Visitor ID HubSpot uses to connect visits to contact records. |
vuid |
Vimeo | Analytics cookie set by embedded Vimeo videos. |
Marketing and Advertising Cookies
Need consent before they run in the EU and must honor opt-outs and Global Privacy Control in US privacy states. More on this type.
| Cookie | Set by | What it does |
|---|---|---|
_fbp |
Meta | Meta Pixel browser ID used to track and target ads. |
fr |
Meta | Meta advertising cookie used to deliver and measure ads. |
_uetvid |
Microsoft Advertising | UET visitor ID that tracks Microsoft Ads conversions across visits. |
_uetsid |
Microsoft Advertising | UET session ID for Microsoft Ads conversion tracking. |
MUID |
Microsoft | Microsoft user ID used across Microsoft sites and ads. |
_gcl_au |
Google Ads | Google conversion linker cookie for ad conversions. |
_gcl_aw |
Google Ads | Stores the Google Ads click ID that brought a visitor in. |
_gac |
Holds Google Ads campaign data for Analytics. | |
__gads |
Google ad-serving cookie on publisher sites. | |
IDE |
Google (DoubleClick) | DoubleClick cookie used to show and measure ads. |
test_cookie |
Google (DoubleClick) | Checks whether the browser accepts cookies for ad serving. |
DV |
Google cookie used for ad personalization. | |
NID |
Stores Google preferences and supports ad personalization. | |
SID |
Google account cookie also used to personalize ads. | |
APISID |
Google account cookie used to personalize ads and embeds. | |
SSID |
Google account cookie used to personalize ads. | |
_uit |
LinkedIn cookie used with LinkedIn ads and tracking. | |
ad-privacy |
Amazon | Amazon advertising cookie tied to ad privacy preferences. |
Don’t See Your Cookie?
We add new cookie guides regularly, but most websites set cookies that aren’t on any public list: custom cookies from your own developers, plugin cookies and tags added by marketing. The fastest way to see all of them is to scan your site. Our cookie scanner lists every cookie and tracker, sorts them by type and shows which ones fire before consent.
Get a Free Privacy Audit Talk to a Privacy Expert
Cookie Database FAQ
What is a cookie database?
A cookie database is a reference list of known website cookies that explains who sets each cookie, what it does and which category it falls into. Consent platforms use cookie databases to sort the cookies they find so they can block the right ones until visitors agree.
How do I find out what cookies my website uses?
You can see cookies in your browser’s developer tools, but that only shows what loaded on one visit. A cookie scanner crawls your site, records every cookie and tracker, and flags the ones that fire before consent.
Do all cookies need consent?
No. In the EU, strictly necessary cookies are exempt, but analytics, marketing and most third-party cookies need consent before they run. In US states with privacy laws, visitors must be able to opt out of cookies used to sell or share their data, including through Global Privacy Control.
Can the same cookie be in more than one category?
Yes. Cookies are also grouped by who sets them (first-party or third-party) and by how long they last (session or persistent). Our types of cookies guide explains how those groupings overlap.
Put this into practice
Turn privacy guidance into working controls.
Captain Compliance helps teams discover tracking technologies, enforce consent, manage privacy requests and document the evidence behind every decision.