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