Named privacy contact in API security
"Contact us" is not a privacy contact. A named officer or a dedicated address is.
7 of 20 companies we measured here publish it, that is 35%. Last checked 2026-10-17.
35% here against 36% across every category we measure. API security sits below the overall share for this criterion.
This page counts companies, not product entries: a company with two products in this category is one company here and two rows below.
Back to Named privacy contact across all categories, or to API security.
- Found7
- Not found at checked addresses13
- Not measured4
24 companies in total. Unmeasured companies are excluded from the published share.
Published
A data protection officer or a dedicated privacy address is named.
| Vendor | What we found |
|---|---|
| Approov | https://approov.io/privacy/Checked |
| Cequence | https://www.cequence.ai/legal/privacyChecked |
| Data Theorem | https://www.datatheorem.com/privacy/Checked |
| FireTail | https://www.firetail.ai/privacyChecked |
| Impart Security | https://www.impart.ai/legal/privacy-policyChecked |
| Pynt | https://www.pynt.io/privacy-policyChecked |
| Salt Security | https://salt.security/privacy-policyChecked |
No named privacy contact 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 checkedChecked |
| Akto | 7 addresses checkedChecked |
| Aptori | 7 addresses checkedChecked |
| Beagle Security | 7 addresses checkedChecked |
| Cloudbric | 7 addresses checkedChecked |
| Corsha | 7 addresses checkedChecked |
| Cyber Chief | 7 addresses checkedChecked |
| Ghost Security | 7 addresses checkedChecked |
| Levo.ai | 7 addresses checkedChecked |
| PortSwigger | 7 addresses checkedChecked |
| Reblaze | 7 addresses checkedChecked |
| ThreatX | 7 addresses checkedChecked |
| ZAP | 7 addresses checkedChecked |
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 |
|---|---|
| APIsec | The vendor’s server blocked or rate-limited our crawler, so this was not measured.Checked |
| Curity | The vendor’s robots.txt excludes us from at least one of these addresses, so this was not measured.Checked |
| Traceable | The vendor’s server blocked or rate-limited our crawler, so this was not measured.Checked |
| Wallarm | The vendor’s server blocked or rate-limited our crawler, so this was not measured.Checked |
Other criteria in API security
- Data processing agreement
- Subprocessor list
- Data location stated
- Status page with history
- Public pricing
- Certifications named
- Uptime SLA with a figure
- HTTPS enforced with HSTS
- No third-party tracking before consent
- security.txt (RFC 9116)
- Notice before subprocessors change
Named privacy contact in related categories
Found something we missed? Tell us. A correction moves that vendor into our next nightly run. That run reads the same fixed addresses we check for every vendor, not the address you send.