Privacyboard

Employee data and the GDPR: what HR tools must cover

By the Privacyboard teamPublished 16 November 20269 min read
Short answer

Employers process employee data mainly because a contract or a law requires it, or on legitimate interests, rarely on consent, which regulators say is unlikely to be free at work. Each HR tool needs a legal basis per purpose, a processor agreement, a retention period, a line in the register and a notice to staff. Monitoring and profiling tools often need a DPIA.

The GDPR applies to staff data exactly as it applies to customer data, with one big difference. Because employees depend on their employer, consent is almost never a valid legal basis at work. Most HR processing rests on the employment contract, a legal obligation (tax, social security, labour law) or legitimate interests.

In practice, every HR tool you use (HR software, payroll, recruiting, time tracking, chat, monitoring) needs the same five things: a legal basis for each purpose, a contract with the vendor, a retention period, a line in your record of processing activities, and clear information for staff. This guide walks through each one, as of 16 November 2026. It is general information, not legal advice.

#Why is employee data different from customer data?

The rules are the same GDPR, but three things change the picture.

  • The power imbalance. An employee who says no to the employer may fear consequences. This shapes which legal basis you can use.
  • The volume and sensitivity. HR files hold bank details, ID documents, sick notes, sometimes trade union membership or disability information. Health data and union membership are special categories under Article 9.
  • National labour law. Article 88 lets EU countries adopt "more specific rules" for the employment context. Many have, so the GDPR is the floor and national law often adds to it.

On that last point, the EU Court of Justice set a limit in case C-34/21 (30 March 2023). A national rule only counts as a "more specific rule" under Article 88 if it adds real employment-specific content and safeguards, with attention to transparency, transfers within a group and monitoring systems. A rule that simply repeats the GDPR's general conditions should not be applied; processing then falls back on the GDPR itself.

Rarely. The European Data Protection Board's guidelines on consent (05/2020) say it is "unlikely" that an employee can refuse an employer's request "without experiencing the fear or real risk" of consequences. The Board concludes that for most processing at work, the legal basis "cannot and should not be" employee consent.

Consent is not banned outright. The same guidelines accept it "in exceptional circumstances, when it will have no adverse consequences at all" whether the person agrees or not. Their example: a film crew shoots in part of an office, and staff who do not want to appear are moved to an equivalent desk elsewhere, with no penalty. An optional photo in the staff directory is the same kind of case.

The older Article 29 Working Party Opinion 2/2017 on data processing at work, adopted on 8 June 2017, says the same and is still the reference on monitoring.

Pick the basis per purpose, not per tool. One HR platform can run several purposes on different bases.

HR purposeTypical toolUsual legal basis (Article 6)Watch out for
Contract, pay, holidaysHR software, payrollContract (6(1)(b))Bank details, access limited to HR and payroll
Tax and social security filingsPayrollLegal obligation (6(1)(c))Fixed national retention periods
Sick leave, occupational healthHR software, health providerLegal obligation or contract, plus an Article 9 condition (9(2)(b) employment law, 9(2)(h) occupational medicine)Store diagnoses separately, if at all
RecruitmentApplicant tracking systemSteps before a contract (6(1)(b)) or legitimate interestsTalent pools, automated screening
Performance reviewsHR softwareContract or legitimate interestsAccess by managers only for their team
IT security, access badgesBadge system, endpoint toolsLegitimate interestsProportionality, short log retention
Monitoring of activity or locationTime tracking, GPS, monitoring softwareLegitimate interests (or a legal obligation for working time)DPIA, prior information, national limits
Staff directory photoIntranet, chatConsent can work if truly optionalEasy to withdraw with no consequence

When you use legitimate interests, run and write down the three-part test: purpose, necessity, balance. For monitoring, the balance is often where the case fails.

#What must an HR tool cover?

Whatever the tool, check these points before you roll it out, and again at renewal.

#A processor agreement

An HR software vendor or payroll provider that handles staff data on your behalf is a processor. Article 28 requires a written contract (a DPA) covering instructions, confidentiality, security, sub-processors, help with rights requests, deletion at the end and audits. Most vendors publish one; read it and keep the signed copy.

#Where the data goes

Check where the vendor stores and accesses the data, and its sub-processors. Transfers outside the EEA (or the UK) need a transfer tool, such as an adequacy decision, the EU-US Data Privacy Framework for certified US companies, or standard contractual clauses.

#Access control and logs

Staff files should be visible only to the people who need them. The CNIL's guidance for employers says HR staff see personnel files, managers see what their role needs (such as evaluations and pay of their team), and actions on the data by authorised people should be logged.

#Retention periods you can set

Good HR tools let you set deletion or archiving rules per type of record. Without that, data piles up for years after people leave.

#Export for access requests

Employees can ask for a copy of their data. The tool should let you find and export everything about one person quickly.

#How long can you keep employee data?

The GDPR gives no fixed periods. National law does, and some regulators publish reference tables. In France, the CNIL published a reference on HR retention periods on 2 April 2026. Some of its periods, as of 16 November 2026:

Record (France, CNIL HR reference)Period
Rejected candidatesDuring the recruitment, then archived up to 5 years after the post is filled (evidence for discrimination claims)
Payslip data6 rolling years after the payroll declaration (DSN); payslips kept 5 years after they are sent to the worker
Single staff register5 years after the employee leaves
Working time recordsUntil the payslip for the period, then 1 year in archive (3 years for fixed-days arrangements)
Access badge logs3 months (6 months for biometric access logs)
Video surveillance1 month, unless a disciplinary or criminal procedure needs the images

In the UK, PAYE payroll records must be kept for 3 years from the end of the tax year they relate to, and the ICO published final guidance on keeping employment records on 5 February 2025. For other countries and record types, see our retention guide.

#When does HR processing need a DPIA?

A DPIA is required when processing is likely to result in a high risk (Article 35). Employees count as potentially vulnerable people because of the power imbalance, which is one of the nine criteria regulators use. Two criteria together usually mean a DPIA.

Regulators' lists make this concrete:

  • The CNIL's HR reference lists HR profiling and constant monitoring of employees' activity as processing that needs a DPIA.
  • Germany's DPIA list names large-scale processing of data on employees' conduct, including data loss prevention tools that build employee profiles, geolocation of employees and central recording of internet and email traffic at work.
  • The ICO's monitoring checklist asks employers to consider a DPIA for any monitoring, to carry one out for biometric monitoring, and to consider asking workers or their representatives for their views.

If a DPIA shows a high risk you cannot reduce, you must consult the regulator before starting.

#What do you have to tell employees?

Articles 13 and 14 apply to staff as to anyone else. An employee privacy notice covers who the controller is, each purpose and legal basis, whether giving the data is required, who receives it (payroll provider, pension fund, authorities), transfers, retention periods, rights and the right to complain to the regulator.

The CNIL puts the rule for monitoring simply: no information about an employee may be collected by a system they were not told about beforehand. Many countries also require informing or consulting staff representatives before monitoring tools go live. The ICO's checklist expects workers to be told the nature, extent and reasons for any monitoring.

#How do employee access requests work?

Employees have the same rights as customers, and access requests often arrive during a dispute. The ICO is clear that you "cannot simply refuse" a request because the worker is in a grievance or tribunal process. You answer within one month, extendable by two months for complex or multiple requests.

If staff use business chat tools such as Microsoft Teams or WhatsApp for work, the ICO says you must search them for personal information in scope. Note that the ICO marks its employment guidance as under review after the Data (Use and Access) Act, so check the current version.

#Checklist: employee data and HR tools

  • List every tool that holds staff or candidate data: HR, payroll, recruiting, time tracking, chat, email, badges, monitoring.
  • Record each HR purpose in your register with its legal basis, data, recipients and retention.
  • Remove consent as a basis wherever refusing would have consequences.
  • Add an Article 9 condition for health, union or other special category data.
  • Sign a DPA with each HR vendor and check its sub-processors and transfers.
  • Limit access: HR, payroll and each manager for their own team only.
  • Set retention rules in each tool, including for rejected candidates and leavers.
  • Run a DPIA before any monitoring, profiling, geolocation or biometric system.
  • Inform or consult staff representatives where national law requires it.
  • Publish an employee privacy notice and a separate one for candidates.
  • Prepare to answer employee access requests within one month, including chat tools.

Privacyboard's processing register includes ready-made activities for employee records and HR administration, payroll and recruitment that you can adapt.

#FAQ

Usually not. The EDPB says consent at work is unlikely to be freely given because of the imbalance of power. Use contract, legal obligation or legitimate interests, and keep consent for truly optional things, such as a directory photo, where refusing has no consequence.

#Is my HR software provider a processor or a controller?

Usually a processor, because it handles staff data on your instructions. You then need an Article 28 contract with it. Some services, such as a pension fund or an occupational health provider acting under its own legal duties, may be controllers in their own right.

#Do I need a DPIA to monitor employees?

Often yes. Employees are treated as potentially vulnerable people, and systematic monitoring is another of the criteria regulators use. The CNIL lists constant monitoring of employees' activity as needing a DPIA, and Germany's list covers geolocation and central recording of internet and email traffic.

#Do job candidates have GDPR rights too?

Yes. Candidates must be told how their data is used, and they can request access or erasure. Set a retention period for rejected applications, and ask before keeping them in a talent pool if your national rules require it.

#Do national laws change the rules for employee data?

Yes. Article 88 allows more specific national rules for employment, and many countries have them, along with labour law rules on monitoring and staff representatives. Since the CJEU's C-34/21 ruling, a national rule that only repeats the GDPR does not count as such a rule.

#Sources

Privacyboard is a guidance tool, not legal advice. This article explains general rules in plain language and was accurate on the date above; laws and guidance change. For an unusual situation, ask a qualified professional. Spotted a mistake? Write to hello@privacyboard.io.

Keep reading