Aadhaar (UIDAI) 6
KYC & Onboarding 3
Digital Signatures 2
Data Privacy (DPDP) 2
MOSIP (National ID) 1
Products
Aadhaar number protection, as UIDAI mandates
A UIDAI-compliant Aadhaar Data Vault: every Aadhaar number is encrypted inside an HSM and replaced with a reference key your systems can safely store.
The Vault
Tokenise Aadhaar numbers and store e-KYC data through a simple XML API or the Java SDK.
Request
<StoreIdentifier> <apiKey>your-api-key</apiKey> <identifier>9999 8888 7777</identifier> <type>AADHAAR</type> </StoreIdentifier>
Response
<StoreIdentifierResponse>
<referenceKey>
0199C2B64A1E7A3B9D4F6E8C0A2B4D6F
</referenceKey>
<error>false</error>
</StoreIdentifierResponse>
// same Aadhaar → same reference key,
// so your records always line up
The vault returns a reference key for every Aadhaar number. Your databases, logs and reports never need to hold the number itself.
Aadhaar numbers are encrypted by keys that live in your HSM. Key material never leaves the hardware.
e-KYC XML and related documents are envelope-encrypted with a fresh session key per record, stored in the database or on secure file storage.
Storing the same Aadhaar twice returns the same reference key, so records across your systems reconcile cleanly.
A simple XML API for any stack, plus a Java SDK with signing and serialisation handled for you.
Per-application permissions decide who can store, who can read, and whether a retrieved Aadhaar comes back masked.
How it works
Your app sends the Aadhaar number or e-KYC data over a secured channel.
The vault encrypts it through your HSM and records a tamper-evident integrity check.
Your systems keep only the reference key, and exchange it back for data when authorised.
Security & Operations
Every control the UIDAI circular expects — key rotation, audit trails, access separation — running in your own data centre.
Each business unit or client gets its own isolated database and connection pool, provisioned through the admin API.
HSM keys rotate on your schedule. The vault tracks current and previous keys so reads keep working through a rotation.
Store and retrieve operations are logged with user, IP and timestamp, each record carrying its own integrity check.
Applications authenticate with API keys or digital signatures, restricted by IP, with store and read rights granted separately.
Database passwords and HSM credentials are encrypted at rest in configuration and in the vault's own tables.
Runs on-premises on MySQL, PostgreSQL, Oracle or SQL Server — no data leaves your infrastructure.
One platform, three jobs
Runs on
Java 17 · Jakarta EE WildFly application server MySQL / PostgreSQL / Oracle / SQL Server PKCS#11 HSMs
Compliance
UIDAI Aadhaar Data Vault circular (2017) Reference-key tokenisation HSM-held encryption keys Access & audit controls