DEVICE INTELLIGENCE
Recognize returning devices and review the evidence behind them
A browser script assesses the visitor's browser and returns a site-scoped device handle with a risk read. Your backend reads the record and applies your own policy.
Device evidence you can review and carry into policy
Each assessment gives your team a handle, risk fields, and the context behind them.
- Earlier visit
- Later visit, same browser
Handle A
Risk read: level, confidence, reasons
- After clearing storage
New handle B
Continuity broke. A new or missing handle is not a low-risk result.
Site-scoped device handle
Risk read with reasons
History and comparison
Consent-aware collection
From browser evidence to your backend decision
Your page
Collector script
Assesses the browser on your provisioned origin.
Noxtica
Handle and risk read
Evidence from the page
A site-scoped device handle, or an unavailable state.
Your server
Authenticated lookup
Just the device identifier
Reads the record with a server-held credential.
Your policy
Your decision
Level, confidence, reasons
You choose the action. Noxtica does not decide.
Collect in the browser
Read on your server
Apply your policy
What a device handle cannot tell you
- Not a person. A device handle is not a verified person or account owner.
- Continuity varies. A missing result is not a low-risk result.
- Estimates, not facts. Scores, risk levels, and reasons are probabilistic. Your team makes every decision.
- Your responsibilities. Device handles and browser characteristics can be personal data, depending on law and use. You own the notices, consent, and legal basis for collecting them.
Scores, reasons and verdicts are probabilistic estimates, not statements of fact. Your team makes every decision.Read the disclaimer