Transparency alternatives to Passpack
Other Password management vendors we measure, sorted by how much we found at them and not at Passpack. This is a comparison of disclosure, not of features or fitness.
12 shown of 21 that differ from Passpack on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Passpack has 10 gaps in what we could measure: Data processing agreement, Subprocessor list, Status page with history, Certifications named, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “Found there, not found at Passpack” is the one that closes them.
| Vendor | Score | Found there, not found at Passpack | Found at Passpack, not found there | |
|---|---|---|---|---|
| Heyloginheylogin.comSee also Transparency alternatives to Heylogin | 35/100 | 5 Data processing agreement, Certifications named, HTTPS enforced with HSTS, +2 | 2 Data location stated, Public pricing | Compare |
| Password Pusherpwpush.comSee also Transparency alternatives to Password Pusher | 57/100 | 4 Data processing agreement, HTTPS enforced with HSTS, Notice before subprocessors change, +1 | nothing | Compare |
| Nightfallnightfall.aiSee also Transparency alternatives to Nightfall | 30/100 | 3 Status page with history, Certifications named, HTTPS enforced with HSTS | 1 Data location stated | Compare |
| Teampassteampass.netSee also Transparency alternatives to Teampass | 26/100 | 3 Certifications named, No third-party tracking before consent, security.txt (RFC 9116) | 1 Data location stated | Compare |
| Passwordstateclickstudios.com.auSee also Transparency alternatives to Passwordstate | 17/100 | 3 HTTPS enforced with HSTS, security.txt (RFC 9116), Named privacy contact | 2 Data location stated, Public pricing | Compare |
| Passworkpasswork.proSee also Transparency alternatives to Passwork | 17/100 | 3 Certifications named, HTTPS enforced with HSTS, security.txt (RFC 9116) | 2 Data location stated, Public pricing | Compare |
| Onetimesecretonetimesecret.comSee also Transparency alternatives to Onetimesecret | 39/100 | 2 HTTPS enforced with HSTS, No third-party tracking before consent | nothing | Compare |
| NordPassnordpass.comSee also Transparency alternatives to NordPass | 23/100 | 2 Status page with history, Certifications named | 1 Data location stated | Compare |
| TeamPasswordteampassword.comSee also Transparency alternatives to TeamPassword | 22/100 | 2 Certifications named, HTTPS enforced with HSTS | 1 Data location stated | Compare |
| Truffle Securitytrufflesecurity.comSee also Transparency alternatives to Truffle Security | 22/100 | 2 Data processing agreement, HTTPS enforced with HSTS | 2 Data location stated, Public pricing | Compare |
| Psonopsono.comSee also Transparency alternatives to Psono | 13/100 | 2 No third-party tracking before consent, security.txt (RFC 9116) | 2 Data location stated, Public pricing | Compare |
| Sekursekur.comSee also Transparency alternatives to Sekur | 30/100 | 1 HTTPS enforced with HSTS | nothing | 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.