Multisession Privacy Policy

Local-First, No Accounts, No Tracking

Local-first, no accounts, no tracking. Multisession stores all session data only in your browser via chrome.storage.local. We do not operate servers that receive your browsing data, and the extension makes no network requests of its own.

What Stays on Your Device

• 📁 Session registry (names, colors, fingerprint seeds, stats).
• 📁 Per-session vaults: cookies, localStorage, sessionStorage, IndexedDB snapshots.
• 📁 Active session ID and pending-restore map for crash recovery.

Why These Permissions

• 🔑 cookies — back up and restore per-session cookies during switch-and-replace.
• 🔑 storage — persist sessions and vaults locally; recover after restart.
• 🔑 browsingData — wipe DOM storage, IndexedDB and caches so sessions are truly isolated.
• 🔑 tabs + scripting — dump / restore per-tab storage and reload tabs after a switch.
• 🔑 declarativeNetRequest — apply strict anti-detect header rules only when you opt in per profile.
• 🔑 host_permissions <all_urls> — run the storage bridge on any site you visit so any origin can be isolated.
• 🔑 unlimitedStorage + alarms — hold up to 20 session vaults and keep long switches alive.

What We Never Do

• ⛔ No analytics, telemetry, crash reporters, or remote logging.
• ⛔ No sale, sharing, or syncing of your data to HtmlRunner or third parties.
• ⛔ No history, bookmarks, or passwords access — only data the switch engine needs.

Retention & Deletion

Data lives until you delete it: right-click → Delete per profile, or Danger zone → delete all inactive sessions. Uninstalling the extension removes its chrome.storage.local area from the browser.

Children & Changes

Not directed at children under 13. If this policy changes materially we will bump the extension version and note it in the About changelog. Questions: contact@htmlrunner.com.