Effective 28 October 2026
Privacy policy
Local Session Switcher does not collect data. There is no account, no analytics, no telemetry, and no server operated by the developer.
What the extension stores
Projects, test-user names, captured cookies, localStorage /
sessionStorage snapshots, optional login credentials, and auth-recipe
configuration are saved in chrome.storage.local inside your browser profile.
That store is not encrypted. Treat it like the rest of your local test setup: use test
accounts, not production secrets.
You can wipe it from Settings → Wipe all data, or by removing the extension.
What it sends
The extension makes no network requests of its own. The only HTTP calls it ever issues are the login, refresh, preflight, and verify URLs you configure on an auth recipe, and those URLs must resolve to one of the project's own origins. A seed file cannot point the extension at a third-party host.
Optional extra host permissions (for *.test, *.local, LAN IPs, and
similar local hosts) are requested only when you add those origins. They are not granted at
install time. Remote origins such as example.com are refused.
What it does not do
- No advertising, no trackers, no crash pings, no update phone-home beyond Chrome's own store/update checks.
- No sale or sharing of data — there is nothing to sell.
- No remote code. Everything runs from the installed package.
- IndexedDB on your sites is never read or written.
Unpacked / GitHub zip installs
If you load the extension from a GitHub Release zip rather than the Chrome Web Store, the same rules apply. GitHub may log that you downloaded the zip; that is GitHub's privacy policy, not this extension transmitting data.
Contact
Questions or reports: private vulnerability reporting or a GitHub issue for non-security topics. Do not paste live session cookies or passwords into issues.