GUÉP
Device Fingerprint · The Machine Factor

The machine factor: recognize every device, expose emulators and farms, and let good users flow.

Kavuka Device Fingerprint is the unique, persistent identification of the device — a combination of hundreds of hardware, system, browser and network attributes that survives cleared cookies, private mode and reinstallation. It is the counterpart of the human factor: the signal that recognizes the machine behind every account, session and transaction.

Persistent
beyond cookie and reinstall
Emulators + farms
exposed on arrival
VPN and spoofed GPS
real location flagged
Graph node
the device linking accounts

Signal in production recognizing devices across fintechs, betting and marketplaces — persistent identification that survives cleared cookies, with explainable signal and audit trail.

A thousand new accounts. Forty devices. Your platform saw a thousand customers.

The device farm that looked like a thousand customers

Promotions and bonuses devoured by device farms and multi-accounting: the same device opening dozens of accounts unseen, and the emulator posing as a phone.

The ATO from a never-seen device — approved

The overnight account takeover comes from a never-seen device and gets approved, because nothing in your defense recognizes the machine — and the cleared cookie already wiped the memory.

The good customer challenged every session

The legitimate customer is treated as a stranger at every login, paying in friction what the right signal would solve in silence — and the cost of friction runs as high as the fraud.

Cost Without the machine factor, fraud at scale is invisible: the device farm looks like a thousand customers, the emulator looks like a phone and the ATO looks like the account holder. And the inverse cost runs too — the legitimate customer treated as a stranger every session, paying in friction what the signal would solve in silence.

How it works

From device to decision — friction only where the risk is.

  1. 01

    Identify

    The persistent fingerprint on web and mobile, via a lightweight SDK — the device ID that survives cleared cookies, private mode and app reinstallation.

  2. 02

    Expose

    Emulators, device farms, automation and bots, remote access (RDP) and root/jailbreak — the arsenal of fraud at scale exposed right on arrival.

  3. 03

    Contextualize

    The device reputation: seen in fraud, across how many accounts, with what pattern — plus VPN, proxy, TOR, spoofed GPS and time-zone mismatch, where the machine really is.

  4. 04

    Decide

    The signal feeds Fraud Prevention, MFA step-up and the link graph: a trusted device flows without friction, a strange device in a sensitive operation triggers step-up.

Coverage

The signal behind every session

A lightweight SDK collects hundreds of device attributes and returns a structured, explainable signal — ready to recognize the trusted device and expose the machine behind the fraud.

Persistent identification

The ID that survives cleared cookies and reinstall

Emulator detection

Emulators and device farms exposed on arrival

Automation and remote access

Bots, scripts and RDP; root/jailbreak flagged

Real location

VPN, proxy, TOR, spoofed GPS and time-zone mismatch

Reputation and consortium

The device against history: seen in fraud elsewhere

Link-graph node

The device linking accounts: the factory lit up

Real-time risk

Per-session device trust signal

Lightweight SDK, web and mobile

Transparent, proportionate collection (data-protection law)

Segments

Who recognizes the machine with Kavuka Device Fingerprint

Regulated

Fintechs & Banks

The signal for login, instant payments and step-up — the counterpart of Fraud Prevention to recognize the trusted device and block the stranger.

Multi-accounting

Betting & Marketplaces

Device farms and multi-accounting exposed; with 1:N Biometrics, the complete cordon against the account factory.

Anti-fraud

E-commerce

The repeat-chargeback device recognized when it returns — before yet another approved loss.

Promotions

Apps with bonuses

The bonus per real person — not per reinstall: the device memory that fraud tries to erase.

Legal shield

Strong signal, transparent collection

Kavuka Device Fingerprint was designed for data-protection law from the moment of collection: the signal is explainable and proportionate, with a documented purpose of security and fraud prevention. No black box — the vetting team understands what is collected and why.

  • Legitimate-interest legal basis with a documented proportionality test (purpose: security and fraud prevention).
  • Transparent, proportionate collection: only the attributes needed for the security signal.
  • Explainable signal, not a black box: every risk decision with a traceable rationale.
  • Configurable retention according to your policy and documented purpose.
  • Encryption in transit and at rest; Data Processing Agreement available for enterprise clients.
Already operating this way
We ran the fingerprint on our base and found a thousand new accounts sharing forty devices. The device farm had nowhere left to hide.
Head of Fraud · betting platform
The new-device account takeover, once approved, now triggers step-up automatically. And the good customer never even notices the defense exists.
CISO · payments fintech
We stopped challenging the ones who flow. The trusted device is recognized, friction went only to the stranger — and conversion rose along with it.
CPO · marketplace

Run the fingerprint on your base: how many "customers" share the same device?

In 15 minutes you see the signal running on your scenario and count the real devices behind the accounts.

  • For businesses only. No purchase commitment.
  • Data used solely for commercial contact.
  • Enterprise leads answered within 1 business day.

In 15 minutes you see the platform in action and get a proposal for your volume.

What device fingerprint is and why the cookie is not enough

Device fingerprint is the unique, persistent identification of a device: the combination of hundreds of hardware, operating-system, browser, network and sensor attributes that form the machine's "fingerprint". Unlike a cookie — which the user clears, which private mode ignores and which reinstallation wipes — the fingerprint survives precisely because it does not rely on an identifier stored on the device, but on the signature the device itself emits. It is the memory the fraudster tries to erase and cannot.

The fingerprint answers questions that a person's identity does not. Not "who is this customer?", but "how many accounts has this machine opened? Has it appeared in fraud? Is it an emulator, a device farm, a remote access? Is it where it claims to be?". It is the machine factor — the counterpart of the human factor, Biometrics. Person verification validates who is on the other side; the fingerprint exposes the scale and the tool: the same device across dozens of accounts, the emulator posing as a phone, automation, RDP, location spoofed by VPN or GPS — the arsenal of industrial fraud, invisible to identity verification on its own.

The market consolidated this lesson: the device signal on its own became a commodity. What wins RFPs is the combination — device intelligence together with behavioral biometrics, the link graph and the identity foundation, in a single engine — and the technical persistence of surviving reinstallation and factory reset. The decisive network effect is the consortium: a device seen in fraud on one platform signals risk on the next. In the Kavuka portfolio, the device is born as a native signal of the platform, not a third-party black box: combined with behavior, the graph and identity, and with the transparency of the signal — explainable, proportionate — as a differentiator before the vetting team and the DPO.

The result for the operation cuts both ways. For the defense: fraud at scale loses its disguise — the device farm that looked like a thousand customers is exposed, the emulator is unmasked, the never-seen-device ATO triggers automatic step-up, and the device becomes a graph node, lighting up together the forty accounts tied to three machines. For the legitimate customer: the trusted device is recognized and flows without friction, never challenged every session. Fingerprint and data-protection law are not opposites: collection is transparent and proportionate, with a documented security purpose, a legitimate-interest legal basis with a recorded test, an explainable signal and configurable retention. The machine does not lie — to those who know how to ask.

FAQ
What is device fingerprint?

It is the unique identification of a device through the combination of hundreds of hardware, system, browser and network attributes — persistent beyond cookies, private mode and reinstallation. It is the "fingerprint" of the machine, the signal that recognizes the device behind every account, session and transaction.

What does it detect that a person's identity does not?

The scale and the tool: the same device across dozens of accounts, the emulator posing as a phone, the device farm, automation and bots, remote access, spoofed location — the arsenal of industrial fraud, invisible to person verification on its own.

Does it work with cookies blocked and private mode?

Yes. The fingerprint does not rely on a cookie: device attributes and persistent identifiers survive data clearing, private mode and, on mobile, app reinstallation. That persistence is precisely the attribute that decides RFPs.

What about privacy (data-protection law)?

Collection is transparent, proportionate and with a documented purpose (security and fraud prevention — legitimate interest with a recorded test). The signal is explainable and retention is configurable. No black box: the vetting team understands what is collected and why.

How does it integrate with my current anti-fraud?

A lightweight SDK (web and mobile) collects the signal and delivers it via API — feeding Kavuka Fraud Prevention natively or your current engine. The trusted device reduces friction; the strange one triggers MFA step-up.

What is a device farm and how does the fingerprint expose it?

A device farm is an operation that uses a few devices (or emulators) to create and operate many accounts, devouring promotions and committing fraud at scale. The fingerprint exposes it by recognizing the same device behind dozens of accounts and turning it into a link-graph node — the accounts tied to the devices light up together.

What is the difference between Device Fingerprint and Biometrics?

Device Fingerprint is the machine factor: it recognizes the device. Biometrics is the human factor: it recognizes the person. Combined — with 1:N Biometrics exposing the same person across several accounts and the fingerprint exposing the same device — they close the complete cordon against multi-accounting and fraud at scale on the Kavuka platform.

Let's talk

Your next high-impact decision starts with the right data.

Talk to a GUÉP specialist and find where applied intelligence creates the most value in your operation.