Reporting channels & reporter experience
How this is scored
The intake side: how a reporter actually submits — web form, anonymous dialog, phone/voice, languages, accessibility — and whether anonymity survives first contact.
0 — A web form that is an email in disguise: no anonymous route, no way to reach the reporter afterwards.
3 — An anonymous form exists but the dialogue ends there — no secured mailbox for follow-up questions, few languages, desktop-only.
5 — Anonymous two-way dialog via a protected mailbox, a usable set of languages, mobile-friendly; voice or phone intake missing or an add-on.
8 — Multiple channels (web, voice message or hotline, QR entry points), broad language coverage with translation support, accessibility considered, and the anonymous dialog is first-class rather than bolted on.
10 — Intake engineered around the frightened reporter: every channel anonymous-capable, dozens of languages, WCAG-conscious, no app install or account required, and the vendor documents how the reporter's identity is kept out of the channel itself.
The Security Auditor
Web form with fully anonymous mode, QR-code entry, in-browser voice messages per §16 Abs. 3 HinSchG that work even anonymously, and two-way dialog via a protected area with Melde-ID and password — the anonymous dialog is first-class, not bolted on. 26 languages with optional DeepL translation and no install required round it out. Held below the top anchor because accessibility is only a self-assessed 'weitgehend kompatibel' with WCAG 2.1 AA and the 'no logs enabling conclusions about whistleblowers' claim is a one-line marketing statement, not documented engineering of how identity stays out of the channel. 2 14 11 1