From typing a password to storing it in the cloud
Four things stand in between.
- ① It is encrypted on your device. Passwords and similar content are encrypted with AES-256, and the server only receives the encrypted result.
- ② Signing in and decrypting are separate. A successful sign-in proves you are the account holder; it does not hand over what is needed to decrypt.
- ③ Everything travels over HTTPS. All requests use TLS, so nothing crosses the network in plain text.
- ④ The cloud only stores ciphertext. Our servers keep the encrypted result and do not open the secret content of new items.
Why we cannot open your passwords either
What is needed to decrypt is generated and used only on your device. What our servers hold is the encrypted data, plus a few pieces of key material that are themselves encrypted, and none of it opens without your Secret Key. The password digest used to check your sign-in is on the server too, and it cannot be turned back into anything that decrypts.
This is also why only you can keep the Secret Key: it is yours to hold, and yours to back up in advance.
Forgetting your password, or losing your Secret Key
Forgetting your master password does not lose your data. Use “Forgot password”, receive a code on your linked email or phone, and set a new one. Nothing in your account is affected.
The Secret Key is yours to keep: it is the only key that opens cloud ciphertext, and we neither store nor reissue it. Back it up once and you can restore on any new device.
- A backup kit can be printed on paper, or exported as a PDF or an image and kept offline.
- Before a backup is recorded, you type the Secret Key once more for a byte-by-byte comparison.
- The Secret Key is never stored or reset by us — it only ever exists on your side.
The encryption we use
| Purpose | Algorithm |
|---|---|
| Symmetric encryption | AES-256 |
| Asymmetric encryption | ECIES (secp256k1) |
| Digest | SHA-256 |
| Key derivation | PBKDF2 (derived from your master password) |
| Sign-in password check | BCrypt (server side) |
What our servers can see
Type by type, so you can judge what belongs in here.
| Data | What the server does |
|---|---|
| Secret fields such as passwords and secret notes | Stores only what your device encrypted, and does not open it |
| Items saved by earlier versions | Some non-password fields in them, such as dates and notes, can be read by the server. That is what lets older app versions still open them |
| Your account, item names and search helper information | Stored encrypted or masked. This part is not covered by end-to-end encryption |
What we collect, and what we do not
| Category | Detail |
|---|---|
| We collect | The minimum needed for registration, sign-in, device verification and sync, plus account security notices |
| We do not collect | Contacts, location or clipboard contents. No third-party analytics, advertising or tracking SDKs |
| This website | No tracking cookies, no behavioural profiling, no retargeting |