Mortgage reporting dataset anonymisation is the removal of applicant identifiers from a reporting file. FCA Handbook SUP 16.11 sets the Product Sales Data (PSD) return most mortgage lenders must submit, covering the reportable loan and applicant-category fields without naming individuals in the return itself. 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 postcode area, matching the categories the SUP 16.11 return expects. Quasi-identifiers can re-link a person under the ICO's motivated-intruder test, so you strip direct fields before the working file is shared internally.
How anonym.plus handles it
- Open the submission file in anonym.plus on your device.
- The tool flags names, NI numbers, and contact fields.
- Local OCR reads any scanned supporting pages.
- Keep the reportable codes and area data intact.
- Swap or black out the confirmed direct fields.
- Save the clean dataset locally.
What you need to provide
- The submission file (CSV, XLSX, or PDF).
- An operator (Replace keeps the codes readable).
- Optional allow-list for reportable code columns.
PII & financial identifiers detected
| Category | anonym.plus entity type | Example |
|---|---|---|
| Names | PERSON | applicant row → [APPLICANT] |
| Identifiers | UK_NINO | QQ 50 88 22 C → [NINO] |
| Money | MONEY | advance amount → [AMOUNT] |
| Location | LOCATION | postcode area → [AREA] |
| Dates | DATE_TIME | completion date → [DATE] |
| Contact | EMAIL_ADDRESS | contact email → [EMAIL] |
Compliance achieved
- Supports privacy care for data collected toward the FCA SUP 16.11 Product Sales Data return.
- Keeps the reportable codes and area fields you must submit.
- Applies the ICO motivated-intruder test (UK GDPR Recital 26) to the quasi-identifiers that remain.
- Offline work keeps the dataset off any server.
Anonymise mortgage reporting datasets offline — see plans & start free →
Limitations & cautions
Stripping names leaves quasi-identifiers like postcode, amount, and date that can re-link a person when combined, against the ICO motivated-intruder test. True anonymisation needs care with those fields; turn the reversible alias map OFF for real anonymity, and remember the SUP 16.11 return itself is submitted to the FCA, not shared as this working file.
Frequently asked questions
Does removing names make the dataset anonymous?
Not by itself. Postcode, amount, and date can re-link a person when combined, which is exactly what the ICO's motivated-intruder test asks about. Generalise or suppress those quasi-identifiers for stronger anonymisation.
Will the reportable fields survive?
Yes. Allow-list the code columns the SUP 16.11 return expects 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 alias map turned off; the regulatory submission itself goes to the FCA through its own separate reporting channel, not through this tool.