Transparency alternatives to Cerb Cloud
Other Helpdesk vendors we measure, sorted by how much they publish that Cerb Cloud does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 37 that differ from Cerb Cloud on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Cerb Cloud has 10 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “publishes and Cerb Cloud does not” is the one that closes them.
| Vendor | Score | Publishes, and Cerb Cloud does not | Cerb Cloud publishes, and they do not | |
|---|---|---|---|---|
| Intercomintercom.com | 70/100 | 7 Data processing agreement, Data location stated, Certifications named, +4 | nothing | Compare |
| Deskprodeskpro.com | 70/100 | 6 Data processing agreement, Subprocessor list, Status page with history, +3 | nothing | Compare |
| Gorgiasgorgias.com | 50/100 | 6 Data processing agreement, Status page with history, Certifications named, +3 | 2 Public pricing, HTTPS enforced with HSTS | Compare |
| Dixadixa.com | 61/100 | 5 Data processing agreement, Data location stated, Uptime SLA with a figure, +2 | nothing | Compare |
| Frontfront.com | 52/100 | 4 Data processing agreement, Data location stated, Certifications named, +1 | nothing | Compare |
| Hiverhiverhq.com | 48/100 | 4 Data location stated, Status page with history, Certifications named, +1 | nothing | Compare |
| Tidiotidio.com | 41/100 | 4 Data location stated, Status page with history, Certifications named, +1 | 1 HTTPS enforced with HSTS | Compare |
| Kayakokayako.com | 39/100 | 4 Data location stated, Status page with history, Certifications named, +1 | 1 HTTPS enforced with HSTS | Compare |
| Zendeskzendesk.com | 26/100 | 4 Data location stated, Certifications named, security.txt (RFC 9116), +1 | 2 Public pricing, HTTPS enforced with HSTS | Compare |
| Crispcrisp.chat | 43/100 | 3 Subprocessor list, No third-party tracking before consent, Named privacy contact | nothing | Compare |
| Helpwisehelpwise.io | 43/100 | 3 Data location stated, Status page with history, Named privacy contact | nothing | Compare |
| Re:amazereamaze.com | 43/100 | 3 Data processing agreement, Notice before subprocessors change, Named privacy contact | nothing | 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.