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