Where Does Privacy Badger Store Tracker Data?
Privacy Badger keeps tracker decisions and settings in per-profile browser extension storage, with export for moves.
Last updated
Privacy Badger stores its tracker decisions in extension storage inside the active profile. Learned domains, slider positions, and options live there. There is no standalone database file.
New profiles start naive and block less until retrained. That learning curve is the migration cost the export avoids. One file carries the whole training history across machines.
Where Privacy Badger stores this, by platform
%LocalAppData%\Google\Chrome\User Data\Default\Extensions (per profile)
Learned tracker data per profile. Export from settings before browser wipes. Import restores sliders and trusted sites without retraining.
~/Library/Application Support/Google/Chrome/Default/Extensions (per profile)
Same model on Mac across Chromium and Firefox builds. Firefox keeps it under ~/Library/Application Support/Firefox/Profiles. Prefer the export file.
Frequently asked questions
How do I move Privacy Badger data to a new browser?
Use the export option in the extension settings, then import on the new profile. Learned tracker sliders and disabled sites travel in that file. Seed data refreshes itself afterward.
Does Privacy Badger re-learn trackers automatically?
Partly. It re-learns quickly from fresh browsing, but custom slider positions and trusted sites need the file. Exporting preserves weeks of training in one step.
Notice an outdated path? Let us know.