Sleight privacy policy

Publisher: slowhandsdev
Contact: https://github.com/slowhandsdev/sleight-privacy/issues
Effective date: 16 November 2026

Sleight — Session Switcher saves a site's login state as named profiles and switches between them. This policy says what it captures, where that data lives and how to delete it.

What Sleight captures

When you save a profile for a site, Sleight reads that site's:

The site is the whole registrable domain. For example, example.com and its subdomains count as one site. Sleight captures this only for sites where you save a profile, and only when you start a save, a switch, a new profile or a blank session. Sleight also finishes a switch you started if it was interrupted, for example if the browser closed part-way. When you switch, Sleight also saves the site's current state back into the active profile.

When you open Sleight's popup on a site that has profiles, Sleight reads that site's cookies to tell whether the current session is saved. It does not store them unless you then save or switch.

Cookies and storage can contain login tokens. Sleight treats them as credentials.

Sleight also stores the profile names you choose, the site each profile belongs to, and which profile is active for each site.

Where it is stored

All of it is stored in your browser's local extension storage, on your device. Profiles are not encrypted there. Anyone who can read your browser's data on this device can read them. Only export files are encrypted.

Sleight does not use browser sync storage, so it does not upload anything to your Google account.

What is transmitted

Nothing. Sleight makes no network requests. It has no analytics, no crash reporting and no remote code. It does not sell your data, share it with anyone or use it for any purpose other than saving and switching sessions.

Export files

On the options page you can export selected profiles to a file. The file is encrypted with a passphrase you choose. It contains live logins. Anyone who has the file and the passphrase can sign in as those accounts. Keep it safe, and delete it when you no longer need it. Sleight does not keep a copy of the file or the passphrase.

Toolbar badge

The toolbar badge shows which profile is active on the current tab's site. To do this, Sleight reads the address (URL) of your open tabs. The browser makes a tab's address visible to Sleight only for sites you have given it access to. Sleight does not store these addresses and does not send them anywhere.

Site access

Sleight asks the browser for access to a site the first time you save a profile there. You can see and remove this access in the browser's extension settings. Sleight does not request access to all sites up front.

Incognito

Sleight is not available in incognito windows.

Deleting your data

Deleting a profile or all data does not log you out of a site. Whatever cookies and storage the browser currently holds for the site stay as they are.

Changes to this policy

If this policy changes, the new version will be published at https://slowhandsdev.github.io/sleight-privacy/ with a new effective date.

Contact

Questions about this policy: open an issue at https://github.com/slowhandsdev/sleight-privacy/issues