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