Implements GDPR-compliant whistleblowing systems per EU Directive 2019/1937, covering anonymous reporting channels, identity protection, retention limits, and access restrictions.
npx claudepluginhub mukul975/privacy-data-protection-skills --plugin privacy-skills-completeThis skill uses the workspace's default tool permissions.
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 co...
Conducts multi-round deep research on GitHub repos via API and web searches, generating markdown reports with executive summaries, timelines, metrics, and Mermaid diagrams.
Dynamically discovers and combines enabled skills into cohesive, unexpected delightful experiences like interactive HTML or themed artifacts. Activates on 'surprise me', inspiration, or boredom cues.
Generates images from structured JSON prompts via Python script execution. Supports reference images and aspect ratios for characters, scenes, products, visuals.
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.
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:
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 |
Lawful basis for whistleblowing data processing:
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:
Criminal offence data — Art. 10: Whistleblowing reports frequently contain allegations of criminal conduct. Art. 10 processing must be authorised by national law.
The Article 29 Working Party's Opinion on whistleblowing schemes, while pre-GDPR, established principles that remain relevant:
| 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 |
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:
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:
Whistleblower identity:
Accused person's identity:
Third parties mentioned in reports: Witnesses, bystanders, and others mentioned in reports have data protection rights. Their data must be:
| 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 |
| 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 |
The Directive prohibits retaliation against whistleblowers (Art. 19). The data protection dimension includes:
Whistleblowing channels require a DPIA because the processing:
The DPIA must assess:
Atlas Manufacturing Group implemented a whistleblowing channel using EQS Integrity Line for its 2,400 employees across four EU jurisdictions.
Configuration:
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.
| 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 |