Named privacy contact in Container and cloud workload security
"Contact us" is not a privacy contact. A named officer or a dedicated address is.
2 of 8 vendors we measured here publish it, that is 25%. Last checked 2026-09-02.
25% here against 42% across every category we measure. Container and cloud workload security sits below the overall share for this criterion.
Back to Named privacy contact across all categories, or to Container and cloud workload security.
Published
A data protection officer or a dedicated privacy address is named.
| Vendor | What we found |
|---|---|
| Prisma Cloud | https://www.paloaltonetworks.com/legal-notices/privacy |
| Sweet Security | https://www.sweet.security/ |
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 |
|---|---|
| Anchore | 7 addresses checked |
| Armo | 7 addresses checked |
| Cast AI | 7 addresses checked |
| Chainguard | 7 addresses checked |
| Kubescape | 7 addresses checked |
| Trivy | 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 |
|---|---|
| Clair | The vendor’s robots.txt excludes us from at least one of these addresses, so this was not measured. |
| Cloudsmith | The vendor’s server blocked or rate-limited our crawler, so this was not measured. |
Found something we missed? Tell us and the next run picks it up.