Transparency alternatives to Qatalyst
Other User research and testing vendors we measure, sorted by how much they publish that Qatalyst does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 36 that differ from Qatalyst on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Qatalyst 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, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “publishes and Qatalyst does not” is the one that closes them.
| Vendor | Score | Publishes, and Qatalyst does not | Qatalyst publishes, and they do not | |
|---|---|---|---|---|
| User Interviewsuserinterviews.com | 83/100 | 8 Data processing agreement, Subprocessor list, Data location stated, +5 | 1 No third-party tracking before consent | Compare |
| Attention Insightattentioninsight.com | 57/100 | 4 Data processing agreement, Data location stated, Certifications named, +1 | 1 No third-party tracking before consent | Compare |
| Ballparkballparkhq.com | 48/100 | 4 Data location stated, Status page with history, Certifications named, +1 | 1 No third-party tracking before consent | Compare |
| Graingrain.com | 48/100 | 4 Data location stated, Status page with history, Certifications named, +1 | 1 No third-party tracking before consent | Compare |
| UserTestingusertesting.com | 48/100 | 4 Data processing agreement, Subprocessor list, Status page with history, +1 | 2 Public pricing, No third-party tracking before consent | Compare |
| Great Questiongreatquestion.co | 43/100 | 4 Data location stated, Certifications named, security.txt (RFC 9116), +1 | 1 No third-party tracking before consent | Compare |
| Useberryuseberry.com | 43/100 | 3 Subprocessor list, Certifications named, Notice before subprocessors change | 1 No third-party tracking before consent | Compare |
| Heliohelio.zurb.com | 39/100 | 3 Subprocessor list, Data location stated, Named privacy contact | 2 HTTPS enforced with HSTS, No third-party tracking before consent | Compare |
| UXArmyuxarmy.com | 39/100 | 3 Data location stated, Certifications named, Named privacy contact | 1 No third-party tracking before consent | Compare |
| Mazemaze.co | 22/100 | 3 Certifications named, security.txt (RFC 9116), Named privacy contact | 2 Public pricing, No third-party tracking before consent | Compare |
| Condenscondens.io | 43/100 | 2 Subprocessor list, Data location stated | 1 No third-party tracking before consent | Compare |
| Aureliusaureliuslab.com | 39/100 | 2 Subprocessor list, Notice before subprocessors change | 1 No third-party tracking before consent | 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.