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