SaaS Ranking

Alternatives to Yopass

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

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

Yopass has 10 gaps in what we could measure: Data processing agreement, Subprocessor list, 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 Yopass does not” is the one that closes them.

VendorScorePublishes, and Yopass does notYopass publishes, and they do not
Heyloginheylogin.com 57/100 5 Data processing agreement, Public pricing, Certifications named, +2 nothing Compare
Password Pusherpwpush.com 57/100 4 Data processing agreement, Public pricing, Notice before subprocessors change, +1 nothing Compare
Nightfallnightfall.ai 43/100 3 Status page with history, Public pricing, Certifications named nothing Compare
NordPassnordpass.com 22/100 3 Status page with history, Public pricing, Certifications named 2 Data location stated, HTTPS enforced with HSTS Compare
Onetimesecretonetimesecret.com 39/100 2 Public pricing, No third-party tracking before consent nothing Compare
Norton Passwordnorton.com 26/100 2 Public pricing, Named privacy contact 1 HTTPS enforced with HSTS Compare
Passwordstateclickstudios.com.au 17/100 2 security.txt (RFC 9116), Named privacy contact 1 Data location stated Compare
Passworkpasswork.pro 17/100 2 Certifications named, security.txt (RFC 9116) 1 Data location stated Compare
Psonopsono.com 13/100 2 No third-party tracking before consent, security.txt (RFC 9116) 2 Data location stated, HTTPS enforced with HSTS Compare
Padlocpadloc.app 9/100 1 No third-party tracking before consent 2 Data location stated, HTTPS enforced with HSTS Compare
Avira Passwordavira.com 4/100 1 security.txt (RFC 9116) 2 Data location stated, HTTPS enforced with HSTS Compare
Spectralspectralops.io 0/100 nothing we found there and not here 2 Data location stated, HTTPS enforced with HSTS 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.