Alternatives to ClickSend
Other Transactional email and notifications vendors we measure, sorted by how much they publish that ClickSend does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 23 that differ from ClickSend on at least one criterion we measured for both. Public transparency score, not a product or security rating.
ClickSend has 7 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116). The column “publishes and ClickSend does not” is the one that closes them.
| Vendor | Score | Publishes, and ClickSend does not | ClickSend publishes, and they do not | |
|---|---|---|---|---|
| Resendresend.com | 83/100 | 6 Data processing agreement, Subprocessor list, Data location stated, +3 | 2 Status page with history, Named privacy contact | Compare |
| Mailosaurmailosaur.com | 74/100 | 4 Subprocessor list, Data location stated, Uptime SLA with a figure, +1 | nothing | Compare |
| Knockknock.app | 65/100 | 4 Data processing agreement, Subprocessor list, Data location stated, +1 | 3 Status page with history, Certifications named, Named privacy contact | Compare |
| Couriercourier.com | 52/100 | 3 Subprocessor list, Data location stated, HTTPS enforced with HSTS | 3 Certifications named, Notice before subprocessors change, Named privacy contact | Compare |
| Novunovu.co | 48/100 | 3 Data processing agreement, Data location stated, HTTPS enforced with HSTS | 3 Status page with history, Notice before subprocessors change, Named privacy contact | Compare |
| Bentobentonow.com | 43/100 | 3 Subprocessor list, Data location stated, HTTPS enforced with HSTS | 4 Status page with history, Certifications named, Notice before subprocessors change, +1 | Compare |
| Ablyably.com | 39/100 | 3 Uptime SLA with a figure, HTTPS enforced with HSTS, security.txt (RFC 9116) | 2 Certifications named, Notice before subprocessors change | Compare |
| Mailtrapmailtrap.io | 48/100 | 2 Data processing agreement, Subprocessor list | 2 Status page with history, Certifications named | Compare |
| Plunkuseplunk.com | 48/100 | 2 Data processing agreement, Data location stated | 2 Status page with history, Certifications named | Compare |
| Streamgetstream.io | 48/100 | 2 Subprocessor list, HTTPS enforced with HSTS | 1 Notice before subprocessors change | Compare |
| Batchbatch.com | 30/100 | 2 Data location stated, HTTPS enforced with HSTS | 4 Public pricing, Certifications named, Notice before subprocessors change, +1 | Compare |
| Copernicacopernica.com | 26/100 | 1 HTTPS enforced with HSTS | 3 Certifications named, Notice before subprocessors change, Named privacy contact | 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.