Privacy Policy
Last updated 15 October 2026
Idently does not collect or transmit any of your data. It makes no network requests of any kind. There is no account, no analytics, no tracking and no Idently server. Everything it stores is kept by Firefox, on your own computer.
What Idently stores
In Firefox's local extension storage, on this computer only:
- Your sessions. For each one: the name, notes and colour you gave it, the site it belongs to, the address it opens, when it was created and last used, and the ID of the Firefox container that holds it.
- Where you parked the notch along the top of the page.
In Firefox's sync storage:
- Your site rules (a site, a selector and an optional pattern for each) and whether the notch is shown.
Sync storage stays on this computer unless you use Firefox Sync, in which case Firefox copies it to your other devices through your own Firefox account, with Mozilla's end-to-end encryption. Idently never sees or handles that transfer.
Your logins themselves, the cookies and site data, are kept by Firefox inside each container, exactly as they would be without Idently. Uninstalling Idently deletes everything listed above. Firefox keeps the containers and their logins, which is what lets Recover containers adopt them back after a reinstall; remove them in Firefox's settings if you don't want them.
What Idently reads
- Cookie counts. When you open the popup, Idently checks whether each session's container still has cookies for its own site, to flag sessions that look logged out. It only checks whether matching cookies exist, on your computer, and stores nothing from them.
- One field on the page, if you set up a rule. On a tab belonging to an unnamed session, a site rule reads the one element it points at (usually the email field on a sign-in form) to name the session. It stops once the session has a name. Without a rule for the site, nothing on the page is read.
- Field candidates, when you ask. Detect automatically in the rule builder scans the page you're on for fields that look like an account name or email, and shows them to you. It never reads password fields.
Backups
Export writes your sessions to a JSON file that you save wherever you choose. If you tick Include cookies / session data, the file also contains the cookies from each session's container, which are live logins: anyone with the file can sign in as you, so treat it like a password. Idently never sends an export anywhere; it only hands it to Firefox's download.
Permissions, and why
| Permission | Used for |
|---|---|
contextualIdentities | Creating, renaming and removing the Firefox containers your sessions live in. |
cookies | Opening tabs in a container, the logged-out check, and exporting or importing cookies when you ask. |
tabs | Opening a session in a new tab and knowing which session the current tab belongs to. |
tabGroups | Filing a session's tabs into a tab group named after its site. |
storage | Keeping the sessions, rules and settings described above. |
| Access to all websites | Showing the notch on whichever site a session is for, and running site rules there. Sessions can be for any site, including localhost. |
Network requests
None. Idently does not contact any server, Idently's or anyone else's. There is no telemetry, crash reporting or usage tracking. The only traffic is the pages you open yourself.
Clipboard
Clicking the notch copies the session's name to your clipboard. Idently never reads the clipboard.
Changes and contact
Any change to this policy is published here with a new date, and the full history is in the source repository. For questions, open an issue on GitHub.