Guise — Privacy Policy

The short version

Guise has no server, no accounts and no ads, and it transmits nothing — nothing you do in Guise ever leaves your computer. It does store data on your device, because that is the whole point of session profiles: a saved profile is a snapshot of a site's cookies, kept locally so you can switch back into that account later. Everything below explains exactly what is kept and where.

What Guise stores on your device

Guise transmits no data to us or to anyone else. It has no server, no account system and no analytics inside the extension. Everything listed here is written to your browser's own extension storage (chrome.storage.local) and never leaves your computer:

• Session profiles — when you save a profile, Guise stores a snapshot of that site's cookies under a name you choose, together with the site's domain and any note you add. Because cookies are what keep you signed in, a saved profile can contain authentication tokens for that site. This is what makes switching accounts without re-login possible. Profiles stay on your device, are never uploaded, and are deleted when you delete the profile or remove the extension.
• Which profile is active for a site, so the popup can show it.
• Your preferences — light/dark theme, and whether you asked not to be shown the switch confirmation again.
• A local counter used to decide whether the “leave a review” line has already been shown. It is a number on your device, not an identifier, and it is not sent anywhere.

If you use Backup & restore or export to cookies.txt, the resulting file is written by your browser to wherever you choose to save it. That file contains your cookie data — treat it like a password file. Guise never uploads it.

Guise collects no browsing history, no usage analytics and no personal data beyond the cookie data described above. If a future version adds optional anonymous usage statistics, this policy and the Chrome Web Store data disclosure will be updated first.

Permissions

• cookies — the core function: read, create, edit and delete cookies for the site you are viewing.
• optional host access — Guise does not request access to all sites up front. When you open the popup on a site, it asks for permission for that site only — or, if you prefer, you can grant access to all sites in one click. Cookies are read and written only for sites you have allowed.
• activeTab — lets Guise see the address of the tab you are on when you open the popup, so it can show the cookies for that site, and reload that tab after you switch profiles. It grants nothing until you click the extension, and nothing about other tabs.
• storage — keeps the session profiles and preferences described above, on your device only.

All cookie data stays in your browser. Guise has no server and transmits nothing.

Website analytics

This website (guise.getoverlab.dev) uses Google Analytics to count visits. This concerns the website only — the extension itself contains no analytics.

Contact

Overlab — via the Chrome Web Store listing support tab.