Transparency alternatives to Levitate
Other Marketing automation vendors we measure, sorted by how much they publish that Levitate does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 35 that differ from Levitate on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Levitate has 9 gaps in what we could measure: Data processing agreement, Subprocessor list, Public pricing, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “publishes and Levitate does not” is the one that closes them.
| Vendor | Score | Publishes, and Levitate does not | Levitate publishes, and they do not | |
|---|---|---|---|---|
| GetResponsegetresponse.com | 57/100 | 5 Data processing agreement, Public pricing, Certifications named, +2 | 1 Data location stated | Compare |
| Insider Oneinsiderone.com | 52/100 | 5 Data processing agreement, Subprocessor list, Certifications named, +2 | 2 Data location stated, Status page with history | Compare |
| Mappmapp.com | 52/100 | 5 Data processing agreement, Public pricing, Certifications named, +2 | 2 Status page with history, HTTPS enforced with HSTS | Compare |
| Keapkeap.com | 61/100 | 4 Data processing agreement, Subprocessor list, Public pricing, +1 | 1 Data location stated | Compare |
| Customerlycustomerly.io | 57/100 | 4 Subprocessor list, Public pricing, Certifications named, +1 | 1 Status page with history | Compare |
| Airshipairship.com | 52/100 | 4 Subprocessor list, security.txt (RFC 9116), Notice before subprocessors change, +1 | 1 Status page with history | Compare |
| Bloomreachbloomreach.com | 43/100 | 4 Subprocessor list, Public pricing, Notice before subprocessors change, +1 | 2 Data location stated, HTTPS enforced with HSTS | Compare |
| CleverTapclevertap.com | 39/100 | 4 Data processing agreement, Public pricing, Certifications named, +1 | 2 Data location stated, HTTPS enforced with HSTS | Compare |
| Loopsloops.so | 52/100 | 3 Data processing agreement, Subprocessor list, Notice before subprocessors change | 1 Data location stated | Compare |
| Brazebraze.com | 35/100 | 3 security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact | 1 Data location stated | Compare |
| Postscriptpostscript.io | 56/100 | 2 Data processing agreement, Public pricing | nothing | Compare |
| Verogetvero.com | 43/100 | 2 Public pricing, Certifications named | nothing | 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.