Alternatives to Passwordstate
Other Password management vendors we measure, sorted by how much they publish that Passwordstate does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 12 that differ from Passwordstate on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Passwordstate has 9 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Public pricing, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, Notice before subprocessors change. The column “publishes and Passwordstate does not” is the one that closes them.
| Vendor | Score | Publishes, and Passwordstate does not | Passwordstate publishes, and they do not | |
|---|---|---|---|---|
| Heyloginheylogin.com | 57/100 | 4 Data processing agreement, Data location stated, Public pricing, +1 | nothing | Compare |
| Password Pusherpwpush.com | 57/100 | 4 Data processing agreement, Data location stated, Public pricing, +1 | 1 security.txt (RFC 9116) | Compare |
| Nightfallnightfall.ai | 43/100 | 4 Data location stated, Status page with history, Public pricing, +1 | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Onetimesecretonetimesecret.com | 39/100 | 3 Data location stated, Public pricing, No third-party tracking before consent | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| NordPassnordpass.com | 22/100 | 3 Status page with history, Public pricing, Certifications named | 3 HTTPS enforced with HSTS, security.txt (RFC 9116), Named privacy contact | Compare |
| Norton Passwordnorton.com | 26/100 | 2 Data location stated, Public pricing | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Yopassyopass.se | 22/100 | 1 Data location stated | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Passworkpasswork.pro | 17/100 | 1 Certifications named | 1 Named privacy contact | Compare |
| Psonopsono.com | 13/100 | 1 No third-party tracking before consent | 2 HTTPS enforced with HSTS, Named privacy contact | Compare |
| Padlocpadloc.app | 9/100 | 1 No third-party tracking before consent | 3 HTTPS enforced with HSTS, security.txt (RFC 9116), Named privacy contact | Compare |
| Avira Passwordavira.com | 4/100 | nothing we found there and not here | 2 HTTPS enforced with HSTS, Named privacy contact | Compare |
| Spectralspectralops.io | 0/100 | nothing we found there and not here | 3 HTTPS enforced with HSTS, security.txt (RFC 9116), Named privacy contact | Compare |
Only criteria we could measure for both are counted. Where we could measure one and not the other, the row is silent: that would be a statement about our measurement, not about either vendor. Every single result with its source is on the two profiles.