Guide

Device fingerprinting, explained

How modern device fingerprinting identifies a returning visitor without cookies — the signals it uses, why clearing cookies does not reset it, and how to use it for fraud prevention accurately and lawfully.

What is device fingerprinting?

Device fingerprinting is the practice of identifying a browser or device from the many signals it exposes — rendering behavior, hardware characteristics, installed fonts, network properties — rather than from a cookie you set. Because those signals are inherent to the device, the resulting visitorId is not reset by clearing cookies or opening a private window — which is exactly why it is the backbone of fraud prevention, bot detection and account-takeover defense, and why it should be used for those purposes and not to follow people around for advertising.

A good fingerprinting system does three things well: it collects high-entropy signals, it fuses them server-side into a single stable identity, and it attaches a confidence score so you can make risk decisions instead of guessing. Prynt does all three, and ships the identity, confidence and risk signals that competitors gate behind a paywall.

The signals a fingerprint is built from

Canvas & WebGL

How a device renders text, emoji and 3D graphics differs by GPU, driver and OS. Prynt uses a perceptual hash so minor driver changes don’t break the match.

Audio & fonts

The AudioContext DSP output and installed-font metrics are highly device-specific and stable over time.

Hardware & math

CPU core count, device memory, screen geometry and transcendental-function (FPU) results narrow the device down further.

Network layer

IP intelligence, ASN, and the JA4 TLS fingerprint captured at the edge add signals a browser can’t patch.

Storage reconciliation

Cookie + localStorage + IndexedDB are fused so a cleared store alone never creates a new identity.

Confidence scoring

Every match ships a 0–100% score of how closely the device matches, so you decide how much to trust it per action.

Why clearing cookies does not reset it

Cookies are per-browser storage you set; a user can wipe them in one click. A fingerprint is derived from the device itself — the GPU that draws a canvas, the CPU that computes a math result, the fonts installed, the screen geometry. None of that changes when someone opens a private window or clears their cache, so the same device maps to the same visitorId — the property that stops a fraudster from creating a fresh identity with one click. Prynt also reconciles cookie, localStorage and IndexedDB, and flags incognito mode as its own Smart Signal. Because it works without cookies, tell your users about it in your privacy notice and keep it to security and fraud prevention.

Fingerprinting vs. bot & fraud detection

A fingerprint answers who is here; fraud detection answers whether to trust them. Prynt layers bot detection, VPN/proxy/Tor/datacenter and residential-proxy detection, behavioral biometrics (mouse and keystroke dynamics), and a reputation network on top of the identity — so a device another account already confirmed as fraud is flagged the moment it reaches you.

Doing it accurately and privately

Fingerprinting for security and fraud prevention can rely on legitimate interest in many jurisdictions, but regulators treat it as unfair when it is used to track people, so state the purpose, disclose it and keep data to what you need. Prynt honors GPC / Do-Not-Track, deletes identification data after your plan’s retention window, supports right-to-erasure, and processes data under our DPA.

Related

Bot detection · Account-takeover prevention · Prynt vs FingerprintJS · Glossary · SDKs