How Protect encryption works
Protect encrypts secure shares in your browser with Argon2id and AES-256-GCM before upload. The server stores only encrypted data and never sees your password.
Last updated: 14 November 2026
Encryption happens on your device
When you create a secure share, your browser encrypts the message and the files before anything is uploaded. Protect is end-to-end encrypted in this sense: only the sender and the people who have the password can read the content.
The algorithms
- Key derivation: your browser turns the password into a 256-bit key with Argon2id, a password hashing method that resists guessing with fast hardware.
- Encryption: the content is encrypted with AES-GCM using that 256-bit key. AES-GCM also detects if the encrypted data was changed.
- Large files: files are encrypted in parts, so big uploads work reliably.
What the server stores
The Protect server stores only the encrypted content, the encrypted file information, the number and sizes of files, the encryption settings and the expiry time. It never receives the password or the readable content, so we cannot read your share, and we cannot recover a lost password.
Expiry and deletion
Every share has an expiry time between 30 minutes and 1 month. After it expires nobody can open it, and an automatic clean-up deletes it, with its link activity, within about an hour.
What encryption does not cover
Encryption protects the content, not the link itself. A short link only makes an address shorter; it does not encrypt the page behind it. Use a secure share when the content must stay private. Read the privacy policy for every detail about the data that Protect handles.