How to whitelist cookies in Chrome

TL;DR: Chrome has a built-in “Sites that can always use cookies” exception list under Settings → Privacy → Cookies. For richer whitelist behavior — subdomain inheritance, wildcard patterns, greylist, and per-tab auto-delete exemption — use CookieVault Guardian’s whitelist instead.

Whitelisting cookies in Chrome is the practice of exempting specific trusted domains from any cookie-clearing policy — whether that is Chrome’s built-in “Clear on exit,” a manual bulk delete, or a per-tab auto-delete extension. The goal is simple: keep logins for the sites you use daily while everything else gets cleaned.

Two approaches compared

In short: Chrome’s built-in whitelist is adequate for “Clear on exit” users. Guardian’s whitelist is the upgrade for users who want per-tab cleanup, broader storage coverage, wildcard support, and cross-device sync.

Method 1: Chrome built-in whitelist

In short: Settings → Privacy → Cookies → “Sites that can always use cookies” → Add. Works for “Clear on exit” exemption; does not work with per-tab extensions.

Eight steps:

1. Open Chrome Settings (three-dot menu → Settings)
2. Navigate to Privacy and security → Cookies and other site data
3. Scroll to “Customized behaviors”
4. Click “Add” under “Sites that can always use cookies”
5. Enter the domain with [*.] prefix for subdomain inheritance (e.g., [*.]example.com)
6. Save
7. Repeat for email, bank, code host, work tools, password manager
8. Test: enable “Clear on exit,” close Chrome, reopen — whitelisted sites should remain logged in

Limitation: this whitelist only affects Chrome’s own “Clear on exit” and third-party cookie blocking. It does not exempt domains from per-tab auto-delete extensions like Guardian.

Method 2: CookieVault Guardian whitelist

In short: Install Guardian → visit site → click toolbar icon → “Add to whitelist.” Subdomain inheritance is on by default. Wildcard patterns for advanced rules. Greylist for session-only keep.

Six steps:

1. Install CookieVault Guardian from the Chrome Web Store
2. Visit a site you trust (Gmail, GitHub, your bank)
3. Click the Guardian toolbar icon → “Add to whitelist”
4. The domain and its subdomains are automatically exempted from tab-close cleanup
5. For advanced rules, open Settings → Whitelist and add wildcard entries (e.g., *.googleapis.com)
6. Use the greylist button for sites you want to keep this session but clean next time

Recommended starter whitelist

A five-entry baseline that covers most users:

• Primary email (Gmail / Outlook / Proton)
• Code host (GitHub / GitLab)
• Work tools (Linear, Notion, Slack, Figma — whichever you use)
• Bank
• Password manager web UI (1Password / Bitwarden)

Everything else: clean on tab close (Guardian) or clean on browser exit (Chrome built-in).

See also

• Auto-delete cookies on tab close — the Guardian setup guide
• Clear cookies but stay logged in — selective deletion for a one-off cleanup
• Cookie whitelist feature — deep dive on Guardian’s whitelist architecture
• CookieVault Guardian — product overview
• How to delete cookies in Chrome — manual deletion methods
• What is a cookie? — the underlying protocol