Alternatives to Onetimesecret
Other Password management vendors we measure, sorted by how much they publish that Onetimesecret does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 12 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 “publishes and Onetimesecret does not” is the one that closes them.
| Vendor | Score | Publishes, and Onetimesecret does not | Onetimesecret publishes, and they do not | |
|---|---|---|---|---|
| Heyloginheylogin.com | 57/100 | 4 Data processing agreement, Certifications named, security.txt (RFC 9116), +1 | 1 No third-party tracking before consent | Compare |
| Password Pusherpwpush.com | 57/100 | 3 Data processing agreement, Notice before subprocessors change, Named privacy contact | 1 No third-party tracking before consent | Compare |
| Nightfallnightfall.ai | 43/100 | 2 Status page with history, Certifications named | 1 No third-party tracking before consent | Compare |
| NordPassnordpass.com | 22/100 | 2 Status page with history, Certifications named | 3 Data location stated, HTTPS enforced with HSTS, No third-party tracking before consent | Compare |
| Passwordstateclickstudios.com.au | 17/100 | 2 security.txt (RFC 9116), Named privacy contact | 3 Data location stated, Public pricing, No third-party tracking before consent | Compare |
| Passworkpasswork.pro | 17/100 | 2 Certifications named, security.txt (RFC 9116) | 3 Data location stated, Public pricing, No third-party tracking before consent | Compare |
| Norton Passwordnorton.com | 26/100 | 1 Named privacy contact | 2 HTTPS enforced with HSTS, No third-party tracking before consent | Compare |
| Psonopsono.com | 13/100 | 1 security.txt (RFC 9116) | 3 Data location stated, Public pricing, HTTPS enforced with HSTS | Compare |
| Avira Passwordavira.com | 4/100 | 1 security.txt (RFC 9116) | 4 Data location stated, Public pricing, HTTPS enforced with HSTS, +1 | Compare |
| Yopassyopass.se | 22/100 | nothing we found there and not here | 2 Public pricing, No third-party tracking before consent | Compare |
| Padlocpadloc.app | 9/100 | nothing we found there and not here | 3 Data location stated, Public pricing, HTTPS enforced with HSTS | Compare |
| Spectralspectralops.io | 0/100 | nothing we found there and not here | 4 Data location stated, Public pricing, HTTPS enforced with HSTS, +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.