MultiLogin Tabs — Privacy Policy — Qiksy
Last updated: 29 July 2026
Who we are
MultiLogin Tabs is a Chrome extension by Qiksy that runs several accounts of the same website side by side, one per tab. This policy explains exactly what browser data it touches, why, and where it stays. Contact: [email protected].
What the extension accesses, and why
To keep two logins on one site from overwriting each other, the extension intercepts the browser state that carries identity — per tab, and only on tabs you have assigned to a session:
- Cookies — HTTP response cookies and JavaScript-set cookies are captured and held in an isolated per-session jar, so each tab sends only its own.
- localStorage — keys are transparently prefixed, giving each session its own namespace.
- IndexedDB — database names are prefixed per session.
- Cache Storage — cache names are prefixed per session.
- Tab URLs — read to work out which cookie domain applies. Never stored, never transmitted.
Where it is stored
Session data lives in chrome.storage.session, which the browser clears when it closes. Your settings live in chrome.storage.local. Both are on your machine. Nothing is sent to an external server, an analytics service, or a third party — the extension makes no network requests of its own.
What we collect
Nothing. To be specific, MultiLogin Tabs has no analytics or telemetry, no tracking pixels or scripts, no user accounts and no registration, no network calls to any server of ours, and shares no data with anyone.
Why each permission is needed
| Permission | What it is for |
|---|---|
cookies | Read cookies on an assigned tab to populate that session’s jar. |
declarativeNetRequest | Rewrite the outgoing Cookie header so each tab sends its own session’s cookies. |
webRequest | Capture incoming Set-Cookie headers from server responses. |
storage | Keep session jars and your settings on your machine. |
tabs | Read the active tab’s URL and id to map it to a session. |
scripting | Inject the session marker when you assign or clear a tab. |
host_permissions (<all_urls>) | Cookie interception has to work on whichever site you choose to isolate. No data is collected from any website. |
An honest limit
Isolation here is a best-effort container built from header rewriting and JavaScript virtualization — not a true browser container. It keeps ordinary logins apart reliably, and we would rather say so than imply a guarantee the technique cannot make.
Changes to this policy
A material change moves the date at the top and ships with the extension update. The core principle does not move: no data ever leaves your browser.