demo · v134 · privacy
Tracker Survival Matrix
Six bounce-tracker techniques against five Chrome versions and three mitigation profiles. Watch which combinations let the tracker keep its ID and which clear it. The v134 row is where the cache loophole closes.
| technique | cookies | localStorage | IndexedDB | service worker | HTTP cache | cache-control: immutable URL |
|---|
how this models the spec
The bounce-tracking mitigations are activated when:
- a top-level site briefly receives traffic (a bounce), and
- that site accesses storage during the bounce.
Pre-v134 the "accesses storage" predicate covered cookies / localStorage / IDB / service workers but not the HTTP cache. A tracker that only stashed an identifier in a cached response (URL-as-ID, ETag-as-ID, Vary-as-ID) survived mitigation because it never "accessed storage" by the predicate's definition.
v134 extends the predicate to include HTTP cache reads/writes during a bounce. The "cache-only" column flips from RED to GREEN at Chrome 134.