Alternatives to Dashlane
Other Password and identity vendors we measure, sorted by how much they publish that Dashlane does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 24 that differ from Dashlane on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Dashlane has 7 gaps in what we could measure: Data processing agreement, Data location stated, Status page with history, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, Notice before subprocessors change. The column “publishes and Dashlane does not” is the one that closes them.
| Vendor | Score | Publishes, and Dashlane does not | Dashlane publishes, and they do not | |
|---|---|---|---|---|
| WorkOSworkos.com | 60/100 | 5 Data processing agreement, Data location stated, Status page with history, +2 | 3 Subprocessor list, HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Keeperkeepersecurity.com | 85/100 | 4 Data processing agreement, Data location stated, Certifications named, +1 | nothing | Compare |
| Ping Identitypingidentity.com | 74/100 | 4 Data location stated, Status page with history, Certifications named, +1 | nothing | Compare |
| 1Password1password.com | 70/100 | 4 Data processing agreement, Data location stated, Status page with history, +1 | 1 Subprocessor list | Compare |
| Clerkclerk.com | 70/100 | 4 Data processing agreement, Data location stated, Status page with history, +1 | 1 Subprocessor list | Compare |
| Oktaokta.com | 61/100 | 3 Data processing agreement, Data location stated, Status page with history | 1 Subprocessor list | Compare |
| Duo Securityduo.com | 48/100 | 3 Data location stated, Status page with history, Certifications named | 2 Subprocessor list, Named privacy contact | Compare |
| Oryory.com | 43/100 | 3 Data location stated, Certifications named, Uptime SLA with a figure | 2 Subprocessor list, Named privacy contact | Compare |
| Fronteggfrontegg.com | 39/100 | 3 Data location stated, Status page with history, Certifications named | 3 Subprocessor list, HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Stytchstytch.com | 45/100 | 2 Data location stated, Status page with history | 2 Subprocessor list, security.txt (RFC 9116) | Compare |
| Passboltpassbolt.com | 43/100 | 2 Data location stated, Certifications named | 1 Subprocessor list | Compare |
| Bitwardenbitwarden.com | 40/100 | 2 Data location stated, Certifications named | 2 Subprocessor list, security.txt (RFC 9116) | 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.