DeepID is reviewed by your security team before any pilot. This page sets out what the SDK does in your app, what is agreed before a pilot, and how decisions are recorded. The full security pack is shared on request.
Your appPayment paused. Your money hasn’t left your account. We’ll call you on +91 •••• 3210.
Your FRMHOLD · active call · screen share · mule-linked payee
Your SIEMDevice and session signals: the shared screen, the remote-access app, the call
The recordThe policy version, every reason that matched and the message shown
One decision, as it reaches your app, your FRM and your SIEM: the action, its reasons and the message, logged with the policy version. The session is the site’s example.
On this page
What the SDK reads, and where.
One SDK for sign-up, login and the session, in place of several point vendors you would each have to review. By family, what it reads and where each check runs.
What the SDK reads and where each check runs, by family
The number, confirmed by the network over mobile data; one silent text from the phone’s own SIM once permission is given; the device, passed by the risk gate before any route runs.
The network check runs between the phone and the carrier, over mobile data. The SIM check sends one text from the phone. A single-use token is redeemed server to server, by your own server, before anyone is signed in.
The selfie and the document; Aadhaar offline KYC, DigiLocker and PAN with the customer’s consent; sanctions, PEP and adverse-media lists.
Liveness gives an instant answer on the phone and the final, fail-closed verdict from the server. Record checks run against the records that issue them. Every face check leaves a signed record, replayable for audit.
Device integrity, remote access and screen sharing; typing and touch rhythm; an active call during a payment or payee change; the payee’s links across your own book.
Read in the session by the SDK and weighed with the rest of the session. Where each signal is scored, and what leaves the device, is set out in the security pack and agreed per engagement.
The action, its reason codes, the message shown to the customer and the policy version that applied.
Returned to your app, and sent as an event to your FRM, case manager or SIEM. Logged with its reasons for audit.
Device integrity
Root, jailbreak, emulator, hooking and cloned-app detection, checked every session.
Injection defence
Virtual cameras and emulators are caught before a face check is trusted, and liveness fails closed.
Remote-access detection
Screen sharing and remote-control apps are read while money moves.
One SDK
One SDK for sign-up, login and the session, in place of several point vendors you would each have to review.
What the SDK asks the phone for.
Mobile dataFor the network check, which runs over mobile data even when the phone is on Wi-Fi.
Permission to send one textFor the SIM check, which sends one text to DeepID from the phone’s own SIM, silently once permission is given.
The cameraFor liveness, the face match and video KYC, only where the journey asks for a face.
Anything furtherAny further permission is listed with the SDK for each platform and agreed before the pilot.
Data handling.
Your data protection officer’s three words come first: a lawful basis, consent and minimisation. A device identifier and a behavioural profile can be personal data, so what is collected, why, and for how long is written into the data processing agreement before a pilot, and the same questions are settled before a retrospective.
Data handling: what is collected, why, for how long, who controls it and where it is hosted
Question
Answer
What the SDK collects
Device, network, SIM, session and behavioural signals, and face images or templates when identity checks are used.
Why
To recognise devices, read the session and prevent fraud on your own journeys. Nothing is shared with any other firm DeepID serves.
How long it is kept
Retention is set for each data type in the data processing agreement. Agreed per engagement.
Who controls it
You are the data controller. DeepID processes data on your instructions.
Where it is hosted
Hosting region and data residency are agreed with you and written into your contract. Agreed per engagement.
Where it runs.
Hosting
Where DeepID runs for your bank is set with your security team before the pilot starts.
Data residency
The country your customers’ data is held in is agreed before any of it is sent.
Retention
How long decision logs and face-check records are kept is settled in writing first.
Sandbox access
Your engineers can wire one moment end to end before any contract is signed.
The hosting options for your bank, and which applies, are agreed per engagement and written into the contract.
How data is protected.
In transit and at restEncryption in transit and at rest.
AccessAccess control and logging on every system that holds customer data.
DevelopmentSecurity built into the development lifecycle.
Key custodyWho holds which keys is agreed per engagement and set out in the security pack.
Every decision leaves a record:
Every decision is logged with its reasons and the message shown to the customer.
Every face check leaves a signed record that can be replayed for audit.
Decisions go to your app, your FRM, your case manager or your SIEM.
Policies are versioned, so you can show what rule applied and when.
The laws it is set against.
DeepID’s privacy programme is aligned with India’s Digital Personal Data Protection Act, 2023, and with each market’s own law where DeepID serves it. You are the controller and DeepID the processor; consent, purpose limitation and erasure follow your instructions and the data processing agreement. The website’s own privacy notice covers this site.
IndiaThe Digital Personal Data Protection Act, 2023.
SingaporeThe Personal Data Protection Act 2012.
The UAEThe Personal Data Protection Law, Federal Decree-Law No. 45 of 2021.
Certifications and audits.
DeepID is certified to SOC 2 Type II and ISO/IEC 27001, and its privacy programme is aligned with the GDPR and the CCPA. The reports and certificates, each with its scope, period and issuer, are in the security pack.
Certifications and audits: each standard, its status, and its scope, issuer and period
Standard
Status
Scope, issuer and period
SOC 2 Type II
Certified
Auditor: to confirm. Period covered: to confirm. To confirm before launch.
ISO/IEC 27001
Certified
Certification body: to confirm. Valid until: to confirm. To confirm before launch.
GDPR
Aligned with
The EU General Data Protection Regulation, for customers and end users it applies to. You are the controller and DeepID the processor.
CCPA
Aligned with
The California Consumer Privacy Act, for customers and end users it applies to.
Availability and decision latency are set in the agreement for each pilot and measured on your own traffic. DeepID’s own measure of decision latency is under 50 ms (DeepID, 2026); the figure that binds you and DeepID is the one in your agreement.
What the security pack contains.
Shared under NDA with a named contact during vendor due diligence. It holds the SOC 2 Type II report and the ISO/IEC 27001 certificate, each with its scope, period and issuer.
The security pack: each item and what you receive
Item
What you receive
Audit reports and certificates
The SOC 2 Type II report and the ISO/IEC 27001 certificate, each with its scope, period and issuer.
Penetration testing
A summary of the latest independent test.
Biometric testing
Presentation and injection attack test results, with the lab, the level and the date.
Data flows
A diagram of what is collected, where it goes and where it is stored.
Contract documents
The data processing agreement and the sub-processor list.
Security researchers can report a finding to the DeepID security team through the contact form, choosing “Security report” as the topic. Say what you found, where, and how to reproduce it; the team replies to the address you give.
See DeepID on a real phone.
We show your fraud, security and engineering leads how DeepID would run your sign-up, login or payment journey, then plan a pilot on your own traffic.