Verifying identity is powerful, but every verification touches personal data — so how you call the API matters as much as that you call it. Data minimisation is the principle that keeps a verification step from quietly becoming a data-hoarding liability.
What minimisation means here
- Request only the attributes you actually need from a verification.
- Store only the result and the minimum you must keep — not the raw inputs.
- Never persist sensitive numbers you don't need (for Aadhaar, the number is never returned or stored).
- Set a retention period and delete when the purpose is met.
Why it protects you
You can't leak what you don't hold. Minimisation shrinks both the likelihood and the blast radius of a breach, and it's a core expectation of the DPDP Act — see the DPDP Act and visitor data and how long to keep records.
Design it into the call
Minimisation is easiest when it's built into the integration: request the narrow result, log the outcome not the payload, and encrypt what you keep — see encryption of visitor data. Retro-fitting it after you've stored everything is far harder.
Minimal by design with Certopact
Certopact Verify returns a purpose-limited result and never returns or stores the Aadhaar number — see Aadhaar masking. This is general information, not legal advice; confirm your obligations with your own counsel.