Transparency alternatives to Legion
Other Retail operations vendors we measure, sorted by how much we found at them and not at Legion. This is a comparison of disclosure, not of features or fitness.
12 shown of 46 that differ from Legion on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Legion has 7 gaps in what we could measure: Data processing agreement, Subprocessor list, Public pricing, 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 Legion” is the one that closes them.
| Vendor | Score | Found there, not found at Legion | Found at Legion, not found there | |
|---|---|---|---|---|
| YOOBICyoobic.comSee also Transparency alternatives to YOOBIC | 70/100 | 5 Data processing agreement, Subprocessor list, Public pricing, +2 | 2 Data location stated, Named privacy contact | Compare |
| MangoAppsmangoapps.comSee also Transparency alternatives to MangoApps | 70/100 | 4 Data processing agreement, Subprocessor list, Public pricing, +1 | 1 Status page with history | Compare |
| Axeroaxerosolutions.comSee also Transparency alternatives to Axero | 61/100 | 4 Data processing agreement, Subprocessor list, Public pricing, +1 | 2 Data location stated, Status page with history | Compare |
| Firstupfirstup.ioSee also Transparency alternatives to Firstup | 61/100 | 4 Data processing agreement, Subprocessor list, Uptime SLA with a figure, +1 | 1 Data location stated | Compare |
| Repslyrepsly.comSee also Transparency alternatives to Repsly | 65/100 | 3 Data processing agreement, Subprocessor list, Notice before subprocessors change | 1 Status page with history | Compare |
| Simpplrsimpplr.comSee also Transparency alternatives to Simpplr | 61/100 | 3 Data processing agreement, security.txt (RFC 9116), Notice before subprocessors change | 1 Named privacy contact | Compare |
| Happeohappeo.comSee also Transparency alternatives to Happeo | 43/100 | 2 Data processing agreement, Notice before subprocessors change | 2 Data location stated, Certifications named | Compare |
| Interactinteractsoftware.comSee also Transparency alternatives to Interact | 39/100 | 2 Data processing agreement, Public pricing | 2 Data location stated, Status page with history | Compare |
| Flipgetflip.comSee also Transparency alternatives to Flip | 30/100 | 2 Public pricing, security.txt (RFC 9116) | 2 Data location stated, Status page with history | Compare |
| V-Countv-count.comSee also Transparency alternatives to V-Count | 26/100 | 2 Public pricing, security.txt (RFC 9116) | 3 Data location stated, Status page with history, Certifications named | Compare |
| Haiilohaiilo.comSee also Transparency alternatives to Haiilo | 39/100 | 1 Public pricing | 1 Status page with history | Compare |
| GoSpotCheckgospotcheck.comSee also Transparency alternatives to GoSpotCheck | 30/100 | 1 Public pricing | 2 Data location stated, Certifications named | 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.