PDF metadata: hidden traces before send and filing

PDFs often carry more than visible text: author names from user accounts, internal paths, editing software vendors, created and modified times, sometimes revisions. On matter papers for opponents or courts that can reveal more than intended - or expose awkward internal working titles.

What typically travels along

Common: “Author” equal to the Windows login, title equal to an old filename (“draft_do_not_send”), producer fields with software versions, XMP from word processing. Merged bundles may retain metadata from parts. Redacting the visible page does not automatically clear those fields.

Not every meta field is critical. The test: would this entry trouble us before client, court or opponent? If yes, clean or regenerate.

Cleaning checklist

• Check title, author, subject before export.
• Remove internal working names from title and filename.
• After merging, re-check metadata on the final file.
• On sensitive matters: consider a “flat” regenerate (print/rebuild PDF).
• Keep version history internally without writing it into the filing file.
• Spot-check with a metadata viewer in the team standard.

Process, not a one-off fix

Ideally the metadata check sits at the same release point as size and orientation. Tools that clean on export reduce forgetfulness. LexLogik focuses on processing quality in the browser; final control of the filing copy remains firm routine - including metadata where the matter requires it.

Word-processing templates

Much metadata is born when the pleading is created. Firm-wide templates with neutral author fields reduce late PDF cleaning more than after-the-fact tools.

On cross-matter templates, do not leave client names in properties. Also check embedded attachments inside PDFs.

Release gate

Hang the metadata check on the same release point as size and orientation. Tools that clean on export reduce forgetfulness.

Link to redaction and data protection

Metadata can hold personal data (staff names, client codes in paths). That ties the topic to GDPR and role clarity: who may produce which final copy?

Metadata checklist before send

Check author, title, firm paths in properties and embedded comments. Strip working names like “client_confidential_v3”. The filing copy should show only what recipients are meant to see.

Batch-clean before bulk send

Before sending several PDFs to client or court: clean metadata in one pass and spot-open author fields. One forgotten internal code in a single exhibit title is enough for awkward questions. Save the cleaned copy under a new version name. You then know which file actually left the desk.

Check embedded file attachments and comment layers, not only visible properties. Some viewers show metadata only in expert views. A short expert look before sensitive sends belongs in the routine.

Producer and keyword fields

Also clear producer, creator and keyword fields when they carry internal project names. Viewers often hide them, so they are easy to miss. A “filing empty” metadata template speeds cleaning.

PDF metadata often reveals more than the visible text: internal paths, author names, version hints. Before send and filing they belong in a short cleaning routine. You then avoid unintended disclosure beside the pleading itself.