Reporting channels & reporter experience
How this is scored
The intake side: how a reporter actually submits — web form, anonymous dialogue, phone or voice message, languages, accessibility — and whether anonymity survives first contact.
0 — Not a reporting channel; a general contact or survey form with no anonymous route and no way to reach the reporter afterwards.
3 — A web form that accepts anonymous reports, with a case number or access code the reporter can use to check the report later.
5 — Anonymous two-way dialogue through a protected mailbox or access code, the reporting page in several languages, and use on mobile devices without an app or account.
8 — Several channels (web, voice message or phone hotline, in-person meeting requests, QR or intranet entry points), broad language coverage with translation of messages, accessibility addressed, and voice distortion or another anonymity measure for spoken reports.
10 — Intake engineered around the frightened reporter: every channel usable anonymously, dozens of languages, WCAG conformance stated, no app or account required, and the vendor documents how the reporter's identity is kept out of the channel itself.
The Security Auditor
Web, mobile app, phone hotline, SMS, live chat and voice intake are all documented channels, and the anonymity side is more than marketing: a randomly generated username, deletion of the reporter's IP address, automatic voice distortion on submission, and a Safe Inbox dialogue documented as hiding the reporter from case managers. Seventy-plus languages with translation and a 24/7 conversational voice agent put this in the strong band; what keeps it off the top is that we found no public information on accessibility conformance or in-person meeting requests. 2 1 8 9 6