Where Does Decentraleyes Store Settings and Libraries?
Decentraleyes keeps its settings in per-profile browser extension storage while bundled libraries update with the extension.
Last updated
Decentraleyes stores a small set of toggles in extension storage inside the active profile. The local CDN libraries it injects ship with the extension package, not in user data.
That makes migration nearly trivial. Fresh installs behave identically within a version. Only custom testing-domain entries need manual re-entry, and most users have none.
Where Decentraleyes stores this, by platform
%LocalAppData%\Google\Chrome\User Data\Default\Extensions (per profile)
Toggles per profile with almost nothing personal. Mirror options by hand on moves. Bundled libraries refresh with extension updates automatically.
~/Library/Application Support/Google/Chrome/Default/Extensions (per profile)
Same minimal model on Mac. Firefox keeps it under ~/Library/Application Support/Firefox/Profiles. Nothing here needs a backup routine.
~/.config/google-chrome/Default/Extensions (per profile)
Chromium profiles under ~/.config and Firefox under ~/.mozilla. Same story: options mirror by hand, libraries update themselves.
Frequently asked questions
How do I move Decentraleyes settings to a new browser?
Open the options and note your toggles, then mirror them on the new profile. There is little to move: a few switches plus the testing utility. Fresh installs protect with defaults.
What exactly needs backing up?
No local file to back up beyond the options themselves. Bundled libraries ship inside the extension package and refresh on update. Screenshots of the options page suffice as documentation.
Notice an outdated path? Let us know.