Metadata scrubbing is the removal of personal data from fields a file carries but never shows. FRCP 34(b)(1)(C) lets the requesting party specify the form of production. The chosen form decides how much of that buried layer travels. anonym.plus clears it locally.
When this applies
Author, Last Saved By, company, and the full file path ride inside every Office file. Photos add EXIF coordinates. A static image form drops most of it; a native form under Rule 34(b)(2)(E)(ii) carries all of it out the door.
How anonym.plus handles it
- Load the files into anonym.plus on your device.
- It reads document properties and buried fields.
- The tool flags author, editor, path, and comment data.
- Confirm the flags in the property layer.
- Strip or replace each confirmed field.
- Save the scrubbed files on your device.
What you need to provide
- The files (DOCX, XLSX, PPTX, or PDF).
- A profile for the property fields to clear.
- An operator; Redact strips the buried values.
PII entity types detected
| Category | anonym.plus entity type | Example |
|---|---|---|
| Names | PERSON | Author property → [NAME] |
| Names | PERSON | Last edited by → [EDITOR] |
| Location | LOCATION | file path C:\Users\jdoe → [PATH] |
| Contact | EMAIL_ADDRESS | company email → [EMAIL] |
| Dates | DATE_TIME | created date → [DATE] |
| Identifiers | PERSON | username token → [USER] |
Compliance achieved
- The production form is fixed by FRCP 34(b)(1)(C) and 34(b)(2)(D).
- Author, Last-Saved-By, company, and file-path values are cleared.
- EXIF coordinates in embedded photos are found, not just document properties.
- Offline work keeps the property layer inside your firm.
Anonymize file metadata offline — see plans & start free →
Limitations & cautions
Buried fields vary by file type and app. Some, like custom XMP tags, may need a specific profile to catch. Always open one scrubbed file and check its properties before a full run, so no field slips through.
Frequently asked questions
Is metadata itself discoverable?
It can be, where it is relevant and proportional under Rule 26(b)(1). What actually travels turns on the agreed form: Rule 34(b)(1)(C) lets the requester name one, and Rule 34(b)(2)(D) makes you state the form you will use if you object.
Which fields leak the most?
Author and Last Saved By name people. The file path names a user account, and often an internal share. Photos carry EXIF coordinates. Those four cause most surprises.
Does it touch the visible content?
No. Scrubbing targets the buried metadata layer. The visible text and layout stay the same.