DEVICE TRUST · ON-DEVICE ANTI-SPOOFING · PLUS

Know the phone can be trusted before you capture.

A device-trust engine that runs a live security check on the handset itself: is it rooted, an emulator, on a VPN, or reporting a fake GPS location? Gate onboarding, capture and payment on the answer, and lock down screenshots of the screen while a sensitive document is on it. It all runs on-device across iOS, Android, Flutter and React Native, so the risk decision happens before any data moves.

On-device · offline Root · emulator · VPN · mock-GPS Screenshot lockdown Real-time monitoring
WHAT IT CATCHES

One call, a full trust picture of the device

A single security report answers the questions your fraud and compliance teams actually ask, computed locally on the phone with no server round-trip.

Rooted device

Checks for tell-tale root binaries and test-key builds. A rooted phone can tamper with the app, the camera feed, and stored data, so you can decline or step up verification.

Emulator

Flags emulators and simulated devices from build fingerprints and hardware signals, a classic sign of an automated fraud farm rather than a real applicant on a real phone.

Mock / spoofed GPS

Detects a location coming from a mock provider, so a proof-of-delivery or field check-in can't be faked from another city. Pairs with location capture for a verified geo-stamp.

VPN in use

Reports an active VPN tunnel. Useful when a session is expected to be domestic, or when a masked network is a risk signal worth weighing in your rules.

Developer mode & USB debugging

Surfaces developer options and ADB/USB debugging being enabled, so instrumentation and injection tooling on the device doesn't slip through unnoticed.

Screenshot & screen-record lockdown

Turn on a secure flag for a screen and the OS blanks it out of screenshots and screen recordings, so a sensitive document or one-time code can't be captured off-screen.

The risk decision happens on the device, before anything is uploaded

Because every check runs locally, you get the trust signals at the exact moment of capture, not after the fact from server logs. Decline, allow, or route to manual review right there in the flow, and no personal data has to leave the phone for the decision to be made.

HOW IT WORKS

A security report and a live watcher

  • ✓ One call returns root, emulator, VPN, mock-location, developer-mode and ADB flags together
  • ✓ Optional live monitoring raises an event the moment developer options or a VPN turn on mid-session
  • ✓ Flip screenshot & screen-record protection on and off around any sensitive screen
  • ✓ Fully on-device, works offline, covers Android 5.0 through the latest release
  • ✓ One integration ships to iOS, Android, Flutter and React Native
java
// One security report, computed on the device
DeviceGuard guard = DeviceGuard.getInstance(this);

guard.getSecurityReport(report -> {
    boolean rooted   = (boolean) report.get("isRooted");
    boolean emulator = (boolean) report.get("isEmulator");
    boolean mockGps  = (boolean) report.get("isLocationSpoofed");
    // gate onboarding / capture on the result
});

// Block screenshots & screen recording on a sensitive screen
guard.enableScreenProtection(this);
USE CASES

Where device trust changes the outcome

FINTECH KYC

Block fraud at onboarding

Run the report before the first document is captured. Rooted phone, emulator or mock GPS routes the applicant to manual review instead of straight-through approval, cutting synthetic-identity and account-farm fraud at the door.

LENDING

Trustworthy loan capture

Instrumented and rooted devices are where income-document tampering starts. Flag them at capture so a risk team can look closer before disbursal.

INSURANCE

Anti-fraud claim intake

A claim photo taken from a spoofed location or a simulated device is a red flag. Attach the trust signals to the claim so adjusters can prioritise the doubtful ones.

GOVERNMENT

Benefit & scheme enrolment

Lock the enrolment screen against screenshots of citizen documents, and refuse emulated devices so one operator can't spin up hundreds of fake enrolments.

FIELD OPS

Honest proof of delivery

Mock-location detection means a delivery can't be marked complete from the wrong place. Combine with location capture to record where the drop really happened.

EXAMS · PROCTORING

Capture integrity

Detect developer mode and VPNs, and block screen recording, so document and identity capture during a remote assessment can't be quietly manipulated.

PLATFORM SUPPORT

Every major mobile platform · one license can cover all

iOS

Swift · UIKit · SwiftUI

Android

Kotlin · Java · Jetpack Compose

Cross-platform

React Native · Flutter

PRICING

Part of the Plus tier

Device Guard ships with the Plus tier of the mobile SDK license, alongside the other fraud-signal and advanced capture features. One flat license, no per-check metering. Pricing shown in your local currency.

Affordable to all

The same anti-fraud engine a bank ships is priced so a lending startup or a single field-ops app can ship it too. Flat annual license, unlimited checks.

See the full mobile SDK →

FAQ

Common questions

What does a mobile device-trust check actually detect?
It returns a single security report flagging whether the phone is rooted, an emulator, on an active VPN, reporting a mock or spoofed GPS location, or has developer options and USB debugging (ADB) enabled. Each signal comes back as a plain boolean from one call, so you can gate onboarding, capture or payment on the combined result.
Does the device-trust check run offline and on-device?
Yes. Every check is computed locally on the handset with no server round-trip, so it works fully offline. No personal data has to leave the phone for the risk decision to be made, and you get the trust signals at the exact moment of capture rather than after the fact from server logs.
Which platforms does the device-trust SDK support?
It ships for iOS, Android, Flutter and React Native from a single integration. On Android it covers version 5.0 through the latest release (API level 21 to 34), so one build spans the current fleet of devices.
How does it detect a rooted phone or an emulator?
Root detection looks for tell-tale su binaries and test-key builds, while emulator detection reads build fingerprints and hardware signals such as model and manufacturer. Both are common signs of a tampered environment or an automated fraud farm rather than a genuine applicant on a real device.
Can the SDK block screenshots and screen recording of a sensitive screen?
Yes. Turning on screen protection sets a secure flag so the operating system blanks the screen out of screenshots and screen recordings, and it can be switched off again once the sensitive screen is dismissed. This stops a KYC document or a one-time code from being captured off-screen.
Can it alert me if the device becomes unsafe during a session?
Yes. Optional live monitoring raises an event the moment developer options are switched on or a VPN is activated mid-session, so a long onboarding or payment flow can react in real time instead of only checking once at the start.
How is a mock or spoofed GPS location detected?
The report flags when a location is coming from a mock provider rather than the real GPS hardware, so a proof-of-delivery or field check-in can't be faked from another city. Pair it with on-device location capture to record a verified geo-stamp alongside the trust result.
Is device trust included in the license, and how is it priced?
Device trust is part of the Plus tier of the mobile SDK license, alongside the other fraud-signal and advanced capture features. It is a flat license with unlimited checks and no per-check metering — see pricing or contact us for a quote.

Add device trust to your capture flow

Free trial. All platforms. On-device. No credit card.