Worried a breach just landed on your desk? Your data breach notification requirements depend on the law: GDPR allows 72 hours, HIPAA 60 days, and the SEC 4 business days.
This guide sits within our wider coverage of business data privacy.
| Notification duty | Deadline |
|---|---|
| GDPR notice to the supervisory authority | 72 hours after becoming aware |
| HIPAA notice to affected individuals | Within 60 calendar days of discovery |
| SEC Form 8-K disclosure (public companies) | 4 business days after determining materiality |
| California notice to affected residents | 30 calendar days from discovery, starting January 1, 2026 |
| California Attorney General notice | 15 calendar days after informing consumers (more than 500 residents) |
These figures come from Decryption Digest’s July 10, 2026 guide and Reform’s GDPR guide. Deadlines and thresholds can change, so check the source before you rely on them.
What counts as a breach, and when does the clock start?
A breach is not only a hack. Under the GDPR, a personal data breach includes accidental or unlawful destruction, loss, alteration, unauthorized disclosure or access, so deleting a database by mistake or misconfiguring a server that exposes customer data also qualifies, according to Reform.
If you are unsure which of your records count as personal data, start with our explainer on what is personally identifiable information.
Ransomware deserves special attention. According to NHI Management Group’s guide, encryption by ransomware counts as a loss of availability and can be notifiable even with no exfiltration.
A serious incident rarely triggers just one duty. Decryption Digest notes that each framework starts its clock at a different moment:
- GDPR’s 72-hour clock starts when you “become aware” of a personal data breach.
- The SEC’s 4-day clock starts when you “determine” materiality.
- HIPAA’s 60-day clock starts at “discovery.”
These are not the same moment. A confirmed ransomware infection is a breach discovery, yet it may not be material for SEC purposes until the investigation establishes scope, and the same source says legal counsel must be involved in setting the clock-start event for each framework.
GDPR: 72 hours to the regulator
GDPR Article 33 applies to organizations that process personal data of EU residents, regardless of where the organization is headquartered, according to Decryption Digest. The data controller notifies the authority, while a processor, such as a cloud provider, must tell the controller “without undue delay” on becoming aware of a breach.
The notice must reach the relevant supervisory authority within 72 hours of becoming aware. “Becoming aware” means reasonable certainty that an incident has occurred: more than a suspicion, but not a finished investigation.
If the full facts are not known in time, a phase-one notification can be filed with what you have and followed up when the investigation ends. Per Article 33, the notice should cover:
- The nature of the breach, including categories and approximate number of data subjects and records concerned.
- The name and contact details of the data protection officer or another contact point.
- The likely consequences of the breach.
- The measures taken or proposed to address the breach and reduce its adverse effects.
Individuals are a separate step. Article 34 requires telling affected people “without undue delay” when a breach is likely to result in high risk to their rights and freedoms, a higher bar than the one for notifying the authority.
Reform lists exceptions to telling individuals, such as when the breached data was encrypted and therefore unreadable, or when later measures have eliminated the high risk.
HIPAA and SEC: the main US federal clocks
HIPAA breach notification
HIPAA’s Breach Notification Rule covers healthcare providers, health plans, clearinghouses and their business associates. Covered entities must notify affected individuals within 60 calendar days of discovery, and the clock runs from the date they knew or should reasonably have known of the breach, per Decryption Digest.
Not every incident must be reported. A four-factor risk assessment looks at the nature of the PHI, who the unauthorized person was, whether the PHI was actually acquired, and how far the risk has been mitigated. Breaches below that harm threshold do not require notification.
The same source describes who else must hear about a reportable breach:
- HHS must be told of all breaches; for 500 or more individuals, at the same time as individuals.
- For fewer than 500 individuals, HHS is notified annually, by March 1 of the following year.
- For 500 or more individuals in a state, prominent media outlets in that state must also be notified.
- Business associates must notify the covered entity within 60 days of discovery, though many agreements require faster notice, within 10 or 30 days.
SEC disclosure for public companies
As of Decryption Digest’s July 2026 article, the SEC’s cybersecurity disclosure rules, effective December 2023, apply to publicly traded companies registered with the SEC. The materiality determination, not discovery, starts the 4 business day clock for a Form 8-K, per that guide.
Delay is narrow. According to IR-OS, in a page updated May 18, 2026, delayed disclosure is available only with a written determination by the U.S. Attorney General that disclosure poses a substantial risk to national security or public safety.
State laws and other countries
In the US, all 50 states plus DC have breach notification laws, and they differ in covered data types, timelines and attorney general notification requirements, according to Decryption Digest. You cannot assume one state’s rule fits another.
California shows how specific these rules get. Per Reform, starting January 1, 2026, SB 446 requires businesses to notify affected residents within 30 calendar days of discovering a breach. For breaches affecting more than 500 California residents, the Attorney General must be notified within 15 calendar days after consumers are informed.
Other regimes run on their own terms. As checked against official or primary sources in October 2026 by NHI Management Group, and in IR-OS’s May 2026 update, the picture looks like this:
- UK GDPR: as soon as possible and, where feasible, within 72 hours (NHI Management Group).
- Canada (PIPEDA): as soon as feasible after determining the breach occurred, where it is reasonable to believe the breach creates a real risk of significant harm (NHI Management Group).
- Singapore: as soon as practicable, no later than 3 calendar days after determining the breach is notifiable (NHI Management Group).
- New York financial services: 72 hours from determining a cybersecurity event has occurred (IR-OS).
- EU NIS2: an early warning within 24 hours, a notification within 72 hours, and a final report no later than one month after that notification (IR-OS).
Building a notification process before you need one
The practical lesson is to decide your approach before an incident. NHI Management Group advises mapping regimes by data subject location, not by your headquarters, and recording every incident, notified or not.
A workable readiness routine looks like this:
- List which laws apply, based on where affected people live and which sector rules cover you.
- Write down the exact time you became aware, discovered or determined materiality, since each clock starts differently.
- Ask legal counsel to confirm the clock-start event for each framework.
- Prepare a phase-one notice template with the content fields the GDPR requires.
- Check vendor and business associate agreements for notice periods shorter than the legal minimum.
- Keep an internal record of every incident, including those you decide not to report.
Your public statements should also match what you actually do with data, so see our guide to privacy policy requirements when you review them.

Frequently asked questions
Do I always have to notify the people affected?
Show answer
No. Under the GDPR, individuals must be told when the breach is likely to result in high risk, and encrypted, unreadable data is one exception listed by Reform. Under HIPAA, a low result on the four-factor risk assessment means no notification is required, per Decryption Digest.
What if I do not have all the facts within 72 hours?
Show answer
The GDPR allows phased reporting. You can file a phase-one notification with the information available and follow up when the investigation is complete, as Decryption Digest explains.
Does a breach at my vendor count?
Show answer
It can. A GDPR processor must notify the controller without undue delay, and a HIPAA business associate must notify the covered entity within 60 days of discovery, though many agreements require faster notice, according to Decryption Digest.
Do all US states use the same deadline?
Show answer
No. All 50 states plus DC have their own laws with different covered data types, timelines and attorney general requirements, so check each state where affected people live, as Decryption Digest notes.



