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