Skip to content
StratQuad

UK GDPR and the Data Protection Act 2018

4 min read

Reference summary, not legal advice. Check the current legislation and take advice for your circumstances.

The UK's core data protection law, including the security and breach notification duties that fall to a security function.

At a glance

Owner
UK Parliament; regulated by the Information Commission, which replaced the Information Commissioner's Office (ICO) on 30 September 2026
Version
UK GDPR and DPA 2018, as amended by the Data (Use and Access) Act 2025
Published
5 Feb 2026
Applies to
Any organisation processing personal data in the UK, or offering goods or services to, or monitoring, people in the UK
Mandatory
Mandatory
Assessed by
Information Commission investigation and enforcement
Cost model
Annual data protection fee payable to the Information Commission by most controllers

Key points

  • Article 32 requires security appropriate to the risk. Article 5(1)(f), the integrity and confidentiality principle, makes security a core principle, not an add on.
  • A personal data breach must be reported to the Information Commission within 72 hours of becoming aware of it, unless it is unlikely to result in a risk to people's rights and freedoms.
  • Where a breach is likely to result in a high risk, the affected people must be told without undue delay.
  • Maximum fines are £17.5 million or 4 per cent of worldwide annual turnover, whichever is higher, with a lower tier of £8.7 million or 2 per cent.
  • The Data (Use and Access) Act 2025 amended the regime. Most changes commenced on 5 February 2026, the new complaints handling duty applied from 19 June 2026, and the Information Commission took over from the ICO on 30 September 2026.

What it is

The UK GDPR is the retained, amended version of the EU General Data Protection Regulation, in force in the UK since the end of the Brexit transition. It sits alongside the Data Protection Act 2018 (DPA 2018), which supplements it with exemptions, conditions for special category data, the law enforcement and intelligence services regimes, and the regulator's powers.

For a security function, the relevant duties are: securing personal data, managing processors, assessing high risk processing, and handling personal data breaches.

Duties that fall to security

  • Article 5(1)(f) Integrity and confidentiality

    Process personal data with appropriate security, including protection against unauthorised processing, loss, destruction and damage.

  • Article 25 Data protection by design and by default

    Build protection into systems and processes from the start.

  • Article 28 Processors

    Use only processors providing sufficient guarantees, under a contract with the terms Article 28 specifies, including security and breach assistance.

  • Article 32 Security of processing

    Implement measures appropriate to the risk, taking account of the state of the art and cost. The Article names pseudonymisation and encryption, ongoing confidentiality, integrity, availability and resilience, the ability to restore access after an incident, and regular testing of the measures.

  • Article 33 Notification to the regulator

    Within 72 hours of becoming aware, unless the breach is unlikely to result in a risk. Document every breach, reported or not.

  • Article 34 Communication to individuals

    Without undue delay where the breach is likely to result in a high risk.

  • Article 35 Data protection impact assessment

    Required before processing likely to result in a high risk.

Breach notification in practice

A personal data breach is a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, personal data. Ransomware that encrypts personal data is a breach even if nothing is exfiltrated, because availability has been lost.

The 72 hour clock starts when the controller is aware: when it has a reasonable degree of certainty that a security incident has compromised personal data. Article 33(4) and the ICO's guidance allow information to be provided in phases where full details are not yet known, provided the initial report is made within 72 hours. A notification made after 72 hours must give the reasons for the delay.

Under Article 33(3) the report should include, where known: the nature of the breach, categories and approximate numbers of people and records, likely consequences, measures taken or proposed, and a contact point.

Practitioner note

Make the data protection officer part of the incident response plan from the first hour, not a recipient of the final report. In ransomware and business email compromise cases the slow step is usually establishing whether personal data was affected and how much; build that question into triage, and record the time and basis of the "aware" decision, because the regulator will ask for both.

Evidence expected

In an investigation, the regulator typically asks for: the breach log; the incident timeline including when the organisation became aware; the risk assessment behind notifying or not notifying individuals; security measures in place at the time, with evidence they operated (patch status, MFA coverage, logging); the relevant DPIA; and processor contracts where a supplier was involved.

What changed under the Data (Use and Access) Act 2025

Changes from Before DUAA 2025 to After commencement

  • Royal Assent on 19 June 2025, with staged commencement.
  • From 5 February 2026: recognised legitimate interests as a lawful basis for specified purposes; relaxed restrictions on automated decision making in some circumstances; a "stop the clock" provision for subject access requests (the rule limiting searches to those that are reasonable and proportionate applied from Royal Assent); cookie consent exemptions for certain cookies; a new framework for international transfers; and a new definition of consent for scientific research.
  • PECR fines raised from a £500,000 maximum to UK GDPR levels from 5 February 2026.
  • PECR breach notification aligned with the UK GDPR 72 hour period from 20 August 2025.
  • From 19 June 2026: controllers must have a process for data protection complaints and acknowledge complaints within 30 days.
  • From 30 September 2026: the Information Commissioner's functions transferred to the Information Commission, a body corporate with a board, under section 119 and SI 2026/1015.

Enforcement and penalties

TierMaximumTypical infringements
Higher£17.5 million or 4% of worldwide annual turnoverBreach of the principles (including Article 5(1)(f)), lawful basis, data subject rights, international transfers
Standard£8.7 million or 2% of worldwide annual turnoverBreach of controller and processor obligations, including Articles 25, 28, 32, 33 and 34

The regulator can also issue reprimands, enforcement notices and assessment notices. For public sector bodies, the ICO stated a preference for reprimands over fines, but fines remain available.

Common failures

Common nonconformity

  • Late notification because no one owned the decision on whether a breach was reportable.
  • Breach log kept only for reported breaches; Article 33(5) requires every breach to be documented.
  • Processor contracts missing the Article 28 terms, especially breach notification to the controller.
  • Security measures stated in policy but not evidenced in operation, a recurring theme in ICO monetary penalty notices after cyber attacks.
  • DPIAs completed for new systems without security input, so the security risks are never assessed.

Sources

Suggest a correction