What it is
Cookies, localStorage, IndexedDB, the cache and service workers are the ways a site remembers you on purpose. They are not fingerprints — you can clear them — but they are the baseline every fingerprint is designed to survive, and the first thing linking two accounts if they are shared.
How websites read it
document.cookie
localStorage.setItem('k', 'v'); indexedDB.open('db');
// isolation = a separate browser directory per profile, not a flagSites drop identifiers into several stores at once and rebuild the ones you clear from the ones you kept. Cache-based and ETag-based identifiers survive a plain cookie wipe.
Why it identifies you
Storage is the strongest link there is when it is present: an ID the site wrote itself. Fingerprinting exists to re-identify you after it is gone, and to notice when two "different" people carry the same stored IDs.
How risk-control systems use it
Risk engines check whether a stored ID reappears under a new account, whether the storage state looks freshly wiped on every visit, and whether cookies and local storage are disabled outright — which is rare for humans and common for scripts.
Common mistakes
Running several accounts in one browser profile; clearing cookies but not IndexedDB or the cache; disabling storage entirely; importing cookies from one profile into another.
Mango is accepting waitlist registrations. These capabilities describe its first release; client access opens with invitations.
How Mango Browser handles it
Not applicableEvery profile is a fully separate browser directory: cookies, storage, cache and extensions never cross.
Check yours
Jump to this signal in your scan results.