01Why this matters now
72 hours. That is how long Article 33 of the UK GDPR gives an organisation to report a qualifying personal data breach to the Information Commissioner's Office, counted from the moment it becomes aware. Where a breach is likely to result in a high risk to individuals, Article 34 also requires the organisation to tell the people affected without undue delay.
Key factThe window Article 33 of the UK GDPR gives an organisation to report a qualifying personal data breach to the ICO.
Meeting those deadlines depends on knowing what personal data you hold, where it is stored, who can reach it and which suppliers process it on your behalf. Many organisations find out how incomplete that picture is only when something goes wrong. The ICO can fine up to £17.5 million or 4% of annual worldwide turnover, whichever is higher, for the most serious infringements.
Article 25 adds a duty that applies long before any breach: data protection by design and by default. Privacy has to be built into systems and processes from the start. The Data (Use and Access) Act 2025 has since updated parts of the UK framework, so policies written even a few years ago may need revisiting.
AI makes all of this harder. Models are trained on large datasets that can include personal information. They can infer things about people that were never directly shared. Individuals still hold rights of access, correction, erasure and objection, and organisations need to be able to honour those rights even when personal data flows through AI systems. Too often, the answers sit in spreadsheets and email chains that only one or two people understand.
02Who this is for
- 01Financial services
- 02Retail and e-commerce
- 03Technology companies
- 04Education providers
- 05Public bodies
- 01Data protection officers
- 02Privacy and legal teams
- 03Information security leads
- 04Product teams
03How Regulativ helps
Supports the core work of a privacy programme. It helps teams:
- Map personal data across systems and suppliers and keep records of processing activities up to date
- Run data protection impact assessments under Article 35 for new projects and technologies
- Manage data subject requests and track them against statutory deadlines
- Prepare for breach response so the right information is to hand within the 72-hour window
Records how each AI system uses personal data, what decisions it supports and who is responsible for it. That makes it easier to answer questions from individuals, regulators and auditors about how AI is being used.
Explore AI GovernorHelps organisations prepare for the National Cyber Security Centre's baseline certification. It covers the technical controls, such as secure configuration, access control and patch management, that reduce the chance of personal data falling into the wrong hands in the first place.
04What this looks like in practice
- ContextA UK retailer with a loyalty scheme of two million members plans to introduce AI-driven personalised offers.
- What happenedBefore launch, the privacy team uses GDPR One to complete a DPIA and confirm the lawful basis for each type of processing.
- SignalThe new system is registered in AI Governor with a named owner.
- ResultWhen a customer later asks why they received a particular offer, the team can explain the logic and the data involved.
05Societal outcome
Privacy is a right, and it only has meaning when organisations take it seriously in practice. People keep more control over information about themselves, and the risk of that information being misused, sold on or exposed in a breach goes down.
Organisations benefit too. They can show regulators, customers and the public exactly how personal data is protected, and that openness builds the trust that digital services depend on.