Under the GDPR and UK GDPR, data breach notification within 72 hours is required for any personal data breach that is likely to result in a risk to people's rights and freedoms. The 72 hours run from when you become aware of the breach, not from when it happened, and you notify the regulator (the ICO in the UK, or your lead supervisory authority in the EU). If the risk to people is high, you must also tell the affected users without undue delay. Every breach, reportable or not, goes in your internal breach log.
Below is a step-by-step response plan for site owners, built around Articles 33 and 34. It is general information, not legal advice; for a serious incident, get legal and technical help quickly.
What counts as a personal data breach?
A personal data breach is a security incident leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, personal data. It covers far more than hacking:
- Confidentiality breaches: a database exposed through a misconfigured storage bucket, a member list emailed to the wrong person, an affiliate partner given access to user-level data it shouldn't have.
- Integrity breaches: records altered by an attacker or a faulty script.
- Availability breaches: ransomware that locks you out of customer data, or deleting data without a backup.
A breach is about the data, not the cause. A careless spreadsheet export is a breach just as much as a credential-stuffing attack.
The GDPR data breach notification 72 hours rule, step by step
- Contain it (hour 0 onwards). Revoke compromised credentials, close the exposed endpoint, take affected systems offline if needed, preserve logs. Don't wipe evidence.
- Start the clock and the log. Record when you became aware. The ICO treats you as aware when you have a reasonable degree of certainty that a security incident has compromised personal data. You may investigate briefly to establish that, but you cannot delay awareness by not looking.
- Establish the facts. What data, how many people, which systems, whether the data was encrypted, who might have it.
- Assess the risk to individuals (see below). This decides whether you notify the regulator, the users, or both.
- Notify the regulator within 72 hours if required. If you don't have every detail, notify with what you have and send the rest in phases. If you are late, explain why.
- Tell affected users without undue delay if the risk is high.
- Fix the cause, then review. Update your DPIA, contracts and controls, and record lessons learned.
Processors: if you are a processor (for example, a tracking platform or host processing data for clients), Article 33(2) requires you to notify the controller without undue delay. The controller then runs the 72-hour clock. Check your contracts for tighter deadlines.
How to assess whether a breach is reportable
Ask how likely it is that the breach will affect people, and how badly. Factors that push risk up:
- Sensitivity: data revealing sex life or sexual orientation, membership of an adult or dating service, identity documents, payment details or passwords. See special category data on adult sites.
- Identifiability: names and emails attached to the data.
- Volume and vulnerability of the people affected.
- Who has the data: a trusted recipient who confirms deletion is very different from a criminal forum.
- Protection: strong encryption with an uncompromised key can make a lost device low-risk.
| Hypothetical incident | Notify regulator? | Notify users? |
|---|---|---|
| Encrypted laptop lost; key not compromised | Probably not; log it | No |
| Newsletter sent with all recipients visible in the "To" line, on a general affiliate deals list | Likely, depending on size and context | Possibly |
| Same mistake on a list for a niche adult or dating offer | Yes | Yes: membership is revealed |
| Attacker downloads member table with emails and hashed passwords | Yes | Yes, with advice to change passwords |
| Ransomware with no exfiltration; restored from backup within hours | Depends on impact; document reasoning | Usually not |
For adult businesses the line moves quickly. The fact that someone holds an account can itself cause serious harm if exposed, so many breaches that would be borderline elsewhere will be clearly reportable for you.
How to report a data breach to the ICO or lead DPA
In the UK, you report through the ICO's breach reporting service. Article 33(3) sets out what the notification must contain:
- the nature of the breach, including categories and approximate numbers of people and records;
- the name and contact details of your DPO or other contact point;
- the likely consequences;
- the measures taken or proposed to deal with it and reduce harm.
In the EU, if you have an establishment there, you notify your lead supervisory authority under the one-stop-shop. If you are not established in the EU but serve EU users, the EDPB's view is that you may need to notify each authority in the Member States where affected users live, which is one reason non-EU operators appoint an Article 27 representative. UK businesses with EU users can therefore face parallel notifications to the ICO and EU regulators for the same incident.
When and how to notify users of a data breach
Article 34 requires you to tell individuals without undue delay when the breach is likely to result in a high risk. The message must be in clear, plain language and include the same core details as the regulator notice, plus practical steps people can take (change passwords, watch for phishing, contact their bank).
You don't need to notify individuals if the data was rendered unintelligible (for example, strongly encrypted), if you have taken steps that mean the high risk is no longer likely, or if individual contact would involve disproportionate effort; in that last case, a public communication is needed instead. Tips for adult and creator businesses:
- use a neutral sender name and subject line so the notice itself doesn't expose users to anyone reading over their shoulder;
- don't include more personal data in the notice than necessary;
- have a support route ready before you send, because replies will come in fast.
Keeping a breach log under GDPR
Article 33(5) requires you to document all personal data breaches, including those you decide not to report. A simple log should record:
- date and time of the incident and of awareness;
- what happened, what data and how many people;
- your risk assessment and the reasoning behind your decision to notify or not;
- notifications made, with dates and reference numbers;
- remedial actions and owners.
Regulators can ask to see it, and a well-kept log is the best evidence that you took a non-reported breach seriously.
Building a personal data breach response plan
The 72 hours go fast, often over a weekend. Prepare before you need it:
- Name an incident lead and a deputy, with out-of-hours contacts.
- Keep a contact sheet for your host, payment processor, tracking platform, legal adviser and insurer.
- Pre-draft regulator and user notification templates.
- Know where your data lives; your DPIA and records of processing help here (see when a DPIA is required).
- Check processor contracts give you prompt notice and cooperation; our guide to controller and processor roles covers what to include.
- Run a short tabletop exercise once a year.
Note that the EU's Digital Omnibus proposal would extend the deadline to 96 hours and limit regulator notification to high-risk breaches, but that is only a proposal. The 72-hour rule applies in both the EU and UK today.
Frequently asked questions
Do the 72 hours include weekends?
Yes. The period is 72 hours, not three working days, so plan for incidents discovered on a Friday evening.
What if I don't have all the facts within 72 hours?
Notify with what you know and provide the rest in phases. Waiting for a complete picture is not a reason to miss the deadline.
Can I be fined for not reporting a breach?
Yes. Failing to notify is a separate infringement from the breach itself, and regulators can and do take it into account.
Next steps
Write your plan now and test it against your hosting set-up. Your host's security and logging matter a great deal in an incident, so compare providers in our adult web hosting directory and read our guide to adult-friendly web hosting before you next renew.