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