A fingerprint is a combination, not one secret ID
The W3C defines browser fingerprinting as the capability to identify or re-identify a user, user agent, or device through configuration settings and other observable characteristics. A site does not need one perfect value when several ordinary values become distinctive in combination.
Some signals are passive, meaning they arrive with a normal request, such as headers and network information. Others are active: page code asks the browser about rendering, available features, dimensions, timing, or other characteristics. The exact mixture varies by site and changes as browsers change.
Why clearing cookies is not the same defense
Cookies are stored state with browser controls for deletion. A fingerprint is inferred again from what a session exposes. The W3C notes that fingerprinting can correlate activity across sessions or origins even when cookie policy prevents a cross-site cookie from being read.
That does not mean every returning-site experience proves fingerprinting. Accounts, IP addresses, local storage, referral context, cached state, and ordinary business records can also explain recognition. Fingerprinting is one possible layer, not a diagnosis for every familiar page.
Reduction has tradeoffs
A defense can remove access to a signal, reduce its precision, standardize it across more users, or make collection easier to detect. The W3C describes these as mitigation levels rather than a complete solution and says eliminating fingerprinting by a determined party through widely deployed technical measures is implausible.
Randomizing every value is not automatically stronger. Contradictory or rare outputs can create a different identifier, and disabled features can break legitimate page behavior. A measured defense changes selected high-value signals while trying to remain compatible with the wider browser population.
What Cloak means by recognition reduction
Paid Cloak protection enters the page at document start and uses a fresh cryptographic seed for every document. It applies bounded changes to selected Canvas and Web Audio readbacks; normalizes selected WebGL, font, media-device, CPU, memory, language, and battery signals; withholds covered high-entropy Client Hints; and intercepts explicit fingerprint identifiers without intentionally clearing ordinary cart, login, product, or preference storage.
On covered shopping hosts, a dedicated hardware layer also reports a charging, full battery plus common device-pixel-ratio and screen-depth values. The W3C identifies high-precision battery status as a fingerprinting vector. Cloak treats battery as a recognition input; it does not claim that a retailer used battery level to set a price.
The extension pairs selected recognition reduction with selected tracker and fingerprint-endpoint blocking, fingerprint-header reduction, and clean-link rules, then records browser-visible actions locally. It does not hide an IP address, erase account-linked activity, prevent every active script, or make Chrome anonymous.
Primary sources