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