On-Device, Continuous Bot Detection
A purpose-built on-device intelligence engine with a proprietary architecture. Rather than routing device data to the cloud, Cynopta AI human behavior models run locally - delivering instant, continuous bot detection scoring. Cynopta tells your app whether a human is present. Your policy decides which agents to admit and which to stop.
Inside the App - Zero Friction
Runs silently as a lightweight SDK inside your mobile app. A single integration point for iOS and Android. No cloud integration is needed for scoring. No separate agent to install, no user interaction required, no perceptible performance impact.
Continuous Monitoring
Continuously monitors device behavior and context in real time, in an ultra-low footprint. Behavioral context is already available when interaction begins, not only at login or payment checkpoints.
Context That Builds Over Time
Device and session checks apply to every assessment. Longitudinal behavioral context takes from 3 days to 3 months to become meaningful, so confidence grows as the phone's daily routine builds up.
Privacy by Design - Scored on the device
Cynopta computes its score on the phone, and computing it doesn't require raw behavioral data to leave the device. What the SDK sends to Cynopta depends on your settings and is listed in our data-flow documentation.
Battery Efficiency
A mini-OS design keeps battery use below 1% over a full working day. It is designed to stay within the OS's background and battery limits, with no noticeable impact on UX.
No Prompts, No Ad IDs
Operates without user-facing permission prompts and without advertising identifiers. Scoring runs on-device using the app's own runtime.
Every Layer Asks a Question.
One Was Never Asked.
Mobile apps are already defended in depth: the perimeter judges traffic, cloud engines judge requests, the OS guards itself, attestation certifies genuineness, shielding protects code, and authentication proves identity at a moment. Each layer is worth keeping - and not one of them can see who, or what, is physically operating the device. Cynopta sits in the one position closest to the human hand, asking the question the rest of the stack was never built to ask.
CDN = Content Delivery Network · WAF = Web Application Firewall
DDoS = Distributed Denial of Service · RASP = Runtime Application Self-Protection
MFA = Multi-Factor Authentication · OS = Operating System
Signals Invisible to Cloud-Based Systems
Cynopta analyzes thousands of on-device signals and data points that cloud-based fraud systems cannot observe. These signals span both device integrity and real-time behavioral context - providing a uniquely rich picture of whether a user is human or an automated bot.
Device Integrity Signals
Continuous analysis of the device itself - hardware state, runtime environment, motion sensor patterns, and timing signals that help distinguish genuine human operation from automated scripts.
Real-Time Behavioral Context
Human life has a consistent rhythm. Cynopta reads the physical life of the phone, on the phone: is it carried, does it commute, does it rest somewhere at night. None of this is sent as a location. Automation finds this kind of lived context hard to fake.
Wake-up time, commute frequency, driving patterns, daily schedule outliers
Nearby devices are summarized on the phone; full device addresses are never sent. A real person's device ecosystem is distinctive
Country changes and travel patterns from network and motion context, without a location permission - phone farms stand out
This depth of on-device context enables security decisions that are effective even when devices are clean and network traffic appears legitimate. Cloud and perimeter systems cannot directly observe these on-device signals - they are only accessible from inside the running app, on the device itself.
From Raw Signals to a Local Score
On-device and continuous are not slogans - they are a pipeline. Eight independent families of passive signals converge in a fusion stage where, like a synapse, no single signal decides anything and all of them together decide everything. The engine runs on the phone and asks the user for no permissions. Its output - a local human-likelihood score - does two jobs at once: the app reads it locally and can act before any network request, and for server-side enforcement the SDK can optionally attach a result token for your backend. Computing the score doesn't require raw behavioral data to leave the device. Each score is computed on the phone, with no call to Cynopta. The SDK renews its license with Cynopta once a day; what else it sends depends on your settings and is listed in our data-flow documentation.
Device boundary
Eight signal families, 16,000 on-device data points, all analyzed locally
One Integration, Full Coverage
A single SDK integration gives you continuous protection on Android and iOS, within what each platform allows (see the specifications below). You need no server of your own to get a score - one assessment equals one local SDK call. And because the score exists before any server round-trip, automated traffic can be stopped at the edge - inside the app - before it ever touches your backend.
Install the SDK
Single integration point for iOS and Android. No mandatory cloud integration for local scoring. Less than 1% battery over a full working day, transparent to the user.
Set Your Policy
Decide in your app what happens at each score: step-up authentication, silent flagging, block, or challenge. The rules live in your code.
Call the Assessment API
At any decision point, request a local human-likelihood score via a single API call. One assessment equals one API call.
Act on the Score
Use the returned risk score to trigger downstream actions in your app or backend. Pipe it into the fraud engine, risk orchestration, and step-up flows you already run - Cynopta strengthens your existing stack, it doesn't replace it.
Built for Production Mobile Environments
SDK and Integration
Detection engine
Performance and Efficiency
Privacy and Output
{
"score": 0.97,
"device_realness_score": 0.94,
"session_bot_risk": 0.03,
"reasons": [],
"action_name": "login",
"timestamp": 1794326400000,
"latency_ms": 9
}
Your app reads the result locally. Classification and reason codes explain why a session was flagged.