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