Device Fingerprinting
Device fingerprinting builds a stable identifier from browser and hardware attributes, letting operators link accounts that share a device even across cleared cookies.
What it means
Device fingerprinting assembles a stable identifier from attributes a browser or app exposes: canvas and WebGL rendering characteristics, installed fonts, audio stack behaviour, screen and timezone configuration, hardware concurrency, and dozens of smaller signals. Combined, these are distinctive enough to recognise the same device again. A good implementation survives incognito mode, cleared cookies and app reinstalls, because it doesn't depend on anything stored client-side.
Why it matters for operators
It's the single strongest link signal for multi-accounting and the backbone of most bonus abuse detection. It also carries the sharpest false-positive risk in the stack: shared household devices, internet cafés and office machines all produce genuine links between unrelated people. Treating a fingerprint match as proof rather than as one input is how operators end up explaining a voided withdrawal to a complaints body.
There's a compliance dimension too. Fingerprinting for fraud prevention is generally handled as a legitimate-interest processing activity in the EU and UK, but it isn't automatically exempt from transparency and minimisation duties, and regulator treatment varies. Document the purpose, limit retention, disclose the practice in the privacy notice, and take local advice per licensed market — "it's for fraud" is not a blanket answer.
Example
Two accounts opened eight weeks apart share a fingerprint. One belongs to a long-standing player, the other to a new registration that immediately claimed a welcome offer. The link triggers review rather than a block; the payment-instrument check decides the outcome.