Transparency alternatives to Dex
Other CRM vendors we measure, sorted by how much they publish that Dex does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 103 that differ from Dex on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Dex has 10 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “publishes and Dex does not” is the one that closes them.
| Vendor | Score | Publishes, and Dex does not | Dex publishes, and they do not | |
|---|---|---|---|---|
| Clarifyclarify.ai | 70/100 | 6 Data processing agreement, Data location stated, Status page with history, +3 | nothing | Compare |
| EspoCRMespocrm.com | 65/100 | 5 Data processing agreement, Subprocessor list, Data location stated, +2 | 1 Certifications named | Compare |
| Teamleaderteamleader.eu | 59/100 | 5 Data processing agreement, Status page with history, HTTPS enforced with HSTS, +2 | nothing | Compare |
| EngageBayengagebay.com | 57/100 | 5 Data processing agreement, Data location stated, HTTPS enforced with HSTS, +2 | 1 Certifications named | Compare |
| HubSpothubspot.com | 52/100 | 5 Data location stated, Status page with history, HTTPS enforced with HSTS, +2 | nothing | Compare |
| Twentytwenty.com | 52/100 | 5 Data processing agreement, Data location stated, HTTPS enforced with HSTS, +2 | 1 Certifications named | Compare |
| Freshworksfreshworks.com | 39/100 | 5 Data location stated, Uptime SLA with a figure, HTTPS enforced with HSTS, +2 | 1 Public pricing | Compare |
| Capsulecapsulecrm.com | 52/100 | 4 Data processing agreement, Status page with history, HTTPS enforced with HSTS, +1 | nothing | Compare |
| Nutshellnutshell.com | 52/100 | 4 Data processing agreement, Status page with history, HTTPS enforced with HSTS, +1 | nothing | Compare |
| Coppercopper.com | 43/100 | 4 Data location stated, Status page with history, HTTPS enforced with HSTS, +1 | 1 Certifications named | Compare |
| Vtigervtiger.com | 43/100 | 4 Data location stated, Status page with history, HTTPS enforced with HSTS, +1 | 1 Certifications named | Compare |
| Raynetraynetcrm.com | 39/100 | 4 Data processing agreement, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | 1 Certifications named | 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.