Fingerprint

Device Fingerprinting:
One Fingerprint. Every Surface.

A device ID, a browser cookie, an IP address — each one is easy to fake on its own. NonaShield ties identity to something that can't be: the device itself. The same model, live on mobile and on the web.

Mobile
Web
22
Details Combined Into One Identity
✓
Checked Every Session, Automatically
Built-In
Tied to the Device's Own Security Chip
0
Risky Permissions Required
One Identity Model, Two Surfaces

Mobile. Web.
One Identity.

Mobile

What You Can Verify.

  • This is a real, physical phone — not an emulator, a bot farm, or a script pretending to be one.
  • It's the same phone as last time — tied to the device itself, not to something an app can reset or fake.
  • The phone hasn't been tampered with — no signs of rooting, hacking tools, or unauthorised modification.
  • It's connecting the way it usually does — flagging when a trusted device suddenly shows up on an unfamiliar network.
  • One phone isn't posing as many — catching device farms trying to look like hundreds of separate customers.

What it requires: a small piece of code added to your app. No risky permissions, no extra steps for your users.

See How It Works →
Web

The Same Idea, for Browsers.

Built on the same principle as mobile — no single signal is trusted on its own. Works the same way on any browser, any device.

  • Recognize a returning visitor — even if they've cleared cookies or switched browsers.
  • See where a visitor is really connecting from — and flag traffic coming through a VPN or anonymising service instead.
  • Tell a person from a bot — separating genuine visitors from scripted or automated traffic.
  • Spot a tampered or hidden browser — including incognito/private mode and browsers altered to hide their tracks.
  • Get a confidence level, not a guess — every match comes with how sure we are, not a flat yes or no.

Fingerprint is $99 per month, with a 7-day free trial.

Start the free 7-day trial →
How the Fingerprint Is Built

One signal isn't identity.

A device ID, a User-Agent string and an IP address are each spoofable alone. NonaShield fuses about 22 independent signals into a fingerprint anchored in hardware rather than software claims. The SDK reads 13 baseline fields on every session, with no dangerous permissions required.

The 13 baseline fields

Hardware IDAndroid device IDBuild fingerprintOS version / API levelSecurity patch levelScreen resolutionCPU core countTotal RAMApp version code / namePackage nameAPK certificate fingerprintDebug-build flagInstaller source

Every one of these lives in software, so a rooted device can read and forge them, and emulator farms fake all 13 in bulk. A fingerprint is only as strong as its weakest anchor, which is why the hardware anchor matters.

Hardware-attested device key

The SDK generates an ECDSA P-256 key in the hardware keystore with StrongBox-first, TEE-fallback logic, and reports which hardware tier actually backed it.

Stable device ID

Not a random UUID: the stable device ID is the SHA-256 hash of the device's own hardware-backed public key, formatted as a UUID. It changes only if the key material itself changes.

Device anchor

A persistent SSAID (Android) or identifierForVendor (iOS) flags factory-reset and device-swap attempts.

Wi-Fi network fingerprint

SHA-256-hashed SSID and BSSID, never raw network names, for "same network as before" comparison.

Emulator and farm fingerprint

Kernel device nodes, QEMU markers, build-property strings and sensor-count anomalies fused into a hard and soft evidence model.

Software fingerprints identify a claim. A hardware-attested fingerprint identifies a chip. How hardware-backed possession works →

Where It's Used

One Fingerprint,
Many Fights.

Account Takeover Prevention

Recognize when a login is coming from a device that has never touched this account before.

Payment Fraud

Tie a transaction to the actual device making it, instead of a token that's easy to fake.

New Account / Synthetic Identity Fraud

Catch one device applying under many names before disbursal or approval, not after.

Bot & Automation Detection

Separate emulator farms and scripted traffic from real users, on-device and in-browser.

Returning-User Recognition

Recognize a genuine returning device without relying on cookies or app storage alone.

Ask About Fingerprint.

One SDK for mobile. The same identity model on the web.

FAQ

Frequently asked questions

What is device fingerprinting?

Device fingerprinting builds a stable identifier for a phone or browser from its hardware and software traits, so the same device can be recognised across accounts and sessions without relying on cookies or advertising IDs.

How is device fingerprinting different from biometric fingerprint login?

Biometric fingerprint login checks a person's finger on the phone. Device fingerprinting identifies the device itself. NonaShield uses it to spot emulators, clones and one handset behind many accounts.

Does NonaShield fingerprint web as well as mobile?

Yes. The same fingerprint idea covers mobile apps and web sessions, with a separate web integration guide for browsers.