Browser fingerprinting recognizes a returning client by combining stable traits of the browser and device, rather than relying only on a stored cookie.
The same technique can support fraud checks or quiet tracking, so the purpose and the notice to people decide whether it is acceptable.
How it works
Traits can include language, screen size, installed fonts, time zone, and how the browser reports its features.
None of these is a password, yet together they can be specific enough to link visits even after cookies are cleared.
Fingerprints change when a person updates a browser or moves to another machine, which creates both missed matches and accidental links between different people who share a standard setup.
Treat the result as a clue that still needs corroboration before you block a customer.
Concrete examples
- A merchant notices that many new accounts share one unusual font and screen combination and reviews them before shipping.
- A person who clears cookies still sees the same logged out recommendations because the site recognized the browser traits.
- Two employees on identical company laptops produce similar fingerprints, so the site must not treat that match as a single human.
Protective measures
- Tell visitors when you collect device traits for fraud control, and do not reuse that collection for unrelated advertising by default.
- Avoid irreversible blocks that rest on a fingerprint alone, because shared or updated devices will collide or drift.
- Store only the traits you need, set a retention limit, and protect the store like other identity data.
- Pair fingerprint clues with a real account signal before you freeze payment, mail changes, or password resets.