Redaction, Encryption or a Password: Which Protects a Document?
A shared PDF can carry a password, be encrypted, or be redacted. Each protects against a different threat: what to use, and when to combine them.
Redaction removes information for good. Encryption scrambles a file so only someone with the key can read it. A password just checks who gets to open or edit the file, and the three do very different jobs. Mixing them up is the easiest way to send a document that looks protected but is not.
What do redaction, encryption and a password protect against?
Redaction means deleting specific data from a document before you share it: a name, an account number, an address. Done right, the information is gone from the file itself, not hidden under a black box someone could still lift. Redaction protects against one thing: a reader who opens the file legitimately and was never meant to see that one value.
Encryption scrambles the whole file with a mathematical key, so anyone without that key sees only noise. It protects a document while it travels over a network or sits on a stolen laptop. It does nothing once the file has been opened by someone who holds the key, or has been decrypted and saved back as a normal, readable copy.
A PDF can carry two different passwords. An open password must be typed before the file appears at all: this is real encryption, and a strong one is hard to break. A permissions password, sometimes called a restrictions password, lets anyone open the file but is supposed to block printing, editing or copying. In Adobe's Acrobat tools, restricting editing and encrypting the file to open are two separate actions, not one and the same.
Is a PDF permissions password real protection?
That second kind, the permissions password, is not the same protection. Adobe's own tools let you restrict editing without ever encrypting the file's text. Online services built to remove these restrictions can strip them in seconds, PDF security vendor LockLizard notes, because compliant behavior depends on the reader app choosing to respect them.
| What you need | Redaction | Encryption | Password protection |
|---|---|---|---|
| Remove specific words or numbers so a reader never sees them | Yes, if applied correctly and flattened | No, the data stays in the file, just scrambled | No, the data is fully readable once the file is open |
| Stop someone who intercepts the file in transit from reading it | No, once open the rest is fully visible | Yes, that is its main job | Partly, only for as long as the recipient lacks the password |
| Stop a reader who already has the file from printing or copying it | No, that is not what redaction does | No, encryption controls nothing once it is decrypted | Partly, with a permissions password, but it is easy to strip |
| Keep data unreadable if the file is stolen from a laptop or a cloud drive | No | Yes, if the drive or file is encrypted at rest | No, the content is exposed once someone opens it |
What does GDPR Article 32 say about these measures?
GDPR Article 32 does not name redaction directly. It asks controllers to apply security measures that fit the risk, and gives two named examples: pseudonymising data and encrypting it. Both reduce the harm if a file ends up in the wrong hands, which is likely why they sit side by side in the text.
the pseudonymisation and encryption of personal data — Article 32(1)(a), GDPR.
Redaction is not listed by name, but it serves a related goal: cutting the personal data in a file down to what the recipient actually needs, an idea GDPR Article 5 calls minimisation. A password is not named either, and on its own it usually does not count as one of these measures, since a permissions password is easy to remove and a weak open password is easy to guess.
How do you combine them to share a document safely?
The strongest habit is to layer the three. Redact whatever the recipient does not need to see first, so the raw values are gone even if the file leaks later. Then choose a channel that protects the file in transit: an encrypted email service, a link that expires, or a password-protected archive sent through a channel separate from the password itself.
ONYRI Sanitize handles the redaction part of this chain. It scans a PDF, Word file or scan in your browser, masks the values you choose, and exports a flattened copy with no text hiding under the bars. It does not encrypt or password-protect the result, so the file you download still needs a secure channel before it leaves your hands.
- Decide what the recipient truly needs to see, and redact the rest first.
- Export a flattened copy so no hidden text sits under the black bars or tokens.
- Send the file through an encrypted channel: TLS-protected email, a secure portal, or an encrypted archive.
- If you add a password, send it through a different channel than the file, such as a text message instead of the same email.
- Keep the original, unredacted file somewhere separate, with its own access controls.
Common mistakes that undo the protection
- Sending the password in the same email as the file, which defeats it instantly.
- Treating "restrict editing" as if it were encryption, when it is only a setting a reader can ignore.
- Drawing a black box over text in a word processor without flattening the file, so the words are still there underneath.
- Reusing one short password for every file, so a single leak exposes every document that used it.
None of these tools is a silver bullet on its own. Redaction, encryption and a password each answer a different question: what should the reader never see, what should nobody in between ever read, and who is allowed to open the file at all. Ask all three questions before you hit send, especially for anything that touches real people's data.
Frequently asked questions
Is redacting a document the same as encrypting it?
No. Redaction removes specific data from the file itself, so it is gone even for someone who opens it normally. Encryption scrambles the whole file so it cannot be opened at all without a key. A document can be redacted and still sent in the clear, or encrypted and still show everything once opened.
Does a password on a PDF count as encryption?
Only the open password does. It is tied to the same encryption that locks the file until the correct password is entered. A permissions password does not encrypt anything: the file opens freely, and the password only tries to stop printing, editing or copying, a setting that Adobe's own tools present as a separate action from encrypting the file to open.
What does GDPR actually require: encryption or something else?
GDPR Article 32 does not require encryption in every case. It asks for measures appropriate to the risk, and lists pseudonymisation and encryption as examples among several. For many everyday documents, redacting the sensitive values and sending the rest through a secure channel can meet that same standard.
What is the safest way to send a confidential document outside your organisation?
Redact anything the recipient does not need first, so the raw values cannot leak later. Then send the file through an encrypted channel, such as a secure portal or TLS-protected email, and if you add a password, share it separately from the file itself, never in the same message.
Sources & references
- Article 32(1)(a) GDPR — security of processingIntersoft Consulting (GDPR full text)
- Encryption and data protectionUK Information Commissioner's Office (ICO)
- Password protected PDFs and PDF securityAdobe
- How to restrict PDF editing (and why passwords don't work)LockLizard