All articles
Security & Privacy7 min read

PDF Security: Passwords, Sharing and Browser Privacy

Document security tends to fail in ordinary ways: the password travels in the same email as the file, or a confidential contract is uploaded to a random website to be compressed. Both are avoidable with a few simple habits.

What a PDF password does and does not do

PDF supports two kinds of password. An open (user) password encrypts the content, so the file genuinely cannot be read without the passphrase. An owner password only sets permission flags — no printing, no copying — which many viewers politely ignore.

If confidentiality actually matters, you want the open password. Treat permission flags as a hint to well-behaved software, not as protection.

Choosing and sharing a passphrase

Encryption strength is irrelevant if the secret is guessable. Four unrelated words beat a short password with a symbol substituted in, and they are easier to dictate over the phone.

  • Never send the password in the same message as the document.
  • Use a different channel — a phone call, a messaging app, or an in-person handover.
  • Store the passphrase in a password manager before you send the file; an unrecoverable PDF is genuinely unrecoverable.
  • Use a unique password per recipient when you need to know who leaked a document.

The hidden risk of online converters

Most online PDF tools work by uploading your file to a server, processing it there and giving you a link back. That means a copy of your document exists on infrastructure you do not control, subject to a retention policy you probably did not read.

For a holiday photo that is fine. For a signed contract, a payslip or a patient record, it may breach your own obligations — including data protection rules that treat any transfer to a third party as processing.

Why local, in-browser processing is different

Modern browsers can render, rewrite and encrypt PDFs entirely in JavaScript on your own device. No upload happens, so there is no server copy, no retention question and no transfer to disclose.

There is a simple way to verify the claim: start a conversion, then switch your device to airplane mode. If the tool finishes the job offline, the processing was genuinely local.

A short checklist before you send anything

Security is mostly discipline, and a repeatable checklist supplies it.

  • Have you removed pages the recipient should not see, rather than just blacking them out visually?
  • Does the document need a watermark to signal DRAFT or CONFIDENTIAL status?
  • Should it be encrypted, and is the password going out separately?
  • Have you kept an unmodified original for your own records?

Try it yourself — everything runs privately in your browser.

Protect a PDF