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