Transparency alternatives to Hanzo
Other eDiscovery and archiving vendors we measure, sorted by how much we found at them and not at Hanzo. This is a comparison of disclosure, not of features or fitness.
12 shown of 38 that differ from Hanzo on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Hanzo has 7 gaps in what we could measure: Data processing agreement, Status page with history, Public pricing, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change. The column “Found there, not found at Hanzo” is the one that closes them.
| Vendor | Score | Found there, not found at Hanzo | Found at Hanzo, not found there | |
|---|---|---|---|---|
| DISCOcsdisco.comSee also Transparency alternatives to DISCO | 52/100 | 3 Data processing agreement, HTTPS enforced with HSTS, Notice before subprocessors change | 2 Data location stated, Uptime SLA with a figure | Compare |
| Mailbutlermailbutler.ioSee also Transparency alternatives to Mailbutler | 43/100 | 3 Status page with history, Public pricing, HTTPS enforced with HSTS | 3 Subprocessor list, Certifications named, Uptime SLA with a figure | Compare |
| Shieldshieldfc.comSee also Transparency alternatives to Shield | 35/100 | 3 Data processing agreement, HTTPS enforced with HSTS, Notice before subprocessors change | 4 Subprocessor list, Data location stated, Uptime SLA with a figure, +1 | Compare |
| Everlaweverlaw.comSee also Transparency alternatives to Everlaw | 30/100 | 3 Status page with history, HTTPS enforced with HSTS, security.txt (RFC 9116) | 3 Subprocessor list, Data location stated, Uptime SLA with a figure | Compare |
| Nuixnuix.comSee also Transparency alternatives to Nuix | 26/100 | 3 Status page with history, HTTPS enforced with HSTS, security.txt (RFC 9116) | 4 Subprocessor list, Data location stated, Certifications named, +1 | Compare |
| Jatheonjatheon.comSee also Transparency alternatives to Jatheon | 45/100 | 2 Data processing agreement, HTTPS enforced with HSTS | 2 Subprocessor list, Uptime SLA with a figure | Compare |
| Magnet Forensicsmagnetforensics.comSee also Transparency alternatives to Magnet Forensics | 39/100 | 2 Status page with history, HTTPS enforced with HSTS | 2 Subprocessor list, Uptime SLA with a figure | Compare |
| GoldFynchgoldfynch.comSee also Transparency alternatives to GoldFynch | 35/100 | 2 Public pricing, HTTPS enforced with HSTS | 3 Subprocessor list, Certifications named, Uptime SLA with a figure | Compare |
| Lighthouselighthouseglobal.comSee also Transparency alternatives to Lighthouse | 35/100 | 2 Public pricing, HTTPS enforced with HSTS | 3 Subprocessor list, Certifications named, Uptime SLA with a figure | Compare |
| Digital WarRoomdigitalwarroom.comSee also Transparency alternatives to Digital WarRoom | 24/100 | 2 Public pricing, HTTPS enforced with HSTS | 4 Subprocessor list, Data location stated, Uptime SLA with a figure, +1 | Compare |
| Behavoxbehavox.comSee also Transparency alternatives to Behavox | 22/100 | 2 HTTPS enforced with HSTS, No third-party tracking before consent | 4 Subprocessor list, Data location stated, Uptime SLA with a figure, +1 | Compare |
| CloudNinecloudnine.comSee also Transparency alternatives to CloudNine | 22/100 | 2 Public pricing, HTTPS enforced with HSTS | 4 Subprocessor list, Data location stated, Uptime SLA with a figure, +1 | Compare |
Only criteria we could measure for both are counted. Where we could measure one and not the other, the row is silent: that would be a statement about our measurement, not about either vendor. Every single result with its source is on the two profiles.