Transparency alternatives to Close
Other CRM vendors we measure, sorted by how much we found at them and not at Close. This is a comparison of disclosure, not of features or fitness.
12 shown of 109 that differ from Close on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Close 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 Close” is the one that closes them.
| Vendor | Score | Found there, not found at Close | Found at Close, not found there | |
|---|---|---|---|---|
| Clarifyclarify.aiSee also Transparency alternatives to Clarify | 70/100 | 4 Data processing agreement, Data location stated, security.txt (RFC 9116), +1 | 1 Named privacy contact | Compare |
| EspoCRMespocrm.comSee also Transparency alternatives to EspoCRM | 65/100 | 4 Data processing agreement, Subprocessor list, Data location stated, +1 | 3 Status page with history, Certifications named, Named privacy contact | Compare |
| EngageBayengagebay.comSee also Transparency alternatives to EngageBay | 57/100 | 3 Data processing agreement, Data location stated, Notice before subprocessors change | 2 Status page with history, Certifications named | Compare |
| Twentytwenty.comSee also Transparency alternatives to Twenty | 52/100 | 3 Data processing agreement, Data location stated, security.txt (RFC 9116) | 2 Status page with history, Certifications named | Compare |
| Insightlyinsightly.comSee also Transparency alternatives to Insightly | 48/100 | 3 Subprocessor list, security.txt (RFC 9116), Notice before subprocessors change | 2 HTTPS enforced with HSTS, Named privacy contact | Compare |
| SuiteDashsuitedash.comSee also Transparency alternatives to SuiteDash | 48/100 | 3 Data processing agreement, Data location stated, security.txt (RFC 9116) | 3 Status page with history, Certifications named, Named privacy contact | Compare |
| Freshworks (Freshsales)freshworks.comSee also Transparency alternatives to Freshworks (Freshsales) | 39/100 | 3 Data location stated, Uptime SLA with a figure, security.txt (RFC 9116) | 2 Status page with history, Public pricing | Compare |
| Teamleaderteamleader.euSee also Transparency alternatives to Teamleader | 59/100 | 2 Data processing agreement, Notice before subprocessors change | nothing | Compare |
| Capsulecapsulecrm.comSee also Transparency alternatives to Capsule | 52/100 | 2 Data processing agreement, Notice before subprocessors change | 1 Named privacy contact | Compare |
| HubSpothubspot.comSee also Transparency alternatives to HubSpot | 52/100 | 2 Data location stated, security.txt (RFC 9116) | nothing | Compare |
| Nutshellnutshell.comSee also Transparency alternatives to Nutshell | 43/100 | 2 Data processing agreement, Notice before subprocessors change | 2 Status page with history, Named privacy contact | Compare |
| Ontraportontraport.comSee also Transparency alternatives to Ontraport | 39/100 | 2 Data processing agreement, Notice before subprocessors change | 3 Certifications named, HTTPS enforced with HSTS, 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.