Alternatives to Broadly
Other Customer reviews and testimonials vendors we measure, sorted by how much they publish that Broadly does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 18 that differ from Broadly on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Broadly has 8 gaps in what we could measure: Data processing agreement, Subprocessor list, Status page with history, Certifications named, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, Notice before subprocessors change. The column “publishes and Broadly does not” is the one that closes them.
| Vendor | Score | Publishes, and Broadly does not | Broadly publishes, and they do not | |
|---|---|---|---|---|
| Vocal Videovocalvideo.com | 52/100 | 3 Data processing agreement, HTTPS enforced with HSTS, Notice before subprocessors change | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Birdeyebirdeye.com | 39/100 | 3 Status page with history, Certifications named, HTTPS enforced with HSTS | 2 Public pricing, security.txt (RFC 9116) | Compare |
| Boastboast.io | 39/100 | 3 Data processing agreement, HTTPS enforced with HSTS, Notice before subprocessors change | 3 Data location stated, security.txt (RFC 9116), Named privacy contact | Compare |
| G2g2.com | 39/100 | 2 Data processing agreement, HTTPS enforced with HSTS | 2 Public pricing, security.txt (RFC 9116) | Compare |
| Influitiveinfluitive.com | 26/100 | 2 Certifications named, HTTPS enforced with HSTS | 3 Public pricing, security.txt (RFC 9116), Named privacy contact | Compare |
| Vouchvouchfor.com | 13/100 | 2 Certifications named, HTTPS enforced with HSTS | 4 Data location stated, Public pricing, security.txt (RFC 9116), +1 | Compare |
| Storypromptstoryprompt.com | 22/100 | 1 HTTPS enforced with HSTS | 2 Data location stated, security.txt (RFC 9116) | Compare |
| VideoAskvideoask.com | 17/100 | 1 Status page with history | 3 Data location stated, security.txt (RFC 9116), Named privacy contact | Compare |
| Basebase.al | 9/100 | 1 No third-party tracking before consent | 4 Data location stated, Public pricing, security.txt (RFC 9116), +1 | Compare |
| Grade.usgrade.us | 9/100 | 1 HTTPS enforced with HSTS | 4 Data location stated, Public pricing, security.txt (RFC 9116), +1 | Compare |
| NiceJobnicejob.com | 9/100 | 1 HTTPS enforced with HSTS | 4 Data location stated, Public pricing, security.txt (RFC 9116), +1 | Compare |
| Featured Customersfeaturedcustomers.com | 17/100 | nothing we found there and not here | 2 Public pricing, security.txt (RFC 9116) | 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.