Transparency alternatives to MyCase
Other Legal practice management vendors we measure, sorted by how much we found at them and not at MyCase. This is a comparison of disclosure, not of features or fitness.
12 shown of 49 that differ from MyCase on at least one criterion we measured for both. Public transparency score, not a product or security rating.
MyCase has 8 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change. The column “Found there, not found at MyCase” is the one that closes them.
| Vendor | Score | Found there, not found at MyCase | Found at MyCase, not found there | |
|---|---|---|---|---|
| Luminanceluminance.comSee also Transparency alternatives to Luminance | 65/100 | 5 Data processing agreement, Subprocessor list, Data location stated, +2 | 2 Status page with history, Public pricing | Compare |
| Cerenadecerenade.comSee also Transparency alternatives to Cerenade | 48/100 | 4 Data processing agreement, Subprocessor list, Certifications named, +1 | 3 Status page with history, Public pricing, Named privacy contact | Compare |
| Amberloamberlo.ioSee also Transparency alternatives to Amberlo | 43/100 | 3 Data processing agreement, Data location stated, Certifications named | 2 Status page with history, HTTPS enforced with HSTS | Compare |
| Filevinefilevine.comSee also Transparency alternatives to Filevine | 30/100 | 3 Subprocessor list, Data location stated, Certifications named | 4 Status page with history, Public pricing, HTTPS enforced with HSTS, +1 | Compare |
| Matters.Cloudmatters.cloudSee also Transparency alternatives to Matters.Cloud | 35/100 | 2 Subprocessor list, Data location stated | 3 Status page with history, HTTPS enforced with HSTS, Named privacy contact | Compare |
| Smokeballsmokeball.comSee also Transparency alternatives to Smokeball | 35/100 | 2 Data location stated, Certifications named | 2 Public pricing, Named privacy contact | Compare |
| Eliteelite.comSee also Transparency alternatives to Elite | 30/100 | 2 Data location stated, Certifications named | 2 Status page with history, Public pricing | Compare |
| Legitolegito.comSee also Transparency alternatives to Legito | 29/100 | 2 Data location stated, Certifications named | 2 HTTPS enforced with HSTS, Named privacy contact | Compare |
| CARET Legalcaretlegal.comSee also Transparency alternatives to CARET Legal | 26/100 | 2 Data location stated, Certifications named | 3 Status page with history, HTTPS enforced with HSTS, Named privacy contact | Compare |
| Definelydefinely.comSee also Transparency alternatives to Definely | 26/100 | 2 Data location stated, Certifications named | 3 Status page with history, Public pricing, Named privacy contact | Compare |
| Josefjoseflegal.comSee also Transparency alternatives to Josef | 26/100 | 2 Data location stated, Certifications named | 3 Status page with history, Public pricing, Named privacy contact | Compare |
| LEAPleap.usSee also Transparency alternatives to LEAP | 26/100 | 2 Data location stated, Certifications named | 3 Status page with history, Public pricing, Named privacy contact | 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.