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