To encrypt, type the password you want; to decrypt, type the existing one.
Download. Remember the password — we do not keep it.
This one needs an upload, and is deleted afterwards
Browsers cannot do this calculation, so the file goes to our server. It is deleted automatically 60 minutes after the job finishes, and the working copy lives in a memory filesystem that is wiped whenever the server restarts.
We do not log file names and do not log file contents — that is a hard rule in our engineering standards, not a setting.
What it does — and what it doesn't
An open password is real protection — without it the file does not open, and that is enforced cryptographically.
"No printing" and "no copying" permission flags are not. They are a marker inside the file that software may choose to respect; anything can ignore them. That is why our interface never describes them as security — doing so would mislead you.
Forget the password and the file stays shut. There is no back door and no copy kept anywhere.
Decrypting requires knowing the password already. This is not a tool for opening files that are not yours.
Common questions
Is my password logged?
No. It is used for the operation and never written anywhere — the system does not even record file names.
Why do you make a point about permission flags?
Because plenty of tools sell them as a feature. They stop accidents, not anyone who knows how. Better to say so than let you believe the document is protected.
Can I use other tools on an encrypted file?
No — decrypt it first. Encrypted files cannot be read in, by design.