Alternatives to Loop11
Other User research and testing vendors we measure, sorted by how much they publish that Loop11 does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 23 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 “publishes and Loop11 does not” is the one that closes them.
| Vendor | Score | Publishes, and Loop11 does not | Loop11 publishes, and they do not | |
|---|---|---|---|---|
| Great Questiongreatquestion.co | 57/100 | 6 Subprocessor list, Data location stated, Certifications named, +3 | 2 Data processing agreement, Notice before subprocessors change | Compare |
| Ballparkballparkhq.com | 48/100 | 5 Data location stated, Status page with history, Certifications named, +2 | 2 Data processing agreement, Notice before subprocessors change | Compare |
| Graingrain.com | 48/100 | 5 Data location stated, Status page with history, Certifications named, +2 | 2 Data processing agreement, Notice before subprocessors change | Compare |
| UXArmyuxarmy.com | 39/100 | 4 Data location stated, Certifications named, HTTPS enforced with HSTS, +1 | 2 Data processing agreement, Notice before subprocessors change | Compare |
| Mazemaze.co | 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.com | 57/100 | 3 Data location stated, Certifications named, HTTPS enforced with HSTS | nothing | Compare |
| Aureliusaureliuslab.com | 52/100 | 3 Subprocessor list, Data location stated, HTTPS enforced with HSTS | 1 Data processing agreement | Compare |
| Sprigsprig.com | 52/100 | 3 Data location stated, Status page with history, HTTPS enforced with HSTS | 1 Public pricing | Compare |
| Useberryuseberry.com | 43/100 | 3 Subprocessor list, Certifications named, HTTPS enforced with HSTS | 1 Data processing agreement | Compare |
| Heliohelio.app | 39/100 | 3 Subprocessor list, Data location stated, Named privacy contact | 2 Data processing agreement, Notice before subprocessors change | Compare |
| Userbrainuserbrain.com | 35/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | 2 Data processing agreement, Notice before subprocessors change | Compare |
| Condenscondens.io | 30/100 | 2 Subprocessor list, HTTPS enforced with HSTS | 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.