Transparency alternatives to DISCO
Other eDiscovery and archiving vendors we measure, sorted by how much we found at them and not at DISCO. This is a comparison of disclosure, not of features or fitness.
12 shown of 38 that differ from DISCO on at least one criterion we measured for both. Public transparency score, not a product or security rating.
DISCO has 6 gaps in what we could measure: Data location stated, Status page with history, Public pricing, Uptime SLA with a figure, No third-party tracking before consent, security.txt (RFC 9116). The column “Found there, not found at DISCO” is the one that closes them.
| Vendor | Score | Found there, not found at DISCO | Found at DISCO, not found there | |
|---|---|---|---|---|
| Mailbutlermailbutler.ioSee also Transparency alternatives to Mailbutler | 43/100 | 3 Data location stated, Status page with history, Public pricing | 4 Data processing agreement, Subprocessor list, Certifications named, +1 | Compare |
| Hanzohanzo.coSee also Transparency alternatives to Hanzo | 39/100 | 2 Data location stated, Uptime SLA with a figure | 3 Data processing agreement, HTTPS enforced with HSTS, Notice before subprocessors change | Compare |
| Magnet Forensicsmagnetforensics.comSee also Transparency alternatives to Magnet Forensics | 39/100 | 2 Data location stated, Status page with history | 3 Data processing agreement, Subprocessor list, Notice before subprocessors change | Compare |
| GoldFynchgoldfynch.comSee also Transparency alternatives to GoldFynch | 35/100 | 2 Data location stated, Public pricing | 4 Data processing agreement, Subprocessor list, Certifications named, +1 | Compare |
| Lighthouselighthouseglobal.comSee also Transparency alternatives to Lighthouse | 35/100 | 2 Data location stated, Public pricing | 4 Data processing agreement, Subprocessor list, Certifications named, +1 | Compare |
| Everlaweverlaw.comSee also Transparency alternatives to Everlaw | 30/100 | 2 Status page with history, security.txt (RFC 9116) | 3 Data processing agreement, Subprocessor list, Notice before subprocessors change | Compare |
| Logikculllogikcull.comSee also Transparency alternatives to Logikcull | 30/100 | 2 Data location stated, Status page with history | 4 Data processing agreement, Subprocessor list, HTTPS enforced with HSTS, +1 | Compare |
| ComplyKEYcomplykey.comSee also Transparency alternatives to ComplyKEY | 26/100 | 2 Data location stated, Public pricing | 5 Data processing agreement, Subprocessor list, Certifications named, +2 | Compare |
| Nuixnuix.comSee also Transparency alternatives to Nuix | 26/100 | 2 Status page with history, security.txt (RFC 9116) | 4 Data processing agreement, Subprocessor list, Certifications named, +1 | Compare |
| Jatheonjatheon.comSee also Transparency alternatives to Jatheon | 45/100 | 1 Data location stated | 2 Subprocessor list, Notice before subprocessors change | Compare |
| Smarshsmarsh.comSee also Transparency alternatives to Smarsh | 39/100 | 1 Data location stated | 3 Data processing agreement, Certifications named, HTTPS enforced with HSTS | Compare |
| KLDiscoverykldiscovery.comSee also Transparency alternatives to KLDiscovery | 30/100 | 1 Data location stated | 3 Data processing agreement, Subprocessor list, Notice before subprocessors change | 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.