
employee-privacy-skills
11 employee privacy skills: monitoring DPIA, BYOD policy, biometric data, whistleblower, background checks, workplace email
- version
- 1.0.0
- GitHub stars
- 340
Install
/plugin install employee-privacy-skills@privacy-data-protection-skillsRun it inside Claude Code after adding the marketplace with /plugin marketplace add mukul975/Privacy-Data-Protection-Skills.
Contents
Discovered from sourceSkills 11
Background Check Privacy
Overview
Pre-employment background checks involve processing personal data that ranges from routine reference verification to highly sensitive criminal record data. Art. 10 GDPR provides specific restrictions on processing data relating to criminal convictions and offences, requiring that such processing be authorised by EU or Member State law providing appropriate safeguards. Beyond criminal data, background checks may involve credit history, educational qualifications, professional registration, social media presence, and right-to-work verification — each carrying distinct proportionality and data minimisation requirements. The principle that governs all background checking is role-based necessity: the scope of a background check must be proportionate to the specific role and its associated risks, not applied uniformly across all positions.
Legal Framework
Art. 10 — Criminal Conviction Data
"Processing of personal data relating to criminal convictions and offences or related security measures based on Article 6(1) shall be carried out only under the control of official authority or when the processing is authorised by Union or Member State law providing for appropriate safeguards for the rights and freedoms of data subjects."
Key requirements:
- Criminal data processing requires specific national law authorisation (not merely a legitimate interest)
- The national law must provide appropriate safeguards
- A comprehensive register of criminal convictions may be kept only under the control of official authority
Art. 6(1) — Lawful Basis for Background Checks Generally
| Check Type | Lawful Basis | Notes |
|---|---|---|
| Reference verification | Art. 6(1)(b) contract + Art. 6(1)(f) legitimate interest | Necessary for employment decision; limited to professional references |
| Criminal record check | Art. 6(1)(c) legal obligation or Art. 6(1)(e) public task | Only where national law mandates or authorises the check for the specific role |
| Credit check | Art. 6(1)(f) legitimate interest | Limited to roles with financial responsibility; must pass balancing test |
| Qualification verification | Art. 6(1)(b) contract | Necessary to verify contractual requirements |
| Right-to-work check | Art. 6(1)(c) legal obligation | Mandatory under national immigration law |
| Social media screening | Art. 6(1)(f) legitimate interest | Highly restricted; see detailed analysis below |
| Health screening | Art. 9(2)(b) + national law | Only where role requires specific fitness standard |
National Criminal Record Check Frameworks
United Kingdom — DBS (Disclosure and Barring Service)
Three levels of disclosure:
| Level | Content | Eligible Roles |
|---|---|---|
| Basic DBS | Unspent convictions only | Any role; self-applied by the individual |
| Standard DBS | Spent and unspent convictions, cautions, reprimands, final warnings | Roles listed in the Rehabilitation of Offenders Act 1974 (Exceptions) Order 1975 (e.g., solicitors, accountants, healthcare professionals) |
| Enhanced DBS | Standard + relevant police intelligence + barred list check where applicable | Regulated activity involving children or vulnerable adults, positions of trust in national security |
Key GDPR compliance requirements:
- The Rehabilitation of Offenders Act 1974 prohibits considering spent convictions for most employment purposes
- DBS certificates belong to the applicant, not the employer
- Employers should not retain a copy of the DBS certificate; they should record only the DBS certificate number, date of issue, and the result (clear/not clear)
- DBS Update Service allows ongoing status checks without requesting new certificates
Germany — Führungszeugnis (Certificate of Good Conduct)
- Belegart N (standard): Shows convictions with sentences exceeding 90 daily rates or 3 months imprisonment (with exceptions)
- Belegart O (extended): Includes all convictions for roles involving minors
- Employers may request a Führungszeugnis only where the role justifies it; routine requests for all positions are disproportionate
- Employers may view the certificate but should not retain a copy; they should record only the confirmation that the check was satisfactory
France — Extrait de Casier Judiciaire
- Bulletin No. 3 (most common for employment): Shows only the most serious convictions (imprisonment over 2 years without suspension)
- Employer may request Bulletin No. 3 only for specific roles justified by the nature of the activity
- For public sector roles, the administration may access Bulletin No. 2 directly
Netherlands — Verklaring Omtrent het Gedrag (VOG)
- The VOG (Certificate of Conduct) is issued by the Ministry of Justice
- The VOG states only whether the individual's judicial record contains relevant information for the specific role — it does not disclose the convictions themselves
- The employer specifies the screening profile (e.g., "persons" for working with vulnerable people, "finances" for financial roles)
Spent Convictions — Rehabilitation Principle
Most European jurisdictions implement the rehabilitation principle: after a specified period, convictions become "spent" and may no longer be considered for employment purposes. Processing spent convictions where they are protected by rehabilitation legislation violates both national law and the GDPR data minimisation principle.
| Jurisdiction | Rehabilitation Framework | Key Rule |
|---|---|---|
| UK | Rehabilitation of Offenders Act 1974 | Spent convictions may not be disclosed or considered except for excepted roles |
| Germany | BZRG (Federal Central Register Act) | Convictions removed from certificate after specified periods (5-15 years) |
| France | Art. 133-16 Code pénal | Automatic rehabilitation after specified periods |
| Netherlands | Wet justitiële en strafvorderlijke gegevens | Judicial data removed after 20 years (adults) or 5 years (minors) |
Proportionality Framework
Role-Based Necessity Assessment
Not all roles justify the same level of background checking. The proportionality principle requires that the scope of checks be tailored to the specific risks of the role.
| Role Category | Appropriate Checks | Disproportionate Checks |
|---|---|---|
| General office worker | Right-to-work, references, qualification verification | Criminal record, credit check, social media screening |
| Financial controller | Right-to-work, references, qualifications, credit check, basic criminal record (fraud offences) | Enhanced criminal record, social media screening |
| Teacher / youth worker | Right-to-work, references, qualifications, enhanced criminal record with barred list | Credit check, social media screening |
| Security guard | Right-to-work, references, SIA licence verification, standard criminal record | Enhanced criminal record (unless regulated activity), credit check |
| Warehouse operative | Right-to-work, references | Criminal record (unless handling high-value goods), credit check, qualification verification |
| Senior executive | Right-to-work, references, qualifications, directorship checks, basic criminal record | Enhanced criminal record (unless regulated role) |
Atlas Manufacturing Group Example: Atlas conducted a proportionality review of its background check programme and found that it was requesting basic DBS checks for all positions including warehouse operatives and canteen staff. Following DPO advice, Atlas implemented a tiered checking framework:
- All roles: right-to-work verification, two professional references
- Roles with financial access (finance, procurement, senior management): credit check + basic DBS
- Roles with access to R&D laboratory: basic DBS (given intellectual property value)
- Roles working with site visitors under 18 (apprenticeship supervisors): enhanced DBS with barred list
Social Media Screening
Social media screening of candidates is one of the most privacy-invasive background check activities. It may reveal:
- Political opinions (Art. 9(1))
- Religious or philosophical beliefs (Art. 9(1))
- Trade union membership (Art. 9(1))
- Health information (Art. 9(1))
- Sexual orientation (Art. 9(1))
- Racial or ethnic origin (Art. 9(1))
When social media screening may be justified:
- Public-facing roles where the candidate's public statements may directly affect the organisation's reputation
- Senior leadership roles with significant public profile
- Roles requiring security clearance where national law authorises screening
Requirements if conducted:
- Limited to publicly available information (no friend requests, no fake profiles)
- Limited to information relevant to the role
- Conducted at the latest possible stage (after shortlisting, before final offer)
- Documented with a clear record of what was reviewed and what was found
- Candidate must be informed that social media screening is part of the process
- Special category data encountered incidentally must not be recorded or used in the employment decision
Data Minimisation and Retention
Data Minimisation in Collection
- Collect only the specific check results relevant to the role, not blanket screening
- Do not retain copies of identity documents beyond the verification point (photograph the document, verify, delete the image — retain only a record that verification was completed)
- Do not retain copies of criminal record certificates — record only the certificate reference number, date, and result
- Do not collect more references than needed (two professional references is standard; personal character references are generally disproportionate)
Retention Limits
| Data Type | Retention Period | Justification |
|---|---|---|
| Right-to-work verification record | Duration of employment + 2 years | Legal obligation (Immigration Act requirements) |
| Reference responses | 6 months from hire decision | Sufficient for probation period disputes |
| Criminal record check result (reference number + outcome only) | Duration of employment | Required for ongoing regulatory compliance in regulated roles |
| Credit check result | 6 months from hire decision | No ongoing necessity after employment decision |
| Qualification verification records | Duration of employment | Ongoing professional registration may be required |
| Social media screening notes | 6 months from hire decision or immediately if candidate not hired | Minimal retention; highly sensitive |
| Unsuccessful candidate background check data | 6 months maximum | Legal claim limitation period (extended to 12 months if discrimination claim risk identified) |
Unsuccessful Candidates
Background check data for candidates who are not hired must be:
- Deleted within 6 months of the hiring decision (12 months where a discrimination claim risk is identified)
- Not retained in a general candidate database for future recruitment
- Deleted earlier if the candidate withdraws consent or requests erasure
Candidate Rights
Right to Be Informed — Art. 13
Before conducting any background check, the candidate must be informed of:
- The specific checks that will be conducted
- The lawful basis for each check
- Who will conduct the checks (third-party screening provider, if applicable)
- What data will be obtained
- How the data will be used in the employment decision
- Retention periods
- Their rights under Arts. 15-22
Right to Challenge
- Candidates must be given the opportunity to discuss and challenge adverse check results before a final employment decision is made
- If a criminal record check reveals a conviction, the candidate must be allowed to provide context (rehabilitation evidence, mitigating circumstances)
- An automatic disqualification policy (rejecting any candidate with any criminal record) is unlawful — each case must be assessed individually, considering the nature of the offence, its relevance to the role, and the time elapsed
Third-Party Screening Providers
Where background checks are conducted by a third-party provider:
- A Data Processing Agreement under Art. 28 GDPR must be in place
- The provider is a processor acting on the employer's (controller's) instructions
- The employer must specify what checks may be conducted; the provider must not conduct checks beyond the scope authorised
- The provider must delete check data after transmitting results to the employer, per the agreed retention schedule
- International transfers (common with global screening providers) must comply with Chapter V GDPR
Enforcement Precedents
| Authority | Case | Fine/Outcome | Key Issue |
|---|---|---|---|
| ICO (UK) | Experian, 2020 | Enforcement notice | Experian's employment screening services processed personal data without adequate transparency to data subjects |
| CNIL (France) | SAN-2019-007 | EUR 30,000 | Employer retained criminal record certificates in personnel files beyond the verification period |
| AEPD (Spain) | PS/00321/2020 | EUR 50,000 | Employer conducted social media screening of candidates without informing them and used special category data in hiring decisions |
| Autoriteit Persoonsgegevens (NL) | 2021 Investigation | Corrective order | Employer requested VOG for all roles without role-based necessity assessment |
| Garante (Italy) | Provvedimento 2020-0893 | Warning | Employer retained background check data for unsuccessful candidates for 5 years — excessive retention |
Integration Points
- Employment Consent Limits: Consent is not the appropriate lawful basis for most background checks (see employment-consent-limits skill).
- Employee DSAR Response: Candidates and employees may request access to background check data (see employee-dsar-response skill).
- HR System Privacy Config: Background check data storage and access must be configured with appropriate restrictions (see hr-system-privacy-config skill).
- Employee Health Data: Pre-employment health screening is governed by separate rules (see employee-health-data skill).
BYOD Privacy Policy
Overview
Bring Your Own Device (BYOD) programmes create a complex privacy intersection where corporate data security requirements meet employee personal privacy rights. When employees use personal smartphones, tablets, and laptops for work purposes, the employer gains a legitimate interest in protecting corporate data on those devices — but this interest must be balanced against the employee's right to privacy in their personal data, communications, and device usage. The GDPR, national labour laws, and ECHR Art. 8 jurisprudence impose strict limits on what employers can monitor, access, and delete on personal devices.
This skill provides a compliance framework for BYOD programmes that satisfies corporate security requirements while respecting employee privacy boundaries, including data separation architecture, MDM configuration, consent management, and data wiping limitations.
Legal Framework
GDPR Requirements
Lawful Basis for BYOD Data Processing:
- Art. 6(1)(b) contract performance: Processing corporate data on employee devices is necessary for the employment contract where the employer has authorised BYOD
- Art. 6(1)(f) legitimate interest: Protecting corporate data on personal devices — must pass the three-part balancing test
- Art. 6(1)(a) consent: May be appropriate for specific BYOD features that go beyond minimum security requirements, but only if participation in BYOD is genuinely voluntary (not a condition of employment)
Transparency — Art. 13/14: Employees must receive a comprehensive privacy notice before enrolling in the BYOD programme, detailing exactly what data the employer can and cannot access on the personal device.
Data Minimisation — Art. 5(1)(c): The employer must collect only the minimum data necessary to protect corporate information. This prohibits blanket monitoring of personal device activity.
National Labour Law Considerations
France — CNIL Guidance (2019):
- Employer access to personal devices must be strictly limited to the corporate container/partition
- Employees must be able to use personal devices for personal purposes without any corporate monitoring
- MDM must not enable access to personal photos, messages, browsing history, or app usage
Germany — BDSG Section 26 + Works Council Rights:
- BYOD constitutes technical monitoring under Section 87(1)(6) BetrVG, requiring works council co-determination
- The employer cannot compel BYOD participation; corporate-provided devices must be available as an alternative
- Private use of personal sections of the device may not be restricted
Italy — Workers' Statute Art. 4:
- Remote monitoring capabilities of MDM software require trade union agreement or labour inspectorate authorisation
- Monitoring must be limited to organisational, production, safety, and asset protection purposes
Data Separation Architecture
Principle: Corporate and Personal Data Must Be Logically Separated
The foundational privacy requirement for BYOD is that corporate data and personal data must occupy separate, isolated environments on the device. The employer has legitimate access to the corporate environment only.
Containerisation
Definition: A software container creates an encrypted, isolated space on the personal device where corporate data is stored and accessed. Corporate applications run within the container; personal applications run outside it.
Technical Implementation:
| Feature | Corporate Container | Personal Space |
|---|---|---|
| Corporate email accessed via managed email client within container | Personal email unaffected and inaccessible to employer | |
| Files | Corporate documents stored in container with encryption | Personal files unaffected and inaccessible to employer |
| Browsing | Corporate intranet accessed via managed browser | Personal browsing unaffected and not logged |
| Applications | Corporate apps installed within container (managed app catalogue) | Personal apps unaffected; employer cannot see installed personal apps |
| Clipboard | Cross-container clipboard may be disabled to prevent data leakage | Personal clipboard within personal space |
| Camera | Photos taken within corporate apps stored in container | Personal photos inaccessible to employer |
Platform Solutions:
- Microsoft Intune: App Protection Policies create a managed app layer without full device enrolment
- VMware Workspace ONE: Container-based approach with separate work profile
- Android Enterprise Work Profile: OS-level separation between work and personal profiles
- Samsung Knox: Hardware-backed separation with separate encrypted container
- Apple Managed Apps: Per-app VPN and managed open-in restrictions without full MDM
Full MDM vs. App-Level Management
| Approach | Employer Capabilities | Privacy Impact | Recommendation |
|---|---|---|---|
| Full Device MDM Enrolment | Full device inventory, location tracking, browsing history, app list, remote full wipe | Very High — employer has visibility into personal data | Not recommended for BYOD; use only for corporate-owned devices |
| Work Profile / Container | Corporate container management, selective wipe of corporate data only, no visibility into personal space | Low to Medium — personal data isolated | Recommended for BYOD |
| App-Level Management (MAM) | Per-app policies (encryption, DLP, remote app data wipe), no device-level access | Lowest — management limited to specific corporate apps | Recommended for light BYOD scenarios |
Atlas Manufacturing Group Example: Atlas implemented Microsoft Intune with App Protection Policies for its BYOD programme. Instead of full device enrolment, Atlas deploys managed versions of Outlook, Teams, OneDrive, and the corporate intranet app. These managed apps enforce encryption, prevent copy-paste of corporate data to personal apps, and can be selectively wiped without affecting personal data. Atlas explicitly chose not to require full MDM enrolment on personal devices after the DPO advised that full enrolment would grant disproportionate access to personal data.
MDM Capabilities and Privacy Boundaries
Permitted MDM Capabilities on BYOD
| Capability | Permitted | Justification |
|---|---|---|
| Enforce device passcode/biometric lock | Yes | Necessary to protect corporate data if device is lost/stolen |
| Encrypt corporate container | Yes | Necessary to protect corporate data at rest |
| Remote wipe of corporate container only | Yes | Necessary to protect corporate data on lost/stolen devices or termination |
| Push corporate apps to container | Yes | Necessary to provide access to corporate applications |
| Enforce OS version minimum | Yes, with caveat | Acceptable to ensure security patches are applied; must allow reasonable update period |
| VPN configuration for corporate traffic | Yes | Necessary to secure corporate data in transit |
| Certificate-based authentication | Yes | Necessary for secure corporate access |
Prohibited MDM Capabilities on BYOD
| Capability | Prohibited | Reason |
|---|---|---|
| Full device remote wipe | Yes | Disproportionate; destroys personal data. Only selective corporate data wipe is permitted |
| Personal app inventory | Yes | Reveals personal interests, health conditions (medical apps), political views (news apps), religion (prayer apps) — constitutes special category processing without lawful basis |
| Personal browsing history | Yes | Reveals sensitive personal information; not necessary for corporate data protection |
| Personal location tracking | Yes | Disproportionate; corporate need does not extend to tracking employee personal movements |
| Personal email access | Yes | Violates Art. 8 ECHR right to correspondence |
| Personal photo/media access | Yes | No corporate justification; disproportionate invasion of personal privacy |
| Microphone/camera remote activation | Yes | Extreme intrusion; no lawful basis |
| Personal call log access | Yes | Violates correspondence privacy |
| Keylogging on personal device | Yes | Captures both corporate and personal input; disproportionate |
Employee Consent and Enrolment
Voluntariness Requirement
BYOD participation must be genuinely voluntary. The employer must offer a corporate-provided alternative device for employees who decline BYOD:
- Valid BYOD consent: "You may choose to use your personal device for work. A corporate laptop/phone is available if you prefer. Your decision has no employment consequences."
- Invalid BYOD consent: "To access work email, you must install our MDM app on your personal phone." (No alternative offered — consent is not freely given)
BYOD Enrolment Privacy Notice
Before enrolment, employees must receive a clear privacy notice covering:
| Element | Content |
|---|---|
| What is collected | Specific data elements collected from the device (device type, OS version, corporate app data) |
| What is not collected | Explicit statement of data not collected (personal apps, photos, messages, browsing, location) |
| Who has access | Which corporate roles can access device management data |
| Remote actions | What remote actions the employer can take (selective wipe only — not full wipe) |
| Monitoring | Whether any activity monitoring occurs within the corporate container |
| Termination | What happens to corporate data on the device if employment ends |
| Withdrawal | How to un-enrol from BYOD and what happens to data |
| Retention | How long enrolment logs and device data are retained |
BYOD Agreement
The BYOD agreement is a separate document from the employment contract and must include:
- Confirmation that BYOD participation is voluntary
- Description of the separation architecture (container/work profile)
- Employer's obligations (what they will and will not access)
- Employee's obligations (passcode, OS updates, reporting lost devices)
- Remote wipe scope (corporate data only, never personal data)
- Termination procedures
- Dispute resolution mechanism
- Signature and date
Data Wiping Limitations
Selective Wipe (Permitted)
Selective wipe removes only corporate data and applications from the personal device. This is triggered by:
- Employee leaves the organisation
- Employee reports device lost or stolen
- Employee un-enrols from BYOD programme
- Device found to be non-compliant (jailbroken, below minimum OS version)
Implementation: Using containerisation, the selective wipe removes the corporate container, managed apps, and associated data. Personal data remains intact.
Full Device Wipe (Not Permitted on BYOD)
Full device wipe resets the device to factory settings, destroying all personal data. This action is:
- Disproportionate under Art. 5(1)(c) data minimisation — the corporate interest in data protection does not justify destroying personal photos, messages, contacts, and app data
- Potentially illegal under national property law — the device belongs to the employee, and destroying its contents may constitute damage to property
- A DPIA failure — any DPIA approving full wipe capability on personal devices would need to identify this risk as Very High with no adequate mitigation
Enforcement: The Autoriteit Persoonsgegevens (Netherlands) investigated an employer that remotely wiped an employee's personal phone after termination, destroying personal photos and contacts. The DPA found the action disproportionate and ordered the employer to compensate the employee and implement a selective wipe solution.
Lost or Stolen Device Procedure
- Employee reports device lost/stolen to IT helpdesk immediately
- IT initiates selective wipe of corporate container within 4 hours
- Employee is offered a temporary corporate device for continued work
- IT documents the selective wipe in the incident register
- If selective wipe cannot be confirmed (device offline), corporate access credentials are revoked
- Personal data recovery is the employee's responsibility (from personal backup services)
BYOD for Remote Workers
Remote work BYOD introduces additional considerations:
- Home network security: The employer may require VPN usage for corporate traffic but cannot monitor personal internet usage on the home network
- Shared devices: If the personal device is shared with family members, the corporate container must be protected by separate authentication
- Printing: Corporate documents printed at home raise data security concerns; the BYOD policy should address printing restrictions for sensitive documents
- Video conferencing: If employees use personal devices for video calls, camera and microphone access is controlled by the meeting application, not the MDM
Enforcement Precedents
| Authority | Case | Outcome | Key Issue |
|---|---|---|---|
| Autoriteit Persoonsgegevens (NL) | 2020 Investigation | Compensation order | Employer remotely wiped personal phone; disproportionate |
| CNIL (France) | Guidance Note 2019 | Compliance framework | Employers must limit MDM to corporate data; personal data inaccessible |
| Garante (Italy) | Provvedimento 2021-0547 | Processing restriction | MDM on BYOD devices granted employer access to personal app list — disproportionate |
| ICO (UK) | Employment Practices Code Part 3 | Guidance | MDM must be proportionate; full device wipe on personal devices is not acceptable |
| LfDI Hamburg (Germany) | 2021 Audit | Corrective measures | Employer's BYOD programme lacked works council agreement and collected personal app data |
Integration Points
- Employee Monitoring DPIA: BYOD programmes with monitoring capabilities require DPIA (see employee-monitoring-dpia skill).
- Employment Consent Limits: BYOD consent must be genuinely voluntary (see employment-consent-limits skill).
- Remote Work Monitoring: BYOD in remote work contexts requires additional safeguards (see remote-work-monitoring skill).
- HR System Privacy Config: MDM integration with HR systems must respect data separation (see hr-system-privacy-config skill).
- Employee DSAR Response: BYOD enrolment data is within scope of employee DSARs (see employee-dsar-response skill).
Employee Biometric Data
Overview
Biometric data is classified as a special category of personal data under Art. 9(1) GDPR when processed for the purpose of uniquely identifying a natural person. Processing biometric data for employee timekeeping and access control is one of the most frequently scrutinised activities by European supervisory authorities. The general prohibition on processing special category data under Art. 9(1) means that employers must identify a specific exception under Art. 9(2), satisfy the proportionality requirement, demonstrate that no less intrusive alternative exists, and implement robust safeguards. National DPAs have issued substantial fines for biometric processing that fails these tests, including the landmark Clearview AI enforcement actions and sector-specific decisions on workplace fingerprint systems.
Legal Framework
Art. 4(14) — Definition of Biometric Data
"Biometric data means personal data resulting from specific technical processing relating to the physical, physiological or behavioural characteristics of a natural person, which allow or confirm the unique identification of that natural person, such as facial images or dactyloscopic data."
Art. 9(1) — General Prohibition
"Processing of [...] biometric data for the purpose of uniquely identifying a natural person [...] shall be prohibited."
Critical distinction: Biometric data processed for purposes other than unique identification may not be classified as special category data under Art. 9(1). However, in the employment context, biometric processing for timekeeping and access control is almost always for identification purposes.
Art. 9(2) — Exceptions Applicable to Employment
| Exception | Article | Applicability to Employment Biometrics |
|---|---|---|
| Explicit consent | Art. 9(2)(a) | Rarely valid due to employment power imbalance (see employment-consent-limits skill) |
| Employment law obligation | Art. 9(2)(b) | Valid where national law specifically mandates or authorises biometric processing for employment purposes |
| Substantial public interest | Art. 9(2)(g) | Valid where national law establishes biometric access control requirements for critical infrastructure |
| Not applicable | Art. 9(2)(e) | Data "manifestly made public" — employees do not manifestly make their biometric data public |
Key National Derogations
France — Art. L.1121-1 Labour Code + CNIL Framework:
- CNIL published dedicated guidance: "Règlement type biométrie" (Deliberation No. 2019-001, 10 January 2019)
- Biometric access control is permitted for access to premises, devices, and applications where justified by the context
- Storage preference hierarchy: (1) individual device held by employee (badge), (2) centralised database with employee control, (3) centralised database without employee control (requires strongest justification)
- The employee must be informed and provided an alternative non-biometric access method
Germany — Section 26(3) BDSG:
- Processing of special category data including biometrics is permitted for employment purposes where necessary for the exercise of rights or obligations under employment law, social security law, or social protection law
- Works council co-determination rights under Section 87(1)(6) BetrVG apply
Netherlands — UAVG Art. 29:
- Biometric processing is permitted for authentication or security purposes where necessary
- The Dutch DPA (Autoriteit Persoonsgegevens) has issued specific guidance restricting biometric processing to high-security contexts
Italy — Workers' Statute Art. 4 + Garante Guidance:
- Biometric access control requires trade union agreement or labour inspectorate authorisation
- The Garante has issued multiple decisions restricting biometric timekeeping to specific sectors
Sweden — Datainspektionen Decisions:
- The Swedish DPA fined a school SEK 200,000 for using facial recognition for attendance monitoring (DI-2019-2221), setting a strong precedent that biometric monitoring for attendance is disproportionate when simpler alternatives exist
Biometric Technologies in Employment
Fingerprint Recognition
Use cases: Timekeeping (clocking in/out), physical access control, device authentication.
Technical processing: Fingerprint scanner captures an image of friction ridges → image is processed to extract minutiae points → minutiae template is compared against stored templates → match/no-match result.
Privacy considerations:
- Template storage: Store templates on individual smart cards held by the employee (less intrusive) rather than in a centralised database (more intrusive)
- Revocability: Unlike passwords, fingerprints cannot be changed if compromised
- False acceptance rate (FAR) and false rejection rate (FRR) must be documented
- Employees with skin conditions, injuries, or disabilities affecting fingerprints must have an alternative access method
Atlas Manufacturing Group Example: Atlas installed fingerprint scanners for access to its R&D laboratory where proprietary formulations are developed. The DPO approved the deployment based on Art. 9(2)(b) (German BDSG Section 26(3)) for the R&D laboratory only, with the following conditions: (1) fingerprint templates stored on employee ID badges, not in a central database, (2) alternative PIN access available for employees who object or have medical conditions, (3) DPIA completed before deployment, (4) works council consulted and agreement obtained.
Facial Recognition
Use cases: Contactless access control, time and attendance, security zones.
Technical processing: Camera captures facial image → facial geometry is measured (distance between eyes, nose shape, jawline contour) → geometry data converted to mathematical template → template compared against enrolled images.
Privacy considerations:
- Facial recognition is significantly more intrusive than fingerprint scanning because it can operate without the employee's active cooperation or awareness (passive vs. active biometric)
- Continuous facial recognition in the workplace may constitute systematic monitoring, triggering additional DPIA requirements
- Risk of function creep: facial recognition deployed for access may be expanded to emotion detection, attention monitoring, or behavioural analysis
- Bias and accuracy: Facial recognition systems have documented higher error rates for certain demographic groups, creating discrimination risk
Supervisory Authority Position: Most European DPAs take the position that facial recognition for general time and attendance purposes is disproportionate when simpler alternatives (badge, PIN, fingerprint) are available. Facial recognition may be justified only for high-security access control where contactless verification is necessary (cleanroom environments, nuclear facilities).
Iris Scanning
Use cases: High-security access control, authentication in environments where hand-based biometrics are impractical (e.g., clean environments requiring gloves).
Privacy considerations:
- Among the most accurate biometric modalities (FAR below 0.0001%)
- Less affected by environmental factors than fingerprint
- Generally limited to high-security contexts where the heightened intrusion is justified
Voice Recognition
Use cases: Telephone-based authentication, call centre agent verification, voice-activated systems.
Privacy considerations:
- Voice data may reveal health information (fatigue, intoxication, emotional state), potentially creating additional Art. 9 issues
- Voice templates are more susceptible to spoofing than other biometric modalities
- Ambient noise and voice changes (illness, ageing) affect accuracy
Behavioural Biometrics
Use cases: Keystroke dynamics, gait analysis, mouse movement patterns.
Privacy considerations:
- Often collected passively without explicit employee action
- May reveal health conditions (tremor, cognitive impairment)
- The EDPB has not yet issued specific guidance on behavioural biometrics in employment, but existing principles on proportionality and transparency apply
Necessity Test Framework
Before deploying any biometric system, the employer must demonstrate that the biometric processing is genuinely necessary and that no less intrusive alternative would achieve the same purpose.
Step 1: Define the Specific Purpose
The purpose must be concrete, documented, and limited:
- "Controlling access to the R&D laboratory containing proprietary formulations" — acceptable
- "Improving workforce management" — too vague
- "Ensuring accurate time and attendance records" — biometric processing is unlikely to be necessary for this purpose
Step 2: Evaluate Less Intrusive Alternatives
| Purpose | Biometric Solution | Less Intrusive Alternative | Necessity of Biometrics |
|---|---|---|---|
| Physical access to high-security area | Fingerprint scanner | Smart card + PIN | Biometric may be justified if tailgating/card sharing is a documented security concern |
| General building access | Facial recognition | Badge/proximity card | Biometric is disproportionate; badge provides equivalent security |
| Time and attendance | Fingerprint clock | Badge, PIN code, supervisor sign-off | Biometric is disproportionate; buddy punching can be addressed through supervision |
| Device authentication | Fingerprint/face unlock | Password, smart card | Biometric may be justified for high-sensitivity devices where password risk is documented |
| Cleanroom access | Iris scan | Badge + airlock | Biometric may be justified where contactless identification is operationally necessary |
Step 3: Proportionality Assessment
Even if biometric processing passes the necessity test, it must also be proportionate:
- Is the security risk significant enough to justify processing special category data?
- Is the biometric system targeted (limited to specific areas/roles) or blanket (all employees)?
- Are adequate safeguards in place (template storage, retention, access controls)?
- Is an alternative non-biometric method available for employees who object?
Employee Objection Procedures
Regardless of the lawful basis, employers must provide a meaningful objection mechanism:
Objection Process
-
Information at enrolment: When employees are asked to enrol biometric data, they must be informed of:
- The specific purpose of biometric processing
- The lawful basis (Art. 9(2) condition and Art. 6(1) basis)
- The availability of an alternative non-biometric method
- Their right to object or withdraw (where consent is the basis)
- Data retention period and deletion procedures
-
Alternative access method: A non-biometric alternative must be available at all times:
- PIN code + proximity badge for access control
- Manual sign-in sheet or supervisor confirmation for timekeeping
- Password or smart card for device authentication
-
No adverse consequences: Employees who use the alternative method must not suffer any disadvantage:
- No additional time required to use the alternative
- No flagging in attendance systems
- No negative note in personnel records
-
Formal objection handling: Objections must be:
- Recorded in the privacy management system
- Acknowledged within 5 working days
- Actioned immediately (switch to alternative method)
- Reviewed by the DPO
Special Circumstances
- Disability: Employees with conditions affecting biometric characteristics (skin conditions, prosthetics, facial differences) must be provided accessible alternatives without requirement to disclose their condition
- Religious objections: Some employees may object to biometric collection on religious grounds; the alternative must accommodate this
- Trade union representatives: Works council members may object on behalf of represented employees under national co-determination rights
Data Protection Safeguards
Template Storage Hierarchy (per CNIL Règlement Type Biométrie)
| Storage Method | Risk Level | When Appropriate |
|---|---|---|
| Individual device (badge, token) held by employee | Lowest | Default preferred method for all biometric deployments |
| Centralised database with employee-controlled access key | Medium | Where individual device storage is technically infeasible |
| Centralised database without employee control | Highest | Only for specific, documented security requirements with strongest justification |
Technical Safeguards
- Biometric templates must be encrypted at rest (AES-256 minimum) and in transit (TLS 1.3)
- Raw biometric data (fingerprint images, facial photographs) must not be stored; only derived templates should be retained
- Template format must be system-specific to prevent cross-system matching
- Anti-spoofing measures (liveness detection) must be implemented
- Biometric systems must be isolated from general IT networks
- Access to biometric databases must be restricted to authorised security personnel with multi-factor authentication
- Audit logs of all biometric system access must be maintained
Retention and Deletion
- Biometric templates must be deleted immediately upon termination of employment
- Biometric templates must be deleted immediately upon employee objection or consent withdrawal
- Biometric templates must be deleted when the processing purpose ceases (e.g., employee transfers to a role that does not require access to the secured area)
- Deletion must be verified and documented with certificates of destruction
Enforcement Precedents
| Authority | Case | Fine/Outcome | Key Issue |
|---|---|---|---|
| Datainspektionen (Sweden) | DI-2019-2221 | SEK 200,000 | School used facial recognition for student attendance — disproportionate, simpler alternatives available |
| CNIL (France) | Clearview AI, 2022 | EUR 20,000,000 | Biometric processing (facial recognition) without lawful basis or DPIA |
| AEPD (Spain) | PS/00218/2021 | EUR 20,000 | Employer required fingerprint for timekeeping without necessity assessment or alternative method |
| Garante (Italy) | Provvedimento 9832838, 2021 | Processing prohibited | Employer deployed facial recognition for access control without necessity analysis or Art. 9(2) condition |
| Autoriteit Persoonsgegevens (NL) | 2020 Investigation | Warning + cease order | Employer used fingerprint timekeeping; AP found it disproportionate for attendance purposes |
| ICO (UK) | Enforcement notice, 2022 | Processing ordered to cease | Employer deployed palm vein scanning for general access without DPIA |
Integration Points
- Employee Monitoring DPIA: Biometric systems must undergo DPIA (see employee-monitoring-dpia skill).
- Employment Consent Limits: Consent for biometric processing is constrained by employment power imbalance (see employment-consent-limits skill).
- HR System Privacy Config: Biometric integration with HR/timekeeping systems requires privacy configuration (see hr-system-privacy-config skill).
- Background Check Privacy: Biometric data collected for access control must be separated from background check data (see background-check-privacy skill).
Employee DSAR Response
Overview
Employee Data Subject Access Requests (DSARs) are among the most complex and resource-intensive DSARs that organisations receive. Unlike customer DSARs, which typically involve a defined set of transactional data, employee DSARs can span the entire employment lifecycle and encompass data held across dozens of systems: HR records, emails (sent, received, and about the employee), CCTV footage, access control logs, telephone recordings, performance reviews, investigation files, grievance records, occupational health reports, training records, payroll data, expense claims, monitoring data, and informal notes and communications between managers. The scope, combined with the need to redact third-party personal data and assess legal privilege, makes employee DSARs a distinct operational and legal challenge.
This skill provides a structured response process, a comprehensive data source inventory, and decision frameworks for the exemptions and redactions most commonly encountered in employee DSARs.
Art. 15 — Right of Access
What the Employee Is Entitled To
Under Art. 15(1), the employee has the right to obtain from the controller:
| Information | Detail |
|---|---|
| Confirmation of processing | Whether personal data concerning the employee is being processed |
| Access to the data | A copy of the personal data undergoing processing |
| Purposes | The purposes of the processing |
| Categories | The categories of personal data concerned |
| Recipients | Recipients or categories of recipients to whom data has been or will be disclosed |
| Retention | The envisaged period of storage, or criteria used to determine the period |
| Rights | The right to rectification, erasure, restriction, and objection |
| Source | Where data was not collected from the employee, information about the source |
| Automated decisions | The existence of automated decision-making including profiling under Art. 22, with meaningful information about the logic, significance, and envisaged consequences |
| Transfer safeguards | Where data is transferred to a third country, the appropriate safeguards under Art. 46 |
Art. 15(3) — Format
The controller shall provide a copy of the personal data undergoing processing. For any further copies requested, the controller may charge a reasonable fee based on administrative costs. Where the request is made by electronic means, the information shall be provided in a commonly used electronic form, unless otherwise requested.
Art. 15(4) — Third-Party Rights
"The right to obtain a copy referred to in paragraph 3 shall not adversely affect the rights and freedoms of others."
This provision is the legal basis for redacting third-party personal data from DSAR disclosures.
Employee DSAR Data Source Inventory
Comprehensive Search Scope
The following data sources must be searched when processing an employee DSAR:
| Data Source | System/Location | Data Types |
|---|---|---|
| HR Information System | Workday, SAP SuccessFactors, BambooHR, etc. | Personal details, employment history, contract, salary, benefits, absence records, performance ratings |
| Email system | Microsoft 365, Google Workspace | Emails sent by the employee, received by the employee, and about the employee |
| CCTV system | On-premise recording system | Video footage where the employee is identifiable |
| Access control system | Badge/proximity card system | Entry/exit logs, access attempts to restricted areas |
| Time and attendance | Timekeeping system, biometric readers | Clock-in/out records, attendance patterns |
| Payroll system | SAP, ADP, Sage | Salary history, tax records, pension contributions, benefits |
| Performance management | Workday, Lattice, Culture Amp, etc. | Performance reviews, objectives, competency assessments, calibration data, 360 feedback |
| Learning management system | Cornerstone, SAP LMS, etc. | Training records, certifications, mandatory training completion |
| Recruitment system | Greenhouse, Lever, Workable | Application data, interview notes, assessment scores (for recent hires) |
| Disciplinary and grievance files | HR case management, paper files | Investigation notes, witness statements, outcome letters |
| Occupational health records | OH provider system | Fitness-for-work reports, referral correspondence |
| Monitoring systems | DLP, web proxy, MDM | Email monitoring alerts, internet usage logs, device management data |
| Expenses system | Concur, Expensify | Expense claims, receipts, approval records |
| Informal records | Line manager email, notes, instant messages | Notes about the employee, performance observations, management discussions |
| Telephone system | Call recording platform | Recorded calls where the employee is a participant |
| IT system logs | Active Directory, service desk | Account activity, password resets, service desk tickets |
| File servers and SharePoint | Shared drives, collaboration platforms | Documents authored by or concerning the employee |
Search Strategy
Not every data source must be searched exhaustively for every DSAR. The search scope should be proportionate to:
- The request scope: If the employee has specified particular data they are seeking (e.g., "I request copies of all performance reviews from 2022-2025"), the search can be focused accordingly
- The employment context: A current employee's DSAR typically spans the entire employment period; a former employee's data may have been partially deleted under retention policies
- Reasonableness: Art. 12(5) allows refusal of requests that are "manifestly unfounded or excessive" — a request for "every email I was ever mentioned in" across a 20-year career may be excessive, but the bar for refusal is high
Response Timeline
Standard Timeline — Art. 12(3)
- One calendar month from receipt of the DSAR
- The month runs from the day after receipt (if received on 15 March, the deadline is 15 April)
- If the deadline falls on a weekend or public holiday, the deadline extends to the next working day (ICO guidance)
Extension — Art. 12(3)
- The deadline may be extended by two further months where the request is complex or the controller has received numerous requests from the same individual
- The controller must inform the employee of the extension within one month of receipt, together with the reasons for the delay
- Employee DSARs frequently justify extension due to the volume of data sources, redaction complexity, and legal privilege review
Employee DSAR Response Process
Day 1: Receipt and Acknowledgment
- Log the DSAR in the central DSAR register with a unique reference number
- Verify the employee's identity (for current employees, identity is typically confirmed through the employment relationship; for former employees, additional verification may be needed)
- Send acknowledgment confirming receipt and expected response date
- Assign a DSAR coordinator (typically from the privacy/DPO team)
Days 2-5: Scoping
- Review the request to determine scope — is the request for all data, or specific categories?
- If the request is unclear, contact the employee to clarify scope (the clarification period does not pause the clock unless the request genuinely cannot be processed without clarification — ICO guidance)
- Map the request to the data source inventory
- Identify custodians for each data source and issue collection instructions
- Assess whether an extension is likely needed; if so, notify the employee within the first month
Days 5-20: Collection
- Each data custodian searches their system(s) and exports relevant data
- Email searches: search for the employee's name and email address in mailboxes of direct managers, HR business partners, and relevant stakeholders
- CCTV: identify time periods and locations where footage may contain the employee
- Paper files: retrieve physical personnel file and any archived records
- All collected data must be logged with source, custodian, and date of extraction
Days 15-25: Review and Redaction
- Review all collected data for personal data of the requesting employee
- Identify and redact third-party personal data (see redaction framework below)
- Identify and withhold legally privileged material (see privilege framework below)
- Identify and assess any other applicable exemptions
- Compile the disclosure package
Days 25-30: Quality Check and Dispatch
- DPO or senior privacy officer reviews the disclosure package for completeness and proper redaction
- Prepare a covering letter explaining: scope of search, any exemptions applied, the employee's right to complain to the supervisory authority
- Deliver the disclosure to the employee via secure channel (encrypted email, secure portal, or registered post)
Redaction Framework
Third-Party Personal Data — Art. 15(4)
The right of access must not adversely affect the rights and freedoms of others. This requires redaction of third-party personal data unless:
- The third party has consented to disclosure, or
- It is reasonable in all circumstances to disclose without consent
Redaction decision matrix:
| Data Type | Redact? | Reasoning |
|---|---|---|
| Names of other employees mentioned in emails about the requesting employee | Generally yes, unless the third party's name is already known to the requestor (e.g., their line manager) | Balance third-party privacy against requestor's right |
| Witness statements in disciplinary investigations | Redact witness identity; disclose substance of allegations | Witness confidentiality vs. right to know allegations |
| 360 feedback with named reviewers | Redact reviewer names; disclose feedback content | Reviewers' reasonable expectation of anonymity |
| Email addresses in CC fields | Generally redact unless already known to requestor | Minimal privacy expectation but apply consistently |
| References provided by the employee's former employer | Disclose — this is the requestor's personal data | The employee has a right to see references about them |
| Performance calibration meeting notes naming other employees | Redact other employees' names and performance data | Other employees' performance data is their personal data |
Practical Redaction Technique
- Use permanent redaction (not highlight or track-changes redaction)
- Replace names with "Person A," "Person B" consistently throughout the disclosure
- Redact email addresses, phone numbers, and job titles that could identify third parties
- Do not redact the requesting employee's own data or information they already know
Legal Privilege Exemption
UK — DPA 2018, Schedule 2, Part 4, Paragraph 19
Personal data is exempt from Art. 15 to the extent that disclosure would involve disclosing information in respect of which a claim to legal professional privilege (LPP) or confidentiality of communications could be maintained in legal proceedings.
Types of Privilege
| Privilege Type | Scope | Application |
|---|---|---|
| Legal advice privilege | Confidential communications between client and lawyer for the purpose of obtaining or giving legal advice | Employment law advice about the employee's situation, HR consulting legal counsel about a grievance |
| Litigation privilege | Communications created for the dominant purpose of litigation that is in progress or reasonably anticipated | Documents prepared in anticipation of an employment tribunal claim |
| Without prejudice privilege | Communications made in a genuine attempt to settle a dispute | Settlement negotiation correspondence |
Privilege Review Process
- All documents flagged as potentially privileged must be reviewed by legal counsel
- Legal counsel determines whether privilege applies to each document
- Privileged documents are withheld and listed in a privilege log
- The covering letter to the employee must state that certain information has been withheld under the legal privilege exemption, without revealing the privileged content
- If only part of a document is privileged, the non-privileged portions must be disclosed
Other Exemptions Applicable to Employee DSARs
Ongoing Proceedings Exemption
Where disclosure would prejudice ongoing legal proceedings, disciplinary investigations, or regulatory investigations:
| Scenario | Exemption | Scope |
|---|---|---|
| Active disciplinary investigation | May withhold investigation materials that would prejudice the investigation | Temporary — must be disclosed once the investigation concludes |
| Pending employment tribunal claim | Litigation privilege applies to documents prepared for the dominant purpose of litigation | Duration of the legal proceedings |
| Regulatory investigation (e.g., FCA, HSE) | May withhold documents that would prejudice the regulatory investigation | Coordinate with the regulator |
Management Planning Exemption — UK DPA 2018, Schedule 2, Part 4, Paragraph 24
Personal data processed for management forecasting or management planning is exempt from Art. 15 to the extent that disclosure would prejudice the planning or forecasting. This may cover:
- Redundancy selection criteria before announcement
- Organisational restructuring plans naming affected employees
- Succession planning documents
Limitation: This exemption is narrow and temporary — it applies only while disclosure would genuinely prejudice the planning activity.
Negotiations Exemption — UK DPA 2018, Schedule 2, Part 4, Paragraph 25
Personal data consisting of a record of the controller's intentions in relation to negotiations with the data subject is exempt to the extent that disclosure would prejudice those negotiations. This may cover:
- Employer's settlement offer strategy
- Planned salary adjustment before communication
- Internal discussion of disciplinary sanction before outcome notification
Common Pitfalls
| Pitfall | Risk | Resolution |
|---|---|---|
| Failing to search email for "about" data | Incomplete disclosure; ICO complaint | Search line manager and HR mailboxes for the employee's name |
| Over-redaction of manager names | Excessive withholding undermines the right of access | Manager names may be disclosed where the employment relationship means the employee already knows their identity |
| Missing the one-month deadline | Regulatory complaint; enforcement action | Implement automated deadline tracking; request extension early if needed |
| Disclosing third-party special category data | Breach of Art. 9 + third-party complaint | Review all disclosures for special category data of third parties |
| Ignoring informal records | Manager personal notes are personal data and must be searched | Include managers' informal notes in the search scope |
| Treating all DSAR as routine | Employee DSARs often indicate a grievance or impending legal claim | Alert legal counsel when a DSAR is received from an employee in a dispute |
Atlas Manufacturing Group Example
Atlas received a DSAR from an employee who had recently been placed on a Performance Improvement Plan (PIP). The DSAR coordinator:
- Logged the request and acknowledged within 24 hours
- Scoped the request: employee sought "all personal data held about me"
- Mapped data sources: HR system (SAP SuccessFactors), email (Microsoft 365 — employee's mailbox, line manager's mailbox, HR BP's mailbox), performance management (SuccessFactors Performance & Goals), time and attendance (badge system), occupational health (two referrals on file), CCTV (not requested but technically in scope — employee informed that CCTV search would require specific dates/locations), and the disciplinary file containing the PIP documentation
- Extended the deadline by two months due to the volume of email data and the need for legal privilege review (the employee had instructed a solicitor, and settlement discussions were ongoing)
- Redacted: names of other employees mentioned in performance calibration, witness names from an earlier informal investigation, and third-party email addresses
- Withheld under privilege: three emails between the HR Director and employment lawyer regarding the PIP and potential tribunal claim, and the without-prejudice settlement correspondence
- Disclosed: 847 pages of material including HR records, performance reviews, PIP documentation, line manager emails about performance, training records, and absence records
- The covering letter listed exemptions applied, advised the employee of the right to complain to the ICO, and confirmed the search methodology
Enforcement Precedents
| Authority | Case | Fine/Outcome | Key Issue |
|---|---|---|---|
| ICO (UK) | Mermaids, 2023 | Enforcement notice | Failure to respond to employee DSARs within statutory timeframe |
| CNIL (France) | SAN-2022-009 | EUR 800,000 | Employer failed to provide employee with access to performance evaluation data within one month |
| AEPD (Spain) | PS/00231/2021 | EUR 70,000 | Employer refused employee DSAR claiming disproportionate effort without conducting proper search |
| Autoriteit Persoonsgegevens (NL) | 2022 Decision | EUR 525,000 | Employer provided incomplete DSAR response, omitting email data about the employee |
| Garante (Italy) | Provvedimento 2021-0234 | Corrective order | Employer over-redacted employee DSAR response, withholding non-privileged management communications |
| Datainspektionen (Sweden) | DI-2022-1456 | SEK 200,000 | Employer failed to search backup systems for former employee's DSAR |
Integration Points
- Employee Monitoring DPIA: Monitoring data is within DSAR scope (see employee-monitoring-dpia skill).
- Employee Health Data: Health data in DSARs must be handled with particular care regarding access controls (see employee-health-data skill).
- HR System Privacy Config: DSAR compliance depends on the HR system's ability to extract and export employee data (see hr-system-privacy-config skill).
- Background Check Privacy: Background check data for current/former employees is within DSAR scope (see background-check-privacy skill).
- Whistleblower Data: Whistleblower identity data has special access restrictions that may limit DSAR disclosure (see whistleblower-data skill).
Employee Health Data
Overview
Employee health data is among the most sensitive categories of personal data processed in the employment context. It falls under Art. 9(1) GDPR as "data concerning health," defined in Art. 4(15) as "personal data related to the physical or mental health of a natural person, including the provision of health care services, which reveal information about his or her health status." Employers routinely process health data for absence management, fitness-for-work assessments, occupational health surveillance, workplace adjustments for disability, and return-to-work programmes. Each of these processing activities requires identification of a valid Art. 9(2) exception, strict data minimisation, and clear boundaries between what the employer needs to know (fitness/unfitness and any required adjustments) and clinical details (diagnosis, treatment, prognosis) that must remain with the occupational health provider.
Legal Framework
Art. 9(2) Exceptions for Employee Health Data
| Exception | Article | Employment Application |
|---|---|---|
| Explicit consent | Art. 9(2)(a) | Rarely valid due to power imbalance; may apply for genuinely voluntary wellness programmes |
| Employment law obligations | Art. 9(2)(b) | Primary basis: processing necessary for carrying out obligations in employment, social security, and social protection law — to the extent authorised by national law with appropriate safeguards |
| Vital interests | Art. 9(2)(c) | Emergency situations where employee is physically incapacitated and health data is needed for emergency response |
| Health professional processing | Art. 9(2)(h) | Processing for preventive or occupational medicine, assessment of working capacity, medical diagnosis — by or under the responsibility of a health professional bound by professional secrecy |
| Public health | Art. 9(2)(i) | Public health threats (pandemic response) — must be based on national or EU law |
| Substantial public interest | Art. 9(2)(g) | Where national law establishes a substantial public interest basis, e.g., disability discrimination legislation requiring processing to assess reasonable adjustments |
Art. 9(2)(b) — Employment Obligations
This is the most commonly relied upon exception. It requires:
- National law authorisation: The processing must be authorised by EU or Member State law (not merely the employment contract)
- Appropriate safeguards: The national law must provide appropriate safeguards for the fundamental rights and interests of the data subject
- Necessity: The processing must be necessary for carrying out obligations — not merely useful
National implementations:
| Jurisdiction | Legal Basis | Scope |
|---|---|---|
| UK | DPA 2018, Schedule 1, Part 1, Para 1 | Processing necessary for employment obligations including health and safety duties, statutory sick pay, disability adjustments |
| Germany | BDSG Section 26(3) | Processing of special category data for employment purposes where necessary for exercising rights or obligations under employment or social security law |
| France | Labour Code Art. L.4624-1 et seq. | Occupational health surveillance; employer receives fitness/unfitness conclusion only, not diagnosis |
| Netherlands | UAVG Art. 30(1)(a) | Processing necessary for employment rights and obligations under law or collective agreement |
| Italy | D.Lgs. 81/2008, Art. 25 and 41 | Occupational health surveillance; competent doctor (medico competente) conducts assessments and communicates fitness judgment only |
Art. 9(2)(h) — Health Professional Exception
Processing is permitted when carried out by or under the responsibility of a health professional subject to professional secrecy. This applies to:
- Occupational health physicians conducting fitness-for-work assessments
- Company nurses providing on-site health services
- Employee Assistance Programme (EAP) counsellors
Critical limitation: The health professional may share with the employer only the conclusion (fit/unfit/fit with adjustments) and not the underlying clinical details. The diagnosis remains confidential between the health professional and the employee.
Processing Scenarios
Scenario 1: Sickness Absence Management
What the employer needs: Dates of absence, whether the absence is certified, expected return date, any workplace adjustments required.
What the employer must not receive: Diagnosis, treatment details, prognosis, medication, mental health specifics.
Data flow:
- Employee notifies employer of absence per sickness absence policy
- Employee provides a fit note (UK: Statement of Fitness for Work) or equivalent medical certificate from their GP or treating physician
- The fit note states: (a) date range, (b) whether the employee is "not fit for work" or "may be fit for work with adjustments," and (c) any recommended adjustments
- The employer records: absence dates, fit note dates, adjustment requirements
- The employer does not require or record the diagnosis (the diagnosis field on UK fit notes is visible but the employer should not record it in HR systems unless the employee voluntarily shares it for adjustment purposes)
Atlas Manufacturing Group Example: Atlas's sickness absence policy states that employees self-certify for absences up to 7 days and provide a fit note for absences exceeding 7 days. The HR system records absence dates and the fit/unfit conclusion only. The diagnosis field from fit notes is not entered into the HR system. If an employee's absence exceeds 4 weeks, a referral to occupational health is offered — the occupational health report to the employer addresses fitness, adjustments, and anticipated return date, but not clinical diagnosis.
Scenario 2: Fitness-for-Work Assessment
Trigger: Safety-critical roles (drivers, machine operators, work at height), return from long-term absence, concerns about an employee's capacity to perform their role safely.
Data flow:
- Employer refers employee to occupational health provider with a specific, written referral question (e.g., "Is the employee fit to operate forklift equipment? Are any workplace adjustments required?")
- The referral must not contain health information the employer does not already legitimately hold
- The occupational health provider examines the employee (with the employee's cooperation)
- The provider issues a report to the employer addressing the referral question only: fit/unfit/fit with adjustments
- If adjustments are recommended, they are described functionally (e.g., "reduced lifting to a maximum of 10kg for 6 weeks") without clinical explanation
- The employee receives a copy of the report and may request amendments before it is sent to the employer (Access to Medical Reports Act 1988, UK)
Art. 9(2)(h) application: The occupational health provider is a health professional bound by professional secrecy (GMC, NMC, or equivalent registration). The processing is carried out under their responsibility. They share with the employer only what is necessary for the employment decision.
Scenario 3: Occupational Health Surveillance
Scope: Statutory health surveillance required for employees exposed to occupational hazards (noise, vibration, hazardous substances, ionising radiation, asbestos, lead).
Legal basis: Art. 9(2)(b) — legal obligation under national health and safety law implementing Framework Directive 89/391/EEC.
Key obligations:
- Health surveillance must be conducted by a competent occupational health professional
- The employer receives a fitness certificate indicating whether the employee is fit for the specific exposure
- Individual health records are maintained by the occupational health provider, not the employer
- The employer receives aggregate statistical data (number of employees fit/unfit) for risk assessment purposes
- Individual results may only be shared with the employer if the employee consents or if national law specifically authorises it
Scenario 4: Disability and Reasonable Adjustments
Legal basis: Art. 9(2)(b) read with national disability discrimination law (UK: Equality Act 2010; EU: Framework Employment Directive 2000/78/EC).
Data minimisation principle: The employer needs to know:
- That the employee has a condition meeting the legal definition of disability (or may have such a condition)
- What functional limitations arise from the condition in the work context
- What adjustments would enable the employee to perform the role
The employer does not need: The specific diagnosis, medication, treatment history, or prognosis — unless the employee voluntarily shares this information to support the adjustment process.
Scenario 5: COVID-19 Testing and Vaccination (Legacy)
Context: Many organisations implemented COVID-19 testing and vaccination status checking during the pandemic. Residual data and policies may remain.
Current obligations:
- COVID testing data collected during the pandemic must be reviewed for retention compliance
- Vaccination status records must be deleted unless ongoing legal obligation requires retention (e.g., healthcare workers in specific jurisdictions)
- Test results and vaccination records are health data under Art. 9(1)
- The lawful basis for pandemic processing (typically Art. 9(2)(b) or (i)) may no longer apply as pandemic legal frameworks are revoked
Atlas Manufacturing Group Example: Atlas collected COVID test results and vaccination status during 2020-2022 under Art. 9(2)(b) (UK health and safety legal obligation) and Art. 9(2)(i) (public health). Following the revocation of mandatory testing guidance in 2022, Atlas conducted a retention review and deleted all COVID testing data and vaccination records in March 2023, retaining only aggregate statistical data for occupational health reporting.
Scenario 6: Employee Wellness Programmes
Description: Employer-offered wellness programmes including health risk assessments, fitness challenges, mental health support, and biometric screenings.
Lawful basis: Art. 9(2)(a) explicit consent — wellness programmes are the rare employment scenario where consent may be valid, because:
- Participation is genuinely voluntary
- Non-participation has no adverse employment consequences
- The programme is offered for the employee's benefit
Conditions:
- Consent must be granular (separate consent for each programme element)
- The employer must not receive individual health data; a third-party wellness provider should process the data and provide only aggregate anonymised reports to the employer
- Employees must be able to withdraw at any time
- Line managers must not know who participates
Data Minimisation Framework
What the Employer May Hold
| Data Element | Permitted | Lawful Basis |
|---|---|---|
| Absence dates | Yes | Art. 6(1)(b) contract + Art. 9(2)(b) employment obligation |
| Fit/unfit conclusion | Yes | Art. 9(2)(b) employment obligation |
| Required workplace adjustments | Yes | Art. 9(2)(b) disability legislation |
| Occupational health referral correspondence | Yes | Art. 9(2)(h) health professional |
| Fitness-for-work certificates | Yes | Art. 9(2)(b) health and safety obligation |
What the Employer Must Not Hold
| Data Element | Prohibited | Reason |
|---|---|---|
| Clinical diagnosis | Yes (unless voluntarily shared) | Not necessary for employment decisions |
| Treatment details | Yes | Not necessary; disproportionate intrusion |
| Medication information | Yes | Not necessary; may reveal conditions not relevant to work |
| Mental health counselling records | Yes | Processed under professional secrecy by health professional |
| GP/hospital records | Yes | No lawful basis for employer access |
| Genetic test results | Yes | Art. 9(1) + Art. 9(4) specific national restrictions |
Access Controls for Health Data
Need-to-Know Hierarchy
| Role | Access Level |
|---|---|
| HR Manager (employee relations) | Absence dates, fit/unfit conclusion, adjustment requirements |
| Line Manager | Absence dates and expected return date only; no health details |
| Occupational Health Provider | Full clinical information (under professional secrecy) |
| DPO | Access to processing records and policy compliance; no individual health data |
| Payroll | Absence dates for statutory sick pay calculation only |
| IT | No access to health data content; system administration only |
Technical Controls
- Health data must be stored in a separate, access-controlled area of the HR system (not in the general employee record)
- Access to health data fields requires specific role permission and is audit-logged
- Health data must be encrypted at rest (AES-256)
- Health data must not be included in general HR reporting or analytics
- Automated alerts must notify the DPO if health data access patterns indicate unusual activity
Enforcement Precedents
| Authority | Case | Fine/Outcome | Key Issue |
|---|---|---|---|
| LfDI Hamburg (Germany) | H&M, 2020 | EUR 35,258,707.95 | Employer systematically recorded employee health details from return-to-work conversations, including diagnoses and family health issues |
| CNIL (France) | SAN-2021-015 | EUR 150,000 | Employer collected excessive health data during COVID screening beyond what was legally required |
| Garante (Italy) | Provvedimento 2022-0156 | Processing restricted | Employer required employees to disclose diagnosis on sickness absence forms |
| ICO (UK) | Enforcement notice, 2021 | Processing ordered to cease | Employer shared employee mental health data with line managers without necessity or consent |
| AEPD (Spain) | PS/00142/2022 | EUR 100,000 | Employer processed employee COVID vaccination status after legal basis expired |
Integration Points
- Employment Consent Limits: Consent for health data processing is constrained in employment (see employment-consent-limits skill).
- Employee DSAR Response: Health data is frequently requested in employee DSARs (see employee-dsar-response skill).
- HR System Privacy Config: Health data requires dedicated access controls in HR systems (see hr-system-privacy-config skill).
- Employee Monitoring DPIA: Wellness programmes with health data require DPIA (see employee-monitoring-dpia skill).
- Background Check Privacy: Pre-employment health questions are restricted by disability discrimination law (see background-check-privacy skill).
Employee Monitoring DPIA
Overview
Employee monitoring represents one of the highest-risk processing activities under GDPR because it combines multiple EDPB WP248rev.01 risk factors: systematic monitoring (criterion 3), data concerning vulnerable data subjects — employees are explicitly classified as vulnerable due to the inherent power imbalance in the employment relationship (criterion 7), and often innovative technology (criterion 8). The European Data Protection Board's Guidelines 3/2019 on processing of personal data through video devices and the Article 29 Working Party's Opinion 2/2017 on data processing at work establish that any employee monitoring system requires a DPIA under Art. 35(1) GDPR before deployment.
This skill provides a structured DPIA methodology tailored specifically to employee monitoring scenarios, incorporating the proportionality framework from Barbulescu v Romania (Grand Chamber, ECHR, Application No. 61496/08, 5 September 2017) and national supervisory authority guidance from the CNIL, ICO, and German Federal Commissioner for Data Protection.
DPIA Trigger Analysis for Employee Monitoring
Why Employee Monitoring Always Requires a DPIA
Employee monitoring meets at least three of the nine EDPB WP248rev.01 criteria:
| Criterion | Applicability to Employee Monitoring |
|---|---|
| Criterion 3: Systematic monitoring | All forms of employee monitoring constitute systematic observation of individuals in the workplace |
| Criterion 7: Vulnerable data subjects | Employees are explicitly listed as vulnerable data subjects by the EDPB due to the power imbalance inherent in the employment relationship |
| Criterion 5: Large-scale processing | Enterprise monitoring systems typically process data about all employees continuously |
| Criterion 8: Innovative technology | AI-powered productivity tools, keystroke dynamics, screen capture, and behavioural analytics involve novel technologies |
| Criterion 1: Evaluation or scoring | Monitoring data used for performance evaluation constitutes scoring of individuals |
Meeting two or more criteria triggers a presumptive DPIA requirement. Employee monitoring typically meets three to five, making a DPIA mandatory in virtually all cases.
National Supervisory Authority Confirmation
- CNIL (France): Deliberation No. 2018-327 explicitly lists "systematic employee monitoring (productivity, keystroke, screen capture)" as requiring a DPIA.
- ICO (UK): Employment Practices Data Protection Code, Part 3: Monitoring at Work confirms DPIA requirement for all workplace monitoring systems.
- BfDI (Germany): Section 26 BDSG (Federal Data Protection Act) imposes additional requirements for employee data processing, reinforcing the DPIA obligation.
- AEPD (Spain): Guide on Data Protection in Labour Relations (2021) mandates DPIA for all systematic employee monitoring.
Monitoring Categories and Risk Profiles
Category 1: Video Surveillance (CCTV)
Description: Fixed or mobile camera systems recording visual images of employees in the workplace.
Applicable EDPB Guidance: Guidelines 3/2019 on processing of personal data through video devices, Section 8 (Processing in the employment context).
Legal Basis Analysis:
- Art. 6(1)(f) legitimate interest is the most common lawful basis for workplace CCTV
- Art. 6(1)(c) legal obligation where national law mandates security monitoring (e.g., financial institutions)
- Art. 6(1)(a) consent is not valid due to the employment power imbalance (WP29 Opinion 2/2017, Section 5.1)
Proportionality Requirements:
- Cameras must not be positioned in break rooms, toilets, changing areas, or trade union meeting rooms
- Recording should be limited to security-relevant areas: entrances, server rooms, cash handling areas, warehouse loading docks
- Continuous recording must be justified; motion-activated recording is less intrusive
- Retention period must not exceed 72 hours unless a specific security incident requires longer retention for investigation — CNIL recommends a maximum of 30 days
- Audio recording alongside video is prohibited in most jurisdictions absent specific statutory authorisation
Atlas Manufacturing Group Example: Atlas Manufacturing Group operates 14 CCTV cameras across its production facility. The DPIA identified that 3 cameras positioned in the staff canteen were disproportionate to the stated security purpose. The DPIA recommended removal of canteen cameras and retention reduction from 30 days to 72 hours for all remaining cameras, with exception procedures for documented security incidents.
Category 2: Email and Internet Monitoring
Description: Systems that log, scan, or analyse employee email communications and internet browsing activity.
Legal Basis Analysis:
- Art. 6(1)(f) legitimate interest for preventing data leakage, detecting security threats, and enforcing acceptable use policies
- Must be balanced against Art. 8 ECHR right to respect for private life and correspondence
Proportionality Requirements per Barbulescu v Romania (Grand Chamber): The ECHR Grand Chamber established six criteria that must be satisfied:
- Has the employee been notified in advance of the possibility that their communications may be monitored?
- What is the extent of the monitoring and the degree of intrusion into the employee's privacy?
- Does the employer have legitimate reasons to justify monitoring?
- Would monitoring with less intrusive methods be possible?
- What are the consequences of the monitoring for the employee?
- Has the employee been provided with adequate safeguards?
Risk Assessment Specific Factors:
- Content monitoring (reading actual emails) is significantly more intrusive than metadata monitoring (sender/recipient/time)
- Keyword scanning represents an intermediate level of intrusion
- Personal email accounts must never be monitored even if accessed from corporate devices
- Privileged communications (with legal counsel, trade union representatives, medical professionals) must be excluded
Category 3: GPS and Location Tracking
Description: Vehicle tracking systems, mobile device location monitoring, and geofencing for field employees.
Legal Basis Analysis:
- Art. 6(1)(f) legitimate interest for fleet management, lone worker safety, and route optimisation
- Art. 6(1)(b) performance of employment contract where location tracking is essential to the role (delivery drivers, field engineers)
Proportionality Requirements:
- Tracking must be limited to working hours; tracking outside working hours is disproportionate unless the vehicle is used exclusively for business
- Real-time tracking is more intrusive than periodic location logging and requires stronger justification
- Geofencing alerts are less intrusive than continuous tracking and should be preferred where sufficient
- Employees must be able to disable tracking when using a company vehicle for personal purposes (if permitted)
- Speed monitoring and driving behaviour analysis must be justified by specific safety concerns
Atlas Manufacturing Group Example: Atlas Manufacturing Group implemented GPS tracking on 23 delivery vehicles. The DPIA identified that real-time tracking was active 24/7 despite drivers being permitted limited personal vehicle use. The DPIA required implementation of a "personal use" toggle on the vehicle dashboard that suspends tracking and notifies fleet management that the vehicle is in personal use mode.
Category 4: Keystroke Logging and Screen Capture
Description: Software that records individual keystrokes, takes periodic or triggered screenshots, and monitors application usage.
Risk Classification: Very High — this is the most intrusive form of employee monitoring.
Legal Basis Analysis:
- Art. 6(1)(f) legitimate interest is difficult to establish because the severity of the intrusion typically outweighs any legitimate interest
- National DPAs have consistently found keystroke logging to be disproportionate for general productivity monitoring
- CNIL Decision No. MED-2019-006: Keystroke logging is justified only when investigating a specific, documented security incident and must be time-limited
Proportionality Requirements:
- Keystroke logging as a default monitoring tool is almost certainly disproportionate and will fail the DPIA
- Screen capture at fixed intervals (e.g., every 5 minutes) captures private information and personal passwords
- Application-level monitoring (which applications are open and for how long) is less intrusive than screen capture
- Any deployment must be time-limited, targeted to specific roles or individuals, and supported by a documented security justification
Supervisory Authority Enforcement:
- CNIL (France): Fined an employer EUR 20,000 for deploying keystroke logging software on employee workstations without conducting a DPIA and without adequate transparency (Decision SAN-2021-003).
- Garante (Italy): Prohibited a company from using continuous screen capture software, ruling it disproportionate to the stated productivity monitoring purpose (Provvedimento No. 9834141, 2022).
Category 5: Productivity and Behavioural Analytics
Description: Software platforms that aggregate data from multiple sources (email, calendar, application usage, badge swipes, collaboration tools) to generate productivity scores and behavioural profiles.
Risk Classification: Very High — combines evaluation/scoring with systematic monitoring and innovative technology.
Legal Basis Analysis:
- Art. 6(1)(f) legitimate interest requires a rigorous balancing test
- If productivity scores are used for employment decisions (promotion, dismissal, pay), Art. 22 automated decision-making restrictions apply
- Profiling under Art. 4(4) is triggered when monitoring data is used to evaluate work performance aspects
Proportionality Requirements:
- Aggregate/team-level analytics are less intrusive than individual-level scoring
- Employees must be informed of exactly which data sources contribute to productivity metrics
- Employees must have the right to access and challenge their productivity profiles under Art. 15 and Art. 22(3)
- Human review must be guaranteed before any adverse employment decision based on monitoring data
DPIA Methodology for Employee Monitoring
Phase 1: Preliminary Assessment (Week 1)
- Identify the monitoring system: Document the specific technology, vendor, deployment scope, and data flows.
- Classify the monitoring category: Map to one or more of the five categories above.
- Confirm DPIA obligation: Count WP248rev.01 criteria met (employee monitoring will always meet at least two).
- Assemble the DPIA team: Processing owner (typically HR Director), DPO, IT Security Officer, Legal Counsel, and employee representative or works council member per Art. 35(9).
- Notify the works council: In jurisdictions with works council requirements (Germany, France, Netherlands, Austria), the works council has co-determination rights over monitoring systems under national labour law.
Phase 2: Systematic Description (Week 2)
Document the following for each monitoring system:
| Element | Details Required |
|---|---|
| Data categories | Precisely what data is collected (e.g., email metadata, email content, URLs visited, keystrokes, screenshots, GPS coordinates, video images) |
| Data subjects | All employees, specific departments, specific roles, contractors, visitors |
| Volume | Number of employees monitored, frequency of data collection, daily data volume |
| Retention | How long monitoring data is stored, deletion procedures, archive policies |
| Access | Who can access raw monitoring data, who can access reports/dashboards, role-based access controls |
| Recipients | Internal recipients (HR, line managers, IT security), external recipients (monitoring software vendor, cloud hosting provider) |
| Transfers | Whether monitoring data is transferred outside the EEA (common with US-based SaaS monitoring tools) |
| Legal basis | Specific Art. 6(1) basis and, where applicable, Art. 9(2) condition |
Phase 3: Necessity and Proportionality Assessment (Week 3)
Apply the following proportionality test for each monitoring measure:
Step 1 — Legitimate aim: What specific, documented objective does the monitoring serve? (Security, fraud prevention, regulatory compliance, productivity management, health and safety)
Step 2 — Necessity: Is monitoring necessary to achieve the objective, or can the objective be achieved through less intrusive means?
| Monitoring Measure | Less Intrusive Alternative |
|---|---|
| Continuous video surveillance | Motion-activated recording, access control logs |
| Email content scanning | Metadata analysis, data loss prevention rules on attachments only |
| Keystroke logging | Application usage logging, output-based performance measurement |
| Real-time GPS tracking | Route completion verification, periodic check-ins |
| Continuous screen capture | Active window logging, time-tracking software with manual entries |
| Behavioural analytics scoring | Regular supervisor reviews, objective output metrics |
Step 3 — Proportionality: Even if necessary, is the monitoring proportionate to the aim? Apply the Barbulescu six-factor test.
Step 4 — Safeguards: What measures mitigate the impact on employees? (Transparency, access rights, retention limits, data minimisation, grievance procedures)
Phase 4: Risk Assessment (Week 3-4)
Assess risks specific to employee monitoring:
| Risk | Likelihood | Severity | Inherent Risk |
|---|---|---|---|
| Chilling effect on legitimate workplace communication and trade union activity | Likely | Significant | High |
| Disproportionate surveillance creating hostile work environment | Possible | Significant | High |
| Monitoring data used for discriminatory employment decisions | Possible | Maximum | High |
| Unauthorised access to monitoring data by line managers | Likely | Limited | Medium |
| Function creep: monitoring data used for purposes beyond original justification | Likely | Significant | High |
| Cross-border transfer of monitoring data to non-adequate jurisdictions | Possible | Significant | High |
| Employee inability to exercise DSAR rights over monitoring data | Possible | Significant | High |
| Capture of privileged communications (legal, medical, union) | Possible | Maximum | Very High |
Phase 5: Mitigation Measures (Week 4-5)
For each identified risk, document specific technical and organisational measures:
Technical Measures:
- Automated exclusion of privileged communications from monitoring scope (whitelisting legal counsel, medical providers, and trade union email addresses)
- Role-based access controls restricting monitoring dashboard access to authorised HR personnel only
- Automated retention enforcement with irreversible deletion at expiry
- Data minimisation: collect metadata before content; aggregate before individual-level data
- Encryption of monitoring data at rest (AES-256) and in transit (TLS 1.3)
- Audit logging of all access to monitoring data with tamper-proof logs
Organisational Measures:
- Acceptable Use Policy updated to reflect monitoring scope and provided to all employees before monitoring begins
- Privacy notice under Art. 13/14 specifically addressing monitoring, delivered before system activation
- Employee grievance procedure for challenging monitoring decisions
- Annual proportionality review to confirm monitoring remains necessary
- Training for managers on permissible use of monitoring data
- Restriction on using monitoring data as sole basis for adverse employment decisions
Phase 6: DPO Review and Works Council Consultation (Week 5-6)
- Present completed DPIA to the DPO for independent advice per Art. 35(2).
- Document DPO advice and whether it was accepted; if not, record the justification.
- Submit DPIA findings to the works council where co-determination rights apply.
- Conduct employee consultation per Art. 35(9) — this may be satisfied through works council engagement.
- Obtain senior management sign-off acknowledging residual risks.
- If residual risk remains High or Very High after mitigation, initiate Art. 36 prior consultation with the supervisory authority.
Ongoing Review Requirements
Employee monitoring DPIAs must be reviewed:
- Before any new monitoring technology is deployed
- When the monitoring scope is expanded (new departments, new data categories)
- When monitoring software is upgraded or vendor is changed
- Following any employee complaint related to monitoring
- Following any supervisory authority guidance or enforcement action relevant to employee monitoring
- At minimum annually as part of the privacy programme calendar
Enforcement Precedents
| Authority | Case | Fine/Outcome | Relevance |
|---|---|---|---|
| CNIL (France) | SAN-2021-003 | EUR 20,000 | Keystroke logging deployed without DPIA or transparency |
| Garante (Italy) | Provvedimento 9834141, 2022 | Processing prohibited | Continuous screen capture ruled disproportionate |
| AEPD (Spain) | PS/00120/2021 | EUR 60,000 | GPS tracking of employee vehicles outside working hours |
| Datainspektionen (Sweden) | DI-2020-11370 | SEK 300,000 | Facial recognition for employee time tracking without valid consent or DPIA |
| Hellenic DPA (Greece) | Decision 26/2019 | EUR 150,000 | Continuous employee CCTV monitoring without proportionality assessment |
| ICO (UK) | ENF/2021/00352 | Enforcement notice | Employer required to cease covert monitoring of employee personal devices |
Integration Points
- Employment Consent Limits: This DPIA must confirm that consent has not been relied upon as the lawful basis for monitoring (see employment-consent-limits skill).
- Workplace Email Privacy: Email monitoring components of this DPIA feed into the workplace-email-privacy skill for detailed Barbulescu compliance.
- Employee DSAR Response: Monitoring data is within scope of employee DSARs (see employee-dsar-response skill).
- Remote Work Monitoring: Remote monitoring raises additional proportionality concerns covered in the remote-work-monitoring skill.
- Art. 36 Prior Consultation: Where residual risk remains high, escalation to the supervisory authority is required.
Employment Consent Limits
Overview
Consent is rarely a valid lawful basis for processing employee personal data under GDPR. The Article 29 Working Party's Opinion 2/2017 on data processing at work (WP249) and the EDPB's subsequent guidance establish a clear presumption against reliance on consent in the employment context. The rationale is straightforward: the inherent power imbalance between employer and employee means that consent cannot be "freely given" as required by Art. 4(11) GDPR when refusal or withdrawal of consent may result in real or perceived adverse consequences for the employee.
Art. 88(1) GDPR explicitly empowers Member States to provide more specific rules for processing in the employment context, and many have enacted legislation that further restricts or modifies the role of consent in employment data processing. This skill maps the consent prohibition landscape, identifies the narrow exceptions where consent may be valid, and provides a decision framework for selecting appropriate alternative lawful bases.
The Consent Problem in Employment
Art. 4(11) — Definition of Consent
Consent must be:
- Freely given: The data subject must have a genuine and free choice and must be able to refuse or withdraw consent without detriment
- Specific: Consent must be given for one or more specific purposes
- Informed: The data subject must be informed about the controller's identity, the purpose, the data processed, the right to withdraw, and any automated decision-making
- Unambiguous indication: A clear affirmative action is required
Why Consent Fails in Employment — WP29 Opinion 2/2017
The Article 29 Working Party stated in Section 5.1 of Opinion 2/2017:
"Employees are almost never in a position to freely give, refuse, or revoke consent, given the dependency that results from the employer/employee relationship. Given the imbalance of power, employees can only give free consent in exceptional circumstances, when no consequences at all are connected to acceptance or rejection of an offer."
Key factors that negate free consent in employment:
| Factor | Explanation |
|---|---|
| Power imbalance | The employer controls terms of employment, pay, promotion, and termination |
| Perceived consequences | Even where no actual consequence follows refusal, employees reasonably fear adverse effects |
| Inability to refuse | Processing may be presented as mandatory regardless of the consent mechanism |
| Withdrawal difficulty | Employees may fear that withdrawing consent will be noted negatively |
| Granularity problems | Consent for multiple processing activities may be bundled, preventing genuine choice |
Recital 43 — Imbalance of Power
Recital 43 GDPR states: "Consent should not provide a valid legal ground for the processing of personal data in a specific case where there is a clear imbalance between the data subject and the controller." The employer-employee relationship is the paradigmatic example of this imbalance.
EDPB Confirmation
The EDPB Guidelines 05/2020 on consent under Regulation 2016/679 (Section 3.1.1) reaffirmed that consent is "highly unlikely to be a legal basis for data processing at work, unless employees can refuse without adverse consequences."
Narrow Exceptions — When Consent May Be Valid
Despite the general presumption against consent in employment, there are limited scenarios where genuine free choice may exist:
Exception 1: Purely Voluntary Benefits
Where an employer offers an optional benefit and participation is genuinely voluntary with no consequence for declining:
- Optional corporate wellness programme with health data processing
- Voluntary employee discount programme requiring sharing of personal preferences
- Optional employee photo directory
Conditions: The benefit must be genuinely optional, non-participation must have no negative consequences, and the employee must be able to withdraw at any time with immediate cessation of processing.
Atlas Manufacturing Group Example: Atlas offers an optional cycle-to-work scheme that requires processing of home address data for distance calculation. Employees who decline are not disadvantaged in any way. The DPO approved consent as the lawful basis with documented safeguards: the consent form explicitly states that non-participation has no employment consequences, and the scheme administrator is separate from line management.
Exception 2: Employee-Initiated Processing
Where the employee specifically requests processing for their own benefit:
- Employee requests a reference letter (requiring disclosure of employment data to a third party)
- Employee requests salary advance (requiring additional financial data processing)
- Employee requests flexible working arrangement (requiring processing of personal circumstances)
Exception 3: Art. 9(2)(a) Explicit Consent for Special Category Data
In limited circumstances, explicit consent under Art. 9(2)(a) may be appropriate for special category data where:
- No other Art. 9(2) condition applies
- The processing is genuinely in the employee's interest
- Refusal has absolutely no adverse consequence
- National law does not prohibit or restrict consent for this purpose
Example: An employee voluntarily discloses a disability to access workplace adjustments, and no legal obligation to process this data exists under national disability discrimination law.
Alternative Lawful Bases for Employment Processing
Art. 6(1)(b) — Performance of the Employment Contract
Scope: Processing necessary for the performance of the contract of employment.
| Processing Activity | Art. 6(1)(b) Applicability |
|---|---|
| Payroll processing | Yes — directly necessary for contract performance |
| Work scheduling and shift management | Yes — necessary for organising contractual duties |
| Performance management against contractual objectives | Yes — contractual performance evaluation |
| Absence management | Yes — managing contractual leave entitlements |
| Provision of contractual benefits (pension, insurance) | Yes — contractual obligation |
| Background checks beyond contractual requirements | No — extends beyond contract necessity |
| Post-termination data retention beyond legal requirements | No — contract has ended |
Limitation: The processing must be genuinely necessary for the contract, not merely useful or convenient. The EDPB has emphasised that "necessary" must be interpreted strictly — what is necessary is determined by the nature of the contract, not the employer's business model.
Art. 6(1)(c) — Legal Obligation
Scope: Processing required by law, including employment law, tax law, social security law, and health and safety law.
| Processing Activity | Legal Obligation |
|---|---|
| Tax withholding and reporting | National tax law (e.g., Income Tax Act, PAYE regulations) |
| Social security contributions | National social security legislation |
| Working time recording | EU Working Time Directive 2003/88/EC, as confirmed in CCOO v Deutsche Bank (CJEU, C-55/18, 2019) |
| Health and safety incident reporting | Framework Directive 89/391/EEC |
| Right-to-work verification | National immigration law |
| Gender pay gap reporting (UK) | Equality Act 2010 (Gender Pay Gap Information) Regulations 2017 |
| Whistleblower channel operation | EU Whistleblowing Directive 2019/1937 |
Art. 6(1)(f) — Legitimate Interest
Scope: Processing necessary for the legitimate interests of the employer, provided these interests are not overridden by the interests, rights, or freedoms of the employee.
Three-part legitimate interest test (Art. 6(1)(f) + WP217):
- Purpose test: Is there a legitimate interest? (Business security, fraud prevention, IT security, organisational efficiency)
- Necessity test: Is the processing necessary for that interest, or could the aim be achieved by less intrusive means?
- Balancing test: Do the employer's interests override the employees' fundamental rights? Consider:
- The nature of the data (sensitive vs. non-sensitive)
- The reasonable expectations of employees
- The impact on the employee
- The safeguards in place
| Processing Activity | Legitimate Interest Analysis |
|---|---|
| CCTV in production areas for safety | Likely valid — safety interest is strong, cameras in work areas expected |
| Email metadata monitoring for security | Likely valid if limited to metadata and employees are informed |
| Productivity scoring from monitoring data | Unlikely valid — significant impact on employee autonomy, less intrusive alternatives available |
| Social media screening of job applicants | Questionable — high intrusiveness, limited to publicly available professional profiles if at all |
Art. 6(1)(e) — Public Interest (Public Sector Employers)
For public sector employers, processing may be based on the performance of a task carried out in the public interest or in the exercise of official authority.
Art. 88 — National Derogations
Art. 88(1) permits Member States to provide more specific rules for processing in the employment context by law or collective agreements. Key national implementations:
Germany — Section 26 BDSG
- Employee data may be processed if necessary for the employment decision, performance of the employment contract, exercise or enjoyment of rights from collective agreements, or termination of employment
- Consent in the employment context is valid only if the employee derives a legal or economic advantage or the employer and employee pursue the same interest
- Consent must be in writing (unless electronic consent is appropriate due to circumstances)
- The works council (Betriebsrat) has co-determination rights under Section 87(1)(6) BetrVG for any technical monitoring of employee behaviour
France — Labour Code (Code du travail)
- Art. L.1121-1: No employer may restrict the rights of individuals or individual and collective freedoms unless justified by the nature of the task and proportionate to the aim pursued
- Art. L.1222-4: No information concerning an employee personally may be collected by a device that has not been previously brought to their attention
- CNIL Deliberation No. 2019-160: Specific requirements for employee monitoring transparency and proportionality
Netherlands — UAVG (Implementing Act GDPR)
- Art. 30 UAVG: Employee consent for processing by the employer is deemed not freely given due to the dependency relationship, unless the processing is clearly in the interest of the employee
- Works council (ondernemingsraad) has consent rights under Art. 27(1)(k) and (l) WOR for personal data processing decisions
Spain — Organic Law 3/2018 (LOPDGDD)
- Art. 87-91: Specific provisions for digital rights in the employment context
- Art. 87: Right to digital privacy at work
- Art. 89: Right to digital privacy in relation to video surveillance and sound recording at the workplace — employees must be informed of monitoring in advance
- Art. 90: Right to digital privacy in the context of geolocation at work
Italy — Workers' Statute (Legge 300/1970) and Jobs Act (D.Lgs. 151/2015)
- Art. 4: Remote monitoring of employees is permitted only for organisational, production, safety, or asset protection purposes, and only with trade union agreement or labour inspectorate authorisation
- Individual performance monitoring through remote control systems remains prohibited
Decision Framework: Selecting the Lawful Basis
START: Employer needs to process employee personal data
│
├─ Is the processing required by a specific law or regulation?
│ ├─ YES → Art. 6(1)(c) — Legal Obligation
│ └─ NO → Continue
│
├─ Is the processing necessary for performance of the employment contract?
│ ├─ YES → Art. 6(1)(b) — Contract Performance
│ │ └─ Apply strict necessity test: would the contract fail without this processing?
│ └─ NO → Continue
│
├─ Is the employer a public authority processing for a public task?
│ ├─ YES → Art. 6(1)(e) — Public Interest
│ └─ NO → Continue
│
├─ Does the employer have a legitimate interest?
│ ├─ YES → Conduct three-part LIA under Art. 6(1)(f)
│ │ ├─ Balancing test favours employer → Art. 6(1)(f) — Legitimate Interest
│ │ └─ Balancing test favours employee → Processing cannot proceed on this basis
│ └─ NO → Continue
│
├─ Is the processing genuinely voluntary with zero employment consequences?
│ ├─ YES → Art. 6(1)(a) — Consent (with documented safeguards)
│ │ └─ Document: (1) no consequence for refusal, (2) easy withdrawal, (3) separate from employment terms
│ └─ NO → Consent is not valid. Reassess whether processing is necessary at all.
│
└─ END: If no lawful basis can be identified, the processing must not proceed.
Common Compliance Failures
| Failure | Risk | Remediation |
|---|---|---|
| Using consent as default lawful basis for all employment processing | Invalid processing; enforcement action; employee claims | Audit all employment processing and reassign to appropriate lawful basis |
| Bundling consent for multiple purposes in one form | Consent is not specific per Art. 4(11) | Separate consent requests with granular choices |
| No mechanism for consent withdrawal | Consent invalid from inception | Implement withdrawal mechanism and cease processing on withdrawal |
| Presenting consent as mandatory during onboarding | Consent not freely given | Separate mandatory processing (with alternative lawful basis) from optional processing |
| Ignoring national Art. 88 derogations | Non-compliance with national law | Map all employment processing to applicable national requirements |
Enforcement Precedents
| Authority | Case | Fine/Outcome | Issue |
|---|---|---|---|
| Hellenic DPA | Decision 26/2019 | EUR 150,000 | Employer relied on consent for employee CCTV monitoring — consent invalid due to power imbalance |
| Austrian DPA | DSB-D123.270/0009-DSB/2018 | EUR 4,800,000 (reduced on appeal) | Systematic employee monitoring based on invalid consent |
| ICO (UK) | Mermaids Charity, 2023 | Enforcement notice | Processing of employee special category data without valid lawful basis |
| CNIL (France) | Deliberation SAN-2022-018 | EUR 600,000 | Employer collected excessive employee data, purporting to rely on consent |
| LfDI Baden-Württemberg | 2020 | EUR 35,258,707.95 | Employer processed employee health data based on consent that was not freely given (H&M case, contributed to by German Federal Commissioner) |
Integration Points
- Employee Monitoring DPIA: DPIAs for monitoring must confirm that consent is not relied upon (see employee-monitoring-dpia skill).
- Employee Biometric Data: Biometric processing requires Art. 9 condition — consent validity is even more constrained (see employee-biometric-data skill).
- Employee Health Data: Health data processing has specific Art. 9(2)(b) and (h) alternatives to consent (see employee-health-data skill).
- BYOD Privacy Policy: BYOD arrangements may appear to require consent but often have alternative bases (see byod-privacy-policy skill).
HR System Privacy Configuration
Overview
Enterprise HR systems are the central repository for employee personal data, processing everything from recruitment to retirement. Systems like SAP SuccessFactors, Workday, and BambooHR contain names, addresses, national identifiers, salary data, performance evaluations, absence records, health-related fitness conclusions, disciplinary records, and benefits information. The default configuration of these systems is designed for operational efficiency, not GDPR compliance. Privacy professionals must actively configure role-based access controls, data retention automation, cross-border transfer settings, audit logging, and field-level security to ensure that the HR system enforces — rather than merely documents — privacy requirements.
This skill provides configuration guidance for the three most widely deployed HR platforms, focusing on the privacy-critical settings that determine who can see what data, how long data is retained, and how data subject rights are facilitated.
Cross-Platform Privacy Requirements
Requirement 1: Role-Based Access Controls (RBAC)
Principle: No employee should have access to more HR data than is necessary for their specific role. Line managers need access to their direct reports' data; HR business partners need access to their client group; payroll needs salary and tax data; IT administrators need system access but not data content.
Standard RBAC Matrix:
| Role | Personal Details | Salary/Compensation | Performance Reviews | Absence Records | Health Data | Disciplinary Records | Recruitment Data |
|---|---|---|---|---|---|---|---|
| Employee (self) | Full | Own salary only | Own reviews | Own absence | Own OH reports | Own records | Own application |
| Line Manager | Direct reports: name, contact, role, start date | No (unless approval workflow) | Direct reports only | Direct reports: dates only (no diagnosis) | No | No (unless involved in process) | Hiring manager: interview candidates |
| HR Business Partner | Client group: full | Client group: full | Client group: full | Client group: dates + fit note status | Fit/unfit conclusion only | Client group: full | Client group: all candidates |
| Payroll | Minimal: name, employee ID, bank details, tax code | Full: all employees | No | Statutory sick pay relevant data only | No | No | No |
| Benefits Administrator | Name, employee ID, enrolment selections | Salary bands (for benefits calculation) | No | No | No | No | No |
| IT Administrator | System access management: name, employee ID, department, email | No | No | No | No | No | No |
| DPO | Audit access to all processing records; no routine access to individual data | Audit only | Audit only | Audit only | Audit only | Audit only | Audit only |
| Senior Leadership | Aggregate reports only | Aggregate/anonymised | Aggregate/anonymised | Aggregate/anonymised | No | No | No |
Requirement 2: Data Retention Automation
Principle: Data should be automatically deleted or anonymised when the retention period expires. Manual deletion is unreliable and non-compliant.
Standard Retention Schedule for HR Data:
| Data Category | Retention Trigger | Retention Period | Post-Retention Action |
|---|---|---|---|
| Recruitment — unsuccessful candidates | Application decision date | 6 months (12 months where discrimination claim risk) | Delete application, CV, interview notes, assessment scores |
| Employment contract | Termination date | 6 years post-termination (contractual claim limitation) | Delete or archive to restricted storage |
| Payroll and tax records | End of tax year | 6-7 years (varies by jurisdiction) | Delete |
| Performance reviews | Termination date | 2 years post-termination (unless ongoing dispute) | Delete |
| Absence records | End of absence year | 2 years current + 1 year archive | Delete detail; retain aggregate statistics |
| Disciplinary records | Outcome date | Per policy: warnings expire after 6-12 months; dismissal records 6 years | Delete expired warnings; retain dismissal records for limitation period |
| Health/occupational health records | Termination date or end of health surveillance | Varies: standard employment 6 years; occupational health surveillance 40 years (asbestos, radiation) | Transfer to occupational health archive |
| Training records | Termination date | 3 years post-termination | Delete |
| DSAR response records | Response date | 2 years | Delete copies; retain log entry |
Requirement 3: Cross-Border Transfer Configuration
For multinational organisations, HR systems transfer employee data across borders. Each transfer must comply with Chapter V GDPR.
Transfer scenarios requiring configuration:
| Scenario | Transfer Mechanism | System Configuration |
|---|---|---|
| EU headquarters → EU subsidiary | No restriction (intra-EEA) | Ensure data residency within EEA data centres |
| EU headquarters → UK subsidiary | UK adequacy decision (valid until June 2025, extended) | Configure UK entity as adequate recipient |
| EU headquarters → US subsidiary | EU-US Data Privacy Framework (where US entity is certified) or SCCs | Verify DPF certification; configure SCC-based transfer if not certified |
| EU entity → cloud HR provider (US-hosted) | DPF + SCCs + supplementary measures | Verify provider DPF status; enable encryption; configure data residency if available |
| EU entity → India/Philippines shared services | SCCs + TIA | Implement SCCs; conduct Transfer Impact Assessment; enable supplementary measures |
Requirement 4: Audit Logging
Mandatory audit events:
| Event | Log Content | Retention |
|---|---|---|
| Data access | Who accessed which employee's record, when, from where | 2 years |
| Data modification | Who changed what field, old value, new value, when | 2 years |
| Data export | Who exported data, scope, format, destination | 2 years |
| Report generation | Who ran what report, parameters, number of records | 2 years |
| Access permission changes | Who granted/revoked access, to whom, scope | 3 years |
| Data deletion | What was deleted, by whom, automated or manual | Permanent (audit trail survives data deletion) |
| Failed access attempts | Who attempted to access data they were not authorised to see | 1 year |
SAP SuccessFactors Configuration
Role-Based Permissions
SuccessFactors uses a Role-Based Permissions (RBP) framework:
- Permission Roles: Create roles corresponding to the RBAC matrix (Employee Self-Service, Line Manager, HR BP, Payroll, Benefits Admin, IT Admin, DPO Audit)
- Permission Groups: Define target populations for each role (e.g., Line Manager sees direct reports only; HR BP sees client group employees)
- Field-Level Permissions: For each role, configure read/write/no-access at the individual field level
- Health data fields: No access for all roles except HR BP (read-only for fit/unfit fields) and Employee (own data)
- Salary fields: No access for Line Manager, IT Admin; read-only for HR BP; read-write for Payroll
- Disciplinary fields: No access for Line Manager (unless party to process), read-only for HR BP
- IP Restriction: Restrict admin access to corporate network IP ranges
Data Retention Management (DRM)
SuccessFactors provides a Data Retention Management module:
- Purge Rules: Configure automated purge rules per data category:
- Inactive employees: purge personal data X years after termination date (configure per retention schedule)
- Recruitment: purge unsuccessful candidate data after configured period
- Performance: purge historical reviews per retention policy
- Data Purge Requests: Create purge requests targeting specific employee populations based on termination date
- Anonymisation: Where full deletion is not possible (e.g., data required for aggregate reporting), configure anonymisation to replace personal identifiers with pseudonyms
- Audit Trail: DRM maintains an audit trail of all purge activities, including what was deleted and by whom
Cross-Border Data Handling
- Data Centre Selection: SuccessFactors operates data centres in the EU (Germany, Netherlands), UK, US, and APAC. Configure the instance to use the EU data centre for EEA employee data
- Employee Central Global Assignment: For international assignments, configure transfer rules that apply appropriate safeguards when data moves between legal entities in different jurisdictions
- Integration Centre: API integrations that export employee data to third-party systems must be configured with data residency restrictions
DSAR Facilitation
- Personal Data Report: SuccessFactors provides a Personal Data Report feature that compiles all data fields containing the requesting employee's personal data
- Data Subject Request Tool: Automated workflow for receiving, tracking, and responding to DSARs with configurable deadlines and escalation
- Right to Erasure: The system supports targeted deletion of specific employee records while maintaining the audit trail
Workday Configuration
Security Groups
Workday uses a Security Group model:
- Role-Based Security Groups: Map to the RBAC matrix:
- Manager: inherits based on supervisory organisation
- HR Partner: assigned to specific supervisory organisations
- Payroll Administrator: assigned to specific companies/pay groups
- Benefits Administrator: assigned to benefit groups
- Domain Security Policies: Control access to functional areas (Compensation, Talent, Absence, Recruitment) independently
- Field-Level Security: Configure visibility and editability per field per security group
- Segment-Based Security: Restrict access to specific employee segments (e.g., executives, works council members, employees under investigation)
Business Process Security
Workday business processes (hire, promote, terminate, compensation change) have their own security:
- Initiator permissions: Who can start the process
- Approval chain: Who must approve at each step
- Notification restrictions: Who is notified (avoid sending sensitive data in email notifications)
- Document attachment security: Restrict who can view supporting documents (offer letters, performance evidence)
Data Retention
Workday provides Data Purge functionality:
- Purge Framework: Configure purge rules by data type and retention period
- Worker History Purge: Systematically remove historical data for terminated workers after the retention period
- Recruitment Purge: Automatically delete unsuccessful candidate records
- Archive and Purge: Move data to archive before permanent deletion, allowing recovery within a grace period
Cross-Border Transfers
- Tenant Configuration: Workday allows configuration of data residency at the tenant level
- Multi-Region Deployment: Large enterprises may have separate tenants for different regions
- Integration Security: Workday integrations (HCM, Payroll, Benefits) that transfer data across borders must be assessed under the TIA framework
BambooHR Configuration
Access Levels
BambooHR uses a simpler access model suitable for small to medium enterprises:
- Access Levels: Pre-defined levels (Employee Self-Service, Manager, HR Admin, Payroll Admin, No Access) plus custom levels
- Field Visibility: Each access level defines which fields are visible and editable
- Custom Access Levels: Create privacy-compliant custom levels:
- DPO Audit: Read-only access to processing records and audit logs, no access to individual employee data
- Restricted HR: Access to specific employee populations only
- Benefits Only: Access to benefits fields only
Reporting Restrictions
- Report Filters: Configure default report filters to prevent inadvertent disclosure (e.g., reports automatically exclude health data fields)
- Custom Reports: Restrict who can create custom reports (custom reports can bypass field visibility if not properly configured)
- Data Export: Restrict CSV/Excel export permissions to authorised roles only
Retention Configuration
BambooHR provides:
- Inactive Employee Management: Configure rules for archiving and deleting terminated employee records
- Document Purge: Automated deletion of uploaded documents (offer letters, ID copies, certificates) after configured retention period
- Application Tracking Purge: Delete unsuccessful candidate data after configured period
Privacy Configuration Checklist
Initial Setup
- Map organisational roles to HR system security roles/groups
- Configure field-level access for each role per RBAC matrix
- Restrict health data fields to authorised roles only
- Restrict salary/compensation fields to authorised roles
- Configure manager access to direct reports only (not entire organisation)
- Disable default admin access to personal data content
- Enable audit logging for all data access, modification, and export events
Data Retention
- Configure automated purge rules for each data category
- Set retention triggers (termination date, application decision date, etc.)
- Test purge rules in sandbox environment before production deployment
- Verify that purge rules maintain required audit trails
- Configure anonymisation for data required for aggregate reporting post-retention
Cross-Border Transfers
- Verify data centre location for EEA employee data
- Assess all integrations that transfer data outside the EEA
- Implement SCCs or verify DPF certification for US transfers
- Conduct TIA for transfers to non-adequate countries
- Configure data residency restrictions on APIs and integrations
DSAR Compliance
- Test the system's ability to export a complete copy of an individual's data
- Verify that the export includes all modules (core HR, performance, absence, recruitment)
- Configure DSAR workflow with deadline tracking and escalation
- Test rectification capability: can specific fields be corrected without system integrity issues?
- Test erasure capability: can individual records be deleted while maintaining referential integrity?
Ongoing Monitoring
- Schedule quarterly access reviews — review who has access to what
- Review audit logs monthly for anomalous access patterns
- Test retention automation quarterly — verify that purge rules execute correctly
- Review security configuration after system upgrades (upgrades may reset security settings)
- Conduct annual privacy assessment of HR system configuration
Atlas Manufacturing Group Example
Atlas Manufacturing Group uses SAP SuccessFactors for 2,400 employees across Germany, France, UK, and the Netherlands. The DPO conducted a privacy configuration audit and identified the following issues:
- Over-broad manager access: Line managers had read access to salary data for all employees in their department, not just direct reports. Remediation: Reconfigured RBP to limit manager access to direct reports only.
- No automated retention: Terminated employee data was retained indefinitely. Remediation: Implemented DRM purge rules — personal data purged 6 years after termination, with 40-year retention for occupational health records of employees in the chemical production unit.
- Cross-border transfer gap: The SuccessFactors integration with a US-based benefits provider was transferring employee data without SCCs. Remediation: Verified the benefits provider's DPF certification and implemented supplementary encryption measures.
- Missing audit logging: Data exports to Excel were not logged. Remediation: Enabled export audit logging and restricted export permissions to HR BP and Payroll roles.
- Health data visibility: The absence management module displayed the "reason for absence" field (which sometimes contained health information) to line managers. Remediation: Removed reason field visibility for managers; managers see absence dates and type (sick, annual leave, other) only.
Enforcement Precedents
| Authority | Case | Fine/Outcome | Key Issue |
|---|---|---|---|
| LfDI Hamburg (Germany) | H&M, 2020 | EUR 35,258,707.95 | HR system used to record excessive employee health and personal data; insufficient access controls |
| CNIL (France) | Dedalus Biologie, 2022 | EUR 1,500,000 | Insufficient access controls on health data in information systems |
| ICO (UK) | British Airways, 2020 | GBP 20,000,000 | Insufficient technical and organisational measures — includes system access controls |
| AEPD (Spain) | CaixaBank, 2021 | EUR 6,000,000 | Insufficient granularity in access controls for personal data systems |
| Autoriteit Persoonsgegevens (NL) | 2022 Audit | Corrective measures | HR system retained terminated employee data beyond retention period |
Integration Points
- Employee DSAR Response: HR system must support data export for DSARs (see employee-dsar-response skill).
- Employee Health Data: Health data fields require dedicated access controls (see employee-health-data skill).
- Employee Biometric Data: Biometric integration with timekeeping requires privacy configuration (see employee-biometric-data skill).
- Background Check Privacy: Background check data storage must comply with retention limits (see background-check-privacy skill).
- Remote Work Monitoring: HR system integration with monitoring tools must respect data separation (see remote-work-monitoring skill).
Remote Work Monitoring
Overview
The shift to remote and hybrid work accelerated by the COVID-19 pandemic created unprecedented employer demand for monitoring technologies designed to verify that employees working from home are productive and engaged. Software platforms offering screen capture, keystroke logging, webcam activation, mouse movement tracking, application usage monitoring, and AI-powered productivity scoring saw adoption rates increase dramatically from 2020 onwards. However, monitoring employees in their homes raises fundamentally different privacy concerns than monitoring in the workplace: the home is the employee's private domain, protected by Art. 8 ECHR and Art. 7 EU Charter of Fundamental Rights, and monitoring technologies that might be marginally acceptable in an office setting become highly intrusive when deployed in an employee's personal living space.
European supervisory authorities have responded with increasing scrutiny of remote monitoring tools. The EDPB, CNIL, ICO, and national DPAs have issued guidance establishing that the proportionality standard for home monitoring is significantly more demanding than for office monitoring, and that many commonly deployed remote monitoring technologies fail that standard.
Legal Framework
Heightened Privacy Expectations at Home
Art. 8 ECHR: The right to respect for the home is explicitly protected. Monitoring technologies that capture the home environment (webcam activation, screen capture showing personal browser tabs, microphone recording ambient conversations) constitute interference with the right to respect for private life and the home.
Art. 7 EU Charter: The right to respect for private and family life, home, and communications applies directly in the GDPR context.
EDPB position: While the EDPB has not yet issued dedicated guidelines on remote work monitoring, its existing frameworks — Guidelines 3/2019 on video devices and WP29 Opinion 2/2017 on data processing at work — establish principles that apply with even greater force in the home context:
- Employees retain privacy rights regardless of location (Opinion 2/2017, Section 5.3)
- Monitoring in the home context must satisfy a higher proportionality threshold than workplace monitoring
- The home setting means that monitoring may inadvertently capture data about family members (including children), who are not employees and whose data has no lawful basis for processing
National DPA Positions
CNIL (France):
- Questions & Answers on teleworking (2020, updated 2022): Employers must not implement continuous monitoring of employees working from home. Screen capture, keystroke logging, and webcam surveillance are disproportionate for remote work monitoring.
- Employers may use connection logs and output-based metrics but must not monitor mouse movements, screen activity, or ambient audio/video.
- Employees must not be required to keep their webcam on continuously during working hours.
ICO (UK):
- Employment Practices Code, Part 3 — Monitoring at Work: Monitoring must be proportionate. The ICO has stated that technologies deployed purely to check whether employees are at their desks are unlikely to be proportionate.
- The ICO's guidance on remote monitoring emphasises that employers should focus on output rather than surveillance.
Garante (Italy):
- Workers' Statute Art. 4 applies to remote monitoring: remote control equipment requires trade union agreement or labour inspectorate authorisation.
- The Garante has issued decisions prohibiting continuous screen monitoring of remote workers.
BfDI (Germany):
- Section 26 BDSG applies: remote monitoring is employee data processing requiring necessity and proportionality.
- Works council co-determination under Section 87(1)(6) BetrVG applies to remote monitoring tools.
- The Federal Labour Court has held that keylogger evidence is inadmissible if monitoring was disproportionate.
AEPD (Spain):
- Guide on Data Protection in Labour Relations (2021): Remote work monitoring must comply with Art. 87-90 LOPDGDD on digital rights in employment.
- Employers must inform remote workers of any monitoring tools before deployment.
- The AEPD has fined employers for GPS-tracking remote workers during non-working hours.
Monitoring Technologies and Proportionality Assessment
Category 1: Screen Capture and Recording
Description: Software that takes periodic screenshots (every 1-15 minutes) or continuously records the employee's screen.
Proportionality assessment: Disproportionate in almost all cases
| Factor | Assessment |
|---|---|
| Intrusiveness | Very High — captures personal browser tabs, private messages, health information, financial data |
| Home context | Captures personal content displayed on screen during brief personal use (checking personal email, banking) |
| Family member risk | If the device is shared or the screen is visible to family members, their data may be captured |
| Less intrusive alternatives | Application usage logging (which apps are active), output-based metrics, task completion tracking |
| Supervisory authority position | CNIL, Garante, and ICO have all stated that screen capture is disproportionate for remote work |
Verdict: Screen capture should not be deployed for general remote work monitoring. It may be justified only in narrow, time-limited circumstances for investigating specific, documented suspected misconduct.
Category 2: Webcam Monitoring
Description: Requiring employees to keep their webcam on during working hours, periodic "check-in" photos, or AI-powered presence detection.
Proportionality assessment: Disproportionate
| Factor | Assessment |
|---|---|
| Intrusiveness | Very High — captures the employee's home environment, personal appearance, family members, living conditions |
| Special category data | May reveal health conditions, religious items, disability, family composition |
| Home context | The home is the employee's private domain; requiring camera access is equivalent to allowing the employer to look into the employee's home |
| Family member data | Children, partners, and visitors may be captured without consent or lawful basis |
| Less intrusive alternatives | Login/logout times, active status indicators, scheduled check-in meetings |
Enforcement: The Dutch court in Chetu Inc v Employee (Tilburg District Court, 2022) ruled that an employee was wrongfully dismissed for refusing to keep their webcam on during working hours. The court found that requiring continuous webcam monitoring was a disproportionate invasion of privacy and the employee's refusal was justified.
Category 3: Keystroke Logging
Description: Software that records individual keystrokes typed by the employee.
Proportionality assessment: Disproportionate — prohibited for remote work
| Factor | Assessment |
|---|---|
| Intrusiveness | Maximum — captures everything typed, including personal passwords, private messages, medical searches, banking details |
| Home context | On a personal device or during personal time, captures entirely private activity |
| Less intrusive alternatives | Application usage monitoring, output metrics, supervised deadline tracking |
| Supervisory authority position | CNIL has explicitly prohibited keystroke logging for general monitoring; German Federal Labour Court has ruled keylogger evidence inadmissible |
Category 4: Mouse Movement and Activity Tracking
Description: Software that tracks mouse movements, clicks, scrolling, and keyboard activity to generate "activity scores" or "active time" metrics.
Proportionality assessment: Generally disproportionate
| Factor | Assessment |
|---|---|
| Intrusiveness | Medium-High — does not capture content but creates a continuous surveillance record |
| Accuracy | Poor correlation between mouse activity and actual productivity (thinking, reading documents, phone calls, video meetings do not involve mouse movement) |
| Employee impact | Creates anxiety and behavioural modification; employees may use "mouse jiggler" tools, indicating the metric drives evasion rather than productivity |
| Less intrusive alternatives | Task completion metrics, project management tools, regular manager check-ins |
Category 5: Application Usage Monitoring
Description: Tracking which applications are active and for how long (e.g., 3 hours in Excel, 2 hours in email, 1 hour in browser).
Proportionality assessment: May be proportionate with appropriate safeguards
| Factor | Assessment |
|---|---|
| Intrusiveness | Low-Medium — captures application names and duration, not content |
| Utility | Provides meaningful data about work patterns without capturing personal content |
| Limitations required | Must be limited to corporate applications; must not log personal application usage on personal devices |
| Transparency | Employees must be informed that application usage is logged |
Conditions for deployment: Application monitoring is one of the less intrusive remote monitoring tools and may be justified if:
- Limited to corporate-managed applications (not personal apps on BYOD)
- Aggregate reporting (team-level) preferred over individual reporting
- Not used as the sole basis for performance evaluation or disciplinary action
- Employees are informed before deployment
Category 6: AI-Powered Productivity Scoring
Description: Platforms that aggregate data from multiple sources (email, calendar, messaging, file editing, meeting participation) to generate individual "productivity scores" or "engagement scores."
Proportionality assessment: Disproportionate for individual-level scoring
| Factor | Assessment |
|---|---|
| Intrusiveness | High — aggregated surveillance creates a comprehensive behavioural profile |
| Accuracy | Algorithms may not capture the complexity of knowledge work; rewards visible activity over deep work |
| Discrimination risk | Scoring algorithms may disadvantage employees with disabilities, caring responsibilities, or different work patterns |
| Art. 22 risk | If scores influence employment decisions, Art. 22 automated decision-making restrictions apply |
| Less intrusive alternatives | Regular 1:1 meetings, objective-based performance management, peer feedback |
Microsoft Viva Insights (formerly Workplace Analytics): Microsoft explicitly states that Viva Insights should not be used for surveillance. Individual data is visible only to the individual employee; managers see only aggregate team-level data. Using administrative access to view individual productivity data may violate both Microsoft's terms and GDPR proportionality requirements.
Category 7: Login/Logout and VPN Connection Logging
Description: Recording when employees log into corporate systems, connect to VPN, and log out.
Proportionality assessment: Generally proportionate
| Factor | Assessment |
|---|---|
| Intrusiveness | Low — records connection times only, not activity |
| Utility | Confirms working hours for contractual and regulatory compliance (Working Time Directive) |
| Less intrusive alternatives | Few alternatives are less intrusive; self-reporting is the only less intrusive option |
| Transparency | Employees should be informed that login times are recorded |
This is the least intrusive form of remote monitoring and is generally acceptable provided employees are informed and the data is used only for working time management, not for micro-management.
The Output-Based Alternative
The recommended approach to remote work management is output-based rather than surveillance-based:
Output-based management framework:
| Element | Implementation |
|---|---|
| Clear objectives | Documented, measurable objectives agreed between manager and employee |
| Regular check-ins | Scheduled 1:1 meetings (daily, weekly) for progress updates |
| Task management tools | Project management platforms (Jira, Asana, Monday.com, Trello) for visibility into task progress |
| Delivery milestones | Regular deliverables with agreed deadlines |
| Team communication | Daily stand-ups, team channels, asynchronous updates |
| Trust-based culture | Management training on leading remote teams without surveillance |
Supervisory authority endorsement: Both the ICO and CNIL have explicitly recommended output-based management as the proportionate alternative to remote monitoring tools.
Implementation Requirements
Step 1: Necessity Assessment
Before deploying any remote monitoring tool, the employer must document:
- What specific, legitimate objective does the monitoring serve? (A vague desire to "ensure productivity" is insufficient.)
- Can the objective be achieved through less intrusive means (output-based management, regular check-ins)?
- Is the monitoring proportionate to the objective, considering the home context?
Step 2: DPIA
All remote monitoring systems require a DPIA because they involve:
- Systematic monitoring (WP248 criterion 3)
- Vulnerable data subjects (employees — WP248 criterion 7)
- Innovative technology (WP248 criterion 8, for AI-powered tools)
- Evaluation/scoring (WP248 criterion 1, for productivity scoring)
Step 3: Transparency
Before activating any monitoring:
- Update the privacy notice to describe the specific monitoring tools, what data is collected, and what is not collected
- Update the acceptable use policy
- Provide individual notification to each affected employee
- Allow a reasonable period (at least 2 weeks) between notification and activation
Step 4: Works Council / Employee Representatives
In jurisdictions with co-determination rights:
- Germany: Works council co-determination under Section 87(1)(6) BetrVG is mandatory
- France: CSE (Comité social et économique) consultation is required
- Netherlands: Works council consent under Art. 27(1)(l) WOR is required
- Italy: Trade union agreement or labour inspectorate authorisation under Workers' Statute Art. 4
Step 5: Safeguards
- Monitoring must be limited to working hours (no tracking outside agreed working time)
- Monitoring must be limited to corporate applications and data (no access to personal data, personal browsing, or personal communications)
- Data must be retained for the minimum period necessary (typically 30-90 days for working time logs)
- Access to monitoring data must be restricted to authorised persons (HR, not line managers)
- Employees must have the right to access their own monitoring data and challenge decisions based on it
Atlas Manufacturing Group Example
When Atlas transitioned 400 office-based employees to hybrid working (3 days office, 2 days home), the HR Director proposed deploying Time Doctor for screen capture and activity tracking. The DPO conducted a proportionality assessment and rejected the proposal:
DPO Assessment:
- Screen capture in the home environment is disproportionate — captures personal living space and potentially family members
- Activity tracking (mouse movement scoring) has poor correlation with actual productivity and creates a surveillance culture
- The legitimate objective (ensuring remote workers are productive) can be achieved through less intrusive means
Approved alternative:
- VPN connection logging to confirm working hours (proportionate, low intrusiveness)
- Microsoft Teams active/away status visible to managers (existing functionality, minimal additional intrusion)
- Output-based management: weekly task objectives set in Asana, reviewed in Friday team meetings
- Monthly 1:1 meetings between each employee and their manager to discuss workload and productivity
- Atlas did not deploy any screen capture, keystroke logging, webcam monitoring, or productivity scoring tools
Result: After 18 months of hybrid working, Atlas's employee engagement survey showed higher satisfaction and lower attrition in hybrid roles compared to office-only roles. Productivity measured by output metrics (units produced, projects completed, customer response times) remained consistent with pre-pandemic levels.
Enforcement Precedents
| Authority | Case | Fine/Outcome | Key Issue |
|---|---|---|---|
| Dutch Court (Tilburg) | Chetu Inc v Employee, 2022 | Wrongful dismissal; EUR 75,000 compensation | Employee dismissed for refusing to keep webcam on; court ruled disproportionate surveillance |
| CNIL (France) | SAN-2022-021 | EUR 32,000 | Employer deployed screen capture software on remote workers without DPIA or transparency |
| Garante (Italy) | Provvedimento 2023-0089 | Processing prohibited | Continuous screen monitoring of remote workers via corporate laptop; disproportionate |
| AEPD (Spain) | PS/00089/2022 | EUR 120,000 | Employer tracked remote workers' location via GPS outside working hours |
| BfDI (Germany) | Federal Labour Court, 2023 | Evidence excluded | Keystroke logging evidence from home-working employee excluded as disproportionate monitoring |
| ICO (UK) | Advisory, 2023 | Guidance | ICO warned that employers deploying productivity-tracking software to remote workers without necessity assessment may face enforcement |
Integration Points
- Employee Monitoring DPIA: Remote monitoring requires a DPIA with heightened proportionality assessment (see employee-monitoring-dpia skill).
- Employment Consent Limits: Consent is not valid for remote monitoring (see employment-consent-limits skill).
- BYOD Privacy Policy: Remote work on personal devices requires BYOD privacy compliance (see byod-privacy-policy skill).
- Workplace Email Privacy: Email monitoring of remote workers follows the same Barbulescu framework with additional home-context considerations (see workplace-email-privacy skill).
- HR System Privacy Config: Remote monitoring tool integration with HR systems must respect data separation (see hr-system-privacy-config skill).
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:
- Proportionality: Whistleblowing schemes should be limited to serious matters (financial misconduct, health and safety, environmental violations) — not used for routine HR complaints
- Confidentiality: The identity of the whistleblower must be kept confidential from the accused and from anyone not directly involved in the investigation
- Anonymous reports: Organisations should not actively encourage anonymous reporting, but must be prepared to handle anonymous reports when received
- Accused person's rights: The accused must be informed of the allegations as soon as doing so does not jeopardise the investigation
- 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:
- Anonymous and identified reporting both accepted
- Access restricted to two designated Ethics Officers (Chief Compliance Officer and Deputy)
- Where a report concerns the CCO, the report is automatically routed to the Chair of the Board Audit Committee
- Retention configured at 2 months post-investigation closure (aligned with CNIL requirements for the French entity — the strictest applicable standard)
- Reports involving potential criminal conduct are flagged for legal review; retention extends to the duration of any proceedings
- DPIA completed before channel launch, reviewed annually
- 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
- 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).
Workplace Email Privacy
Overview
Workplace email and internet monitoring sits at the intersection of employer legitimate interests and employee fundamental rights to privacy and correspondence under Art. 8 of the European Convention on Human Rights (ECHR), Art. 7 of the EU Charter of Fundamental Rights, and the GDPR. The landmark Grand Chamber judgment in Barbulescu v Romania (Application No. 61496/08, 5 September 2017) established a six-factor proportionality test that all European employers must satisfy before monitoring employee electronic communications. This skill provides a compliance framework for implementing email and internet monitoring that respects these legal boundaries.
Legal Framework
ECHR Art. 8 — Right to Respect for Private Life and Correspondence
Art. 8(1): "Everyone has the right to respect for his private life, family life, his home and his correspondence."
Art. 8(2): Interference is permitted only where it is "in accordance with the law," pursues a "legitimate aim," and is "necessary in a democratic society."
The ECHR has consistently held that "correspondence" includes electronic communications sent from the workplace, and that "private life" encompasses activities in the professional context (Niemietz v Germany, Application No. 13710/88, 1992).
Barbulescu v Romania — The Six-Factor Test
The Grand Chamber overturned the Chamber's earlier judgment and established that States have a positive obligation to ensure that domestic law provides adequate protection for employees' Art. 8 rights in the workplace monitoring context. The Court articulated six factors that national courts and employers must consider:
Factor 1: Prior Notification Has the employee been notified in advance of the nature and extent of monitoring? The notification must be clear, specific, and provided before monitoring begins. A general statement that "communications may be monitored" is insufficient — the employee must understand what is monitored (content, metadata, or both), when monitoring occurs, and who has access to the results.
Factor 2: Extent of Monitoring and Degree of Intrusion What is the scope of the monitoring? Content monitoring (reading the actual text of communications) is significantly more intrusive than metadata monitoring (sender, recipient, time, subject line). Real-time monitoring is more intrusive than retrospective review. Continuous monitoring is more intrusive than targeted, incident-based monitoring.
Factor 3: Legitimate Reasons Does the employer have legitimate reasons to justify the monitoring and access to the actual content of communications? Legitimate reasons include: preventing data leakage, enforcing information security policies, investigating specific misconduct, complying with regulatory obligations (financial services), and protecting trade secrets.
Factor 4: Less Intrusive Alternatives Could the employer's aims be achieved through less intrusive methods? This is the proportionality requirement — if monitoring email metadata would suffice, monitoring content is unjustified. If automated keyword scanning detects policy violations, human review of content is disproportionate.
Factor 5: Consequences for the Employee What are the consequences of the monitoring for the employee subjected to it? If monitoring data can lead to disciplinary action or dismissal, the intrusion is more severe and requires stronger justification. The Court found that in Barbulescu's case, the monitoring directly led to his dismissal, making the intrusion particularly severe.
Factor 6: Adequate Safeguards Has the employee been provided with adequate safeguards, particularly when the monitoring is intrusive? Safeguards include: limitation on who can access monitoring data, prohibition on monitoring privileged communications, right to be informed of monitoring results, right to challenge monitoring decisions, time limits on data retention, and independent oversight.
Libert v France (ECHR, Application No. 588/13, 2018)
The Court held that files clearly marked as "personal" on an employee's work computer could not be opened by the employer without the employee being present or having been duly summoned, unless there was a "serious risk" to the company.
Köpke v Germany (ECHR, Application No. 420/07, 2010)
Covert video surveillance of an employee suspected of theft was held to be justified, but only because: (a) there was a concrete suspicion, (b) the surveillance was limited in time and scope, (c) there were no less intrusive alternatives to detect the theft, and (d) the footage was used only for the specific investigation.
Monitoring Categories and Compliance Requirements
Category 1: Email Metadata Monitoring
What is captured: Sender address, recipient address(es), timestamp, subject line, attachment names and sizes, email volume per employee.
Intrusiveness level: Low to Medium.
Typical legitimate purposes: Information security (detecting unusual data transfer patterns), capacity management, regulatory compliance (financial services communications monitoring).
Compliance requirements:
- Prior notification: Inform employees that metadata is logged
- Acceptable use policy: Reference metadata logging in the AUP
- Retention: Metadata logs should be retained no longer than necessary for the stated purpose (typically 90 days for security purposes, up to 7 years for regulated financial communications)
- Access: Restrict access to IT security team; line managers should not have routine access to individual email metadata
Category 2: Email Content Monitoring
What is captured: Full text of email messages, attachments.
Intrusiveness level: High.
Typical legitimate purposes: Data loss prevention (DLP), regulatory compliance (financial services), investigation of specific alleged misconduct.
Compliance requirements:
- Prior notification: Explicit, detailed notification that email content may be reviewed under specified circumstances
- Proportionality: Content monitoring must be targeted, not blanket. Automated DLP scanning with keyword triggers is more proportionate than human review of all emails
- Exclusions: Legal professional privilege communications, trade union correspondence, medical correspondence must be excluded from monitoring scope
- Access: Content review limited to authorised personnel (DLP team, compliance officer) — never to direct line managers
- Retention: Content captured by DLP alerts should be reviewed promptly and deleted if no policy violation is confirmed
Atlas Manufacturing Group Example: Atlas implemented Microsoft Purview DLP policies scanning outbound emails for patterns matching customer credit card numbers, employee national insurance numbers, and files classified as "Confidential." The DLP system flags matching emails for review by the Information Security Manager. The employee's line manager is not notified unless a confirmed policy violation is escalated through HR. Atlas's acceptable use policy explicitly states that outbound emails are subject to automated content scanning for data protection purposes.
Category 3: Internet Browsing Monitoring
What is captured: URLs visited, browsing duration, bandwidth consumption, download activity.
Intrusiveness level: Medium to High (browsing history can reveal sensitive information about health, political views, religion, sexual orientation).
Typical legitimate purposes: IT security (preventing malware), bandwidth management, enforcement of acceptable use policies, preventing access to illegal content.
Compliance requirements:
- Prior notification: Inform employees that browsing activity is logged
- Filtering vs. monitoring: URL blocking (preventing access to categories of sites) is less intrusive than logging (recording which sites were visited). Prefer blocking over logging where the purpose is prevention
- Sensitive categories: Browsing data may inadvertently reveal special category data (health websites, political forums, religious sites). Processing this data without an Art. 9(2) condition is unlawful
- Personal browsing: If the employer permits limited personal use of internet during breaks, monitoring of personal browsing during permitted times requires specific justification
- Aggregation: Aggregate browsing statistics (bandwidth usage per department) are less intrusive than individual browsing logs
Category 4: Instant Messaging and Collaboration Tools
What is captured: Messages in corporate chat platforms (Microsoft Teams, Slack, Google Chat), file sharing activity, meeting participation.
Intrusiveness level: Medium to High — messaging platforms create an expectation of conversational informality that increases the privacy expectation.
Compliance requirements:
- Prior notification: Employees must know that messages on corporate platforms are logged and may be reviewed
- Retention: Corporate messaging platforms retain messages by default. Retention policies must be configured to delete messages after a defined period (typically 1-3 years, or as required by industry regulation)
- eDiscovery: Distinguish between routine monitoring and litigation/regulatory hold requirements. eDiscovery searches should be authorised by legal counsel and limited in scope
- Personal communications: Employees may use corporate messaging for personal conversations. Monitoring policies must address this reality
Acceptable Use Policy Requirements
An Acceptable Use Policy (AUP) is the foundational document for workplace communications monitoring compliance. The AUP serves as the transparency mechanism under Art. 13/14 GDPR and satisfies Barbulescu Factor 1 (prior notification).
Mandatory AUP Elements
| Element | Content Required |
|---|---|
| Scope | Which systems are covered (email, internet, messaging, phone, BYOD) |
| Permitted personal use | Whether personal use is permitted, and under what conditions |
| Monitoring disclosure | What monitoring takes place (metadata, content, both), when, and by whom |
| Monitoring purpose | The specific purposes for which monitoring is conducted |
| Content exclusions | Categories excluded from monitoring (privileged communications, medical, union) |
| Access controls | Who has access to monitoring data |
| Consequences | What may happen as a result of policy violation or monitoring detection |
| Employee rights | Right to access monitoring data about them, right to challenge, grievance procedure |
| Retention | How long monitoring data is retained |
| Review | When the policy is reviewed and how employees are notified of changes |
Legitimate Expectation of Privacy
The AUP directly shapes whether employees have a "legitimate expectation of privacy" in their workplace communications:
- AUP prohibits all personal use and warns of monitoring: Employee's privacy expectation is reduced but not eliminated. The ECHR in Barbulescu held that even where personal use was prohibited, the employee retained some privacy expectation because the employer had not clearly communicated the nature and extent of monitoring.
- AUP permits personal use with monitoring warning: Employee has a moderate privacy expectation for personal communications. Monitoring of personal communications during permitted personal use time requires strong justification.
- No AUP exists: Employee has a strong legitimate expectation of privacy. Any monitoring is likely to be disproportionate.
Implementation Workflow
Step 1: Audit Current Monitoring Capabilities
Document all existing email and internet monitoring systems, including:
- Email archiving and DLP tools
- Web proxy and content filtering systems
- Messaging platform retention settings
- Network traffic analysis tools
Step 2: Conduct Proportionality Assessment
For each monitoring capability, apply the Barbulescu six-factor test:
For each monitoring system:
1. Is prior notification provided? [Yes/No → Remediate]
2. What is the extent of monitoring? [Metadata only / Content / Both]
3. What is the legitimate reason? [Document specific purpose]
4. Is there a less intrusive alternative? [If yes → Switch to less intrusive method]
5. What are the consequences for employees? [Document potential adverse effects]
6. What safeguards are in place? [Document access controls, retention, exclusions]
If any factor is not satisfied → Monitoring must be modified or ceased.
Step 3: Draft or Update Acceptable Use Policy
Ensure the AUP covers all mandatory elements listed above. The AUP must be:
- Written in clear, plain language
- Provided to all employees before monitoring begins
- Acknowledged in writing by each employee
- Refreshed when monitoring capabilities change
Step 4: Configure Technical Controls
- Implement whitelists excluding privileged communications from monitoring scope
- Configure DLP rules to minimise false positives and reduce unnecessary content review
- Set retention periods on email archives and messaging platforms
- Implement role-based access controls on monitoring dashboards
- Enable audit logging for all access to monitoring data
Step 5: Train Relevant Staff
- Train IT security staff on permissible scope of monitoring reviews
- Train HR staff on the boundary between monitoring data and disciplinary evidence
- Train line managers that they do not have direct access to email monitoring data
Step 6: Conduct DPIA
Email and internet monitoring requires a DPIA (see employee-monitoring-dpia skill). Document the proportionality assessment and residual risks.
Covert Monitoring — Exceptional Circumstances Only
Covert monitoring (monitoring without employee knowledge) is permissible only in narrowly defined circumstances:
Requirements for lawful covert monitoring (based on Köpke v Germany and ICO guidance):
- There must be reasonable suspicion of criminal activity or serious misconduct
- The investigation must be authorised at a senior level (typically CEO or Board level)
- The monitoring must be proportionate to the suspected misconduct
- The monitoring must be time-limited (typically no more than a few weeks)
- The scope must be narrowly defined (targeted employee, specific communication channels)
- Less intrusive investigation methods must have been considered and found insufficient
- The investigation must be documented in advance
- Legal counsel must be consulted before covert monitoring begins
- The results of the monitoring must be disclosed to the employee within a reasonable time, even if no misconduct is found
Atlas Manufacturing Group Example: Atlas suspected an employee of leaking confidential product designs to a competitor. After consulting legal counsel and the DPO, the CEO authorised targeted monitoring of the suspect's outbound email attachments for a period of 14 days. The monitoring was limited to attachments containing CAD file formats and was not extended to personal communications. The investigation was documented in advance with a written justification and time limit.
Enforcement Precedents
| Authority | Case | Outcome | Key Issue |
|---|---|---|---|
| ECHR Grand Chamber | Barbulescu v Romania (2017) | Violation of Art. 8 | Employer monitored employee Yahoo Messenger without adequate prior notification or safeguards |
| ECHR | Libert v France (2018) | No violation | Employer accessed non-personal files on work computer; personal files were identifiably marked and protected |
| CNIL (France) | SAN-2020-012 | EUR 75,000 | Employer conducted systematic monitoring of employee internet browsing without transparency or proportionality assessment |
| Garante (Italy) | Provvedimento 303/2016 | Processing prohibited | Employer used software to monitor all employee emails in real time without DPIA or adequate transparency |
| AEPD (Spain) | PS/00050/2020 | EUR 40,000 | Employer read employee personal emails sent from corporate account without prior notification |
| BfDI (Germany) | Federal Labour Court BAG 2-AZR-681/16 (2017) | Dismissal overturned | Employer used keystroke logger evidence; court ruled monitoring was disproportionate and evidence inadmissible |
Integration Points
- Employee Monitoring DPIA: Email monitoring must be assessed through the DPIA process (see employee-monitoring-dpia skill).
- Employment Consent Limits: Consent is not a valid lawful basis for email monitoring (see employment-consent-limits skill).
- Remote Work Monitoring: Email monitoring of remote workers raises additional proportionality concerns (see remote-work-monitoring skill).
- Employee DSAR Response: Employees have the right to access monitoring data about their own communications (see employee-dsar-response skill).
- BYOD Privacy Policy: Monitoring of email on personal devices requires specific BYOD policy provisions (see byod-privacy-policy skill).
Sponsors
Details
- Marketplace
- mukul975/Privacy-Data-Protection-Skills
- Source
- plugins/employee-privacy-skills
- Author
- Mahipal
- Category
- Compliance
- License
- Apache-2.0
- Keywords
- employee-privacy, monitoring, byod, workplace
More from mukul975/Privacy-Data-Protection-Skills
All 21- gdpr-compliance-skillsv1.0.0
- global-privacy-regulations-skillsv1.0.0
- healthcare-privacy-skillsv1.0.0
- privacy-audit-skillsv1.0.0
- privacy-by-design-skillsv1.0.0
- privacy-engineering-skillsv1.0.0
- privacy-impact-assessment-skillsv1.0.0
- privacy-skills-completev1.0.0
- records-of-processing-skillsv1.0.0
- us-state-privacy-skillsv1.0.0
- vendor-privacy-management-skillsv1.0.0
- ai-privacy-governance-skillsv1.0.0
- children-privacy-skillsv1.0.0
- consent-management-skillsv1.0.0
- cookie-consent-skillsv1.0.0
- cross-border-transfers-skillsv1.0.0
- data-breach-response-skillsv1.0.0
- data-classification-skillsv1.0.0
- data-retention-skillsv1.0.0
- data-subject-rights-skillsv1.0.0