HR holds some of the most sensitive personal data in any organisation, and much of it is processed by people and systems that were never designed with data protection in mind. Health and sickness records, disciplinary files, diversity data, background checks, pay and bank details all sit in HR systems, shared drives and managers' inboxes, often for far longer than anyone can justify. This guide covers the lawful handling of HR records under UK GDPR and the Data Protection Act 2018, with notes on EU GDPR and California: choosing a lawful basis, special category and criminal offence data, retention schedules, staff subject access requests, and who should be able to see what in the HR system. It is written for HR, privacy and security practitioners. Workplace monitoring is covered separately in the Employee Monitoring and Privacy Guide.
Key takeaways
- Consent is rarely the right basis for HR data. The ICO points out that employers usually hold a position of power, so consent is often not freely given. Contract, legal obligation and legitimate interests carry most HR processing.
- Special category data needs two legal hooks, and usually a policy document. A lawful basis plus an Article 9 condition, and for the UK employment condition a Schedule 1 DPA 2018 condition and an appropriate policy document.
- Retention is set by purpose and by other laws. Data protection law sets no fixed periods; tax, employment and health and safety law set some minimums. A written retention schedule with automated review is the control that works.
- Staff access requests are the hardest test of your records. One month to respond, a reasonable and proportionate search, and exemptions for management information, negotiations and confidential references that must be documented.
- HR system access is a privacy control. Managers should see what they need for their team and nothing more; field-level and role-based restrictions do more for HR privacy than any policy statement.
Scope: what counts as HR data, and which rules apply
The ICO's employment records guidance uses "worker" broadly: employees, contractors, volunteers, and gig and platform workers. HR data runs from recruitment through to records kept after someone leaves. Treat each of these as a separate processing activity in your record of processing; see the Data Mapping and ROPA Guide. Under GDPR Article 30(5) the exemption for organisations with fewer than 250 staff does not apply where processing is not occasional or involves special category or criminal offence data, which covers routine HR processing.
| Jurisdiction | Main rules for HR data | Points to note |
|---|---|---|
| United Kingdom | UK GDPR and the Data Protection Act 2018, Schedule 1 conditions; ICO employment practices guidance | The ICO marks its employment guidance as under review following the Data (Use and Access) Act 2025, so check for updates |
| European Union | EU GDPR; Article 88 allows member states to set more specific rules for employment by law or collective agreement | National rules vary; Germany is the best-known example. See Germany BDSG and TDDDG |
| California | CCPA as amended by CPRA | The California Privacy Protection Agency confirms that employees and job applicants have the same rights as other consumers; the employment data exemption ended on 31 December 2022. See CCPA and CPRA |
Article 88 is worth reading even outside the EU. It lists the stages of employment it applies to (recruitment, performance of the contract, management and organisation of work, equality and diversity, health and safety, protection of property, benefits, and termination) and requires safeguards for workers' dignity and fundamental rights, with particular attention to transparency, transfers within a corporate group and monitoring systems. It is a useful checklist of where HR processing happens.
Choosing a lawful basis for each HR record
The ICO guidance on collecting and keeping employment records sets out how each lawful basis applies in employment. Map every HR record type to one basis and write it into the privacy notice.
| Lawful basis | Typical HR use | Limits the ICO highlights |
|---|---|---|
| Contract | Pay, contractual benefits, job details, working pattern | Rely on it once an offer has been accepted; it does not cover duties under employment law |
| Legal obligation | Sharing pay and address details with HMRC, statutory pay, right to work records | Covers duties under statute or common law, not contractual duties |
| Legitimate interests | Holding references, internal directories, workforce planning, investigations | Needs a documented legitimate interests assessment weighing the worker's interests |
| Consent | Genuinely optional schemes, such as a voluntary cycle-to-work scheme | Often not freely given in employment; withdrawal must be as easy as giving it; not appropriate if you would process anyway |
| Vital interests | Emergency medical information | Very narrow, generally life or death situations |
Be honest about the basis. A common error is asking staff to "consent" to processing that is actually required by contract or law. If the worker cannot realistically refuse, consent is the wrong basis, and relying on it creates a withdrawal right you cannot honour.
Special category and criminal offence data
HR processes special category data constantly: sickness and occupational health records, disability adjustments, trade union membership for subscriptions, ethnicity and religion for equality monitoring, and biometrics for access systems. Each use needs a lawful basis and an Article 9 condition.
- Employment, social security and social protection (Article 9(2)(b)): applies where processing is necessary to meet obligations or exercise rights under employment, social security or social protection law, authorised by law or a collective agreement with suitable safeguards. The ICO says you must identify the specific legal obligation, the processing must be necessary and proportionate, and purely contractual duties do not qualify. In the UK this also needs the associated Part 1 Schedule 1 condition and an appropriate policy document.
- Substantial public interest: for example equality of opportunity or treatment monitoring, which needs a Part 2 Schedule 1 condition and in most cases an appropriate policy document.
- Legal claims: establishing, exercising or defending legal claims, such as retaining records relevant to an employment tribunal.
- Criminal offence data: background and criminal record checks need official authority or one of the Schedule 1 conditions, decided and documented before collection. The ICO gives the example that a spent conviction under the Rehabilitation of Offenders Act should be erased once no longer needed.
Appropriate policy document: keep one document that lists each Schedule 1 condition relied on, the procedures for complying with the data protection principles, and the retention and erasure policy for that data. The ICO publishes a template. Equality monitoring data should be anonymised where possible. Where you introduce new high-risk HR processing, such as biometric time recording or analytics on sickness absence, run a DPIA first; see the DPIA Guide.
Retention schedules for HR records
Article 5(1)(e) GDPR limits storage to as long as necessary for the purpose. The ICO is explicit that data protection law sets no fixed periods, that other laws may require certain records for set periods, and that keeping records to meet those laws is not keeping them too long. It recommends a retention schedule listing record types, purposes and periods, with automated review or deletion flags.
| Record type | Driver for the period | How to set it |
|---|---|---|
| Payroll and PAYE records (UK) | HMRC requires PAYE records for 3 years from the end of the tax year they relate to | Statutory minimum; minimum wage and statutory leave records follow separate rules |
| Right to work check copies (UK) | Home Office employer's guide (current edition dated 1 October 2026) | Follow the period stated in the current guide |
| Recruitment records for unsuccessful candidates | Defending discrimination claims | Set by limitation period for claims plus a short margin; record your reasoning |
| Sickness, occupational health and adjustment records | Employment law duties and potential claims | Keep separate from the main file, restrict access, review at leaving |
| Disciplinary and grievance records | Policy-defined warning periods and potential claims | Expired warnings should stop being used; decide whether the record is deleted or retained for claims |
| Criminal record check results | Schedule 1 condition and need | Record the outcome, not the certificate content, unless you have a specific reason |
| Leaver records | References, pensions, claims | Reduce to a core record after the claims window; delete the rest |
Put the schedule into your HR system as rules, not a PDF. Most platforms support retention or purge policies by record type and event (leaving date, end of recruitment campaign). See the Data Retention and Disposal Policy Template for the policy wording and the Data Retention and Secure Deletion Guide for deletion methods. Do not forget copies outside the HR system: exports to spreadsheets, interview notes in email, and investigation files on shared drives.
Staff subject access requests
Requests from current and former staff are often linked to a grievance, dismissal or tribunal claim. They are larger and more contested than customer requests because the data is spread across email, chat, HR systems and managers' notes. The general process is in the DSAR Guide; the employment-specific points are below.
- Time limit: respond without undue delay and within one month (GDPR Article 12(3)). You can extend by up to two further months if the request is complex or there are several requests, telling the requester why within the first month.
- Clarification: you may ask for clarification only where reasonably needed; the clock pauses until they reply, but you cannot force them to narrow the request.
- Search: the ICO guidance, updated in July 2026 for the Data (Use and Access) Act 2025, says you must make a reasonable and proportionate search. Document what you searched (mailboxes, chat, HR system, case files) and why.
- Other people's information: colleagues, witnesses and managers appear throughout HR records. You do not have to disclose another person's information unless they consent or it is reasonable to disclose without consent; follow the ICO's three-step approach and record the decision.
- Exemptions employers use: management information (such as restructuring plans), records of negotiations with the requester, confidential references, and legal professional privilege. Apply them item by item and document your reasons.
- Manifestly unfounded or excessive: the threshold is high. A request made to support a tribunal claim is not unfounded on that basis alone.
- Enforced access: requiring a candidate or worker to make a SAR to obtain records about them, for example a criminal record, is a criminal offence in the UK.
Choosing how to run staff requests
| Approach | Suits | Trade-offs |
|---|---|---|
| HR runs requests with privacy oversight | Small and mid-sized organisations with few requests | HR knows the records but may be conflicted in a dispute; privacy should review redactions |
| Privacy team runs all requests, HR supplies records | Larger organisations, regulated sectors | More independent; needs reliable search tooling and HR cooperation |
| Legal leads where litigation is live | Requests linked to tribunal or settlement | Privilege review is easier; must still meet the one-month deadline |
HR system access: who sees what
The ICO guidance expects access limited to authorised staff such as HR, managers given only the information they need, and stronger controls for special category and criminal offence data. In a modern HR platform those expectations translate into concrete settings. Security requirements for choosing a platform are in Security Requirements for Selecting an HR System; the operating model is below.
| Role | Should see | Should not see by default |
|---|---|---|
| Employee (self-service) | Own profile, pay slips, absence, training | Investigation notes or management information about themselves before decisions are made |
| Line manager | Team members' job, absence dates, performance records | Diagnosis or occupational health detail, diversity data, bank details, salary of peers outside the team |
| HR business partner | Full employment record for assigned population | Records outside assigned population; equality data in identifiable form |
| Occupational health | Health records and adjustment recommendations | Disciplinary files unless relevant |
| Payroll | Pay, tax, bank details, statutory deductions | Performance, disciplinary and health detail beyond what pay calculation needs |
| HR system administrators and integrations | Configuration and the fields each integration needs | Standing access to full records; use time-bound elevated access |
- Use the security model, not trust: configure role-based security groups scoped to organisation units and field-level restrictions for sensitive fields.
- Separate the sensitive file: keep occupational health and investigation records in a restricted area or system with its own access list.
- Review access on movement: when a manager changes team, their access to former reports should end automatically, driven by HR events; see the Identity Lifecycle Event Design Guide.
- Control exports: restrict bulk report and export rights to named roles and log every export.
Where identity fits
HR platforms are the source of truth for joiner, mover and leaver events and connect to payroll, benefits, identity governance and many SaaS tools through API keys, OAuth clients and service accounts. Those integration identities often have read access to the whole workforce record, which makes them the largest single privacy exposure in the HR estate. Scope each integration to the fields it needs, rotate its credentials, and review it like a privileged account. Hard-coded credentials in code repositories have exposed staff records before: in the United Nations breach, researchers used exposed Git credentials to reach more than 100,000 UNEP staff records. See the Joiner-Mover-Leaver Guide for the identity lifecycle.
Implementing an HR data privacy programme
- Inventory (weeks 1 to 4): list every HR record type, system, export and shared location, including managers' local copies. Record purpose, lawful basis and Article 9 or Schedule 1 condition for each.
- Fix the bases (weeks 4 to 8): remove consent where another basis applies, complete legitimate interests assessments, and write or update the appropriate policy document.
- Update privacy information: tell workers the purposes, lawful bases, conditions, retention, sharing and their rights, at collection and when new uses begin, as the ICO expects.
- Build the retention schedule: agree periods with HR and legal, then configure purge rules in the HR system. Test on a copy or a small population first, check that statutory records survive, and keep a restorable backup during the first purge run as the rollback route.
- Tighten access: redesign roles using the table above, pilot with one business unit, then roll out. Remove standing administrator access.
- Prepare for staff requests: agree the operating model, search sources and redaction rules, and run a mock request against a volunteer's records.
- Monitor and review annually: report the measures below to the data protection lead and re-run the inventory each year.
Small versus large organisations
- Small employers: often one HR person and a payroll bureau. Focus on a short retention schedule, a single restricted folder for sensitive records, and a processor contract with the bureau.
- Large employers: multiple jurisdictions, works councils and group transfers. Article 88 national rules and collective agreements may add requirements, and intra-group sharing needs its own basis and transfer safeguards.
Detection and measurement
- Staff request timeliness: share of staff subject access requests answered within one month, or within a properly notified extension.
- Retention compliance: number of leaver records past their scheduled review date.
- Access hygiene: number of users with access to health or diversity fields, trended down to the agreed list; managers retaining access to former reports.
- Export activity: bulk exports per month by role, with alerts on exports by users outside named reporting roles.
- Basis coverage: share of HR record types with a documented lawful basis and, where needed, a Schedule 1 condition.
- Integration scope: share of HR integrations reviewed in the last year with field-level scope recorded.
Common failure patterns
- Consent as a catch-all: staff are asked to consent to everything in their contract, creating rights the employer cannot honour.
- Keeping everything forever: leaver records, unsuccessful candidates and old investigations are never deleted because nobody owns the schedule.
- Health data in the main file: sick notes and occupational health reports visible to every manager who can open the employee record.
- Unscoped integrations: payroll, benefits or analytics connectors reading the full workforce record with long-lived credentials.
- Staff requests treated as litigation only: legal teams delay the response while preparing for a claim and miss the statutory deadline.
- Shadow copies: spreadsheets exported for a restructure or pay review sit in email and shared drives long after the project ends.
Framework mapping
| Framework | Reference | Relevance to HR data |
|---|---|---|
| UK and EU GDPR | Articles 5(1)(e), 6, 9(2)(b), 12(3), 15, 30, 35, 88 | Storage limitation, lawful basis, special category condition, request timing, access, records, DPIA, employment rules |
| Data Protection Act 2018 | Schedule 1 | Conditions for special category and criminal offence data, appropriate policy document |
| NIST CSF 2.0 | PR.AA-05 | Access permissions and authorisations defined and managed with least privilege |
| NIST CSF 2.0 | PR.DS-01 | Confidentiality, integrity and availability of data at rest protected |
| NIST SP 800-53 Rev. 5 | PT-2, PT-3, SI-12, AC-6 | Authority and purpose for processing, information retention, least privilege |
| ISO/IEC 27001:2022 | Annex A 5.34 | Privacy and protection of personal identifiable information |
Practitioner checklist
- Record every HR record type with purpose, lawful basis and any Article 9 or Schedule 1 condition.
- Remove consent as the basis wherever contract, legal obligation or legitimate interests applies.
- Maintain an appropriate policy document covering the Schedule 1 conditions relied on.
- Publish a worker privacy notice and refresh it when new HR processing starts.
- Configure the retention schedule as purge rules in the HR system and test them before go-live.
- Separate health and investigation records from the main employee file with their own access list.
- Scope manager, payroll and integration access to the fields they need and log bulk exports.
- Agree a staff subject access request process with search sources, redaction rules and exemption logging.
- Review HR integrations and their credentials at least annually.
Standards and references
- EUR-Lex: Regulation (EU) 2016/679, General Data Protection Regulation
- ICO: Collecting and keeping employment records
- ICO: Using employment records
- ICO: A guide to subject access
- EDPB: Guidelines 01/2022 on data subject rights, right of access
- California Privacy Protection Agency: Frequently asked questions
- GOV.UK: PAYE for employers, keeping records
- GOV.UK: Employer's guide to right to work checks
Related NHI Mgmt Group resources: Employee Monitoring and Privacy Guide · Security Requirements for Selecting an HR System · DSAR Guide · Identity Lifecycle Event Design Guide. This guide summarises data protection rules for HR records and is not legal advice.