Transparency alternatives to Relativity
Other eDiscovery and archiving vendors we measure, sorted by how much they publish that Relativity does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 39 that differ from Relativity on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Relativity has 10 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Public pricing, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, Notice before subprocessors change, Named privacy contact. The column “publishes and Relativity does not” is the one that closes them.
| Vendor | Score | Publishes, and Relativity does not | Relativity publishes, and they do not | |
|---|---|---|---|---|
| DISCOcsdisco.com | 52/100 | 5 Data processing agreement, Subprocessor list, Certifications named, +2 | 1 security.txt (RFC 9116) | Compare |
| Hanzohanzo.co | 39/100 | 5 Subprocessor list, Data location stated, Certifications named, +2 | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Jatheonjatheon.com | 45/100 | 4 Data processing agreement, Data location stated, Certifications named, +1 | nothing | Compare |
| Mailbutlermailbutler.io | 43/100 | 4 Data location stated, Status page with history, Public pricing, +1 | 1 security.txt (RFC 9116) | Compare |
| Magnet Forensicsmagnetforensics.com | 39/100 | 4 Data location stated, Status page with history, Certifications named, +1 | 1 security.txt (RFC 9116) | Compare |
| Smarshsmarsh.com | 39/100 | 4 Subprocessor list, Data location stated, Notice before subprocessors change, +1 | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Logikculllogikcull.com | 30/100 | 4 Data location stated, Status page with history, Certifications named, +1 | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| GoldFynchgoldfynch.com | 35/100 | 3 Data location stated, Public pricing, Named privacy contact | 1 security.txt (RFC 9116) | Compare |
| Lighthouselighthouseglobal.com | 35/100 | 3 Data location stated, Public pricing, Named privacy contact | 1 security.txt (RFC 9116) | Compare |
| Shieldshieldfc.com | 35/100 | 3 Data processing agreement, Certifications named, Notice before subprocessors change | 1 security.txt (RFC 9116) | Compare |
| Everlaweverlaw.com | 30/100 | 3 Status page with history, Certifications named, Named privacy contact | nothing | Compare |
| KLDiscoverykldiscovery.com | 30/100 | 3 Data location stated, Certifications named, Named privacy contact | 1 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.