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