Subprocessor list in API security
Naming the actual subprocessors is what turns a privacy promise into something you can check.
2 of 12 vendors we measured here publish it, that is 17%. Last checked 2026-09-02.
17% here against 10% across every category we measure. API security sits above the overall share for this criterion.
Back to Subprocessor list across all categories, or to API security.
Published
The actual list is published, not just a promise to keep one.
| Vendor | What we found |
|---|---|
| FireTail | https://www.firetail.ai/sub-processors |
| Salt Security | https://salt.security/subprocessors |
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 |
|---|---|
| 42Crunch | 7 addresses checked |
| Akto | 7 addresses checked |
| APIsec | 7 addresses checked |
| Approov | 7 addresses checked |
| Aptori | 7 addresses checked |
| Beagle Security | 7 addresses checked |
| Cequence | 7 addresses checked |
| Data Theorem | 7 addresses checked |
| Pynt | 7 addresses checked |
| ThreatX | 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.
None. Every vendor here was measured for this criterion.
Found something we missed? Tell us and the next run picks it up.