Production Metadata Scrub with anonym.plus

Clear PII from hidden property fields before a file leaves your firm.

Metadata scrubbing is the removal of personal data from the buried properties of files produced in the form set by FRCP 34(b). anonym.plus runs locally and clears author, editor, and path fields you cannot see.

When this applies

A clean-looking file can still carry the author name, edit history, and a path full of usernames in its properties. That layer leaks on disclosure.

How anonym.plus handles it

  1. Load the files into anonym.plus on your device.
  2. It reads document properties and buried fields.
  3. The tool flags author, editor, path, and comment data.
  4. Confirm the flags in the property layer.
  5. Strip or replace each confirmed field.
  6. Save the scrubbed files on your device.

What you need to provide

PII entity types detected

Categoryanonym.plus entity typeExample
NamesPERSONAuthor property → [NAME]
NamesPERSONLast edited by → [EDITOR]
LocationLOCATIONfile path C:\Users\jdoe → [PATH]
ContactEMAIL_ADDRESScompany email → [EMAIL]
DatesDATE_TIMEcreated date → [DATE]
IdentifiersPERSONusername token → [USER]

Compliance achieved

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

Why scrub buried file properties?

Files carry author, editor, and path data that leak names and usernames on disclosure. FRCP 34(b) lets parties specify the production form, and scrubbing fits a static form.

What fields get cleared?

Author, last-edited-by, created and modified dates, file paths, comments, and custom properties, depending on your profile.

Does it touch the visible content?

No. Scrubbing targets the buried metadata layer. The visible text and layout stay the same.