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