Scan uploaded files for personally identifiable information (PII). Detect emails, SSNs, phone numbers, dates of birth, IP addresses, MRNs, and GPS coordinates with severity-rated findings and HIPAA Safe Harbor anonymization guidance.
Load example Metadata Anonymization data to see the full workflow
Drop your file here to scan for PII
Accepts CSV, TSV, JSON, XML, and TXT files. All processing happens locally in your browser.
CSVTSVJSONXMLTXT
When to use
Screen research datasets before depositing in public repositories (e.g., Dryad, Figshare, ICPSR)
Check clinical data exports for residual PHI before analysis on non-secure systems
Audit anonymization pipelines by verifying outputs are free of PII patterns
Review data files before sharing with collaborators or including as journal supplements
Quick pre-check before submitting data to IRB or data safety monitoring boards
Do not use for
As the sole method for HIPAA compliance -- this is a screening aid, not a certification tool
For binary files (XLSX, DOCX, PDF) -- convert to text-based formats first
To detect indirect identifiers or re-identification risk from quasi-identifier combinations
As a replacement for expert review by a privacy officer or qualified statistician
PII can hide in free-text fields
Clinical notes, comments, and free-text columns often contain names, dates, and other identifiers that structured de-identification misses. Always scan entire files, not just structured columns.
Dates of birth vs. study dates
This tool flags date patterns that could be dates of birth. Study dates and procedure dates may also need anonymization under HIPAA if they relate directly to an individual. Review flagged dates in context.
Column headers reveal data structure
Even if PII values are removed, column headers like "patient_name" or "ssn" signal that the dataset was derived from identified sources. Consider renaming columns to neutral labels (e.g., "subject_id").
Pseudonymization is not anonymization
Replacing names with codes (pseudonymization) is reversible if the key exists. Under GDPR, pseudonymized data is still personal data. True anonymization means no key exists to reverse the mapping.
1
Method
The scanner reads uploaded files as plain text and applies regular expressions for each PII category. Email, SSN, phone, IP address, date, MRN, and GPS patterns are matched line-by-line with severity classification (high for direct identifiers, medium for indirect). Column headers in the first row are checked against known PII field name patterns. Results include redacted samples (first/last 2 characters preserved), line numbers, and HIPAA Safe Harbor-aligned anonymization suggestions. All processing is client-side; no data leaves the browser.
2
Published
Published 2026-04-05. Calculations support planning and documentation; verify procurement decisions against manufacturer specifications or institutional SOPs.
3
How to cite
How to Cite
ConductScience Metadata Anonymization Checker. ConductScience, Inc. 2026. Available at: https://conductscience.com/tools/metadata-anonymization-checker
U.S. Department of Health and Human Services. Guidance Regarding Methods for De-identification of Protected Health Information in Accordance with the HIPAA Privacy Rule. 2012.
El Emam K, Arbuckle L. Anonymizing Health Data: Case Studies and Methods to Get You Started. O'Reilly Media; 2013.
Data Anonymization Fundamentals
Research data sharing accelerates scientific progress but introduces privacy risks when datasets contain personally identifiable information (PII). Effective anonymization must balance two goals:
Privacy protection -- ensuring no individual can be re-identified from the released data
Data utility -- preserving enough information for meaningful analysis
The most common approach in biomedical research is HIPAA de-identification using the Safe Harbor method, which requires removal of 18 specific identifier categories. However, removal alone may be insufficient when combinations of seemingly anonymous variables (quasi-identifiers like age + ZIP + gender) can be linked to external datasets.
Key anonymization techniques include:
Suppression -- removing the identifier entirely (e.g., deleting a name column)
Generalization -- reducing precision (e.g., exact age to age range, ZIP code to state)
Pseudonymization -- replacing identifiers with consistent codes (e.g., patient ID)
Perturbation -- adding noise to continuous values while preserving distributions
k-Anonymity -- ensuring every record is indistinguishable from at least k-1 others
The 18 HIPAA Safe Harbor Identifiers
The HIPAA Safe Harbor method (45 CFR 164.514(b)(2)) requires removal of these 18 identifier categories:
1. Names
2. Geographic data smaller than state (street address, city, ZIP code)
3. Dates (except year) directly related to an individual
4. Phone numbers
5. Fax numbers
6. Email addresses
7. Social Security numbers
8. Medical record numbers
9. Health plan beneficiary numbers
10. Account numbers
11. Certificate/license numbers
12. Vehicle identifiers and serial numbers
13. Device identifiers and serial numbers
14. Web URLs
15. IP addresses
16. Biometric identifiers
17. Full-face photographs and comparable images
18. Any other unique identifying number, characteristic, or code
After removing these identifiers, the covered entity must have no actual knowledge that the remaining information could be used alone or in combination to identify an individual.
Frequently asked
What is PII (Personally Identifiable Information)?
PII is any data that can be used to identify a specific individual, either alone or in combination with other information. Common examples include names, email addresses, Social Security numbers, phone numbers, dates of birth, medical record numbers, and IP addresses. In research contexts, PII must be removed or de-identified before datasets can be shared, published, or deposited in repositories.
What is HIPAA de-identification?
HIPAA de-identification is the process of removing protected health information (PHI) from datasets so that individuals cannot be identified. The HIPAA Privacy Rule provides two methods: the Safe Harbor method, which requires removal of 18 specific identifier types, and the Expert Determination method, which requires a qualified statistical expert to certify that the risk of identification is very small. This tool checks for patterns matching the 18 Safe Harbor identifiers.
What is the Safe Harbor method?
The Safe Harbor method (45 CFR 164.514(b)(2)) requires removal of 18 categories of identifiers: names, geographic data smaller than state, dates (except year), phone numbers, fax numbers, email addresses, SSNs, medical record numbers, health plan beneficiary numbers, account numbers, certificate/license numbers, vehicle identifiers, device identifiers, URLs, IP addresses, biometric identifiers, full-face photos, and any other unique identifying number. After removal, the covered entity must have no actual knowledge that remaining information could identify an individual.
Does this tool store or transmit my data?
No. All file scanning happens entirely in your browser using client-side JavaScript. Your files are never uploaded to any server. The text content is read into memory, scanned against regex patterns, and results are generated locally. When you close or refresh the page, all data is discarded.
What file formats are supported?
The tool accepts CSV, TSV, JSON, XML, and plain text (TXT) files. Any text-based format will work since the scanner reads the file as plain text and applies pattern matching across all lines. Binary formats (XLSX, DOCX, PDF) are not supported -- convert them to CSV or text first.
Can this tool guarantee my data is fully de-identified?
No. This tool uses pattern matching (regex) to detect common PII formats and is intended as a screening aid, not a certification tool. It cannot detect all forms of PII -- for example, it cannot identify indirect identifiers, rare name formats, or context-dependent information that could be used for re-identification. For HIPAA compliance, consult a qualified privacy officer or use the Expert Determination method with a statistician.