Aadhaar (UIDAI) 6
KYC & Onboarding 3
Digital Signatures 2
Data Privacy (DPDP) 2
MOSIP (National ID) 1
Products
Personal data discovery for the DPDP Act
PiiScan reads your systems from inside your own network, without changing them. It finds the personal data they hold and tells you what it could not read, and why.
Discovery
Databases, file shares, mailboxes and cloud storage, read where they are with read-only access.
Databases, file shares, mailboxes, object storage and cloud apps, scanned and reported from one place.
Aadhaar, PAN, GSTIN, UPI ID, voter ID, ABHA number, EPFO UAN and 21 more Indian types, beside global, US and UK ones.
Where an identifier has a check digit or a fixed structure, PiiScan checks it: Aadhaar by its check digit, cards and IMEI by the Luhn check, GSTIN and IBAN by their own rules. A number that fails its check is dropped, never reported as an Aadhaar; a column merely named for Aadhaar is flagged for review, without a value.
Optional services on your own hardware read text from scanned pages and images of ID cards, and recognise person names. Without OCR, images are listed as unread.
HL7 v2 messages, FHIR resources, CDA documents and DICOM headers are read as patient records, including the documents embedded in them.
Templates for banking, insurance, securities, telecom, hospitals, aviation, US health data and logistics. Copy one, then add your own types and rules.
Where it looks · 38 connectors
Your administrator adds each source once; PiiScan only reads it. Connectors marked * are included but have not yet been run against a live service, and not every database product and version has been either; ask us to confirm yours before you rely on it.
How it works
Add each source once, with a read-only account. PiiScan stores its credentials encrypted and never shows them again.
Run a scan now, or schedule it with a start time and an optional end time, such as 22:00 to 06:00. A scan still running at the end time pauses and resumes the next day. Schedule it once or daily.
Confirm each finding, dismiss it as a false positive or accept it knowingly, then re-check later whether the data is still there.
Coverage
Every file, table and message a scan sees is counted as read in full, unread or skipped, and a read that fails is counted as an error and listed the same way. An unread one keeps its reason until a scan reads it in full; no report or re-check treats it as clean.
A file or table read only in part is read again on the next scan, never skipped as unchanged. Findings from the part that was read are kept.
Every scan counts what it could not read and lists it, with the reason, in its scan run report. A scan that stops early says why.
A password-protected PDF, a scanned page with OCR switched off, a table larger than its row limit: each gap is named, so you can close it or accept it on purpose.
A re-check reports a value as gone only after re-reading the whole file or table. If it could read only part, the answer is “inconclusive”, never “gone”.
On local, NFS and SFTP sources, PiiScan records who can read each file and flags files that every user on the system can open and that hold personal data.
An inventory scan lists what is there without opening it. Everything it lists stays marked unread until a scan reads it.
Three answers for every file, table and message
Evidence
Each finding records where it sits. Eight reports, as PDF, CSV or JSON, show what was searched.
Each finding records its type, sensitivity, confidence and location: file path, table and column, mail folder and message, attachment, file inside an archive, scanned page or sheet.
By default a finding keeps a keyed hash of the value, not the value. Keeping values is opt-in and encrypted, and every reveal is audited.
Type in one person's identifier and see every place your scans have recorded it, across every source. The identifier is hashed in memory and never stored; the audit log keeps only the hash.
Re-check one finding, a whole scan or a whole source. A finding closes by itself only when a full re-read no longer finds the value, or the file or message is gone from a complete listing. If more than ten files in one source would close at once, a person decides first.
Source passwords and service keys are encrypted with AES-256-GCM under your own master key. No screen or API returns them, nothing logs them, and report files are stored encrypted.
Administrators configure, operators scan and review, auditors read and change nothing. Sign-in is rate-limited and sensitive actions are audited.
Eight reports, one question each
Each comes as PDF, CSV or JSON. Every report built from scan data ends by stating what was searched: which sources, how much of each, and for which kinds of personal data.
It never modifies, masks, moves or deletes anything it reads. Acting on a finding stays with your teams.
It runs on your own server and keeps its findings and reports there. It connects only to the sources you register and the optional services you host. No cloud service, no phone-home.
The readiness report is evidence for an obligation, not a certificate. Your DPO and counsel decide what it means.