Transparency alternatives to Helio
Other User research and testing vendors we measure, sorted by how much we found at them and not at Helio. This is a comparison of disclosure, not of features or fitness.
12 shown of 36 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 “Found there, not found at Helio” is the one that closes them.
| Vendor | Score | Found there, not found at Helio | Found at Helio, not found there | |
|---|---|---|---|---|
| User Interviewsuserinterviews.comSee also Transparency alternatives to User Interviews | 83/100 | 6 Data processing agreement, Certifications named, Uptime SLA with a figure, +3 | nothing | Compare |
| Attention Insightattentioninsight.comSee also Transparency alternatives to Attention Insight | 57/100 | 4 Data processing agreement, Certifications named, HTTPS enforced with HSTS, +1 | 2 Subprocessor list, Named privacy contact | Compare |
| Ballparkballparkhq.comSee also Transparency alternatives to Ballpark | 48/100 | 3 Status page with history, Certifications named, HTTPS enforced with HSTS | 1 Subprocessor list | Compare |
| Graingrain.comSee also Transparency alternatives to Grain | 48/100 | 3 Status page with history, Certifications named, HTTPS enforced with HSTS | 1 Subprocessor list | Compare |
| UserTestingusertesting.comSee also Transparency alternatives to UserTesting | 48/100 | 3 Data processing agreement, Status page with history, HTTPS enforced with HSTS | 2 Data location stated, Public pricing | Compare |
| Great Questiongreatquestion.coSee also Transparency alternatives to Great Question | 43/100 | 3 Certifications named, HTTPS enforced with HSTS, security.txt (RFC 9116) | 1 Subprocessor list | Compare |
| Sprigsprig.comSee also Transparency alternatives to Sprig | 30/100 | 3 Data processing agreement, HTTPS enforced with HSTS, Notice before subprocessors change | 4 Subprocessor list, Data location stated, Public pricing, +1 | Compare |
| Mazemaze.coSee also Transparency alternatives to Maze | 22/100 | 3 Certifications named, HTTPS enforced with HSTS, security.txt (RFC 9116) | 3 Subprocessor list, Data location stated, Public pricing | Compare |
| Aureliusaureliuslab.comSee also Transparency alternatives to Aurelius | 39/100 | 2 HTTPS enforced with HSTS, Notice before subprocessors change | 2 Data location stated, Named privacy contact | Compare |
| UXArmyuxarmy.comSee also Transparency alternatives to UXArmy | 39/100 | 2 Certifications named, HTTPS enforced with HSTS | 1 Subprocessor list | Compare |
| Useberryuseberry.comSee also Transparency alternatives to Useberry | 35/100 | 2 Certifications named, Notice before subprocessors change | 2 Data location stated, Named privacy contact | Compare |
| UXtweakuxtweak.comSee also Transparency alternatives to UXtweak | 35/100 | 2 Data processing agreement, HTTPS enforced with HSTS | 3 Subprocessor list, Public pricing, 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.