Transparency alternatives to 2Chat
Other Contact centre vendors we measure, sorted by how much they publish that 2Chat does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 44 that differ from 2Chat on at least one criterion we measured for both. Public transparency score, not a product or security rating.
2Chat has 8 gaps in what we could measure: Data location stated, Status page with history, 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 “publishes and 2Chat does not” is the one that closes them.
| Vendor | Score | Publishes, and 2Chat does not | 2Chat publishes, and they do not | |
|---|---|---|---|---|
| Aircallaircall.io | 61/100 | 5 Data location stated, Status page with history, Certifications named, +2 | 2 Subprocessor list, Public pricing | Compare |
| CloudTalkcloudtalk.io | 61/100 | 4 Data location stated, Certifications named, HTTPS enforced with HSTS, +1 | 1 Data processing agreement | Compare |
| JustCalljustcall.io | 43/100 | 4 Data location stated, Status page with history, Certifications named, +1 | 3 Data processing agreement, Subprocessor list, Notice before subprocessors change | Compare |
| Nextivanextiva.com | 43/100 | 4 Data location stated, Status page with history, HTTPS enforced with HSTS, +1 | 3 Data processing agreement, Subprocessor list, Notice before subprocessors change | Compare |
| FreeClimbfreeclimb.com | 35/100 | 4 Status page with history, Uptime SLA with a figure, HTTPS enforced with HSTS, +1 | 3 Data processing agreement, Subprocessor list, Notice before subprocessors change | Compare |
| CallMinercallminer.com | 30/100 | 4 Data location stated, Certifications named, HTTPS enforced with HSTS, +1 | 4 Data processing agreement, Subprocessor list, Public pricing, +1 | Compare |
| CallHippocallhippo.com | 59/100 | 3 Data location stated, Certifications named, HTTPS enforced with HSTS | 1 Subprocessor list | Compare |
| Diabolocomdiabolocom.com | 30/100 | 3 Status page with history, HTTPS enforced with HSTS, Named privacy contact | 3 Data processing agreement, Subprocessor list, Notice before subprocessors change | Compare |
| Genesysgenesys.com | 26/100 | 3 Certifications named, HTTPS enforced with HSTS, Named privacy contact | 3 Data processing agreement, Subprocessor list, Notice before subprocessors change | Compare |
| Talkdesktalkdesk.com | 26/100 | 3 Status page with history, security.txt (RFC 9116), Named privacy contact | 3 Data processing agreement, Subprocessor list, Notice before subprocessors change | Compare |
| CallNcalln.com | 22/100 | 3 Data location stated, Certifications named, Uptime SLA with a figure | 4 Data processing agreement, Subprocessor list, Public pricing, +1 | Compare |
| Swyxswyx.com | 17/100 | 3 HTTPS enforced with HSTS, security.txt (RFC 9116), Named privacy contact | 4 Data processing agreement, Subprocessor list, Public pricing, +1 | 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.