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