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