SaaS Ranking

Transparency alternatives to Formbricks

Other Surveys and forms vendors we measure, sorted by how much we found at them and not at Formbricks. This is a comparison of disclosure, not of features or fitness.

12 shown of 48 that differ from Formbricks on at least one criterion we measured for both. Public transparency score, not a product or security rating.

Formbricks has 6 gaps in what we could measure: Subprocessor list, Status page with history, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), Named privacy contact. The column “Found there, not found at Formbricks” is the one that closes them.

VendorScoreFound there, not found at FormbricksFound at Formbricks, not found there
Jotformjotform.comSee also Transparency alternatives to Jotform 65/100 5 Subprocessor list, Status page with history, HTTPS enforced with HSTS, +2 3 Data processing agreement, Uptime SLA with a figure, Notice before subprocessors change Compare
Qualtricsqualtrics.comSee also Transparency alternatives to Qualtrics 30/100 4 Status page with history, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 5 Data processing agreement, Data location stated, Public pricing, +2 Compare
Wufoowufoo.comSee also Transparency alternatives to Wufoo 50/100 3 Status page with history, HTTPS enforced with HSTS, Named privacy contact 3 Data processing agreement, Uptime SLA with a figure, Notice before subprocessors change Compare
Cognito Formscognitoforms.comSee also Transparency alternatives to Cognito Forms 43/100 3 Status page with history, HTTPS enforced with HSTS, Named privacy contact 4 Data processing agreement, Certifications named, Uptime SLA with a figure, +1 Compare
Filloutfillout.comSee also Transparency alternatives to Fillout 43/100 3 Status page with history, HTTPS enforced with HSTS, Named privacy contact 4 Data processing agreement, Certifications named, Uptime SLA with a figure, +1 Compare
Survicatesurvicate.comSee also Transparency alternatives to Survicate 43/100 3 HTTPS enforced with HSTS, security.txt (RFC 9116), Named privacy contact 3 Data location stated, Uptime SLA with a figure, Notice before subprocessors change Compare
LimeSurveylimesurvey.orgSee also Transparency alternatives to LimeSurvey 30/100 3 HTTPS enforced with HSTS, security.txt (RFC 9116), Named privacy contact 5 Data processing agreement, Public pricing, Certifications named, +2 Compare
SoSci Surveysoscisurvey.deSee also Transparency alternatives to SoSci Survey 30/100 3 HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116) 5 Data processing agreement, Data location stated, Certifications named, +2 Compare
Medalliamedallia.comSee also Transparency alternatives to Medallia 22/100 3 HTTPS enforced with HSTS, security.txt (RFC 9116), Named privacy contact 5 Data processing agreement, Data location stated, Public pricing, +2 Compare
NIPO Nfieldnipo.comSee also Transparency alternatives to NIPO Nfield 17/100 3 HTTPS enforced with HSTS, security.txt (RFC 9116), Named privacy contact 6 Data processing agreement, Data location stated, Public pricing, +3 Compare
SurveySparrowsurveysparrow.comSee also Transparency alternatives to SurveySparrow 61/100 2 HTTPS enforced with HSTS, Named privacy contact 1 Uptime SLA with a figure Compare
Refinerrefiner.ioSee also Transparency alternatives to Refiner 57/100 2 HTTPS enforced with HSTS, Named privacy contact 2 Certifications named, 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.