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