Alternatives to Elastic Email
Other Email marketing vendors we measure, sorted by how much they publish that Elastic Email does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 20 that differ from Elastic Email on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Elastic Email has 8 gaps in what we could measure: Data processing agreement, Subprocessor list, Certifications named, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change. The column “publishes and Elastic Email does not” is the one that closes them.
| Vendor | Score | Publishes, and Elastic Email does not | Elastic Email publishes, and they do not | |
|---|---|---|---|---|
| Mailgunmailgun.com | 83/100 | 6 Data processing agreement, Certifications named, Uptime SLA with a figure, +3 | nothing | Compare |
| ActiveCampaignactivecampaign.com | 78/100 | 6 Data processing agreement, Subprocessor list, Certifications named, +3 | 1 Public pricing | Compare |
| Customer.iocustomer.io | 80/100 | 4 Data processing agreement, Subprocessor list, Certifications named, +1 | nothing | Compare |
| Klaviyoklaviyo.com | 65/100 | 4 Data processing agreement, Subprocessor list, Certifications named, +1 | 1 Data location stated | Compare |
| Omnisendomnisend.com | 57/100 | 4 Data processing agreement, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | 1 Data location stated | Compare |
| Mailchimpmailchimp.com | 57/100 | 3 Data processing agreement, Subprocessor list, security.txt (RFC 9116) | 1 Status page with history | Compare |
| CleverReachcleverreach.com | 48/100 | 2 No third-party tracking before consent, security.txt (RFC 9116) | nothing | Compare |
| EmailOctopusemailoctopus.com | 43/100 | 2 Data processing agreement, HTTPS enforced with HSTS | 2 Status page with history, Named privacy contact | Compare |
| Postmarkpostmarkapp.com | 35/100 | 2 Data processing agreement, HTTPS enforced with HSTS | 2 Data location stated, Status page with history | Compare |
| Brevobrevo.com | 23/100 | 2 Certifications named, HTTPS enforced with HSTS | 3 Data location stated, Status page with history, Named privacy contact | Compare |
| Mailmodomailmodo.com | 22/100 | 2 Certifications named, HTTPS enforced with HSTS | 3 Data location stated, Status page with history, Named privacy contact | Compare |
| Substacksubstack.com | 38/100 | 1 HTTPS enforced with HSTS | 1 Public pricing | 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.