Transparency alternatives to Password Pusher
Other Password management vendors we measure, sorted by how much we found at them and not at Password Pusher. This is a comparison of disclosure, not of features or fitness.
12 shown of 21 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 “Found there, not found at Password Pusher” is the one that closes them.
| Vendor | Score | Found there, not found at Password Pusher | Found at Password Pusher, not found there | |
|---|---|---|---|---|
| Teampassteampass.netSee also Transparency alternatives to Teampass | 26/100 | 3 Certifications named, No third-party tracking before consent, security.txt (RFC 9116) | 5 Data processing agreement, Data location stated, HTTPS enforced with HSTS, +2 | Compare |
| Heyloginheylogin.comSee also Transparency alternatives to Heylogin | 35/100 | 2 Certifications named, security.txt (RFC 9116) | 3 Data location stated, Public pricing, Notice before subprocessors change | Compare |
| Nightfallnightfall.aiSee also Transparency alternatives to Nightfall | 30/100 | 2 Status page with history, Certifications named | 4 Data processing agreement, Data location stated, Notice before subprocessors change, +1 | Compare |
| NordPassnordpass.comSee also Transparency alternatives to NordPass | 23/100 | 2 Status page with history, Certifications named | 5 Data processing agreement, Data location stated, HTTPS enforced with HSTS, +2 | Compare |
| Passworkpasswork.proSee also Transparency alternatives to Passwork | 17/100 | 2 Certifications named, security.txt (RFC 9116) | 5 Data processing agreement, Data location stated, Public pricing, +2 | Compare |
| Psonopsono.comSee also Transparency alternatives to Psono | 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.comSee also Transparency alternatives to Onetimesecret | 39/100 | 1 No third-party tracking before consent | 3 Data processing agreement, Notice before subprocessors change, Named privacy contact | Compare |
| TeamPasswordteampassword.comSee also Transparency alternatives to TeamPassword | 22/100 | 1 Certifications named | 4 Data processing agreement, Data location stated, Notice before subprocessors change, +1 | Compare |
| Passwordstateclickstudios.com.auSee also Transparency alternatives to Passwordstate | 17/100 | 1 security.txt (RFC 9116) | 4 Data processing agreement, Data location stated, Public pricing, +1 | Compare |
| Padlocpadloc.appSee also Transparency alternatives to Padloc | 9/100 | 1 No third-party tracking before consent | 6 Data processing agreement, Data location stated, Public pricing, +3 | Compare |
| Vaultwardenvaultwarden.netSee also Transparency alternatives to Vaultwarden | 9/100 | 1 No third-party tracking before consent | 6 Data processing agreement, Data location stated, Public pricing, +3 | Compare |
| Sekursekur.comSee also Transparency alternatives to Sekur | 30/100 | nothing we found there and not here | 3 Data processing agreement, Notice before subprocessors change, 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.