Native-file redaction is the removal of personal data from documents in their original format, which CPR PD 31B lets parties agree as the disclosure form. anonym.plus runs locally on Word, Excel, and PDF files, so the content stays usable, including the layers a converted image would drop.
When this applies
Some disclosure calls for the original format to keep formulae or comments alive, and CPR 31.9 excuses you from producing a second, identical static copy once a native version exists. Those same native files hide names in cells, comments, and tracked changes that a static export would not show.
How anonym.plus handles it
- Open the file in anonym.plus on your device.
- It scans cells, comments, notes, and tracked changes.
- The tool flags names, contacts, and IDs in each area.
- Confirm the flags, including hidden comment text.
- Replace or mask each confirmed value.
- Save the clean document on your device.
What you need to provide
- The file (DOCX, XLSX, PPTX, or PDF).
- An operator; Replace keeps the document usable.
- Optional rules to keep non-PII codes and formulae.
PII entity types detected
| Category | anonym.plus entity type | Example |
|---|---|---|
| Names | PERSON | cell value → [NAME] |
| Contact | EMAIL_ADDRESS | comment email → [EMAIL] |
| Identifiers | UK_NINO | hidden NINO → [NINO] |
| Dates | DATE_TIME | tracked edit date → [DATE] |
| Location | LOCATION | slide footer → [ADDRESS] |
| Contact | PHONE_NUMBER | notes phone → [PHONE] |
Compliance achieved
- Removes PII from native files disclosed under an agreed CPR PD 31B format.
- Scans comments, notes, and tracked changes, not just the visible body text.
- Recognises that CPR 31.9 means one clean native version can stand in for a duplicate static copy.
- Offline work keeps the original data inside your firm.
Anonymise native files offline — see plans & start free →
Limitations & cautions
Such files hide data in comments, hidden rows, and revision history. Confirm those layers are scanned. Disclosing the original format can expose more metadata than an image, so weigh whether a static export fits the request better.
Frequently asked questions
Why disclose native files at all?
The original format keeps formulae, comments, and structure that a static image loses. CPR PD 31B lets parties agree the form, and native is sometimes the only version that shows the real content.
Does it catch hidden cells and comments?
Yes. The tool scans comments, notes, hidden rows, and tracked changes, where names often hide even after a document looks clean on screen.
Can I keep formulae while clearing names?
Yes. An allow-list keeps non-PII codes and formulae while personal data is swapped out, and CPR 31.9 means you will not usually need a second static copy once this one is clean.