Data location stated in API security
Where the data sits decides who can demand access to it and whether a transfer is one at all. It does not by itself decide which privacy law applies.
2 of 20 companies we measured here publish it, that is 10%. Last checked 2026-10-17.
10% here against 24% 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 Data location stated across all categories, or to API security.
- Found2
- Not found at checked addresses18
- Not measured4
24 companies in total. Unmeasured companies are excluded from the published share.
Published
The hosting location is stated on a public page.
| Vendor | What we found |
|---|---|
| Cequence | https://www.cequence.ai/legal/privacyChecked |
| Pynt | https://www.pynt.io/privacy-policyChecked |
No statement about data location 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 |
| Approov | 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 |
| Data Theorem | 7 addresses checkedChecked |
| FireTail | 7 addresses checkedChecked |
| Ghost Security | 7 addresses checkedChecked |
| Impart Security | 7 addresses checkedChecked |
| Levo.ai | 7 addresses checkedChecked |
| PortSwigger | 7 addresses checkedChecked |
| Reblaze | 7 addresses checkedChecked |
| Salt Security | 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
- 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
Data location stated 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.