Alternatives to Userflow
Other Customer success and onboarding vendors we measure, sorted by how much they publish that Userflow does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 27 that differ from Userflow on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Userflow has 6 gaps in what we could measure: Data processing agreement, Subprocessor list, Certifications named, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change. The column “publishes and Userflow does not” is the one that closes them.
| Vendor | Score | Publishes, and Userflow does not | Userflow publishes, and they do not | |
|---|---|---|---|---|
| Custcust.co | 39/100 | 4 Data processing agreement, Certifications named, security.txt (RFC 9116), +1 | 5 Data location stated, Status page with history, Uptime SLA with a figure, +2 | Compare |
| Dockdock.us | 74/100 | 3 Data processing agreement, Certifications named, Notice before subprocessors change | nothing | Compare |
| Gainsightgainsight.com | 61/100 | 3 Subprocessor list, Certifications named, Notice before subprocessors change | 2 Public pricing, Uptime SLA with a figure | Compare |
| Arcadearcade.software | 57/100 | 3 Data processing agreement, Certifications named, Notice before subprocessors change | 3 Status page with history, Uptime SLA with a figure, Named privacy contact | Compare |
| Inline Manualinlinemanual.com | 57/100 | 3 Data processing agreement, Certifications named, Notice before subprocessors change | 3 Uptime SLA with a figure, HTTPS enforced with HSTS, Named privacy contact | Compare |
| Navatticnavattic.com | 57/100 | 3 Data processing agreement, Subprocessor list, Notice before subprocessors change | 3 Data location stated, Status page with history, Uptime SLA with a figure | Compare |
| Akitaakitaapp.com | 48/100 | 3 Data processing agreement, Certifications named, Notice before subprocessors change | 4 Status page with history, Uptime SLA with a figure, HTTPS enforced with HSTS, +1 | Compare |
| GUIDEcxguidecx.com | 43/100 | 3 Data processing agreement, Certifications named, Notice before subprocessors change | 4 Status page with history, Public pricing, Uptime SLA with a figure, +1 | Compare |
| Planhatplanhat.com | 39/100 | 3 Data processing agreement, Certifications named, Notice before subprocessors change | 4 Data location stated, Status page with history, Public pricing, +1 | Compare |
| Arrowsarrows.to | 35/100 | 3 Data processing agreement, Certifications named, Notice before subprocessors change | 5 Data location stated, Status page with history, Public pricing, +2 | Compare |
| ClientSuccessclientsuccess.com | 52/100 | 2 Subprocessor list, Certifications named | 2 Status page with history, Uptime SLA with a figure | Compare |
| Pendopendo.io | 52/100 | 2 Data processing agreement, Certifications named | 2 Public pricing, 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.