Skip to content

Data Breach Reporting in Ireland: The 72-Hour Rules

Data Breach Reporting in Ireland: The 72-Hour Rules

Business lead preparing a personal data breach notification

If personal data in your business is lost, stolen, altered or seen by the wrong people, you must tell Ireland’s Data Protection Commission (DPC) without undue delay and, where feasible, within 72 hours of becoming aware of it, unless the breach is unlikely to put anyone at risk. If the risk to people is high, you must tell them too. The firms that cope best are those whose systems already show them what happened, quickly enough to meet the deadline.

This guide sets out what counts as a breach, when the clock starts, what the report must contain, and how to prepare your IT so that 72 hours is enough.

Lancast
lancast.ie
Prepare IT for Faster Breach Response
LANCAST provides proactive managed services, continuous monitoring and early threat detection to help organizations stay ahead of potential cyber attacks.

Call us today to see how we can help

TL;DR

  • Report to the DPC within 72 hours of becoming aware of a breach, unless you can show it is unlikely to result in a risk to individuals. The 72 hours include weekends.
  • Tell the affected individuals without undue delay when the breach is likely to result in a high risk to them.
  • If you cannot gather everything in time, send what you have and follow up. A late report must explain the delay.
  • Keep a record of every breach, including those you decide not to report, with the reasons.
  • Logging, monitoring, backups and encryption decide how fast you can answer the DPC’s questions.

Table of Contents

What counts as a personal data breach

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. The DPC’s October 2019 guidance lists examples including ransomware, phishing, misdirected emails and accidental loss.

That is wider than most business owners expect. The DPC’s data security guidance points out that a breach is not just a lost USB key or laptop but any loss of control over personal data, including inappropriate access to systems or sending personal data to the wrong people.

In February 2025 the DPC took a broad view again, finding that each incident of plaintext password storage was a breach, as reported by Matheson. Even a security failure with no malicious intent can therefore trigger a duty to assess and possibly notify.

Typical cases in a small or medium business:

  • An invoice with customer details emailed to the wrong recipient.
  • A staff laptop or phone stolen with unencrypted files on it.
  • A phishing email that gives an attacker access to a mailbox.
  • Ransomware that encrypts a file server holding employee or customer records.
  • A fire or flood that destroys the only copy of personnel files.
  • A former employee who still has access to a shared drive.

The Irish College of GPs lists almost the same set for medical practices, which shows how ordinary these events are.

When the 72 hours start

Section 86(1) of the Data Protection Act 2018 requires notification to the DPC without undue delay and, where feasible, within 72 hours of becoming aware of the breach. The DPC’s guidance says you are aware when you have a reasonable degree of certainty that a security incident has occurred and compromised personal data. You do not need a full investigation first.

Two practical points catch businesses out.

First, the clock does not stop for weekends. The Law Society’s breach protocol gives the example of a breach discovered at 3pm on a Friday, which must be notified by 3pm on Monday.

Friday breach discovery and 72-hour reporting deadline

Second, awareness can be judged against what you ought to have known. In a decision on Twitter International Company, the DPC held that the clock began on 3 January 2019, when the company ought to have been aware of a breach at its processor, not 7 January, when it was told, as Hayes Solicitors explain. If a supplier that handles your data, such as a hosting or payroll provider, has an incident, you need a way to hear about it quickly and a contract that makes them tell you.

A processor is a business that handles personal data on your behalf. gov.ie confirms that processors must notify the controller (you, if you decide why and how the data is used) when they become aware of a breach. The Law Society notes that contractual timescales for this are often shorter than 72 hours.

Do you have to report it?

The default is to report. Section 86(3) of the Act exempts a breach only if it is unlikely to result in a risk to the rights and freedoms of the people concerned, judged by the nature of the data and the scope, context and purposes of the processing. The DPC’s October 2019 guidance expects you to be able to demonstrate and record why you concluded there was no risk.

When you assess risk, the DPC asks you to consider the type and nature of the data, how it could be maliciously used and the potential harm. As a rule of thumb:

Situation Likely approach
Encrypted laptop lost, key not compromised Record it; reporting may not be needed if data is unintelligible
Email with a customer’s name and order sent to the wrong person who deletes it Assess and record; risk may be low
Mailbox compromised through phishing Assess promptly; usually reportable
Ransomware on a server holding customer or staff records Report within 72 hours
Bank details or ID documents exposed Report, and consider telling individuals

This table is a guide to the reasoning, not a ruling. Each case turns on its facts.

When you must tell the people affected

The DPC’s breach notification page states that since 25 May 2018 you must inform affected individuals without undue delay where the breach is likely to result in a high risk to them. gov.ie gives stolen bank details as an example of a high-risk situation, and the message must be in clear and plain language.

Section 87 of the Act, read with the DPC’s August 2019 quick guide, allows three exemptions:

  • Encryption or similar measures made the data unintelligible to anyone not authorised to see it.
  • Later measures mean the high risk is no longer likely to materialise.
  • Contacting people would take disproportionate effort, in which case you must use a public communication that informs them equally effectively.

The first exemption is the one that most clearly rewards good IT practice. A lost device with full-disk encryption is a very different event from one without it. The same guide notes you may inform individuals voluntarily even when the risk is not high.

What the report must contain

Section 86(4) requires the notification to include:

  • A description of the breach, including where possible the categories and approximate number of people and records concerned.
  • The likely consequences.
  • The measures taken or proposed to address and reduce the harm.
  • The name and contact details of your data protection officer or other contact point.

If you cannot supply everything within 72 hours, section 86(5) lets you notify with what you have and provide the rest without undue delay. A late notification must include the reason for the delay (section 86(2)). The DPC’s quick guide also recommends saying in your first notification how and when you became aware of the breach.

You submit through the form on the DPC’s breach notification page. It asks for a self-declared risk rating of Low, Medium, High or Severe in the email subject line, whether the report is new or an update, and the organisation name. Cross-border breaches must be flagged, and telecoms and internet providers use a separate form. Acompli’s 2026 research stresses that the rating is an aid, not a substitute for the legal risk test.

LANCAST Infrastructure Solutions, Unit 52, Southern Cross Business Park, Ballywaltrim
Lancast
Strengthen Your Breach Readiness
Explore LANCAST’s IT infrastructure and managed services, including continuous monitoring and early threat detection for organizations navigating technology risks.
LANCAST Infrastructure Solutions
Unit 52, Southern Cross Business Park, Ballywaltrim

Get directions

A response routine that fits inside 72 hours

  1. Contain the incident. Disconnect affected devices, reset credentials, revoke access. This is where monitoring helps most, because you can see which accounts and systems were touched.
  2. Note the time you became aware. Write down how you found out. You will be asked.
  3. Establish what data is involved. Which systems, which people, how many records, and whether the data was encrypted.
  4. Decide controller or processor status. If you are a processor, tell your controller without undue delay.
  5. Assess the risk and record the decision. Log every breach in a register, reportable or not.
  6. Notify the DPC. Send what you know and promise an update if details are outstanding.
  7. Tell individuals if the risk is high. Plain language, what happened, what they should do, who to contact.
  8. Consider your insurer. The Law Society protocol suggests checking whether your policy requires notification.
  9. Review and fix. Close the gap that allowed the breach.

Most of the delay in a real incident is spent on step 3. Businesses without logs, an asset list or tested backups spend days working out what was lost. Those with them can answer in hours. That is why we treat breach readiness as an IT matter as much as a legal one.

What happens if you report late or not at all

The DPC enforces this. According to Byrne Wallace Shields, in 2026 the DPC fined PTSB €250,000 for security infringements and a further €27,500 for failing to notify breaches within 72 hours. The University of Limerick was fined €98,000 for failures that included late notifications to the DPC and not informing individuals of high-risk breaches.

The lesson for a smaller business is that a timely, honest report with a clear record is the safest position. The DPC’s guidance treats notification as the default, and its inquiry into Tusla found a failure to notify without undue delay alongside a failure to have appropriate organisational measures in place.

NIS2: a second clock for some organisations

Some organisations will also fall under the EU’s NIS2 cybersecurity directive. As of 15 October 2026, Four Winds reports that Ireland had not transposed it by the EU’s October 2024 deadline and that it was progressing through the National Cyber Security Bill 2024. For entities in scope it would add a 24-hour early warning, a 72-hour notification and a one-month final report, running alongside the GDPR duty rather than replacing it. Check the status of the Bill before relying on this, and if you supply larger Irish organisations, expect them to ask about it.

Prepare your IT before a breach happens

The reporting rules ask for facts: what was affected, when you knew, what you did. The technical groundwork is what lets you supply them.

Know your data and systems. Keep an up-to-date list of where personal data lives: servers, Microsoft 365, laptops, printers, hosted sites. You cannot report on what you cannot find.

Encrypt devices and backups. Encryption can remove the duty to tell individuals and can change the risk assessment entirely.

Secure email and passwords. Phishing and misdirected email are among the most common causes. See our guides on business email security and password policy.

Monitor continuously. Early detection shortens the gap between an incident and your awareness, and gives you the logs the DPC will want. Our security services include continuous monitoring and early threat detection.

Back up and test recovery. If ransomware hits, restoring clean data matters for both the business and the harm assessment. Our guides on ransomware recovery steps and backup and disaster recovery plans cover the routine.

Write a one-page breach plan. Who decides, who contacts the DPC, who handles customers, and how staff report a suspected incident. The DPC’s data security guidance asks whether staff at all levels know whom to tell.

How we help

We are an Irish IT infrastructure and managed services provider, an HP Amplify Partner and a Microsoft Cloud Service Provider, with 30 years of experience. Our work covers IT security and data protection, penetration testing, vulnerability management, threat risk assessment and planning, anti-virus management, and backup and disaster recovery, delivered through managed support plans with proactive monitoring and remote and onsite support. For a business without in-house IT, that puts the logging, backup and security work that makes a 72-hour report manageable in one place.

If you want to know where your exposure sits before an incident, a threat risk assessment and vulnerability review is the place to start.

Lancast

You can also talk to us about IT consultancy to build a breach-ready setup around your existing systems.

Our perspective

Most breach reports we would want to help with are not hard because the law is complicated. The 72 hours are hard because nobody can say quickly which systems were touched, which accounts were used and whether the data was protected.

That is an infrastructure question. A business that monitors its network, controls who has access, encrypts its devices and tests its backups can answer the DPC’s questions with facts instead of guesses. It can also show that it took appropriate measures before the incident, which is what the regulator looks for.

We built our managed services around that idea: proactive monitoring, security and recovery working together as an extension of your own team, so that a bad day becomes a managed one.

Carl

FAQ

How quickly do you have to report a data breach in Ireland?

Without undue delay and, where feasible, within 72 hours of becoming aware of it, under section 86 of the Data Protection Act 2018. Weekends count. If you cannot meet the deadline, you must give the reasons for the delay in your notification.

Do I have to report every breach to the DPC?

No, but you must be able to show that a breach you did not report was unlikely to result in a risk to individuals. The DPC’s guidance expects you to record that reasoning. Log every incident in an internal register whether you report it or not.

Do I have to tell customers or staff as well?

Yes, when the breach is likely to result in a high risk to them, for example stolen bank details. You must do so without undue delay in clear, plain language. An exemption applies where the data was encrypted so as to be unintelligible, or later measures remove the high risk.

What if I do not yet know the full details?

Notify with the information you have and send the rest without undue delay, as section 86(5) allows. Say how and when you became aware of the breach and what you are doing about it.

Lancast
Discuss Your Breach Preparedness
Talk with LANCAST about proactive managed services, security monitoring and IT consultancy for your organization’s technology needs.

Sources