Where Does Disconnect Store Settings and Blocklists?
Disconnect keeps tracker protection lists in per-profile extension storage with blocklists updating themselves.
Last updated
Disconnect stores settings in extension storage inside the active profile. Tracker lists update with the extension itself. Custom allowlist entries are the only personal data involved.
That thin state makes migration nearly moot. New profiles behave identically within a version. Re-add the handful of custom allowances and move on.
Where Disconnect stores this, by platform
%LocalAppData%\Google\Chrome\User Data\Default\Extensions (per profile, minimal state)
Settings per profile with almost nothing personal. Blocklists update with the extension. Custom allowances need manual re-entry.
~/Library/Application Support/Google/Chrome/Default/Extensions (per profile, minimal state)
Same minimal model on Mac. Fresh installs match within a version. Nothing here needs a backup routine.
~/.config/google-chrome/Default/Extensions (per profile, minimal state)
Same storage under profile trees on Linux. Tracker protection needs no migration planning.
Frequently asked questions
How do I move Disconnect settings to a new browser?
Fresh installs protect with defaults immediately, so little needs moving. Custom allowlists need manual re-entry. There is no export or account to transfer.
Does Disconnect sync between profiles?
No. Each profile holds its own copy in extension storage. Blocklists refresh from updates on every install identically. Only custom choices differ.
Notice an outdated path? Let us know.