What Your PDF Silently Leaks
When you export a document from Microsoft Word, Google Docs, Apple Pages, LibreOffice, or LaTeX to PDF format, the rendering compiler silently embeds extensive metadata tags directly into the binary header and trailer dictionaries.
These tags are invisible when viewing the document in standard PDF readers like Preview or Adobe Acrobat Reader, but can be extracted instantly with command-line tools like pdfinfo or exiftool.
| Dictionary Key | Data Exposed | Privacy Impact |
|---|---|---|
| /Author | Local OS username or domain account | De-anonymizes pseudonymous writers |
| /Producer & /Creator | Exact software name, OS version, printer queue | Fingerprints local machine environment |
| /CreationDate | UTC timestamp + timezone offset (e.g. +05'00') | Reveals geographic location & working hours |
| Adobe XMP Stream | XML document revision history & UUIDs | Enables correlation across disparate files |
How to Sanitize PDF Metadata Client-Side
Traditional web PDF cleaners require uploading your confidential contracts, legal filings, or research whitepapers to a remote server. This creates severe regulatory compliance and data breach exposure.
Our PDF Metadata Sanitizer executes entirely in your browser. It parses the binary array buffer, rebuilds the cross-reference (xref) table, nullifies the /Info catalog object, and wipes the Adobe XMP byte stream in pure JavaScript memory.
"Redacting the visible visual canvas does not protect you. True anonymity requires forensic scrubbing of the underlying binary metadata dictionaries."
— Privacy Engineering Team, Text Cleaner AI