SaaS Ranking

Alternatives to True Key

Other Password management vendors we measure, sorted by how much they publish that True Key does not. This is a comparison of disclosure, not of features or fitness.

12 shown of 18 that differ from True Key on at least one criterion we measured for both. Public transparency score, not a product or security rating.

True Key has 11 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, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “publishes and True Key does not” is the one that closes them.

VendorScorePublishes, and True Key does notTrue Key publishes, and they do not
Heyloginheylogin.com 57/100 6 Data processing agreement, Data location stated, Public pricing, +3 nothing Compare
Password Pusherpwpush.com 57/100 5 Data processing agreement, Data location stated, Public pricing, +2 nothing Compare
Nightfallnightfall.ai 43/100 4 Data location stated, Status page with history, Public pricing, +1 nothing Compare
Teampassteampass.net 26/100 4 Public pricing, Certifications named, No third-party tracking before consent, +1 1 HTTPS enforced with HSTS Compare
Onetimesecretonetimesecret.com 39/100 3 Data location stated, Public pricing, No third-party tracking before consent nothing Compare
Norton Passwordnorton.com 26/100 3 Data location stated, Public pricing, Named privacy contact 1 HTTPS enforced with HSTS Compare
NordPassnordpass.com 22/100 3 Status page with history, Public pricing, Certifications named 1 HTTPS enforced with HSTS Compare
Sekursekur.com 30/100 2 Data location stated, Public pricing nothing Compare
Passwordstateclickstudios.com.au 17/100 2 security.txt (RFC 9116), Named privacy contact nothing Compare
Passworkpasswork.pro 17/100 2 Certifications named, security.txt (RFC 9116) nothing Compare
Psonopsono.com 13/100 2 No third-party tracking before consent, security.txt (RFC 9116) 1 HTTPS enforced with HSTS Compare
Truffle Securitytrufflesecurity.com 22/100 1 Data processing agreement 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.