Alternatives to Psono
Other Password management vendors we measure, sorted by how much they publish that Psono does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 12 that differ from Psono on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Psono has 10 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, HTTPS enforced with HSTS, Notice before subprocessors change, Named privacy contact. The column “publishes and Psono does not” is the one that closes them.
| Vendor | Score | Publishes, and Psono does not | Psono publishes, and they do not | |
|---|---|---|---|---|
| Heyloginheylogin.com | 57/100 | 6 Data processing agreement, Data location stated, Public pricing, +3 | 1 No third-party tracking before consent | Compare |
| Password Pusherpwpush.com | 57/100 | 6 Data processing agreement, Data location stated, Public pricing, +3 | 2 No third-party tracking before consent, security.txt (RFC 9116) | Compare |
| Nightfallnightfall.ai | 43/100 | 5 Data location stated, Status page with history, Public pricing, +2 | 2 No third-party tracking before consent, security.txt (RFC 9116) | Compare |
| Onetimesecretonetimesecret.com | 39/100 | 3 Data location stated, Public pricing, HTTPS enforced with HSTS | 1 security.txt (RFC 9116) | Compare |
| Norton Passwordnorton.com | 26/100 | 3 Data location stated, Public pricing, Named privacy contact | 2 No third-party tracking before consent, security.txt (RFC 9116) | Compare |
| NordPassnordpass.com | 22/100 | 3 Status page with history, Public pricing, Certifications named | 2 No third-party tracking before consent, security.txt (RFC 9116) | Compare |
| Yopassyopass.se | 22/100 | 2 Data location stated, HTTPS enforced with HSTS | 2 No third-party tracking before consent, security.txt (RFC 9116) | Compare |
| Passwordstateclickstudios.com.au | 17/100 | 2 HTTPS enforced with HSTS, Named privacy contact | 1 No third-party tracking before consent | Compare |
| Passworkpasswork.pro | 17/100 | 2 Certifications named, HTTPS enforced with HSTS | 1 No third-party tracking before consent | Compare |
| Padlocpadloc.app | 9/100 | nothing we found there and not here | 1 security.txt (RFC 9116) | Compare |
| Avira Passwordavira.com | 4/100 | nothing we found there and not here | 1 No third-party tracking before consent | Compare |
| Spectralspectralops.io | 0/100 | nothing we found there and not here | 2 No third-party tracking before consent, security.txt (RFC 9116) | 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.