NewReact Native and Expo SDKLearn how

Same device. Same ID.

Open-source device identification and fraud signals, self-hosted. Recognise returning visitors across private windows, cleared cookies and other browsers, even when they stay anonymous.

Or open inCursorClaudeinstall.md

Identifying this browser…

Hello, visitor ID

Last seen
Matched by
Confidence
Browser
OS
Identified in
  • Private window
  • VPN
  • Bot
  • Spoofing

Identifying

Suspect score

See how this is calculated

Identifying

Real demo, run against a Trace test server. Accuracy figures on this page are synthetic. What the demo stores

Works with your stack

26fraud signals, each with a reason
9SDKs: browser, mobile and server
1command to self-host
0per-call fees, ever

Identification

The ID survives.

Cookies come and go; the device stays recognisable. Pick a situation and see what Trace keeps, and how sure it is.

How matching works
trace.get()
Chrome 131yourapp.com/signup
  • Cookiegone
  • Storagegone
  • Private modeoff
  • Device traitsmatched
Visitor IDv8f3k2m9q7x1d4w6zQa2Same ID
Device IDd2n7p4r8t1k6m3q9sXb5Same device
New visitorno match yet

A visitor ID is issued and a first-party cookie set.

Fraud signals

A score you can take apart.

Switch signals on and off. The score is a readable sum of weighted signals, every reason is itemised, and your backend turns it into a decision.

All 26 signals
score.simulate

Start from

Automation & spoofing
Network
Accounts & devices
Behaviour & privacy

Suspect score

Block
90/ 100
90/ 100High risk
  1. Bot / automation+60
  2. Virtual machine+15
  3. Datacenter IP+15

Default weights from scoring.default.json. Tune them, or learn them from your own outcomes.

Suspect score 90 of 100. Decision: Block. 3 signals on.

Use cases

One event. 24 ways to use it.

The same verified result answers sign-up, login, checkout and moderation questions. Pick one to see the signals it leans on.

See all 24 use cases

Spot logins from devices the account has never used.

Read the guide

event · account-takeover
Example

Logins to one account

DeviceNetworkDecision
MacBook, SafariKnown device for this accountHome, CairoAllow
iPhone, SafariKnown deviceMobile, CairoAllow
Windows, ChromeNew device, hosting IP: ask for a codeDatacenter, NLReview
Headless Chromebot and velocityProxy, USBlock
Signals used
VelocityVPNBot / automation

Install with AI

One prompt. Your agent does the integration.

The prompt points your coding agent at a guide written for agents: which SDK fits your stack, where to identify, how to verify on the server and what to do when Trace is down. You review the diff.

Run claude in your app's repository and paste.

Add Trace device identification to this app. Read https://trace.dev/install.md and follow it step by step. Ask me for TRACE_ENDPOINT, TRACE_PUBLIC_KEY and TRACE_SECRET_KEY if they are not already in the environment, and never commit real keys. Show me the diff when you are done.

Claude Code · your-app
illustrative run

  1. Read install.md
  2. Found Next.js (app router) with API routes
  3. npm install @trace-id/sdk-react @trace-id/sdk-node
  4. app/providers.tsx+9
  5. app/signup/form.tsx+12 −2
  6. app/api/signup/route.ts+21
  7. const e = await verifyEvent(eventId, { secretKey, endpoint });
  8. if (e.suspectScore >= 60) return deny(e.eventId);
  9. .env.example+3
  10. npm test14 passed
  11. Signup now sends an eventId; the API verifies it before creating the account.

Integrate by hand

Identify in the browser. Decide on your server.

The browser only hands over an event ID; your backend reads the verified result with a secret key.

Integration guide
signup.js
import { createClient } from '@trace-id/sdk-js';

const trace = createClient({
  apiKey: 'pk_...',
  endpoint: 'https://id.yourapp.com',
});

// On signup: identify, then send the event ID with the form.
const { eventId } = await trace.get({ linkedId: user.id });
await fetch('/api/signup', {
  method: 'POST',
  body: JSON.stringify({ ...form, eventId }),
});
GET /v1/events/:id
200 · verified
{  "eventId": "0193a3f2-7c1e-7b4a-9d2f-5e8c1a6b3f40",  "visitorId": "Q7mZ2xKp9LwR4tVb8NcE",  "deviceId": "Q7mZ2xKp9LwR4tVb8NcE",  "matchKind": "new",  "confidence": 1,  "suspectScore": 90,  "reasons": [    { "signal": "bot", "contribution": 60 },    { "signal": "datacenterIp", "contribution": 15 },    { "signal": "virtualMachine", "contribution": 15 }  ],  "signals": {    "bot": { "detected": true },    "vpn": { "detected": false },    "incognito": { "detected": false }  },  "ip": { "country": "US", "asn": 64501 },  "linkedId": "user_48213"}

Accuracy

Measured on every change.

Matching changes must not regress an accuracy run before they ship. The figures below come from that run, on simulated devices with private windows, cleared storage, updates and travel.

How it is measured
npm run accuracy
Synthetic data
Precision94.5%
matched visits that really were the same device
Recall92.5%
returning devices recognised
Wrong merges3.2%
different devices given one ID (lower is better)

Synthetic data, not real traffic. 1,000 simulated devices. Real-world numbers will differ and are likely lower. Method

Privacy

What it reads. What it never touches.

Collectors do not prompt for permissions, make network requests or read devices, files or location. High-entropy readings are hashed in the browser, and data and IPs stay on your servers.

Privacy details
collectors.md

Reads

  • Screen and GPU
  • Fonts and audio
  • Time zone and languages
  • Pointer rhythm, never text

Never touches

  • Permission prompts
  • Location
  • Files
  • Camera and microphone

Hashed in the browser: canvas a91f3c… audio 07be2d… fonts c4e810…. Details

Questions

Before you install.

Short answers to what people ask first. The rest is in the docs.

Clear your cookies, then open the demo.

Pre-release, open source, no customers yet. Run it, try to fool it, tell us where it breaks.