Transparency alternatives to lemlist
Other Sales engagement vendors we measure, sorted by how much we found at them and not at lemlist. This is a comparison of disclosure, not of features or fitness.
12 shown of 55 that differ from lemlist on at least one criterion we measured for both. Public transparency score, not a product or security rating.
lemlist has 6 gaps in what we could measure: Data processing agreement, Subprocessor list, Status page with history, Uptime SLA with a figure, No third-party tracking before consent, Notice before subprocessors change. The column “Found there, not found at lemlist” is the one that closes them.
| Vendor | Score | Found there, not found at lemlist | Found at lemlist, not found there | |
|---|---|---|---|---|
| Showpadshowpad.comSee also Transparency alternatives to Showpad | 65/100 | 5 Data processing agreement, Subprocessor list, Status page with history, +2 | 3 Data location stated, Public pricing, security.txt (RFC 9116) | Compare |
| Lushalusha.comSee also Transparency alternatives to Lusha | 74/100 | 4 Data processing agreement, Subprocessor list, Status page with history, +1 | 1 Data location stated | Compare |
| ZoomInfozoominfo.comSee also Transparency alternatives to ZoomInfo | 73/100 | 4 Data processing agreement, Subprocessor list, Status page with history, +1 | 2 Public pricing, Certifications named | Compare |
| Clearbitclearbit.comSee also Transparency alternatives to Clearbit | 65/100 | 4 Subprocessor list, Status page with history, Uptime SLA with a figure, +1 | 2 Public pricing, security.txt (RFC 9116) | Compare |
| Mixmaxmixmax.comSee also Transparency alternatives to Mixmax | 74/100 | 3 Data processing agreement, Subprocessor list, No third-party tracking before consent | 1 security.txt (RFC 9116) | Compare |
| Hunterhunter.ioSee also Transparency alternatives to Hunter | 70/100 | 3 Data processing agreement, Subprocessor list, Notice before subprocessors change | 2 Certifications named, security.txt (RFC 9116) | Compare |
| Scratchpadscratchpad.comSee also Transparency alternatives to Scratchpad | 61/100 | 3 Data processing agreement, Subprocessor list, Status page with history | 2 Data location stated, security.txt (RFC 9116) | Compare |
| Apolloapollo.ioSee also Transparency alternatives to Apollo | 57/100 | 3 Data processing agreement, Status page with history, Notice before subprocessors change | 2 Data location stated, security.txt (RFC 9116) | Compare |
| Fathomfathom.videoSee also Transparency alternatives to Fathom | 57/100 | 3 Data processing agreement, Status page with history, Notice before subprocessors change | 3 Certifications named, HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| PhantomBusterphantombuster.comSee also Transparency alternatives to PhantomBuster | 57/100 | 3 Data processing agreement, Subprocessor list, Status page with history | 3 Public pricing, Certifications named, HTTPS enforced with HSTS | Compare |
| Yeswareyesware.comSee also Transparency alternatives to Yesware | 57/100 | 3 Subprocessor list, Status page with history, Notice before subprocessors change | 3 HTTPS enforced with HSTS, security.txt (RFC 9116), Named privacy contact | Compare |
| Revenue.iorevenue.ioSee also Transparency alternatives to Revenue.io | 52/100 | 3 Data processing agreement, Subprocessor list, Notice before subprocessors change | 3 Data location stated, Public pricing, 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.