# whistleblower-data

> Implements data protection compliance for whistleblowing systems under EU Directive 2019/1937 and GDPR. Covers anonymous reporting channels, identity protection for whistleblowers and accused persons, retention limits, access restrictions, and retaliation prevention. Addresses national transpositions and DPA guidance. Keywords: whistleblower, Directive 2019/1937, anonymous reporting, identity protection, retaliation, retention, reporting channel.

- Skill: `mukul975-2/whistleblower-data` (Agent Skill, multi-file: 5 files)
- Install (CLI): `npx skillmds add mukul975-2/whistleblower-data`
- Raw SKILL.md: https://api.skillmd.com/api/skills/mukul975-2/whistleblower-data/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- License: Apache-2.0
- Author: mukul975 (https://skillmd.com/u/mukul975-2)
- Updated: 2026-08-19
- Page: https://skillmd.com/skills/mukul975-2/whistleblower-data

---


# Whistleblower Data Protection

## Overview

The EU Whistleblowing Directive 2019/1937 (Directive on the protection of persons who report breaches of Union law) establishes mandatory internal reporting channels for organisations with 50 or more employees. The Directive creates a fundamental tension with GDPR: whistleblowing channels collect sensitive allegations about identified individuals (the accused), while simultaneously requiring confidentiality protection for the whistleblower. The data protection framework must balance the whistleblower's right to protection, the accused person's right to be informed and to defend themselves, and the organisation's obligation to investigate while complying with data minimisation, purpose limitation, and storage limitation principles.

This skill provides a data protection compliance framework for whistleblowing systems that satisfies both the Directive and GDPR requirements, incorporating guidance from CNIL, the Article 29 Working Party (WP117), and national transposition laws.

## Legal Framework

### EU Whistleblowing Directive 2019/1937

**Scope**: Applies to reporting of breaches of EU law in areas including public procurement, financial services, product safety, transport safety, environmental protection, food safety, public health, consumer protection, data protection, and competition law.

**Organisational requirements**:
- Organisations with 250+ employees: internal reporting channel operational since 17 December 2021
- Organisations with 50-249 employees: internal reporting channel required since 17 December 2023 (with possible national extensions)
- Public sector entities regardless of size

**Key data protection provisions**:

| Article | Provision |
|---------|-----------|
| Art. 16(1) | Member States shall ensure that reporting channels and the actions taken following a report are designed, established, and operated in a secure manner that ensures the confidentiality of the identity of the reporting person and any third party mentioned in the report |
| Art. 16(2) | Personal data that is manifestly not relevant to the handling of a specific report shall not be collected or, if accidentally collected, shall be deleted without undue delay |
| Art. 16(3) | The reporting person and the accused person shall be informed of the processing of their personal data in accordance with GDPR Art. 13 and 14, subject to the limitations in Art. 14(5) and Art. 23 |
| Art. 17(1) | Reporting persons shall have access to a balanced, comprehensive, and easily accessible information set about procedures and prerequisites for external reporting |
| Art. 18 | Records of every report received shall be kept in compliance with confidentiality requirements; reports shall be stored for no longer than necessary and proportionate |

### GDPR Intersection

**Lawful basis for whistleblowing data processing**:
- Art. 6(1)(c) legal obligation: The Directive (as transposed into national law) creates a legal obligation to operate the reporting channel
- Art. 6(1)(e) public interest: Investigation of reported breaches serves the public interest
- Art. 6(1)(f) legitimate interest: The organisation has a legitimate interest in investigating misconduct

**Special category data**: Whistleblowing reports may contain special category data (e.g., allegations of racial discrimination, health-related misconduct). Where special category data is processed:
- Art. 9(2)(b) employment obligations: Processing necessary for obligations in the field of employment law
- Art. 9(2)(g) substantial public interest: Where national law provides a basis for processing special category data in the public interest

**Criminal offence data — Art. 10**: Whistleblowing reports frequently contain allegations of criminal conduct. Art. 10 processing must be authorised by national law.

### WP29 Opinion 1/2006 (WP117)

The Article 29 Working Party's Opinion on whistleblowing schemes, while pre-GDPR, established principles that remain relevant:

1. **Proportionality**: Whistleblowing schemes should be limited to serious matters (financial misconduct, health and safety, environmental violations) — not used for routine HR complaints
2. **Confidentiality**: The identity of the whistleblower must be kept confidential from the accused and from anyone not directly involved in the investigation
3. **Anonymous reports**: Organisations should not actively encourage anonymous reporting, but must be prepared to handle anonymous reports when received
4. **Accused person's rights**: The accused must be informed of the allegations as soon as doing so does not jeopardise the investigation
5. **Retention**: Reports and investigation data should be deleted within 2 months of completing the investigation, unless legal proceedings are initiated

### National Transpositions

| Jurisdiction | Transposition | Key Data Protection Provisions |
|-------------|--------------|-------------------------------|
| France | Loi Waserman (Law No. 2022-401, 21 March 2022) | CNIL reference framework for whistleblowing (Délibération No. 2019-139); retention limit of 2 months post-investigation closure; mandatory DPIA for whistleblowing channels |
| Germany | Hinweisgeberschutzgesetz (HinSchG, effective 2 July 2023) | Art. 10 — confidentiality of reporting persons' identity; Art. 11 — data retention for 3 years after investigation closure; DPO must be involved in channel design |
| Italy | D.Lgs. 24/2023 | Garante del Privacy guidelines on whistleblowing data protection; mandatory DPIA; prohibition on using data for purposes other than the investigation |
| Netherlands | Wet bescherming klokkenluiders (effective 18 February 2023) | Enhanced identity protection; external reporting channel via Huis voor Klokkenluiders |
| Spain | Ley 2/2023 (effective 13 March 2023) | Anonymous reporting must be accepted; retention limit 3 months post-investigation unless proceedings initiated |

## Data Protection Design for Whistleblowing Channels

### Channel Architecture

The whistleblowing channel must be designed to enforce confidentiality by default:

**Technical requirements**:
| Requirement | Implementation |
|------------|---------------|
| End-to-end encryption | All communications between whistleblower and the channel must be encrypted in transit (TLS 1.3) and at rest (AES-256) |
| Access segregation | Only designated persons (typically ethics/compliance officers) have access to reports; IT administrators have system access but not content access |
| Audit logging | All access to reports is logged with user identity, timestamp, and action |
| Secure communication | The channel must provide a secure way for the whistleblower to receive feedback and provide additional information without revealing their identity |
| Anonymous option | The system must support anonymous reporting where the whistleblower chooses not to identify themselves |
| Separate system | The whistleblowing system should be logically separated from HR systems to prevent data leakage |

**Dedicated third-party platforms**: Many organisations use specialised platforms (EQS Integrity Line, NAVEX Global EthicsPoint, WhistleB, Convercent) that provide:
- External hosting separated from the organisation's IT infrastructure
- Anonymous two-way communication channels
- Encryption and access controls by design
- Configurable retention and deletion
- Audit trail and compliance reporting

### Anonymous Reporting

**Directive position**: Art. 6(2) leaves it to Member States to decide whether internal and external reporting channels must accept anonymous reports. Several Member States mandate acceptance of anonymous reports (France, Spain, Italy).

**Data protection considerations for anonymous reports**:
- The organisation must process the report based on its content, not the identity of the reporter
- If the anonymous reporter voluntarily identifies themselves during the investigation, confidentiality protections apply from that point
- Anonymous reports may be more difficult to investigate; the organisation should still conduct a reasonable investigation
- IP addresses and metadata that could identify the anonymous reporter must not be logged by the reporting system

### Identity Protection

**Whistleblower identity**:
- The whistleblower's identity may only be disclosed to persons directly responsible for receiving and following up on reports
- Disclosure to the accused or to others (including management, HR, or legal counsel not involved in the investigation) requires the explicit consent of the whistleblower
- In the event of judicial proceedings, disclosure may be required by national procedural law — the whistleblower must be informed before disclosure

**Accused person's identity**:
- The accused person has Art. 14 GDPR rights (right to be informed) but these may be restricted under Art. 14(5)(b) (where informing would seriously impair the objectives of the processing) or Art. 23 (restriction to safeguard important objectives of general public interest)
- The accused must be informed as soon as doing so would no longer jeopardise the investigation (typically after evidence has been secured and witnesses have been interviewed)
- The accused must not be informed of the whistleblower's identity unless required by judicial order

**Third parties mentioned in reports**: Witnesses, bystanders, and others mentioned in reports have data protection rights. Their data must be:
- Minimised to what is relevant to the investigation
- Protected with the same confidentiality measures
- Deleted when no longer necessary for the investigation

## Access Restrictions

### Designated Persons Model

| Role | Access | Restriction |
|------|--------|------------|
| Ethics/Compliance Officer | Full access to reports and investigation files | Only designated officers; typically 2-3 persons in the organisation |
| Investigation team member | Access to specific assigned cases | Assigned on a case-by-case basis; access revoked when the investigation concludes |
| DPO | Access to processing records and DPIA; no routine access to report content | May access content if required for a data protection assessment of the channel itself |
| Legal counsel | Access to assigned cases where legal advice is sought | Subject to legal professional privilege; access documented |
| CEO/Board | Informed of investigation outcomes; not routine access to report content | Exception: where the report concerns the Ethics/Compliance Officer, the CEO or Board receives the report directly |
| Line managers | No access | Line managers are frequently the subjects of reports; they must not have access to the channel |
| HR | No access unless specifically assigned to an investigation | HR involvement must be authorised by the Ethics Officer |
| IT | System administration; no access to report content | Content encryption prevents IT access |

### Conflict of Interest Protocols

- If a report names the Ethics/Compliance Officer, the report must be routed to an alternative recipient (typically the Chair of the Audit Committee or an external ombudsperson)
- If a report names a Board member, the report must be routed to an external legal counsel or the supervisory authority
- If a report names the DPO, the GDPR oversight function must be temporarily assigned to an alternative

## Data Retention

### Retention Framework (aligned with strictest national requirements)

| Data Category | Retention Period | Trigger |
|--------------|-----------------|---------|
| Report and investigation file — no misconduct found | 2 months after investigation closure (CNIL) / 3 years (Germany HinSchG) — apply stricter of applicable national law | Investigation closure date |
| Report and investigation file — misconduct confirmed, no proceedings | 2 months after investigation closure (CNIL) or per national law | Investigation closure date |
| Report and investigation file — legal proceedings initiated | Duration of proceedings + statutory limitation period | Conclusion of proceedings |
| Whistleblower identity (where disclosed) | Same as investigation file | Same trigger |
| Anonymous report metadata | Same as investigation file | Same trigger |
| Manifestly unfounded reports | Delete immediately after determination | Determination date |
| Data manifestly not relevant (Art. 16(2)) | Delete without undue delay | Upon identification |

### Retention Implementation

- Configure the whistleblowing platform's retention automation to apply the applicable national retention period
- Set automated alerts for retention review at the end of the retention period
- Ensure that deletion is complete: all copies, backups, and references must be removed
- Maintain a deletion log (recording that a report was received, investigated, and deleted — without retaining the substance of the report)

## Retaliation Prevention — Data Protection Dimension

The Directive prohibits retaliation against whistleblowers (Art. 19). The data protection dimension includes:

- **Monitoring whistleblowers**: The organisation must not use monitoring systems (email, internet, CCTV) to identify anonymous reporters
- **Performance data**: Performance reviews, absence records, and disciplinary actions following a report must be reviewed for possible retaliatory motivation
- **Access logs**: Access logs of the whistleblowing system must be monitored to detect unauthorised access attempts (which may indicate attempts to identify the whistleblower)
- **HR system restrictions**: If the whistleblower's identity is known to the Ethics Officer, the HR system must not link the employee record to the whistleblowing file

## DPIA Requirement

Whistleblowing channels require a DPIA because the processing:
- Involves vulnerable data subjects (employees reporting on their employer or colleagues)
- May involve criminal offence data (Art. 10)
- Involves systematic collection of data about identified individuals (accused persons)
- Has significant consequences for data subjects (potential disciplinary action, dismissal, or criminal referral)

The DPIA must assess:
- Risks to whistleblower confidentiality (identity disclosure)
- Risks to accused persons' rights (right to be informed, right of defence)
- Risks of function creep (using the channel for non-whistleblowing purposes)
- Data security risks (unauthorised access to reports)
- Cross-border transfer risks (where the whistleblowing platform is hosted outside the EEA)

## Atlas Manufacturing Group Example

Atlas Manufacturing Group implemented a whistleblowing channel using EQS Integrity Line for its 2,400 employees across four EU jurisdictions.

**Configuration**:
1. Anonymous and identified reporting both accepted
2. Access restricted to two designated Ethics Officers (Chief Compliance Officer and Deputy)
3. Where a report concerns the CCO, the report is automatically routed to the Chair of the Board Audit Committee
4. Retention configured at 2 months post-investigation closure (aligned with CNIL requirements for the French entity — the strictest applicable standard)
5. Reports involving potential criminal conduct are flagged for legal review; retention extends to the duration of any proceedings
6. DPIA completed before channel launch, reviewed annually
7. The DPO conducted an Art. 28 assessment of EQS as a data processor, verified EU data hosting, and confirmed TLS 1.3 encryption in transit and AES-256 at rest
8. Privacy notice provided to all employees explaining the channel, data processing, confidentiality measures, and rights of both reporters and accused persons

**Incident**: An employee submitted an anonymous report alleging that a production manager was falsifying safety inspection records. The Ethics Officer initiated an investigation, securing documentary evidence before informing the accused manager. The manager was informed of the substance of the allegations but not the identity of the reporter (which was unknown due to anonymity). The investigation confirmed the allegations, and the manager was dismissed. The investigation file was retained for the duration of the unfair dismissal proceedings and deleted 6 months after the tribunal decision.

## Enforcement Precedents

| Authority | Case | Fine/Outcome | Key Issue |
|-----------|------|-------------|-----------|
| CNIL (France) | Deliberation SAN-2020-015 | EUR 100,000 | Whistleblowing system retained reports for 5 years — excessive; CNIL requires 2 months post-investigation |
| Garante (Italy) | Provvedimento 2022-0178 | Processing restriction | Whistleblowing channel did not ensure confidentiality; IT staff had access to report content |
| AEPD (Spain) | PS/00123/2023 | EUR 150,000 | Organisation disclosed whistleblower identity to the accused person without consent or legal requirement |
| BfDI (Germany) | 2023 Audit | Corrective measures | Whistleblowing channel did not support anonymous reporting as required by HinSchG |
| Autoriteit Persoonsgegevens (NL) | 2023 Investigation | Warning | Organisation failed to conduct DPIA for whistleblowing channel |

## Integration Points

- **Employee Monitoring DPIA**: Whistleblowing channels are subject to DPIA (see employee-monitoring-dpia skill).
- **Employee DSAR Response**: DSARs from accused persons must be balanced against whistleblower confidentiality (see employee-dsar-response skill).
- **Employment Consent Limits**: Consent is not the lawful basis for whistleblowing processing (see employment-consent-limits skill).
- **HR System Privacy Config**: Whistleblowing data must be separated from HR system data (see hr-system-privacy-config skill).
- **Background Check Privacy**: Investigation findings may inform background check requirements for future roles (see background-check-privacy skill).