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