Privacy Policy — MultiSession Tabs

What data we collect

None. MultiSession Tabs does not collect, transmit, sell, or share any personal data with us or any third party. There is no analytics, no tracking, and no external server — the extension has no backend.

What the extension handles locally (on your device only)

• Login session cookies for the sites you configure. To keep each tab signed in to a different account, the extension reads and re-applies the session cookie per tab. These values are held in your browser's in-memory session storage (chrome.storage.session), are never written to disk by the extension, are cleared when you close the browser, and never leave your device.
• Your settings — the list of hosts you add and the containers you create (their names and colours) — saved locally in your browser (chrome.storage.local). This contains no passwords or credentials.

Permissions and why they are used

• declarativeNetRequest / webRequest — to read and rewrite the Cookie header per tab so each tab uses its own session. Read-only observation of response headers; nothing is transmitted.
• storage — to save your containers and host list locally.
• tabs / scripting — to associate a tab with a container, show its badge, open the configured site, and isolate per-tab page storage.
• Host access — requested at runtime only for the specific site(s) you add in Options. The extension does nothing on any site you have not configured.

Third parties

None. No data is shared with, sold to, or transferred to any third party for any purpose.

Changes to this policy

If this policy changes, the updated version will be posted on this page with a new "last updated" date.

Contact

Questions about this policy: siripong.api43@gmail.com