Subprocessor list in Password and identity
Naming the actual subprocessors is what turns a privacy promise into something you can check.
- 2Published
- 11Vendors measured
- 18%Of those measured
- 2026-08-31Checked
18% here against 16% across every category we measure. Password and identity sits above the overall share for this criterion.
Back to Subprocessor list across all categories, or to Password and identity.
Published
The actual list is published, not just a promise to keep one.
| Vendor | What we found |
|---|---|
| Dashlane | https://www.dashlane.com/privacy/subprocessors |
| Keeper | https://www.keepersecurity.com/legal/sub-processors/ |
No subprocessor list found.
We reached at least one address for each of these vendors and none of them carried it. That is what we found at the addresses we checked, on the date we checked them, and not a statement about what the vendor has.
| Vendor | What we found |
|---|---|
| 1Password | 7 addresses checked |
| Bitwarden | 7 addresses checked |
| Clerk | 7 addresses checked |
| JumpCloud | 7 addresses checked |
| LastPass | 7 addresses checked |
| Okta | 7 addresses checked |
| OneLogin | 7 addresses checked |
| Stytch | 7 addresses checked |
| WorkOS | 7 addresses checked |
Not measured
We could not look at these, or their robots.txt asks us not to. That says something about our measurement, not about them, and they are left out of the percentage above.
| Vendor | What we found |
|---|---|
| Auth0 | The vendor’s robots.txt excludes us from at least one of these addresses, so this was not measured. |
Found something we missed? Tell us and the next run picks it up.