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