Transparency alternatives to Braze
Other Marketing automation vendors we measure, sorted by how much we found at them and not at Braze. This is a comparison of disclosure, not of features or fitness.
12 shown of 34 that differ from Braze on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Braze has 7 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Public pricing, Certifications named, Uptime SLA with a figure, No third-party tracking before consent. The column “Found there, not found at Braze” is the one that closes them.
| Vendor | Score | Found there, not found at Braze | Found at Braze, not found there | |
|---|---|---|---|---|
| Customerlycustomerly.ioSee also Transparency alternatives to Customerly | 57/100 | 4 Subprocessor list, Data location stated, Public pricing, +1 | 3 Status page with history, security.txt (RFC 9116), Named privacy contact | Compare |
| Mappmapp.comSee also Transparency alternatives to Mapp | 52/100 | 4 Data processing agreement, Data location stated, Public pricing, +1 | 3 Status page with history, HTTPS enforced with HSTS, Named privacy contact | Compare |
| Keapkeap.comSee also Transparency alternatives to Keap | 61/100 | 3 Data processing agreement, Subprocessor list, Public pricing | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| GetResponsegetresponse.comSee also Transparency alternatives to GetResponse | 57/100 | 3 Data processing agreement, Public pricing, Certifications named | 1 security.txt (RFC 9116) | Compare |
| Insider Oneinsiderone.comSee also Transparency alternatives to Insider One | 52/100 | 3 Data processing agreement, Subprocessor list, Certifications named | 2 Status page with history, security.txt (RFC 9116) | Compare |
| Bloomreachbloomreach.comSee also Transparency alternatives to Bloomreach | 48/100 | 3 Subprocessor list, Public pricing, Certifications named | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Verogetvero.comSee also Transparency alternatives to Vero | 43/100 | 3 Data location stated, Public pricing, Certifications named | 3 security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact | Compare |
| CleverTapclevertap.comSee also Transparency alternatives to CleverTap | 39/100 | 3 Data processing agreement, Public pricing, Certifications named | 3 HTTPS enforced with HSTS, security.txt (RFC 9116), Notice before subprocessors change | Compare |
| Quentnquentn.comSee also Transparency alternatives to Quentn | 30/100 | 3 Data location stated, Public pricing, No third-party tracking before consent | 5 Status page with history, HTTPS enforced with HSTS, security.txt (RFC 9116), +2 | Compare |
| Postscriptpostscript.ioSee also Transparency alternatives to Postscript | 56/100 | 2 Data processing agreement, Public pricing | 2 security.txt (RFC 9116), Notice before subprocessors change | Compare |
| Airshipairship.comSee also Transparency alternatives to Airship | 52/100 | 2 Subprocessor list, Data location stated | 1 Status page with history | Compare |
| Loopsloops.soSee also Transparency alternatives to Loops | 52/100 | 2 Data processing agreement, Subprocessor list | 2 security.txt (RFC 9116), Named privacy contact | 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.