Transparency alternatives to Plunk
Other Transactional email and notifications vendors we measure, sorted by how much we found at them and not at Plunk. This is a comparison of disclosure, not of features or fitness.
12 shown of 30 that differ from Plunk on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Plunk has 7 gaps in what we could measure: Subprocessor list, Status page with history, Certifications named, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116). The column “Found there, not found at Plunk” is the one that closes them.
| Vendor | Score | Found there, not found at Plunk | Found at Plunk, not found there | |
|---|---|---|---|---|
| Resendresend.comSee also Transparency alternatives to Resend | 83/100 | 5 Subprocessor list, Certifications named, HTTPS enforced with HSTS, +2 | 1 Named privacy contact | Compare |
| Mailosaurmailosaur.comSee also Transparency alternatives to Mailosaur | 74/100 | 5 Subprocessor list, Status page with history, Certifications named, +2 | 1 Data processing agreement | Compare |
| Streamgetstream.ioSee also Transparency alternatives to Stream | 48/100 | 4 Subprocessor list, Status page with history, Certifications named, +1 | 3 Data processing agreement, Data location stated, Notice before subprocessors change | Compare |
| Knockknock.appSee also Transparency alternatives to Knock | 61/100 | 3 Subprocessor list, HTTPS enforced with HSTS, No third-party tracking before consent | 2 Data location stated, Named privacy contact | Compare |
| Bentobentonow.comSee also Transparency alternatives to Bento | 48/100 | 3 Subprocessor list, Certifications named, HTTPS enforced with HSTS | 3 Data processing agreement, Notice before subprocessors change, Named privacy contact | Compare |
| Couriercourier.comSee also Transparency alternatives to Courier | 39/100 | 3 Subprocessor list, Status page with history, HTTPS enforced with HSTS | 4 Data processing agreement, Data location stated, Notice before subprocessors change, +1 | Compare |
| Ablyably.comSee also Transparency alternatives to Ably | 35/100 | 3 Status page with history, HTTPS enforced with HSTS, security.txt (RFC 9116) | 3 Data processing agreement, Data location stated, Notice before subprocessors change | Compare |
| Mailtrapmailtrap.ioSee also Transparency alternatives to Mailtrap | 57/100 | 2 Subprocessor list, HTTPS enforced with HSTS | 1 Data location stated | Compare |
| Novunovu.coSee also Transparency alternatives to Novu | 48/100 | 2 Certifications named, HTTPS enforced with HSTS | 2 Notice before subprocessors change, Named privacy contact | Compare |
| OneSignalonesignal.comSee also Transparency alternatives to OneSignal | 43/100 | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | 2 Data location stated, Named privacy contact | Compare |
| SMTP2GOsmtp2go.comSee also Transparency alternatives to SMTP2GO | 39/100 | 2 Status page with history, HTTPS enforced with HSTS | 3 Data processing agreement, Notice before subprocessors change, Named privacy contact | Compare |
| ClickSendclicksend.comSee also Transparency alternatives to ClickSend | 35/100 | 2 Status page with history, Certifications named | 2 Data processing agreement, Data location stated | 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.