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