See every session an Account holds

Which sites an Account is signed in to, when each session dies, and a deliberate way to hand one of them to another Account.

A cookie count tells you nothing. The Cookies tab opens on the SITES an Account has a session with — biggest first, each with its cookie count and its soonest expiry — and opens to the individual cookies underneath. No cookie’s value is ever shown; the value is the credential.

The jar, by siteSites first, cookies inside. Name, expiry and flags per cookie, with a cross to remove any one of them.
Clear one site, not the lotSign an Account out of one site and leave its other logins exactly where they were.
Hand a session over, on purposeCopy one site from one Account to another. The confirmation says plainly that the two are then one person to that site.
A hand-over leaves bot-management cookies behindSensor cookies are earned by the browser that holds them. The same one on two Accounts would announce that they are one machine, so copying a site leaves them behind — and the panel says how many did. A whole-jar import brings the jar as it was exported.
Still yours to move between machinesExport and import a whole jar as JSON or a cookies.txt, or import a folder of them across a fleet.
backup · sealed
Sealed on your machine
key from your passphrase — never sent
  • we see · ids · sizes · counts
  • we can’t · Accounts · proxies · logins
  • recovery · none
Works with
Accounts & isolationEvery Session a sealed browser of its own.Separation reportSee what still links your Accounts.FingerprintA coherent device per Account — and the proof.

Try it on your own accounts.

Download UmbraRead the guide