How PasswordX security works
What is encrypted, where, with which algorithms — and what it doesn't protect against. No promises you can't check.
Updated
- Passwords and logins
- Site addresses, notes
- 2FA secrets, vault names
- Your public keyvisible
- Internal identifiers, sizes, change timesvisible
- Who you shared withvisible
- Alias addressesvisible
- Alias mail on receiptvisible before encryption
In the clear is only what sync, sharing and mail delivery can't work without.
In short
PasswordX encrypts every record in your browser before it is sent to the server. The vault key is protected by your password through Argon2 and is stored on our side only encrypted. So a server breach, a mistake or a request to us exposes no passwords, no 2FA codes and no site names. The flip side: if you lose both the password and the recovery file, the data can't be recovered.
Four principles
Encrypted before sending
Each record is encrypted with its own key right in the browser. Login, password, site address, notes and the 2FA secret reach the server as ciphertext.
No back door
We don't store your password and can't reset it for you. Only your recovery file restores access.
Rollback detection
The app remembers the vault's signed state and compares it with the server's response. A rollback to an older version gets noticed.
Open standards
OpenPGP per RFC 9580 and the widely used OpenPGP.js library. No home-made cryptography.
Cryptography
| Task | Algorithm | Standard |
|---|---|---|
| Record encryption | AES-256-GCM | RFC 9580 |
| Signing and state verification | Ed25519 | RFC 9580 |
| Key exchange when sharing | X25519 | RFC 9580 |
| Protecting the private key with a password | Argon2 | RFC 9106 |
| Two-factor codes | TOTP, 6 digits, 30 seconds | RFC 6238 |
| Library | OpenPGP.js 6.3 | no home-made primitives |
Field by field, what the server sees: What a password manager's server can see.
What it protects against, and what it doesn't
| Situation | PasswordX | Why |
|---|---|---|
| Our server is breached or leaks | Protects | An attacker gets only ciphertext and key envelopes protected by Argon2. |
| A PasswordX employee, or a request to us | Protects | We don't have the vault key. All we could hand over is encrypted data. |
| The server returns an older or someone else's vault | Protects | The app remembers the signed state and shows a warning. |
| Alias mail at the moment of receipt | Partly | Mail arrives over ordinary SMTP and is visible to the service on receipt, then stored encrypted. |
| Traffic interception | Protects | Records leave already encrypted, on top of TLS. |
| Tampering with the PasswordX page code itself | Partly | A limit of any end-to-end encrypted web app: the page code comes from the server. We say so plainly. |
| Malware on your device | Doesn't protect | It can read what you open or capture the password as you type it. |
| Losing both the password and the recovery file | Doesn't protect | There is no back door, so we can't restore access either. |
Glossary
- End-to-end encryption
- Data is encrypted on the sender's device and decrypted only on the recipient's device. The server it passes through sees only ciphertext.
- Ciphertext
- Data after encryption. Without the key it looks like random characters and reveals nothing about the contents.
- Private and public key
- An OpenPGP key pair. Others encrypt data for you with your public key; you open it with your private key. The PasswordX private key is stored only encrypted with your password.
- Argon2
- A function that turns a password into a key. Each attempt costs a lot of memory and time, which makes password guessing expensive. Specified in RFC 9106.
- TOTP
- A one-time code that changes every 30 seconds, computed from a shared secret and the current time per RFC 6238 — how authenticator apps work.
- Email alias
- A separate email address for one site. Its mail arrives in PasswordX, and the site never learns your main address.
- Recovery file
- The PassX-recovery.json file you download at sign-up. It lets you set a new password and regain access to the vault if you forget the old one.
- Phishing
- A fake sign-in page on a look-alike domain. It copies the design, not the address, so check the domain before typing a password.
Check it with your own data
Create a vault and watch what goes to the server: your browser's developer tools show only ciphertext.
Create accountThis is how we would see that sentence if it were a record in your vault.