Two mechanisms that look like one
This is not a criticism of the format — it is how it was designed. Permission flags were meant to signal intent, not to resist a determined reader. Once you internalise that, the right control for each situation becomes obvious.
Which control for which situation
A contract, a salary file, a customer list going to someone outside your organisation.
PDFnoted: Set an open password and deliver the password through a different channel. The file is unreadable without it, regardless of which viewer or tool is used.
A report you would rather people read on screen than pass around.
PDFnoted: Set printing and copying restrictions. This stops casual misuse and signals intent; it does not stop someone who intends to copy the file.
Material going to several recipients where onward sharing is the real risk.
PDFnoted: A visible or hidden recipient mark makes copies attributable. It does not prevent copying, which is not its job.
Documents that must stay readable for years but should not be altered.
PDFnoted: Archival format for the file; access control at the storage layer for the confidentiality. Encryption inside the file is a poor long-term archive strategy because a lost password means a lost record.
How PDFnoted protects a file
- Work locallyThe document is read on your device, so the password you set is never transmitted anywhere.
- Set the passwordsAn open password to encrypt, a permission password to control usage, or both — and they should differ.
- Choose the permissionsPrinting, copying, editing and extraction, each independently, including print quality.
- Save and testSave the protected copy and reopen it. Confirming the behaviour takes ten seconds and catches every mistaken setting.
Being straight about the limits
✓ Worth doing
- Encrypt with an open password when confidentiality matters
- Use different passwords for opening and for permissions
- Send the password through a different channel from the file
- Clean metadata before sharing, independently of protection
- Reopen the file afterwards and check it behaves as intended
✗ Not worth the risk
- Rely on "no printing" to stop a determined reader
- Put the password in the same email as the attachment
- Use permission flags on a document that must not leak
- Encrypt an archive you still need to read in ten years and then lose the password
- Assume a watermark prevents copying
Compared with the usual options
| Desktop PDF editor | Typical online tool | PDFnoted | |
|---|---|---|---|
| Where the file and password go | Local | Uploaded to a server | Your device |
| AES encryption | Yes | Sometimes | Yes |
| Separate open and permission passwords | Yes | Rarely handled | Yes |
| Granular permission flags | Yes | All-or-nothing | Yes |
| Batch protection | Manual | Sometimes | Yes |
| Metadata cleanup first | No | No | Yes |
Frequently asked questions
Is a password-protected PDF really secure?
If you set an open password, yes: the contents are encrypted with AES and cannot be read without the key. Permission flags are different — they ask the viewer to disable printing or copying, and any tool can simply rewrite the file without them. Treat an open password as a lock and permission flags as a polite request.
What is the difference between the two passwords?
An open password encrypts the document; without it the file cannot be read. A permission password leaves the document readable but controls whether printing, copying and editing are permitted. You can set either or both, and they should be different from each other.
Can someone remove my "no printing" restriction?
Easily, and you should assume they will. The restriction is a flag in the file, not encryption. If preventing printing genuinely matters, do not rely on the flag — send a password-protected file, or send something other than a PDF.
Should I use a watermark instead?
A watermark is a different control with a different purpose: it identifies the recipient and discourages onward sharing by making copies traceable. It does not prevent copying and is not a substitute for encryption. For confidential documents they are often used together.
Does protecting a file change its contents?
No. Encryption wraps the document; pages, fonts and images are unchanged once the file is opened with the right password.
Can I protect several files at once?
Yes. Batch protection applies the same password and permission set across a folder, which is what you want when sending the same material to a group.
What about metadata — is it protected too?
Metadata is inside the file, so it is encrypted along with everything else once an open password is set. But if you are relying on permission flags only, document properties remain readable — which is why cleaning metadata before sharing is worth doing in its own right.
What should I do for genuinely sensitive documents?
Encrypt with an open password and share the password through a different channel. Do not rely on permission flags, do not put the password in the same email as the file, and consider whether a PDF is the right vehicle at all — the recipient can always photograph the screen.
Try it on your own file
Upload a document and see what comes back. Free to start, nothing to install.
Protect a PDF now — free to startKeep going
Sources and further reading: ISO 32000 (PDF specification); Adobe PDF Reference; Schema.org structured data; Aggarwal et al., GEO: Generative Engine Optimization (arXiv:2311.09735). This page is a technical guide, not legal advice.