✗
Data processing agreement (DPA)
weight 3 of 3
No data processing agreement found.
Checked 8 addresses on 2026-10-27.
Show the 8 addresses we checked
https://ziphq.com/legal/dpa – reached, no match (HTTP 404)https://ziphq.com/dpa – reached, no match (HTTP 404)https://ziphq.com/legal/data-processing-agreement – reached, no match (HTTP 404)https://ziphq.com/data-processing-agreement – reached, no match (HTTP 404)https://ziphq.com/legal/data-processing-addendum – reached, no match (HTTP 404)https://ziphq.com/legal/gdpr – reached, no match (HTTP 404)https://ziphq.com/trust/dpa – reached, no match (HTTP 404)https://ziphq.com/privacy/dpa – reached, no match (HTTP 404)
Is this wrong? Send us the URL
Across the market: Data processing agreement in Procurement: 4 of 39 companies
✗
Data location: where they say data is hosted
weight 3 of 3
We found this behind a sign-in, so it is not published openly.
Seen at https://zip.com/zip-privacy-notice · checked 2026-10-27
Show the 7 addresses we checked
https://ziphq.com/security – reached, no match (HTTP 404)https://ziphq.com/trust – reached, no match (HTTP 200)https://ziphq.com/legal/privacy – reached, no match (HTTP 404)https://ziphq.com/privacy – reached, no match (HTTP 404)https://ziphq.com/privacy-policy – found, but behind a sign-inhttps://ziphq.com/compliance – reached, no match (HTTP 404)https://ziphq.com/legal/privacy-policy – reached, no match (HTTP 404)
Is this wrong? Send us the URL
Across the market: Data location stated in Procurement: 10 of 39 companies
✗
Public pricing with figures
weight 2 of 3
No public pricing with figures found.
Checked 5 addresses on 2026-10-27.
Show the 5 addresses we checked
https://ziphq.com/pricing – reached, no match (HTTP 404)https://ziphq.com/pricing/ – reached, no match (HTTP 404)https://ziphq.com/plans – reached, no match (HTTP 404)https://ziphq.com/en/pricing – reached, no match (HTTP 404)https://ziphq.com/pricing-plans – reached, no match (HTTP 404)
Is this wrong? Send us the URL
Across the market: Public pricing in Procurement: 10 of 39 companies
✗
No third-party tracking before consent
weight 2 of 3
Third-party requests seen on the first load, before any interaction.
- Third-party hosts we saw on the first load 15 amazonaws.com, cloudflare.com, cloudfront.net, cookielaw.org, doubleclick.net, google.com, googletagmanager.com, jsdelivr.net, mutinycdn.com, onetrust.com, userled.io, userledclient.io, website-files.com, wistia.com, zip.com.
Show the 15 exact wordings
public-responsival.s3.amazonaws.com
Read at https://ziphq.com/
cdnjs.cloudflare.com
Read at https://ziphq.com/
d3e54v103j8qbb.cloudfront.net
Read at https://ziphq.com/
cdn.cookielaw.org
Read at https://ziphq.com/
ad.doubleclick.net
Read at https://ziphq.com/
www.google.com
Read at https://ziphq.com/
www.googletagmanager.com
Read at https://ziphq.com/
cdn.jsdelivr.net
Read at https://ziphq.com/
client-registry.mutinycdn.com
Read at https://ziphq.com/
geolocation.onetrust.com
Read at https://ziphq.com/
us.api.userled.io, us.assets.userled.io
Read at https://ziphq.com/
sdk.userledclient.io
Read at https://ziphq.com/
cdn.prod.website-files.com
Read at https://ziphq.com/
embed-ssl.wistia.com
Read at https://ziphq.com/
zip.com
Read at https://ziphq.com/
Checked 1 address on 2026-10-27.
Show the 1 address we checked
https://ziphq.com/ – third-party requests before any interaction: ad.doubleclick.net, cdn.cookielaw.org, cdn.jsdelivr.net, cdn.prod.website-files.com, cdnjs.cloudflare.com, client-registry.mutinycdn.com, d3e54v103j8qbb.cloudfront.net, embed-ssl.wistia.com, geolocation.onetrust.com, public-responsival.s3.amazonaws.com, sdk.userledclient.io, us.api.userled.io, us.assets.userled.io, www.google.com, www.googletagmanager.com, zip.com
Is this wrong? Send us the URL
Across the market: No third-party tracking before consent in Procurement: 1 of 43 companies
✗
Uptime SLA with a figure
weight 1 of 3
No uptime figure found.
Checked 6 addresses on 2026-10-27.
Show the 6 addresses we checked
https://ziphq.com/legal/sla – reached, no match (HTTP 404)https://ziphq.com/sla – reached, no match (HTTP 404)https://ziphq.com/legal/service-level-agreement – reached, no match (HTTP 404)https://ziphq.com/trust/sla – reached, no match (HTTP 404)https://ziphq.com/uptime – reached, no match (HTTP 404)https://ziphq.com/legal/uptime-sla – reached, no match (HTTP 404)
Is this wrong? Send us the URL
Across the market: Uptime SLA with a figure in Procurement: 1 of 39 companies