Transparency alternatives to Maze
Other User research and testing vendors we measure, sorted by how much we found at them and not at Maze. This is a comparison of disclosure, not of features or fitness.
12 shown of 36 that differ from Maze on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Maze has 8 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Public pricing, Uptime SLA with a figure, No third-party tracking before consent, Notice before subprocessors change. The column “Found there, not found at Maze” is the one that closes them.
| Vendor | Score | Found there, not found at Maze | Found at Maze, not found there | |
|---|---|---|---|---|
| User Interviewsuserinterviews.comSee also Transparency alternatives to User Interviews | 83/100 | 6 Data processing agreement, Subprocessor list, Data location stated, +3 | nothing | Compare |
| Attention Insightattentioninsight.comSee also Transparency alternatives to Attention Insight | 57/100 | 4 Data processing agreement, Data location stated, Public pricing, +1 | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Ballparkballparkhq.comSee also Transparency alternatives to Ballpark | 48/100 | 3 Data location stated, Status page with history, Public pricing | 1 security.txt (RFC 9116) | Compare |
| Graingrain.comSee also Transparency alternatives to Grain | 48/100 | 3 Data location stated, Status page with history, Public pricing | 1 security.txt (RFC 9116) | Compare |
| UserTestingusertesting.comSee also Transparency alternatives to UserTesting | 48/100 | 3 Data processing agreement, Subprocessor list, Status page with history | 2 Certifications named, security.txt (RFC 9116) | Compare |
| Condenscondens.ioSee also Transparency alternatives to Condens | 43/100 | 3 Subprocessor list, Data location stated, Public pricing | 3 Certifications named, security.txt (RFC 9116), Named privacy contact | Compare |
| Aureliusaureliuslab.comSee also Transparency alternatives to Aurelius | 39/100 | 3 Subprocessor list, Public pricing, Notice before subprocessors change | 3 Certifications named, security.txt (RFC 9116), Named privacy contact | Compare |
| Heliohelio.zurb.comSee also Transparency alternatives to Helio | 39/100 | 3 Subprocessor list, Data location stated, Public pricing | 3 Certifications named, HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Useberryuseberry.comSee also Transparency alternatives to Useberry | 35/100 | 3 Subprocessor list, Public pricing, Notice before subprocessors change | 3 HTTPS enforced with HSTS, security.txt (RFC 9116), Named privacy contact | Compare |
| Loop11loop11.comSee also Transparency alternatives to Loop11 | 30/100 | 3 Data processing agreement, Public pricing, Notice before subprocessors change | 4 Certifications named, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | Compare |
| Great Questiongreatquestion.coSee also Transparency alternatives to Great Question | 43/100 | 2 Data location stated, Public pricing | nothing | Compare |
| UXArmyuxarmy.comSee also Transparency alternatives to UXArmy | 39/100 | 2 Data location stated, Public pricing | 1 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.