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