Transparency alternatives to Kayako
Other Helpdesk vendors we measure, sorted by how much we found at them and not at Kayako. This is a comparison of disclosure, not of features or fitness.
12 shown of 49 that differ from Kayako on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Kayako has 7 gaps in what we could measure: Data processing agreement, Subprocessor list, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change. The column “Found there, not found at Kayako” is the one that closes them.
| Vendor | Score | Found there, not found at Kayako | Found at Kayako, not found there | |
|---|---|---|---|---|
| BoldDeskbolddesk.comSee also Transparency alternatives to BoldDesk | 74/100 | 5 Data processing agreement, Subprocessor list, HTTPS enforced with HSTS, +2 | 1 Data location stated | Compare |
| Intercomintercom.comSee also Transparency alternatives to Intercom | 70/100 | 5 Data processing agreement, Uptime SLA with a figure, HTTPS enforced with HSTS, +2 | 1 Status page with history | Compare |
| Desk365desk365.ioSee also Transparency alternatives to Desk365 | 74/100 | 4 Data processing agreement, Subprocessor list, HTTPS enforced with HSTS, +1 | 1 Status page with history | Compare |
| Deskprodeskpro.comSee also Transparency alternatives to Deskpro | 70/100 | 4 Data processing agreement, Subprocessor list, HTTPS enforced with HSTS, +1 | 1 Data location stated | Compare |
| Dixadixa.comSee also Transparency alternatives to Dixa | 61/100 | 4 Data processing agreement, Uptime SLA with a figure, HTTPS enforced with HSTS, +1 | 2 Status page with history, Certifications named | Compare |
| Frontfront.comSee also Transparency alternatives to Front | 52/100 | 3 Data processing agreement, HTTPS enforced with HSTS, security.txt (RFC 9116) | 2 Status page with history, Named privacy contact | Compare |
| Kustomerkustomer.comSee also Transparency alternatives to Kustomer | 52/100 | 3 Data processing agreement, Uptime SLA with a figure, HTTPS enforced with HSTS | 2 Public pricing, Certifications named | Compare |
| Gorgiasgorgias.comSee also Transparency alternatives to Gorgias | 50/100 | 3 Data processing agreement, security.txt (RFC 9116), Notice before subprocessors change | 2 Data location stated, Public pricing | Compare |
| Crispcrisp.chatSee also Transparency alternatives to Crisp | 43/100 | 3 Subprocessor list, HTTPS enforced with HSTS, No third-party tracking before consent | 3 Data location stated, Status page with history, Certifications named | Compare |
| Re:amazereamaze.comSee also Transparency alternatives to Re:amaze | 43/100 | 3 Data processing agreement, HTTPS enforced with HSTS, Notice before subprocessors change | 3 Data location stated, Status page with history, Certifications named | Compare |
| Dragdragapp.comSee also Transparency alternatives to Drag | 43/100 | 2 HTTPS enforced with HSTS, No third-party tracking before consent | 2 Status page with history, Named privacy contact | Compare |
| Deskudesku.ioSee also Transparency alternatives to Desku | 35/100 | 2 Data processing agreement, Notice before subprocessors change | 3 Data location stated, Status page with history, Named privacy contact | 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.