Transparency alternatives to V-Count
Other Retail operations vendors we measure, sorted by how much they publish that V-Count does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 47 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 9 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, Named privacy contact. The column “publishes and V-Count does not” is the one that closes them.
| Vendor | Score | Publishes, and V-Count does not | V-Count publishes, and they do not | |
|---|---|---|---|---|
| Repslyrepsly.com | 65/100 | 6 Data processing agreement, Subprocessor list, Data location stated, +3 | 2 Public pricing, security.txt (RFC 9116) | Compare |
| Firstupfirstup.io | 61/100 | 6 Data processing agreement, Subprocessor list, Status page with history, +3 | 1 Public pricing | Compare |
| MangoAppsmangoapps.com | 65/100 | 5 Data processing agreement, Subprocessor list, Data location stated, +2 | 1 security.txt (RFC 9116) | Compare |
| Axeroaxerosolutions.com | 61/100 | 5 Data processing agreement, Subprocessor list, Certifications named, +2 | 1 security.txt (RFC 9116) | Compare |
| Simpplrsimpplr.com | 61/100 | 5 Data processing agreement, Data location stated, Status page with history, +2 | 1 Public pricing | Compare |
| YOOBICyoobic.com | 48/100 | 4 Subprocessor list, Status page with history, Certifications named, +1 | 1 security.txt (RFC 9116) | Compare |
| Happeohappeo.com | 43/100 | 4 Data processing agreement, Status page with history, Notice before subprocessors change, +1 | 2 Public pricing, security.txt (RFC 9116) | Compare |
| Legionlegion.co | 39/100 | 4 Data location stated, Status page with history, Certifications named, +1 | 2 Public pricing, security.txt (RFC 9116) | Compare |
| Haiilohaiilo.com | 39/100 | 3 Data location stated, Certifications named, Named privacy contact | 1 security.txt (RFC 9116) | Compare |
| Interactinteractsoftware.com | 39/100 | 3 Data processing agreement, Certifications named, Named privacy contact | 1 security.txt (RFC 9116) | Compare |
| Aurorauror.co | 30/100 | 3 Data location stated, Certifications named, Named privacy contact | 2 Public pricing, security.txt (RFC 9116) | Compare |
| Jostlejostle.me | 30/100 | 3 Data location stated, Certifications named, Named privacy contact | 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.