HMDA Dataset Anonymization with anonym.plus

De-identify an HMDA submission file while the reportable fields stay usable.

HMDA dataset anonymization is the removal of applicant identifiers from a reporting file. HMDA (12 CFR 1003) governs what data a lender reports. anonym.plus marks each item on your device, so the reportable fields stay usable while direct identifiers go.

When this applies

A submission row ties demographics to amounts, dates, and a tract. Quasi identifiers can re-link a person, so you strip direct fields before sharing.

How anonym.plus handles it

  1. Open the submission file in anonym.plus on your device.
  2. The tool flags names, SSNs, and contact fields.
  3. Local OCR reads any scanned supporting pages.
  4. Keep the reportable codes and tract data intact.
  5. Swap or black out the confirmed direct fields.
  6. Save the clean dataset locally.

What you need to provide

PII & financial identifiers detected

Categoryanonym.plus entity typeExample
NamesPERSONapplicant row → [APPLICANT]
IdentifiersUS_SSN509-88-2231 → [SSN]
MoneyMONEYloan amount → [AMOUNT]
LocationLOCATIONcensus tract → [TRACT]
DatesDATE_TIMEaction date → [DATE]
ContactEMAIL_ADDRESScontact email → [EMAIL]

Compliance achieved

Anonymize HMDA datasets offline — see plans & start free →

Limitations & cautions

Stripping names leaves quasi identifiers like tract, amount, and date that can re-link a person when combined. True de-identification needs care with those fields; turn the reversible name map OFF for real anonymity.

Frequently asked questions

Does removing names make the dataset anonymous?

Not by itself. Tract, amount, and date can re-link a person when combined. Generalize or suppress those quasi identifiers for stronger de-identification.

Will the reportable fields survive?

Yes. Allow-list the required code columns so they stay while direct identifiers are removed.

Is the dataset uploaded?

No. The app is fully offline, so the file never leaves your device. For true anonymity, keep the name map turned off.