SaaS Ranking

Transparency alternatives to Buttondown

Other Email marketing vendors we measure, sorted by how much they publish that Buttondown does not. This is a comparison of disclosure, not of features or fitness.

12 shown of 27 that differ from Buttondown on at least one criterion we measured for both. Public transparency score, not a product or security rating.

Buttondown has 5 gaps in what we could measure: Data location stated, Status page with history, Certifications named, Uptime SLA with a figure, No third-party tracking before consent. The column “publishes and Buttondown does not” is the one that closes them.

VendorScorePublishes, and Buttondown does notButtondown publishes, and they do not
Mailgunmailgun.com 83/100 5 Data location stated, Status page with history, Certifications named, +2 2 Subprocessor list, security.txt (RFC 9116) Compare
Customer.iocustomer.io 78/100 3 Data location stated, Status page with history, Certifications named 2 security.txt (RFC 9116), Named privacy contact Compare
ActiveCampaignactivecampaign.com 74/100 3 Status page with history, Certifications named, Uptime SLA with a figure 1 security.txt (RFC 9116) Compare
CleverReachcleverreach.com 48/100 3 Data location stated, Status page with history, No third-party tracking before consent 4 Data processing agreement, Subprocessor list, HTTPS enforced with HSTS, +1 Compare
Klaviyoklaviyo.com 65/100 2 Status page with history, Certifications named 2 security.txt (RFC 9116), Named privacy contact Compare
Kitkit.com 48/100 2 Data location stated, Certifications named 4 Subprocessor list, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 Compare
Brevobrevo.com 36/100 2 Data location stated, Certifications named 4 Data processing agreement, Subprocessor list, Notice before subprocessors change, +1 Compare
Elastic Emailelasticemail.com 35/100 2 Data location stated, Status page with history 5 Data processing agreement, Subprocessor list, HTTPS enforced with HSTS, +2 Compare
Mailchimpmailchimp.com 57/100 1 Data location stated 2 HTTPS enforced with HSTS, Notice before subprocessors change Compare
Omnisendomnisend.com 57/100 1 Status page with history 1 Subprocessor list Compare
Emailableemailable.com 48/100 1 Status page with history 3 Subprocessor list, security.txt (RFC 9116), Named privacy contact Compare
EmailOctopusemailoctopus.com 43/100 1 Data location stated 4 Subprocessor list, security.txt (RFC 9116), Notice before subprocessors change, +1 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.