In short

The server of an end-to-end encrypted password manager stores records only in encrypted form. Passwords, logins, site addresses, notes and 2FA secrets are encrypted in your browser with a key that your password or recovery file unlocks; a recipient you share with gets the key to the chosen record or vault only. The service sees service data — identifiers, sizes, change times, granted access and alias addresses — but not what records contain.

People trust a password manager with what matters most, so the key question isn't “how secure is the server” but “what happens if the server turns out not to be”. The answer depends on where encryption happens.

What's visible and what isn't

DataServer seesWhere it's opened
Passwords and loginsNo, ciphertext onlyIn your browser
Site addresses and namesNoIn your browser
2FA secretsNoThe code is computed in the browser
Notes and vault namesNoIn your browser
Your public keyYesNeeded so others can share a record with you
Internal identifiers, sizes, change timesYesNeeded to sync devices
Who you shared withYes, without the record's contentsNeeded to deliver the key to the recipient
Email alias addressesYesNeeded to receive mail
Alias mail at the moment of receiptYes, before encryptionArrives over ordinary SMTP, then stored encrypted

How it works

At sign-up the app creates a key pair in your browser using the open OpenPGP standard. The private key is protected by your password through Argon2, a function that makes password guessing expensive. Only the protected key envelope goes to the server.

Each record is encrypted with its own key, which is in turn encrypted with the vault key. That's why you can share one record without opening the rest: the recipient gets that record's key, encrypted to their public key.

The same record before and after encryption. The right half is real AES-256-GCM, computed by your browser when this page opened. Without the key it can't be turned back into the left.

If the database is stolen

An attacker gets ciphertext and protected key envelopes. To read the records they'd have to guess your password for each envelope separately, and Argon2 makes every guess slow and memory-hungry. A long, unique PasswordX password turns that guessing into a pointless waste of resources.

Your vault is as strong as your password and your recovery file, not as strong as our server's defences.

Rollback protection

Hiding the contents isn't enough: a server could return an old version of the vault, say one with a password you've since changed. The app remembers the last signed state it saw and compares it with the server's response. If the version has gone back or belongs to someone else, you'll see a warning.

What encryption doesn't solve

  • Malware on your device can read what you open.
  • The site you type your password into receives it in the clear, so check the page address before typing.
  • Alias mail arrives as ordinary email: the service sees it on receipt, and only then is it encrypted.
  • If you lose both your password and your recovery file, we can't restore access: we have no back door.

Sources

  1. RFC 9580. OpenPGP
  2. RFC 9106. Argon2 Memory-Hard Function
  3. RFC 6238. TOTP: Time-Based One-Time Password Algorithm
PasswordX security teamThe engineers who design PasswordX encryption and checks.