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