Signed history
Each vault change is signed by its author and chained to the last. Apps verify the whole chain and remember where they were, so missing, reordered or forked history is caught.
The short version: your devices do all the encrypting, our server stores what it can't open, and your apps check everything it sends back. The full details are in the protocol specification that ships with the source code.
Your vaults are locked by a key that only your devices can work out.
| Data | What the server holds |
|---|---|
| Passwords, notes, cards, one-time code secrets | Encrypted. We can't read them. |
| Vault and item names, websites, usernames | Encrypted. We can't read them. |
| Your master password and Secret Key | Nothing. They never leave your devices. |
| Your email address | Stored, to find your account when you sign in. |
| Who shares a vault with whom | Visible as account IDs, needed to deliver shared vaults. |
| How many items and changes a vault has, and when | Visible, as sizes and times of encrypted data. |
We design for the day our server is broken into, or a rogue insider tries something. Your apps assume it might.
Each vault change is signed by its author and chained to the last. Apps verify the whole chain and remember where they were, so missing, reordered or forked history is caught.
Account keys are published in an append-only Merkle log. Apps check proofs on every lookup, and once a day check that no keys were added in your name.
Keys are exchanged with X-Wing (X25519 with ML-KEM-768) and changes are signed with Ed25519 and ML-DSA-65 together, so breaking one algorithm is not enough.
The desktop app keeps keys in Rust, away from the window, which can't reach the network. The browser extension has no access to pages until you ask it to fill one.
Please don't post security issues publicly. Report them privately through the GitHub repository's Security tab, using Report a vulnerability. You'll hear back within 7 days, and we credit reporters in the advisory unless they prefer not to be named. We ask for up to 90 days to release a fix before details are published.