DSA files you didn't scan yourself.
Partners and field staff send photos, scans and ZIPs in every quality.
Mask partner uploads on arrival, and clean up old loan files in batch.
Test with your NBFC files →For banks, NBFCs, housing finance companies and insurers.Faded, rotated or low-quality copies are what loan files are made of: 99.94% of Aadhaar numbers masked on 10,001 real loan files. Aadhaar Masking covers the first 8 digits of Aadhaar numbers across photos, scans, PDFs and 150+ page loan files, and covers the Aadhaar QR code whole.
Hosted in AWS Mumbai, in your own AWS account, or on your own servers. Every answer carries a per-page record of what was covered.
Illustrative sample, not a real document
Lenders that run Aadhaar masking by HabileLabs
of Aadhaar numbers masked on 10,001 real loan files
of the 2,498 Aadhaar QR codes in the same test covered
pages a minute, measured end to end through the API
documents masked in one week for a small finance bank
Measured on 10,001 real loan files, 15 October 2026; method on the Accuracy page. The one-week figure is a customer project (Utkarsh Small Finance Bank: 2.8 lakh Aadhaar documents masked in one week, offline, inside the bank), as published on habilelabs.io. How it was measured, and the misses.
The real problem in lender archives
Basic masking tools work on a clean, straight e-Aadhaar. Your loan files are full of faded photocopies, field photos and scans. These are the documents that break those tools, and the ones Aadhaar Masking is built for.
Measured on 10,001 real loan files, 15 October 2026; method on the Accuracy page. The 8 numbers it missed are listed there. The pictures above are illustrations, not real documents.
Manual masking can't keep up, and basic OCR misses what it can't read. Either way, unmasked Aadhaar stays in your loan files.
Faded, rotated, multi-page. A 30-minute session for your bank, NBFC, HFC or insurance team, using your own sample files.
The one-digit risk
One page missed in one file is enough. An unmasked Aadhaar number is a finding in your next audit, and a data protection problem under the DPDP Act.
One exposed digit = an incompletely masked Aadhaar.
Inspections and internal audits look at stored KYC copies. An unmasked Aadhaar in an old file is an observation waiting to be written.
The DPDP Act's Schedule caps the penalty for failing reasonable security safeguards at ₹250 crore. See the rules →
Archives get shared with DSAs, vendors and auditors. Every unmasked copy travels with them.
Checking long loan files by eye is slow, tiring and inconsistent. The misses are the pages nobody looked at.
Rules & penalties
RBI, SEBI and IRDAI each put the duty on the regulated entity: it “shall ensure” the Aadhaar number is redacted. These are the regulators' own words, each with its source.
What the law puts at stake
Maximums set by law; the DPDP penalty provisions commence 13 May 2027. Regulators decide actual penalties.
“The bank shall, where its customer submits a proof of possession of Aadhaar Number containing Aadhaar Number, ensure that such customer redacts or blacks out his Aadhaar number through appropriate means”
Paragraph 23, Explanation 1 (the same text stood in Section 16 of the KYC Master Direction, 2016) · 28 November 2025
“Actual Aadhaar number should not be stored in any business databases other than ADV”
Directions to requesting entities · 4 November 2025
“At no point in time, more than last four digits of the Aadhaar number of any individual should be stored by the insurers in physical or digital form.”
Circular of 29 January 2019, as reported · 29 January 2019
“It shall be ensured that full Aadhaar number is not stored and displayed anywhere in the system and wherever required only last 4 digits of Aadhaar number may be displayed.”
SEBI/HO/MIRSD/SECFATF/P/CIR/2023/169 · 12 October 2023
What this means for your teams
Aadhaar appears everywhere
Aadhaar isn't only on the card. It hides inside forms, statements and tables, and in files your team forgot existed.
Buyer, seller and witness Aadhaar inside long legal documents.
Typed or handwritten fields labelled Aadhaar No.
Aadhaar inside rows and columns of statements and reports.
Customer lists and DSA trackers with an Aadhaar column.
Bulk folders from partners and old systems, opened and masked.
Mobile photos of the physical card, front and back.
Multi-page branch scans with mixed documents in one file.
Downloaded e-Aadhaar letters shared by customers.
A second copy lying behind the main document in a photo.
Long files
A home loan file can run to hundreds of pages: KYC, income proofs, property papers, guarantor forms. The engine reads every page, so the copy on page 112 is treated like the one on page 1.
Different formats. Different languages.
The engine looks for the words around a 12-digit number, in English and Hindi, and checks the number's own checksum, to tell an Aadhaar number apart from the other numbers in your files.
Illustrative example
How it works
Mask what's already in your archive, and mask new uploads before they are stored.
01Your files
Send files by API at upload, or run a whole archive: ZIP batches through the API, or a folder on your own servers.
By API or batch02The engine finds
Every page is read, four ways round, in English and Hindi, to find each Aadhaar number by its label and its checksum.
Label and checksum, any angle03Masked
The first 8 digits are covered and the last 4 stay readable, UIDAI's masked form. The Aadhaar QR code is covered whole.
First 8 digits and the QR covered04Proof
Every answer carries a per-page record of what was found and covered, to show an auditor.
A record for every pageUse cases
The same masking engine, set up around where your Aadhaar copies come from.
Partners and field staff send photos, scans and ZIPs in every quality.
Mask partner uploads on arrival, and clean up old loan files in batch.
Test with your NBFC files →Sale deeds, agreements and guarantor forms carry Aadhaar for buyers, sellers and witnesses.
150+ page files masked page by page, kept masked for the life of the loan.
Test with a home loan file →Account opening forms and KYC photocopies scanned at branches over many years.
Back-file clean-up of faded, rotated scans, without replacing core banking.
Plan your back-file clean-up →Millions of pages across products and regions, stored in more than one system.
425 pages a minute measured end to end, with a record for every page.
Book an enterprise walkthrough →Aadhaar arrives with proposal forms, nominee details and claim documents.
Mask at upload, so the stored copy is the masked one.
Test with your forms →Customers upload card photos and e-Aadhaar PDFs in seconds.
One API call before storage, alongside FinHub's KYC and verification APIs.
Add masking to your journey →Common questions
The questions CXOs, CTOs and compliance heads ask us most about Aadhaar masking.
Book a 30-min demoRBI's KYC Directions say the bank shall “ensure that such customer redacts or blacks out his Aadhaar number through appropriate means” when it takes a copy without authenticating the number. SEBI and IRDAI use similar wording for intermediaries and insurers, and UIDAI's Circular 14 of 2025 says the “Actual Aadhaar number should not be stored in any business databases other than ADV”. UIDAI's masked form covers the first 8 digits and leaves the last 4 visible. The quotes and their sources are in the rules section of this page.
Before the copy is stored. The safest setup masks every upload at the point of capture, at the branch, in the DSA app or in your customer app, and runs a batch job on documents already in storage.
The rules speak of the copies you hold, not of when you took them: UIDAI's regulations forbid keeping Aadhaar numbers “for longer than is necessary”. Most lenders start with a back-file clean-up of their DMS and loan archives, then switch on masking for new uploads.
The Digital Personal Data Protection Act's Schedule caps the penalty for failing to take reasonable security safeguards at ₹250 crore, with the penalty provisions commencing 13 May 2027 under the 2025 Rules, and the Rules give seventy-two hours to notify the Board of a breach. Section 37 of the Aadhaar Act makes intentional disclosure of identity information punishable with imprisonment of up to three years. Regulators decide actual penalties; this is context, not legal advice.
Yes. The vault is where full Aadhaar numbers may be kept. Every other copy, such as KYC images, loan files and forms, should carry the masked form.
99.94% of Aadhaar numbers (13,541 of 13,549) and 100% of Aadhaar QR codes (2,498 of 2,498) were masked on 10,001 real loan files sent through the hosted API on 15 October 2026. An independent reader counted the numbers and codes on every page before and after masking, and a person checked every one it said was still readable. The method, the figures and the misses are on the Accuracy page.
It is built for real archives: photocopies of photocopies, sideways or upside-down scans, blurred phone photos, glare, cards in plastic sleeves and screenshots. The page is looked at four ways round and each candidate is read twice. Of the 8 numbers the benchmark missed, six were card photos; they are listed on the Accuracy page.
Yes. Every page is read, so an Aadhaar copy on page 112 is treated like the one on page 1, and the masked file keeps the same page order. Long PDFs run in the background through the API; a 500-page PDF takes about a minute.
English and Hindi; other Indian scripts can be added on request. JPG, PNG, TIFF and PDF files, Excel sheets and ZIP archives, and links to files in your own cloud storage.
It is covered whole, on purpose: the Aadhaar QR code carries the number. All 2,498 Aadhaar QR codes in the benchmark were covered. QR codes that are not Aadhaar's, such as payment codes, e-stamps and links, are decoded and left alone.
Only a number that passes the Aadhaar checksum and the page's evidence, such as a label like Aadhaar No. or आधार संख्या, is covered. PAN, dates, amounts, phone and account numbers are left readable, and a page of figures is not masked on a lucky match.
About 500 pages a minute with 40 parallel masking environments; 425 pages a minute measured end to end through the API. Back-files run in batch, as ZIP files of up to 500 MB through the API or as a folder on your own servers, and new uploads are masked by API.
Three ways. The hosted API runs in AWS Mumbai and deletes documents after masking, typically within 24–48 hours. The AWS Marketplace edition runs inside your own AWS account. The on-premises edition is a Docker image on your own servers. Every answer carries a per-page record of what was found and covered.
Annual page packs on AWS Marketplace, in rupees through AWS India: 2.5 lakh pages a year from ₹75,000 (+GST), down to ₹0.10 a page on the largest pack. The hosted API and the on-premises edition are quoted for your volume, and we share a plan for your volumes within one business day of the first session.
Yes. Send us your hardest sample files, faded and rotated ones included, and we will show you the masked output in a 30-minute session.
Book your demo
A 30-minute session for your company: we run your sample files, faded and rotated ones included, and show you the masked output.