BlogHugoUpdated

HR data breaches and the GDPR: 8 concrete examples

HR data breaches and the GDPR: 8 concrete examples

A compliance officer reviews GDPR documents at their desk

Article 4(12) of the GDPR defines a personal data breach as any security incident that leads to the destruction, loss, alteration or unauthorized disclosure of personal data. In HR, the most frequent breaches involve particularly sensitive information: payslips, social security numbers, health data or disciplinary files. Regulators actively pursue these failures, and GDPR fines can reach 4% of worldwide turnover. The examples below come from France, where the CNIL is the data protection authority; the same mistakes happen in any company with employees in the EU. Understanding them is the first step toward a stronger compliance posture.

1. A poorly secured server migration

Technicians prepare hardware for a server migration

Migrating servers without first deleting the data on the old ones is a breach that can be penalized. A recent case reported in the French press shows that a colleague's accidental access to payslips exposed during a poorly secured migration (in French) can be enough to constitute a breach and end up in court. This kind of incident happens when IT teams move data without checking that the old servers are properly wiped and disconnected.

Leaving HR data on obsolete servers increases the attack surface and exposes the company to litigation years after the fact. Payslips, contracts and reviews stay accessible long after they stop being used if no purge procedure is in place.

Pro tip: Before any migration, draw up a complete inventory of the HR data stored and confirm permanent deletion on every source medium, with a report signed by the CISO.

2. Unauthorized access to employee files

Unauthorized access happens when a manager or colleague opens HR data without the right to do so. It is common in companies where access rights are not segmented by role. Managing HR access (in French) requires sensitive data to be isolated so that managers without authorization cannot reach it.

The risk grows when access logs are not kept or reviewed. Without traceability, the company can neither detect the incident nor show good faith to the regulator.

3. Payslips sent to the wrong person

Sending a payslip by unsecured email to the wrong recipient is one of the most common HR breaches. This kind of human error directly exposes the employee's social security number, gross salary and bank details. Sending by unsecured email (in French) is a documented risk: password protection alone is often not enough.

A compliant digital vault is the recommended way to deliver electronic payslips. With this setup, only the employee concerned can access their document, through personal authentication.

4. Keeping former employees' data too long

Keeping former employees' data indefinitely, or for too long, is the most frequent GDPR compliance trap. Retention periods (in French) are regulated: the CNIL recommends, for example, not keeping badge data beyond three months, and French employers must keep a copy of payslips for five years (article L3243-4 of the Labor Code). Other data, such as unsuccessful applications or performance reviews, must be erased once the applicable legal periods have run. The reference framework is summarized in our guide to the CNIL and EDPB recommendations.

Many companies keep every HR file by default, with no automated purge procedure. That inertia is an ongoing breach, exposed to any inspection.

Processing HR data without a valid legal basis is a direct breach of the GDPR. Employee consent (in French) is often found invalid by regulators, because the imbalance between employer and employee undermines it. The right legal basis in HR is generally performance of the employment contract or compliance with a legal obligation.

This trap mainly concerns employee monitoring, internal investigations and the collection of health data. Basing that processing on consent exposes the company to immediate reclassification during an inspection.

6. Failing to act once a vulnerability is found

Failing to take corrective action after a vulnerability is detected significantly increases potential penalties. Not responding to a known flaw (in French) is in itself a failure of the security obligation (article 32), separate from the original breach: a company that detects an incident and does nothing makes its position worse.

The GDPR requires notifying the regulator within 72 hours when the breach poses a risk to individuals (article 33). If the risk is high, which is often the case for social security numbers or health data, the employees concerned must also be informed directly (article 34).

7. Exposing sensitive data: health, disability, social security numbers

Health and disability data belong to the special categories of article 9 of the GDPR. The French social security number is not one of them, but its use is strictly regulated under French law. Exposing this data generally poses a high risk: on top of notifying the regulator, the employees concerned must then be informed directly (article 34).

This data appears frequently in HR files: sick leave, disability declarations, insurance certificates. Processing it requires a specific legal basis and reinforced security measures, such as GDPR pseudonymization.

8. What GDPR penalties do companies face?

Administrative fines can reach 20 million euros or 4% of worldwide annual turnover. Beyond the amount, regulators can issue formal notices and make their penalties public. HR non-compliance is not a theoretical risk.

Beyond fines, companies face employment litigation. An employee whose data was exposed can go to an employment tribunal to obtain compensation. Reputational risk completes the picture: a public penalty does lasting damage to the employer brand.


Key takeaways

HR data breaches expose companies to fines of up to 4% of worldwide turnover and to employee litigation, which makes GDPR compliance non-negotiable for any HR department.

PointDetails
Server migrationPermanently delete HR data before any migration to prevent residual access.
Retention periodsBadge data: three months recommended by the CNIL; copies of payslips: five years for French employers.
Legal basis in HRUse performance of the contract or a legal obligation, never employee consent.
72-hour notificationNotify the regulator within 72 hours if the breach poses a risk, and inform employees directly if that risk is high.
PseudonymizationPseudonymize sensitive data to reduce the impact of any leak.

For the full method for protecting employee files: Pseudonymizing employee files: the complete guide for HR.

Safe-doc for HR teams

The Safe-doc home page

Several of the breaches described above share a common cause: an HR document circulating in clear text. Safe-doc acts on that specific point, and only on that one. Before a payslip, a sick note or a disciplinary file goes to an AI tool, it is pseudonymized, and the real data only comes back on the user's own computer.

The document is not kept after processing. That does not replace the access controls, the retention policy or the notification procedure described in this article. See the page for HR teams.

Frequently asked questions

What is an HR data breach under the GDPR?

An HR data breach is any security incident that exposes employees' personal data, whether accidental or malicious, as defined in article 4(12) of the GDPR.

Which HR data is most exposed to breaches?

Payslips, social security numbers, health data, disciplinary files and badge logs are the HR data most often involved in breaches.

How long do you have to notify the regulator of an HR breach?

The employer must notify the regulator within 72 hours of becoming aware of the breach, if it poses a risk to individuals. If the risk is high, the employees concerned must also be informed directly.

What penalties does a company face for a GDPR breach in HR?

Fines can reach 20 million euros or 4% of worldwide annual turnover. Employment litigation and reputational damage come on top.

Pseudonymizing documents before any AI processing is the recommended method. It reduces the exposure of personal data without changing the HR team's tools or work habits.

Further reading