A whistleblower reporting channel on a company website is a separate, secured form with tightly restricted access. Not a regular contact form. The Polish Whistleblower Protection Act of 14 June 2024 took effect on 25 September 2024, and some of its provisions, including Chapter 4, only on 25 December 2024.
Check the headcount threshold above which the obligation applies to an employer, and all the deadlines, directly in the text of the Whistleblower Protection Act, because we do not discuss the law here. We deal only with the technical and organizational side: how to accept reports through a website or an application so that their content and the author’s identity do not reach unauthorized people.
Table of contents
Why is a regular contact form not suitable for whistleblower reports?
Because a standard form sends the content as a plain email to a general mailbox that many people read. And that is not all. The same message then stays in several places at once: in the mailbox, in the plugin’s entries, in the WordPress database and in the server backups. Who has seen it? Nobody can tell, because a shared mailbox leaves no trace of who read what. The worst case is a report that lands with the person it concerns, for example an office manager who handles the contact address.
That does not mean the tool itself is bad. A well configured contact form in WordPress works just fine for quote requests. It was simply built for a different purpose: to deliver a message quickly and widely. And here you need the exact opposite.
What should a whistleblower reporting channel on a website include?
The channel is a separate subpage or application with its own form, a separate place of storage and a short list of authorized people. In practice it consists of several building blocks:
- a form for the whistleblower with a description of the case and the option to add attachments,
- an optional contact field that does not have to be filled in,
- a report identifier assigned automatically after submission,
- a panel for the people who handle cases,
- a register of reports with a history of actions.
The link to the channel should be easy to find, for example in the footer. And without logging in to the intranet, because logging in alone reveals who visited the page. The order of work matters too: first the company describes the rules in a document, namely the internal reporting procedure, and only then picks a tool that carries out those arrangements. Not the other way round.
Confidentiality of reports: who has access to the content and the identity?
Only people authorized by name look at the reports, and the reporting person’s data is stored separately from the description of the case. Each of these people has their own account with two-factor login. No passwords shared within the team. Why the separation? It makes it possible to hand the case over for clarification to someone who does not need to know who it came from.
A separate problem is the people who should not read the content but technically can: the server administrator and the agency that maintains the website. This is limited by encrypting the database fields with a key that is not accessible from the hosting level and by keeping the data outside the website installation. Email notifications contain only the information that there is a new case. Never its description. And then there is the metadata, which is easy to forget: the IP address, request headers and author names saved in attachment files.
Acknowledgment of receipt and follow-up contact without revealing data
The reporting person receives a case number and an access password, which let them return to the report without giving an email address. After logging in, they see a two-way inbox that works inside the system: the person handling the case asks follow-up questions and gives feedback there, and the reporting person replies or sends more documents. On top of that come clear statuses (received, under investigation, closed), which show them that the case has not got stuck. The deadlines for acknowledgment and for a response come from the act. That is why the system should allow them to be set in line with its text and should remind the authorized people about them.
Encryption, access logs and where the data is stored
Reports are encrypted in transit and at rest, and every time a case is opened it leaves an entry in the log. The minimum set of technical requirements looks like this:
- an HTTPS connection on the whole subpage and in the panel,
- encryption of the database and the attachments,
- read and change logs with the account name and the time,
- a separate database outside the website installation,
- backups covered by the same access rules,
- a defined retention period and deletion of the data once it has passed.
Three things matter when choosing hosting: the server location, the data processing agreement and separation from the website’s marketing environment. The easiest way to verify this is to order a security and GDPR audit before launching the channel. Oh, and analytics plugins and tracking scripts must not run on the reporting subpage. Leaving them there belongs to the same group of failings as other typical GDPR mistakes on a website.
Anonymous reports: how to handle them technically?
An anonymous report requires a form that does not ask for personal data and does not save information that would make it possible to identify the sender. Does the company accept such reports at all? It decides that itself in its procedure, and the tool is only meant to reflect that decision.
If the answer is yes, then on this subpage you turn off the saving of IP addresses in the application logs, analytics and tracking cookies. Follow-up contact goes through the case identifier instead of an email address. Next to the attachments field I recommend placing a warning that documents and photos store the name of the author, the device or the location, so it is better to clean them beforehand.
A ready-made tool or a custom solution on the company website?
It depends. On the size of the organization, the number of people handling cases and where the company wants to keep the data. When comparing options, assess four things: control over the data, integration with the existing website or application, the cost of maintenance and updates, and the ability to review the logs on your own. An external service takes maintenance off the company’s hands, but hands the data over to the provider. It is a trade-off. With unusual requirements, for example several companies with separate teams or the need to connect to an internal system, custom software development can be a sensible route.
From 25 September 2024 whistleblowers are covered by statutory protection, so it is better to settle the technical matters before the first report than after it. A well prepared whistleblower reporting channel meets several conditions at once: separate storage outside the website, encryption, named accounts with an access log, notifications without content and follow-up contact through the case number.
Frequently asked questions
Is an email address enough as an internal reporting channel?
Email has limitations that configuration cannot get around. The message stays on the server, in email clients and in backups, and people outside the authorized group often have access to the mailbox. There are also no logs showing who read the report and when. And the sender’s address alone reveals their identity.
Can a whistleblower form run on WordPress?
It can. But under several conditions. Reports are saved in a separate place rather than in the plugin’s default tables, they are encrypted, only selected roles have access, and email notifications do not contain the content. And one more thing: the subpage should be free of analytics and marketing scripts.
Who in the company should have access to the reports?
Only people authorized by name and listed in the procedure. The IT department and the agency looking after the website are responsible for keeping the system running, but they should not be readers of the content. Encryption and separation of permissions make sure of that. Every entry into a case should leave a trace in the log.








