Anonymous vs identified reporting, explained

Whether to accept anonymous reports at all is often your decision, not the Directive's

It's easy to assume anonymous reporting is simply a legal requirement, on or off by force of law. It usually isn't. Article 6(2) of the Directive is explicit that, outside any existing obligation under other EU law, the Directive itself "does not affect the power of Member States to decide whether legal entities in the private or public sector... are required to accept and follow up on anonymous reports." Member States took genuinely different positions when they transposed it — some require companies to accept anonymous reports, some are silent and leave it to the company, and a few exclude anonymous reports from certain protections entirely. Check your own country's transposition before assuming either way (see the country guides under the EU Whistleblowing Directive, explained) — this is one of the details national law genuinely changes, not just translates.

Where the law leaves it to you, offering anonymity is a real design choice with a real trade-off on both sides, not a box to tick.

The case for accepting anonymous reports even where you don't have to

The evidence that discourages people from reporting wrongdoing is rarely the wrongdoing itself — it's the fear of being identified as the one who spoke up. A channel that only accepts identified reports screens out exactly the reporters who are most worried about retaliation, which tends to correlate with the reports worth hearing most. Accepting anonymous reports, even where local law doesn't require it, is a bet that more real signal gets through than would otherwise reach you at all.

The trade-off you take on if you do

Anonymity isn't free for the company handling the report. A handler can't ask a clarifying question of someone they have no way to reach outside whatever channel the reporter chose to leave open, and some situations — a reporter willing to act as a witness, or one whose account depends on details only they can supply — genuinely benefit from the handler knowing who they're dealing with. A channel needs some way to keep the door open for two-way follow-up even without an identity behind it, or anonymity ends up costing you the reports you most need to get right.

What "genuinely anonymous" actually requires, mechanically

Offering an "anonymous" option is easy to say and easy to get wrong in practice. A few things have to actually be true, regardless of which platform or process delivers them:

• No identity field forced on submission. If the form requires a name, an internal employee ID, or a login tied to a real identity before it will accept a report, anonymity was never really on offer — it was optional disclosure of who submitted it, layered on top of a system that already knows.
• No metadata trail back to a person. IP addresses, device fingerprints, or email headers attached to a submission can re-identify a reporter just as effectively as a name field would, even when the form itself asked for nothing.
• A way back into the case that doesn't depend on contact details. The 7-day acknowledgement and 3-month feedback obligations (see the 7-day/3-month clock, explained) still apply to an anonymous report — the channel needs some mechanism for a reporter to check status and answer follow-up questions without an email address or phone number ever entering the picture.
• Care in what handlers see and send. A reply-all, a forwarded thread, or a recording that hasn't been altered can expose someone who chose to stay anonymous just as surely as a missing form field would (see voice reports and anonymisation, explained simply for what that means for a spoken report specifically).

How Provoxis has answered this

Provoxis's own answer is to make anonymous reporting always available, on every tenant, with no toggle a company can switch off — the identity-field problem above is closed by design, since no identity field is ever required to submit in the first place. The contact-without-identity problem is solved with a case reference token, issued the instant a report is submitted: it's the only way back into a case, for anonymous and identified reporters alike, and it's how status and messaging work without either side needing an email address on file. Choosing to identify yourself isn't the same as becoming visible to the whole company, either — it's visible only to the staff a company has actually designated as handlers or admins for the channel, the deliberately small, competent group Article 9(1)(c) requires (see designating who handles reports for how to actually choose that group) — and an identified reporter keeps the same two-way messaging and confidentiality protections an anonymous one gets. Identifying yourself buys the handler more context; it doesn't buy you less protection.

Legal basis

• Art. 6(2), Directive (EU) 2019/1937 — Member States' discretion over whether legal entities must accept and follow up on anonymous reports.
• Art. 9(1)(c) — the requirement to designate an impartial person or department competent to follow up on reports, which is what limits who an identified reporter's identity is actually visible to.