The Complete Guide to PDF Document Security

The three questions to ask before you share a PDF

Before sending any document, it helps to run through three quick questions. First, who should be able to open this, and only this person? Second, what inside the file is actually sensitive, and does the recipient even need it? Third, once it has served its purpose, what happens to the copies? Most document leaks are not sophisticated hacks; they are ordinary files that ended up somewhere they should not have, because nobody asked these questions.

Each question maps to a tool or habit. Controlling who can open a file means a password. Controlling what is inside means redaction and stripping hidden data. Controlling what happens afterward means choosing services that delete files and keeping your own copies organised.

Passwords: controlling who can open the file

A password on a PDF is the most direct protection you have. It travels with the file, not the inbox, so even if the email is forwarded ten times, only someone with the password can open the document. This is the right choice for anything with financial, legal or personal detail: statements, agreements, ID scans, payroll runs.

The security of a password is only as good as how you share it. The cardinal rule is to send the password through a different channel than the file. Email the PDF, then send the password by text message or a phone call. If the password sits in the same email thread as the attachment, anyone who sees the thread has both halves and the protection is gone.

When you no longer need protection on a file you own, for example to merge it with other documents or edit it, you can remove the password you already know. This is different from cracking a file you are not authorised to open, which these tools do not do.

Redaction: controlling what is inside

Redaction means permanently removing sensitive content from a document before you share it: an account number on a statement, a name in a report, a signature block, an address. The important word is permanently. Drawing a black rectangle over text in some editors only covers it visually; the underlying text is still in the file and can be copied out. Proper redaction removes the content itself, so what is gone is truly gone.

Redaction is essential whenever a document must be shared but not in full. A landlord sharing a bank statement to prove income should redact the individual transactions. A company publishing a contract should redact names and figures that are not public. A support team sharing a screenshot should redact the customer details. If in doubt, redact more, not less; you can always share an unredacted copy with someone who genuinely needs it.

Watermarks: controlling how a file is used

A watermark does not lock a document, but it changes how it can be used. Stamping DRAFT across a document under review stops an unfinished version being mistaken for the final one. Marking pages CONFIDENTIAL sets expectations for anyone who receives them. Adding a company mark to shared reports discourages casual redistribution and makes the source clear.

Watermarks are a deterrent and a label rather than a hard control. They are most useful for documents that circulate widely, where you cannot password every copy but you want every copy to carry a clear signal about its status and origin.

Signatures: proving who agreed

Signing a PDF replaces the print-sign-scan cycle. You add your signature directly onto the page and send it back, which is faster and produces a cleaner document. For most everyday agreements, an image of your signature placed on the correct line is exactly what the other party expects.

Signatures and passwords solve different problems and often go together: you sign a contract to show you agreed to it, and you may password-protect the signed file before sending it so only the counterparty can open it.

The detail most people miss: hidden metadata

Every PDF carries metadata you never see on the page: the author name, the software used, creation and edit dates, and sometimes the original file path on someone's computer. For a document you publish or send externally, this hidden data can reveal more than you intend, from who really wrote it to when it was last changed.

Stripping metadata before publishing a file is a simple, often-forgotten step. It is especially worth doing for anything that goes onto the public web or to a party you do not know well.

Putting it together: a simple workflow

For a typical sensitive document, a sensible sequence is: redact anything the recipient does not need, strip the hidden metadata, sign it if agreement is required, and password-protect it before sending, with the password shared separately. Not every document needs every step, but running through them takes seconds and closes the gaps that cause most leaks.

Finally, prefer tools that process files and then delete them, rather than services that retain your documents. The less time your sensitive file sits on someone else's server, the smaller the window for anything to go wrong.