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