Transparency alternatives to HappyOrNot
Other Surveys and forms vendors we measure, sorted by how much we found at them and not at HappyOrNot. This is a comparison of disclosure, not of features or fitness.
12 shown of 48 that differ from HappyOrNot on at least one criterion we measured for both. Public transparency score, not a product or security rating.
HappyOrNot has 8 gaps in what we could measure: Data processing agreement, Subprocessor list, Status page with history, Public pricing, Certifications named, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change. The column “Found there, not found at HappyOrNot” is the one that closes them.
| Vendor | Score | Found there, not found at HappyOrNot | Found at HappyOrNot, not found there | |
|---|---|---|---|---|
| Jotformjotform.comSee also Transparency alternatives to Jotform | 65/100 | 5 Subprocessor list, Status page with history, Public pricing, +2 | 1 Uptime SLA with a figure | Compare |
| SurveySparrowsurveysparrow.comSee also Transparency alternatives to SurveySparrow | 61/100 | 4 Data processing agreement, Public pricing, Certifications named, +1 | 1 Uptime SLA with a figure | Compare |
| Formbricksformbricks.comSee also Transparency alternatives to Formbricks | 52/100 | 4 Data processing agreement, Public pricing, Certifications named, +1 | 2 HTTPS enforced with HSTS, Named privacy contact | Compare |
| Typeformtypeform.comSee also Transparency alternatives to Typeform | 45/100 | 4 Data processing agreement, Status page with history, Public pricing, +1 | 3 Data location stated, Uptime SLA with a figure, HTTPS enforced with HSTS | Compare |
| Survicatesurvicate.comSee also Transparency alternatives to Survicate | 43/100 | 4 Data processing agreement, Public pricing, Certifications named, +1 | 2 Data location stated, Uptime SLA with a figure | Compare |
| Refinerrefiner.ioSee also Transparency alternatives to Refiner | 57/100 | 3 Data processing agreement, Public pricing, Notice before subprocessors change | 1 Uptime SLA with a figure | Compare |
| Wufoowufoo.comSee also Transparency alternatives to Wufoo | 50/100 | 3 Status page with history, Public pricing, Certifications named | 1 Uptime SLA with a figure | Compare |
| Formstackformstack.comSee also Transparency alternatives to Formstack | 30/100 | 3 Status page with history, Public pricing, Certifications named | 3 Data location stated, Uptime SLA with a figure, Named privacy contact | Compare |
| Qualtricsqualtrics.comSee also Transparency alternatives to Qualtrics | 30/100 | 3 Status page with history, Certifications named, security.txt (RFC 9116) | 2 Data location stated, Uptime SLA with a figure | Compare |
| SoSci Surveysoscisurvey.deSee also Transparency alternatives to SoSci Survey | 30/100 | 3 Public pricing, No third-party tracking before consent, security.txt (RFC 9116) | 3 Data location stated, Uptime SLA with a figure, Named privacy contact | Compare |
| SurveyMonkeysurveymonkey.comSee also Transparency alternatives to SurveyMonkey | 30/100 | 3 Status page with history, Public pricing, Certifications named | 3 Data location stated, Uptime SLA with a figure, Named privacy contact | Compare |
| Cognito Formscognitoforms.comSee also Transparency alternatives to Cognito Forms | 43/100 | 2 Status page with history, Public pricing | 1 Uptime SLA with a figure | 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.