Hanzo
hanzo.co · eDiscovery and archiving · checked 2026-09-03
Rank 4 of 21 in eDiscovery and archiving, where the median is 22.
- 5 found
- 7 not found
- 0 not measured
We measured 12 of 12 criteria for Hanzo on 2026-09-03. We found 5 with a source and did not find 7 at the addresses we checked. That is a transparency score of 39 out of 100, band E.
Overview
Transparency labelsaas-ranking.com
Hanzo
- A
- B
- C
- D
- E
- F
Published commitments5 of 9 found
- not foundData processing agreement×3
- foundSubprocessor list×3
- foundData location stated×3
- not foundStatus page with history×2
- not foundPublic pricing×2
- not foundNotice before subprocessors change×2
- foundCertifications named×1
- foundUptime SLA with a figure×1
- foundNamed privacy contact×1
Measured behaviour0 of 3 found
- not foundHTTPS enforced with HSTS×2
- not foundNo third-party tracking before consent×2
- not foundsecurity.txt (RFC 9116)×1
Checked 2026-09-03. Every line links the page we found it on. A cross means we found nothing at the addresses we checked, not that the vendor has no such document. A transparency score, not a product rating.
We do not issue badges: a badge is the first step towards a paid placement, and there is none here. The SVG is a document with the date in it, for your own files.
The label is the whole measurement in one object: every criterion with its weight, the band, and the date. Public transparency score, not a product or security rating.
Every line in it links the page we found the result on, or lists the addresses we checked. A cross means we found nothing there, not that Hanzo has no such document.
Gaps, heaviest first
Data processing agreement
weight 3 of 3No data processing agreement found.
Checked 8 addresses on 2026-09-03.
Show the 8 addresses we checked
https://hanzo.co/legal/dpa– reached, no match (HTTP 404)https://hanzo.co/dpa– reached, no match (HTTP 404)https://hanzo.co/legal/data-processing-agreement– reached, no match (HTTP 404)https://hanzo.co/data-processing-agreement– reached, no match (HTTP 404)https://hanzo.co/legal/data-processing-addendum– reached, no match (HTTP 404)https://hanzo.co/legal/gdpr– reached, no match (HTTP 404)https://hanzo.co/trust/dpa– reached, no match (HTTP 404)https://hanzo.co/privacy/dpa– reached, no match (HTTP 404)
Status page with history
weight 2 of 3No public status page found.
Checked 3 addresses on 2026-09-03.
Show the 3 addresses we checked
https://status.hanzo.co/– The name "status.hanzo.co" could not be resolved.https://hanzo.co/status– reached, no match (HTTP 404)https://hanzo.co.statuspage.io/– Could not be fetched: fetch failed.
Public pricing
weight 2 of 3No public pricing with figures found.
Checked 5 addresses on 2026-09-03.
Show the 5 addresses we checked
https://hanzo.co/pricing– reached, no match (HTTP 404)https://hanzo.co/pricing/– reached, no match (HTTP 404)https://hanzo.co/plans– reached, no match (HTTP 404)https://hanzo.co/en/pricing– reached, no match (HTTP 404)https://hanzo.co/pricing-plans– reached, no match (HTTP 404)
HTTPS enforced with HSTS
weight 2 of 3No enforced HTTPS with HSTS found.
Checked 2 addresses on 2026-09-03.
Show the 2 addresses we checked
http://hanzo.co/– redirects to https://hanzo.co/https://hanzo.co/– no HSTS header
No third-party tracking before consent
weight 2 of 3No consent-free first load found.
Checked 1 address on 2026-09-03.
Show the 1 address we checked
https://hanzo.co/– third-party requests before any interaction: cdn.calltrk.com, code.jquery.com, f.clarity.ms, fd-api.cleantalk.org, fd.cleantalk.org, fonts.googleapis.com, fonts.gstatic.com, js.calltrk.com, js.zi-scripts.com, region1.analytics.google.com, s3-us-west-2.amazonaws.com, scripts.clarity.ms, stats.g.doubleclick.net, ws.zoominfo.com, www.clarity.ms, www.google.de, www.googletagmanager.com, www.youtube.com
Notice before subprocessors change
weight 2 of 3No commitment to give notice before subprocessors change found.
Checked 8 addresses on 2026-09-03.
Show the 8 addresses we checked
https://hanzo.co/legal/subprocessors– reached, no match (HTTP 404)https://hanzo.co/subprocessors– reached, no match (HTTP 200)https://hanzo.co/sub-processors– reached, no match (HTTP 404)https://hanzo.co/legal/dpa– reached, no match (HTTP 404)https://hanzo.co/dpa– reached, no match (HTTP 404)https://hanzo.co/legal/data-processing-agreement– reached, no match (HTTP 404)https://hanzo.co/trust/subprocessors– reached, no match (HTTP 404)https://hanzo.co/legal/sub-processors– reached, no match (HTTP 404)
security.txt (RFC 9116)
weight 1 of 3No security.txt found.
Checked 1 address on 2026-09-03.
Show the 1 address we checked
https://hanzo.co/.well-known/security.txt– reached, no match (HTTP 404)
Evidence
The full source lists sit behind these two groups, so that the answer above stays readable.
Published, with a source 5
Subprocessor list
weight 3 of 3The actual list is published, not just a promise to keep one.
Source: https://hanzo.co/subprocessors · checked 2026-09-03
Data location stated
weight 3 of 3The hosting location is stated on a public page.
Source: https://hanzo.co/privacy/ · checked 2026-09-03
Certifications named
weight 1 of 3SOC 2 or ISO 27001 named on a public page.
Source: https://hanzo.co/security · checked 2026-09-03
Uptime SLA with a figure
weight 1 of 3An availability commitment with a figure.
Source: https://hanzo.co/service-level-agreement/ · checked 2026-09-03
Named privacy contact
weight 1 of 3A data protection officer or a dedicated privacy address is named.
Source: https://hanzo.co/privacy/ · checked 2026-09-03
History
Not enough completed runs yet to draw a line. The next runs fill this in.