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