If a system holds Aadhaar numbers, UIDAI's framework doesn't let you keep them lying around in application tables. They're expected to live in an Aadhaar Data Vault — an isolated, encrypted store — with the rest of your system referring to each one only by a reference key. It's a sensible pattern, and often one you can avoid needing at all.
What the Aadhaar Data Vault is
The Data Vault is a dedicated, access-controlled store for Aadhaar numbers, separated from the rest of your data. Nothing outside it holds the actual number; everything else works with a reference key that maps back to the Vault only under tight controls and audit logging.
Reference key, not the number
- The Aadhaar number is stored once, encrypted, inside the Vault.
- Applications, logs and reports carry only the reference key.
- Access to the real number is restricted, logged and purpose-bound.
- If a reference key leaks, the Aadhaar number itself does not.
The better option: don't store it at all
The surest way to meet the obligation is to never hold the number in the first place. Paperless offline e-KYC and the secure QR code let you verify identity from signed, masked data — confirming who someone is without ever retaining their full Aadhaar.
Where Certopact stands
Certopact Entry is built around offline verification (OVSE), so the full Aadhaar number is never stored — which sidesteps most Data Vault obligations entirely. This is general information, not legal advice; confirm your own obligations with counsel.