Need to mask an existing archive, not just new documents? For crores of already-stored KYC images across your DMS, LOS or core-banking attachments, see bulk Aadhaar masking for legacy document archives: on-premise remediation with a per-page audit trail.
Handling personal documents in financial services carries one hard obligation: the Aadhaar number must not sit readable in your systems. RBI's 2019 amendment to the KYC Master Direction requires Aadhaar masking (redaction) when an Aadhaar card is accepted for KYC and IRDAI's 2019 guidance extends the duty to insurers and their agencies. For what the DPDP Rules add for documents you already hold, see whether the DPDP Act requires masking Aadhaar in a legacy archive. Extrieve's Aadhaar masking SDK and API handle this automatically.
As per UIDAI, masking means covering the first eight digits of the number, in physical or digital form, with only the last four left visible. Doing that by hand, page after page, is where operations teams struggle and where automation earns its keep.
What is Aadhaar masking?
Aadhaar masking hides the first 8 digits of the 12-digit number and keeps the last 4 visible, with every other detail on the card untouched. Extrieve’s Aadhaar Redaction Module takes an image file in and returns the masked file, using Splicer image segmentation and OCR.
Aadhaar masking is one module of SplicerAI, Extrieve's document data extraction SDK for KYC and identity documents. See the SplicerAI overview for ID detection, document classification and data extraction.
