Skip to main content
Use device recognition and linked account evidence to detect returning activity after an account restriction.

​
Where to integrate

Identify a new signup or login before granting access. Start with the SDK for your stack and retrieve the result on your backend.

​
What to read

Compare the verified Device ID with your recorded restriction evidence and review linked accounts. Use the current Risk Score and flags, plus High-Risk Events where relevant. Treat a missing or incomplete result as an explicit unverified state.

​
How to act

Apply the account restriction policy or route an ambiguous match to review. Keep reasons, expiry and an appeal path. A household can share a device without sharing responsibility for abuse.

​
Build the example

The runnable tutorial includes the starting app, the completed integration, and steps to test its behavior. Its application policy is stated separately from ShieldLabs detection. For implementation details, see Acting on results and Identification flow. Verify the expected domain, result age and account association, and consume protected actions atomically.