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