Transparency alternatives to Elastic Email
Other Email marketing vendors we measure, sorted by how much we found at them and not at Elastic Email. This is a comparison of disclosure, not of features or fitness.
12 shown of 32 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 7 gaps in what we could measure: Data processing agreement, Subprocessor list, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change. The column “Found there, not found at Elastic Email” is the one that closes them.
| Vendor | Score | Found there, not found at Elastic Email | Found at Elastic Email, not found there | |
|---|---|---|---|---|
| Mailgunmailgun.comSee also Transparency alternatives to Mailgun | 83/100 | 5 Data processing agreement, Certifications named, Uptime SLA with a figure, +2 | nothing | Compare |
| ActiveCampaignactivecampaign.comSee also Transparency alternatives to ActiveCampaign | 74/100 | 5 Data processing agreement, Subprocessor list, Certifications named, +2 | 1 Data location stated | Compare |
| Customer.iocustomer.ioSee also Transparency alternatives to Customer.io | 78/100 | 4 Data processing agreement, Subprocessor list, Certifications named, +1 | 1 Named privacy contact | Compare |
| Klaviyoklaviyo.comSee also Transparency alternatives to Klaviyo | 65/100 | 4 Data processing agreement, Subprocessor list, Certifications named, +1 | 2 Data location stated, Named privacy contact | Compare |
| Buttondownbuttondown.comSee also Transparency alternatives to Buttondown | 61/100 | 4 Data processing agreement, Subprocessor list, security.txt (RFC 9116), +1 | 2 Data location stated, Status page with history | Compare |
| EmailOctopusemailoctopus.comSee also Transparency alternatives to EmailOctopus | 70/100 | 3 Data processing agreement, Subprocessor list, Notice before subprocessors change | 1 Status page with history | Compare |
| Mailchimpmailchimp.comSee also Transparency alternatives to Mailchimp | 57/100 | 3 Data processing agreement, Subprocessor list, security.txt (RFC 9116) | 2 Status page with history, HTTPS enforced with HSTS | Compare |
| Omnisendomnisend.comSee also Transparency alternatives to Omnisend | 57/100 | 3 Data processing agreement, security.txt (RFC 9116), Notice before subprocessors change | 1 Data location stated | Compare |
| Kitkit.comSee also Transparency alternatives to Kit | 48/100 | 3 Data processing agreement, Certifications named, Notice before subprocessors change | 3 Status page with history, HTTPS enforced with HSTS, Named privacy contact | Compare |
| CleverReachcleverreach.comSee also Transparency alternatives to CleverReach | 48/100 | 2 No third-party tracking before consent, security.txt (RFC 9116) | 1 HTTPS enforced with HSTS | Compare |
| Emailableemailable.comSee also Transparency alternatives to Emailable | 48/100 | 2 Data processing agreement, Notice before subprocessors change | 2 Data location stated, Named privacy contact | Compare |
| Postmarkpostmarkapp.comSee also Transparency alternatives to Postmark | 43/100 | 2 Data processing agreement, Notice before subprocessors change | 2 Data location stated, Status page with history | 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.