Transparency alternatives to Convercent
Other Whistleblowing systems vendors we measure, sorted by how much we found at them and not at Convercent. This is a comparison of disclosure, not of features or fitness.
12 shown of 23 that differ from Convercent on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Convercent has 10 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Public pricing, Certifications named, 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 Convercent” is the one that closes them.
| Vendor | Score | Found there, not found at Convercent | Found at Convercent, not found there | |
|---|---|---|---|---|
| FaceUpfaceup.comSee also Transparency alternatives to FaceUp | 43/100 | 5 Data processing agreement, Data location stated, Certifications named, +2 | 2 Status page with history, Named privacy contact | Compare |
| Whistlelinkwhistlelink.comSee also Transparency alternatives to Whistlelink | 35/100 | 3 Data location stated, Certifications named, Uptime SLA with a figure | nothing | Compare |
| Ethenagoethena.comSee also Transparency alternatives to Ethena | 30/100 | 3 Subprocessor list, Public pricing, HTTPS enforced with HSTS | 2 Status page with history, Named privacy contact | Compare |
| NAVEXnavex.comSee also Transparency alternatives to NAVEX | 30/100 | 3 Data processing agreement, HTTPS enforced with HSTS, Notice before subprocessors change | 2 Status page with history, Named privacy contact | Compare |
| Mitratechmitratech.comSee also Transparency alternatives to Mitratech | 26/100 | 3 Data location stated, Certifications named, HTTPS enforced with HSTS | 2 Status page with history, Named privacy contact | Compare |
| Whispliwhispli.comSee also Transparency alternatives to Whispli | 26/100 | 3 Public pricing, Certifications named, HTTPS enforced with HSTS | 1 Status page with history | Compare |
| EQS Groupeqs.comSee also Transparency alternatives to EQS Group | 22/100 | 3 Certifications named, HTTPS enforced with HSTS, security.txt (RFC 9116) | 1 Status page with history | Compare |
| Signalistsignalist.deSee also Transparency alternatives to Signalist | 29/100 | 2 Data location stated, Public pricing | 1 Status page with history | Compare |
| Case IQcaseiq.comSee also Transparency alternatives to Case IQ | 26/100 | 2 Data location stated, HTTPS enforced with HSTS | 1 Status page with history | Compare |
| Ethicoethico.comSee also Transparency alternatives to Ethico | 26/100 | 2 Data location stated, HTTPS enforced with HSTS | 1 Status page with history | Compare |
| Trustytrusty.reportSee also Transparency alternatives to Trusty | 22/100 | 2 Public pricing, HTTPS enforced with HSTS | 1 Status page with history | Compare |
| Ethicontrolethicontrol.comSee also Transparency alternatives to Ethicontrol | 17/100 | 2 Public pricing, HTTPS enforced with HSTS | 2 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.