Alternatives to Helio
Other User research and testing vendors we measure, sorted by how much they publish that Helio does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 23 that differ from Helio on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Helio has 8 gaps in what we could measure: Data processing agreement, Status page with history, 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. The column “publishes and Helio does not” is the one that closes them.
| Vendor | Score | Publishes, and Helio does not | Helio publishes, and they do not | |
|---|---|---|---|---|
| Attention Insightattentioninsight.com | 57/100 | 4 Data processing agreement, Certifications named, HTTPS enforced with HSTS, +1 | 2 Subprocessor list, Named privacy contact | Compare |
| Sprigsprig.com | 52/100 | 4 Data processing agreement, Status page with history, HTTPS enforced with HSTS, +1 | 3 Subprocessor list, Public pricing, Named privacy contact | Compare |
| Great Questiongreatquestion.co | 57/100 | 3 Certifications named, HTTPS enforced with HSTS, security.txt (RFC 9116) | nothing | Compare |
| Ballparkballparkhq.com | 48/100 | 3 Status page with history, Certifications named, HTTPS enforced with HSTS | 1 Subprocessor list | Compare |
| Graingrain.com | 48/100 | 3 Status page with history, Certifications named, HTTPS enforced with HSTS | 1 Subprocessor list | Compare |
| Useberryuseberry.com | 43/100 | 3 Certifications named, HTTPS enforced with HSTS, Notice before subprocessors change | 2 Data location stated, Named privacy contact | Compare |
| Mazemaze.co | 22/100 | 3 Certifications named, HTTPS enforced with HSTS, security.txt (RFC 9116) | 3 Subprocessor list, Data location stated, Public pricing | Compare |
| Aureliusaureliuslab.com | 52/100 | 2 HTTPS enforced with HSTS, Notice before subprocessors change | 1 Named privacy contact | Compare |
| UXArmyuxarmy.com | 39/100 | 2 Certifications named, HTTPS enforced with HSTS | 1 Subprocessor list | Compare |
| Loop11loop11.com | 30/100 | 2 Data processing agreement, Notice before subprocessors change | 3 Subprocessor list, Data location stated, Named privacy contact | Compare |
| Lyssnalyssna.com | 26/100 | 2 Status page with history, HTTPS enforced with HSTS | 3 Subprocessor list, Data location stated, Named privacy contact | Compare |
| dscoutdscout.com | 22/100 | 2 Certifications named, HTTPS enforced with HSTS | 3 Subprocessor list, Data location stated, 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.