What your documents say about you

Open the properties of any PDF on your machine. There is a reasonable chance it names its author, the software that made it, when it was created, when it was last modified, and, depending on how it was produced, the title of whatever template it started life as.

None of this appears on any page. All of it travels with the file.

What is typically in there

Author. Often a personal name, sometimes a system username, occasionally the name of whoever set up the machine years ago.

Title. Frequently left as whatever the source document was called, which for template-based work means the previous client's name.

Creator and producer. The application that authored the file and the one that wrote the PDF. Harmless in itself, though it tells a reader something about your systems.

Timestamps. Creation and modification dates, which can contradict what a covering email says about when something was prepared.

Keywords and subject. Usually empty, occasionally full of internal categorisation.

Where else information hides

Metadata in the document properties is the obvious layer. There are others.

Embedded image metadata. A photograph placed in a document may carry its own EXIF data, including the camera, the time, and sometimes GPS coordinates. Stripping the PDF's properties does not touch this.

Revision history. PDFs can be saved incrementally, with each change appended rather than rewritten. A document that has been through review may contain its earlier states, including text that was deleted.

Comments and annotations. Review comments survive export more often than people expect.

Attachments. Files can be embedded inside a PDF and never appear on a page.

Why it matters more than it sounds

The individual facts are small. The pattern is not. A document sent to a competitor that names the internal author, the template it came from, and the fact it was created four minutes before the deadline tells a story nobody intended to tell.

For anything going outside your organisation, clearing document properties should be a habit rather than a decision.

What to do

Clear the metadata as the last step before sending, after all editing is finished. Editing tools will happily write new metadata over your cleaned file.

Flatten forms if they have been filled in. Sanitise the file if it came from outside and might carry attachments or scripts. And extract the text and read it, which catches revision history and hidden content that properties-clearing does not.

Two minutes, and it removes an entire category of embarrassment.

Where the information comes from

Nobody types this in. It accumulates.

The author field is populated from the account name on the machine that created the document, which is often a full name and sometimes a username that maps to one. The title is inherited from the source file, which for template-based work is whatever the template was called.

Producer and creator record the software chain. Timestamps record when the file was made and last changed, in a form that does not care what a covering note claims.

None of it is edited by anyone. It is simply carried along.

A worked example

A firm sends a proposal to a prospective client. The PDF's title field reads "Proposal, Henderson, v3", because the document began as a copy of the last one.

Nothing on any page mentions Henderson. The recipient opens the document properties out of idle curiosity and now knows who else the firm works for, that this proposal is a variation of another one, and that it reached its third revision.

No page was wrong. Nothing was leaked in the ordinary sense. The document simply carried its history with it.

Removing it properly

Clear the metadata as the last step before sending. Editing tools write new metadata as they save, so clearing it early and then making a change puts it back.

For anything that has been through review, resave the file rather than only clearing fields, which discards accumulated revision history at the same time.

For documents built from photographs, remember that image metadata is separate. A photo taken on a phone may carry the camera, the time and sometimes the location, and clearing the document properties does not touch it.

Making it routine

The reason this catches people is that it happens at the end, under pressure, when the goal is to get something sent.

Treat it as part of sending rather than part of editing. The same way you would check the recipient on an email before pressing send: a fixed, boring step that costs two minutes and removes an entire class of embarrassment.

For anything leaving the organisation, clear the metadata, strip active content, and read the extracted text. Those three take less time than writing the covering email.

Checking before you send, not after

Document properties are visible in every PDF reader, usually under File and then Properties, and take five seconds to look at.

Make it the last thing you do before attaching a file. If the author is a person's name, the title is a previous client's, or the creation date contradicts your covering note, you will want to know before the recipient does.