Before disclosure
Remove Hidden Data From a Legal PDF
Before you file or disclose a legal PDF, remove its hidden metadata — court filings, disclosures and regulatory submissions have repeatedly leaked the drafter's name, the law firm, internal timestamps and even prior content through PDF metadata. A PDF carries an Info dictionary (author, title, subject, keywords, producer, creation and modification dates) and a second XMP stream that survives if you only clear the visible properties. MetaDocu removes both in your browser, with no upload, and produces a verification report so you can disclose the document knowing it reveals only its intended content. For privileged or regulated material, local processing means the file never passes through a third-party server. Drop the PDF in below to scan and clean it.
Scan & clean your legal PDF
Processed in your browser, never uploaded.
Audit Local Metadata Risks
Drag files below to generate an offline privacy audit report.
Supported Scanners
Why legal PDFs leak more than they look
A PDF that began life as a Word document often inherits the original author, company and timestamps into its metadata during conversion, and the conversion tool adds its own producer/creator fingerprint. Because this lives in both the Info dictionary and the XMP packet, clearing one can leave the other behind. For a disclosure where the drafter's identity or timing is sensitive, removing both copies is essential — MetaDocu does this and verifies the result.
Hidden fields in a legal PDF
What MetaDocu finds and removes in a PDF before you disclose it.
| Hidden field | What it exposes | Risk | How MetaDocu removes it |
|---|---|---|---|
Author / Creator dc:creator · PDF /Author | The real name (or Office sign-in name) of whoever first created the file — often your full legal name. | High | Cleared from the OOXML core properties / PDF Info dictionary in browser memory; the field is emptied, not just hidden. |
Application & version Application/AppVersion · PDF /Producer · /Creator | The exact software and version used — a fingerprint for targeting known vulnerabilities or deanonymizing authors. | Low | Normalized/removed from app properties and the PDF Producer/Creator fields. |
Created / Modified dates dcterms:created/modified · PDF /CreationDate /ModDate | Precise creation and last-edit timestamps — builds a timeline of your activity. | Medium | Removed or reset so no editing timeline leaks. |
Title / Subject / Keywords dc:title, dc:subject, cp:keywords · PDF /Title /Subject /Keywords | Internal codenames, client names, or tags left in the properties even when not shown in the document text. | Medium | Cleared from both OOXML properties and the PDF Info dictionary. |
XMP metadata stream /Metadata XMP packet (xmpMM:DocumentID, InstanceID, History) | A second copy of author/tool data plus document/instance IDs that survive even when the Info dictionary is cleared. | High | The XMP packet is removed alongside the Info dictionary so no duplicate metadata remains. |
Frequently asked questions
How do I remove hidden data from a legal or disclosure PDF?
Open the PDF in MetaDocu, scan it, and clear the metadata in one click before downloading — locally, with no upload. It removes the Info dictionary fields (author, title, subject, keywords, producer/creator, creation and modification dates) and the XMP metadata stream so no duplicate copy of the drafter's identity or tool data remains. A verification report confirms the fields are empty, which matters when you must certify that a disclosure contains only its intended content. Because nothing is uploaded, privileged material never touches a third-party server.
Why isn't clearing the PDF's visible properties enough?
Because PDFs commonly store metadata twice — in the Info dictionary and in an embedded XMP stream. Many quick edits or basic property dialogs touch only the Info dictionary, leaving the XMP copy intact, so the author and tool data reappear when the file is inspected with the right viewer. For legal disclosure, that residual copy is exactly the kind of thing that leaks. MetaDocu removes both the Info dictionary and the XMP packet together, which is why a file it cleans doesn't carry a hidden second copy.
Can I be sure the metadata is gone before filing?
Yes. MetaDocu shows a verification report listing what was removed, and you can independently confirm: open the cleaned PDF's Document Properties in any viewer and the author, title, dates and producer fields should be blank. Because MetaDocu strips the fields from the PDF's structure — both the Info dictionary and the XMP stream — rather than hiding them, the values are physically absent, not merely blanked on screen. That gives you something defensible to rely on before a filing.
Disclose the content, not the metadata
Remove the Info dictionary and XMP stream in your browser — nothing uploaded.