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