Privacy Policy

What data does MultiLogin Tabs access?

To function, MultiLogin Tabs intercepts and manages the following browser data on a per-tab basis:

• Cookies — HTTP response cookies and JavaScript-set cookies are captured and stored in memory to maintain isolated session jars.
• localStorage — Keys are transparently prefixed so each session has its own namespace.
• IndexedDB — Database names are prefixed per-session.
• Cache Storage — Cache names are prefixed per-session.
• Tab URLs — Used to determine the cookie domain for isolation. Not stored or transmitted.

Where is this data stored?

All session data is stored locally in your browser using chrome.storage.session (cleared when the browser closes) and chrome.storage.local (for user settings only). No data is sent to any external server, analytics service, or third party.

Data collection

MultiLogin Tabs collects zero data. Specifically:

• No analytics or telemetry
• No tracking pixels or scripts
• No user accounts or registration
• No network requests to external servers
• No data shared with any third party

Permissions explained

• cookies — Read cookies on assigned tabs to populate session jars.
• declarativeNetRequest — Modify outgoing Cookie headers so each tab sends its own session's cookies.
• webRequest — Capture incoming Set-Cookie headers from server responses.
• storage — Persist session data and user settings locally.
• tabs — Get the active tab's URL and ID for session management.
• scripting — Inject session markers into tabs when assigning/unassigning.
• host_permissions (<all_urls>) — Required for cookie interception to work on any website. No data is collected from any website.

Open source

MultiLogin Tabs is open source. You can inspect the full source code to verify these claims.

Changes to this policy

If this privacy policy changes, the update will be published with the extension update. The core principle will remain: no data ever leaves your browser.

Last updated: April 2026