Does the 250-employee exemption apply?
Only for processing that is occasional, unlikely to result in a risk and free of special category or criminal offence data (Article 30(5)). Monthly payroll fails the first test.
UK GDPR. DUAA 2025.
After the DUAA, UK GDPR is checked through records, not policies: each change lands on a log you can keep, from the search limit to the complaints duty.
By Dipal Panchal, co-founder and CEO · Last reviewed: November 7, 2026
UK GDPR applies to personal data processed by organizations established in the UK (UK GDPR Article 3(1)). It also reaches organizations abroad that offer goods or services to people in the UK, or track their behavior there (Article 3(2)).
It works with the Data Protection Act 2018 and the Privacy and Electronic Communications Regulations 2003. The Information Commission supervises all three. It replaced the Information Commissioner on September 30, 2026 (SI 2026/1015), with the same powers, and its office still goes by the ICO.
The Data (Use and Access) Act 2025 amended all three. Its main data protection changes took effect on February 5, 2026 (SI 2026/82), and the complaints duty on June 19, 2026. This page is general information, not legal advice.
How a reviewer labels values from one HR database. The label decides which condition and which record each value needs.
| Value | Detected type | Label | Reason | Kept or rejected |
|---|---|---|---|---|
| QQ 12 34 56 C | National Insurance number | Personal data | Payroll key for a named employee; HMRC never uses Q as a prefix letter | Kept |
| F32.1 in occ_health.diagnosis | Diagnosis code (ICD-10) | Special category: health, Article 9(1) | Sits beside an employee ID, so it reveals that person’s health | Kept |
| Caution, 2024 | Criminal offence data | Article 10; DPA 2018 s.11(2) | A vetting result tied to a named candidate; spent or not, it stays criminal offence data | Kept |
| UNITE subs in payroll.deductions | Trade union membership | Special category, Article 9(1) | A monthly deduction reveals membership | Kept |
| 07700 900461 | UK mobile number | Personal data | Work contact in the HR table; Ofcom’s drama range | Kept |
| ana.ruiz@example.org | Email address | Personal data | A work address that names one employee | Kept |
| EC2V in sites.region | Postcode district | Not personal data | An area code for an office site; it identifies no person | Rejected |
Columns one and two are the law’s requirements. Column four is our recommended record for an auditor. Give each a date, owner and source system.
| Duty (provision) | What the law requires | DUAA 2025 change | Record that shows it |
|---|---|---|---|
| UK GDPR Article 5(2) accountability | Be able to show you meet the Article 5(1) principles, including data minimization and storage limitation. | Section 71 changed Article 5(1)(b) and added 5(3); section 87 changed 5(1)(e) | A dated data map per system; fields matched to purposes; oldest records checked against retention rules |
| UK GDPR Article 30 record of processing activities | Record each processing activity: purposes, categories of people and data, recipients, transfers and erasure time limits. | None of substance; Article 30(4) now names the Commission | The record, with every system matched to a dated search of it |
| UK GDPR Article 9 and UK GDPR Article 10 | Article 9 data needs a 9(2) condition, some also one in Schedule 1; criminal offence data needs a Schedule 1 condition. | Section 72: relevant international law can support Articles 9(2)(g) and 10; section 74 lets regulations add categories | A dated map of where each category sits, its condition, and the appropriate policy document (Schedule 1) |
| UK GDPR Article 12(3), UK GDPR Article 12A and UK GDPR Article 15: access | One month from the relevant time (receipt, ID or fee); two more for complex or many requests, with reasons in month one. | Section 76 added Article 12A on February 5, 2026; section 78 limits the search, treated as in force from January 1, 2024 | A search record: sources searched and left out, why, and the clock dates, including any pause (Article 12A(5)) |
| UK GDPR Article 27 UK representative | Organizations abroad caught by Article 3(2) designate a UK representative in writing, unless Article 27(2) applies. | None | The signed, dated designation, and the privacy notice that names the representative |
| UK GDPR Article 32 security | Technical and organizational measures matched to the risk, from encryption to a process that tests and checks them. | None to Article 32(1) | Dated test reports from your security team, and a dated, scoped check of each store’s protection state |
| UK GDPR Article 33 breach notification | Notify the Commission without undue delay and, where feasible, within 72 hours of awareness, unless risk is unlikely. | Sections 118–119: notices now go to the Commission, from September 30, 2026 | The Article 33(5) breach log with awareness and notice times, and a dated list of what the system held |
| UK GDPR Article 35 impact assessment | Assess processing likely to be high risk before you start it; Article 35(3)(b) names large-scale special category data. | None of substance | The assessment’s data section, built from a dated search of the system |
| DPA 2018 s.164A complaints | Make complaining easy, such as by online form; acknowledge within thirty days of receipt; respond without undue delay. | Inserted by section 103, in force June 19, 2026; access replies must now mention it (Article 15(1)(ea)) | A complaints log: date received, date acknowledged, steps taken and the outcome |
| DPA 2018 s.157(5) higher maximum | s.157(5): £17,500,000, or 4% of an undertaking’s annual worldwide turnover in the preceding financial year if higher. | Section 115 and Schedule 13: PECR fines reach the same maximums, from February 5, 2026 | Not a record: Article 83(5) lists the articles in this tier |
| DPA 2018 s.157(6) standard maximum | s.157(6): £8,700,000, or 2% of an undertaking’s annual worldwide turnover in the preceding financial year if higher. | Breaches of s.164A take this tier (s.157(4A)) | Not a record: Article 83(4) lists the articles in this tier |
Only for processing that is occasional, unlikely to result in a risk and free of special category or criminal offence data (Article 30(5)). Monthly payroll fails the first test.
Section 78 asks for a reasonable and proportionate search, backdated to January 1, 2024. We recommend writing down each source you left out, and why, before the reply goes.
Yes, if Article 3(2) catches you, unless the processing is occasional, low-risk and avoids large-scale special category or criminal offence data, or you are a public body (Article 27(2)).
Not alone. In the audits I’ve seen, each question goes to every application owner, who answers by hand, by email. A dated scan of the system gives you something to check those answers against.
Checked on legislation.gov.uk and gov.uk on November 7, 2026. Next review by February 5, 2027, or sooner if a commencement order lands.
| Item | Status | Instrument |
|---|---|---|
| Regulator | The Information Commission, since September 30, 2026 | SI 2026/1015, with DUAA sections 118–119 |
| DUAA data protection changes | All in force: the main set since February 5, 2026, the complaints duty since June 19, 2026 | SI 2026/82; other parts by SI 2025/904, 2025/996 and 2026/317 |
| Article 12A time limits | In force since February 5, 2026; requests received earlier follow the old rules | SI 2026/82, regulations 2(h) and 4 |
| Reasonable and proportionate search (s.78) | In force since Royal Assent, June 19, 2025; treated as in force from January 1, 2024 | DUAA s.78(5) and s.142(2) |
| Complaints duty (DPA 2018 s.164A) | In force since June 19, 2026, for complaints received from that date | SI 2026/82, regulations 3(a) and 7 |
| UK GDPR wording | The text says “Commission” in place of “Commissioner” from September 30, 2026 | SI 2026/386, brought in by SI 2026/1015 |
| Next scheduled commencement | November 9, 2026: DUAA sections 61–65, on birth and death registers; no data protection change | SI 2026/1167 |
| Review | Editorial review by Sylox; not reviewed by a lawyer | Last reviewed November 7, 2026 |
IRIS maps its evidence to UK GDPR controls through its unified compliance framework. A scored UK GDPR readiness view isn’t in v1; ask us if you need one. Capabilities vary by edition.
UK GDPR Article 30: the systems in your record, checked against what they hold: IRIS produces part of this, for the sources you connect, by source, table, column or file.
Article 9: where special category data sits: IRIS produces part of this, for the data types IRIS detects, such as diagnosis codes.
Articles 12A and 15: the search record for a request: IRIS produces part of this, connected databases only, not files or mailboxes; the change happens in the source system.
UK GDPR Article 32: who can reach each dataset: IRIS produces part of this, where the source exposes permission data.
UK GDPR Article 32: how stored values are protected: IRIS produces part of this, checks sampled values for encryption, masking or hashing, once activated on your install.
UK GDPR Article 5(2): what each scan covered and couldn’t read: IRIS produces this.
Explore evidenceThis sequence is our recommendation; the law doesn’t prescribe it. The data mapping evidence guide goes deeper on each step.
Build the data map behind your Article 30 record from the systems themselves.
The EU text: the same articles, with EU fines and the Article 30(5) exemption in EU terms.
Evidence on sensitive data that traces to a source, table and scan date.
For UK GDPR, IRIS maps its evidence to controls through its unified compliance framework; a scored readiness view isn’t in v1, so ask us if you need one. For the EU GDPR, IRIS scores controls. Mapping shows relevance; your auditors judge whether a control is met.
Yes, as inputs. A dated scan shows which connected systems hold personal data, by category, for the record and the assessment’s data section. The record and the risk judgment stay with your team.
No, not with built-in patterns today. You can add your own formats as custom patterns, and IRIS recognizes global identifiers such as payment-card numbers and IBANs.
No. IRIS searches connected databases for a person, not mailboxes. It logs access, correction and erasure requests; your team makes the change in the source system.
Test one system against your Article 30 record: a free assessment scans one database with a read-only login you create.