Where Does Cookie AutoDelete Store Rules and Lists?
Cookie AutoDelete keeps domain lists and settings in per-profile browser extension storage, with export for moves.
Last updated
Cookie AutoDelete stores its lists in extension storage inside the active profile. Greylisted and whitelisted domains, container rules, and notification settings share that space. There is no user-facing rules file.
New profiles start with empty lists, so logins you meant to keep get swept on tab close. The settings export rescues years of tuning in one file. Keep it with your other browser backups.
Where Cookie AutoDelete stores this, by platform
%LocalAppData%\Google\Chrome\User Data\Default\Extensions (per profile)
Domain lists per profile. Export from settings before wiping. Import restores greylists and container rules without retraining.
~/Library/Application Support/Google/Chrome/Default/Extensions (per profile)
Same model on Mac. Firefox keeps it under ~/Library/Application Support/Firefox/Profiles. Prefer the export file over folder copies.
~/.config/google-chrome/Default/Extensions (per profile)
Chromium profiles under ~/.config and Firefox under ~/.mozilla. Same export workflow. Rules apply on tab close with no local log.
Frequently asked questions
How do I move Cookie AutoDelete rules to a new browser?
Open the settings and export to a file, then import on the new profile. Greylists, whitelists, and container rules travel in that file. Fresh installs protect with defaults immediately.
Do cookie rules sync between profiles?
No. Each profile holds its own lists in extension storage. The export file is the migration path. Without it the new profile relearns nothing and starts empty.
Notice an outdated path? Let us know.