Your browser has a fingerprint, and incognito mode doesn't erase it
When people learn about browser tracking, the usual advice is "use incognito" or "clear your cookies." Both help, but neither addresses a tracking technique that ignores cookies entirely: browser fingerprinting.
The idea is simple. Your browser leaks a surprising amount of information — the exact fonts installed on your system, your screen resolution, your GPU's rendering quirks, your timezone, what plugins you have. Taken individually, none of this identifies you. Combined, they form a fingerprint specific enough that most people are unique across the entire web.
Canvas fingerprinting is the most common variant: a website draws something invisible using the HTML5 canvas API, then reads back the pixel values. Because your GPU and drivers render things slightly differently from everyone else's, the output is consistent for you but distinct from others. No storage required. Reload the page, delete your cookies, open a fresh incognito window — the fingerprint is the same.
The EFF's Cover Your Tracks tool (coveryourtracks.eff.org) will show you your own fingerprint and how unique it is. Most people are "one in a million" or rarer.
The difference from cookies matters: cookies are opt-in by regulation in most jurisdictions (you've seen the banners). Fingerprinting has no consent mechanism, no browser setting that stops it, no banner. The only real defense is making your browser look like everyone else's — which is what Brave does with randomized canvas noise, and what Firefox partially does in Strict mode.
What I find interesting is that this mostly flies under the radar of privacy discourse, which is still focused on cookie banners that fingerprinting quietly makes irrelevant.
Does your browser setup do anything to address this, or did you not know this was happening?
0 replies