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