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