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