If you sell SaaS into the EU and the US, you don't get to pick one breach notification deadline — you have to satisfy all of them at once. GDPR gives you 72 hours to tell a supervisory authority about a breach. No US state matches that speed; most give you 30 to 90 days, or no fixed number at all. The only sane move is building your incident response to the tightest deadline in your stack, then letting counsel subtract obligations per incident.
That's not a compliance nicety. It's the difference between a controlled disclosure and a 2am scramble where your CTO is googling "do we have to tell Delaware."
GDPR's 72-Hour Clock: What It Actually Requires
Article 33 of GDPR is blunt: if you're a controller and you experience a breach likely to risk the rights and freedoms of data subjects, you notify your supervisory authority within 72 hours of becoming aware of it. Not 72 business hours. Not "aware once legal signs off" — aware, full stop.
That notification needs specifics: the nature of the breach, the categories and approximate number of people affected, your DPO's contact details, the likely consequences, and the measures you've taken or plan to take (Article 33(3)). If the breach is high-risk, Article 34 kicks in and you also have to tell the affected individuals directly, "without undue delay."
Here's the part founders miss: the clock starts at awareness, not confirmation. If your on-call engineer flags unusual database access at 11pm on a Friday, that's your starting gun — even if you don't yet know how many records were touched.
If you're a processor (most B2B SaaS tools are, relative to their customers), you don't notify the authority yourself — your customer does. But you still need to tell your customer fast enough for them to hit their own 72-hour window. More on that trap later.
The US Patchwork: Anywhere From 2 to 90 Days
There's no US federal breach notification law. Instead you've got a 50-state patchwork, and per IAPP's analysis, timelines range from 2 days to 90 days, with 30–45 days being the most common window where states bother setting a specific number at all. Plenty of states instead use vaguer language like "without unreasonable delay," which sounds reasonable until you're the one deciding what "unreasonable" means under pressure.
Florida requires notice within 30 days of determining a breach occurred. Delaware gives you 60 days. Some states, per Alston & Bird's tracking, have no fixed number in statute — founders often read that as "more time." Lawyers read it as "more ambiguity, more risk."
The 2026 Changes You Need to Bake Into Your Playbook Now
The patchwork is tightening, and 2026 is the year it bites:
- California SB 446 (effective 1 January 2026) closes a long-standing loophole and requires businesses to notify affected residents within 30 calendar days of discovering a breach. If you've been leaning on California's old flexibility, that's gone.
- New York amended General Business Law §899-aa in 2025 to shorten its reporting window — don't assume the version you read in 2022 still applies.
- Oklahoma (SB 626) and Texas have both updated their breach statutes for 2025–2026, generally moving toward tighter timeframes and broader definitions of personal information.
If your breach playbook was last reviewed before 2025, it's already out of date. That's not a knock — it's just how fast this is moving.
The Sectoral Wildcards Everyone Forgets: India's CERT-In and HIPAA 2025
Most "GDPR vs US" comparison posts stop there. They shouldn't, because two sectoral frameworks are stricter than GDPR's headline number.
India's CERT-In directions require certain categories of incidents to be reported to CERT-In within 6 hours of noticing them — a far tighter window than GDPR's 72 hours. If you're a SaaS company with Indian users or infrastructure, this isn't optional background reading; it's a separate, faster clock running in parallel with everything else. Given India is one of your core markets, this should sit at the top of your incident response doc, not a footnote.
HIPAA's 2025 update tightens obligations for SaaS vendors touching protected health information. Under the revised rule, healthtech SaaS providers must notify affected individuals within 30 days of discovering a breach, and notify HHS within 72 hours if more than 500 individuals are affected. If you're a healthtech startup and PHI flows through your platform as a business associate, you now have a GDPR-speed deadline sitting inside US law.
On the Central African Republic: there's currently no dedicated, actively-enforced comprehensive data protection statute comparable to GDPR, though the broader African Union Malabo Convention signals the regional direction of travel. The practical advice for founders with CAR users is the same advice that applies everywhere else in this post — don't wait for local law to catch up before you build good habits.
Why "GDPR Compliant" Doesn't Mean "US Compliant"
This is the myth that gets founders into trouble: assuming that because you've nailed GDPR, you're covered everywhere. You're not. Consent mechanisms differ — GDPR requires affirmative opt-in for most data processing, while many US states operate on opt-out models. Privacy notice requirements differ in what disclosures are mandatory and when they must be delivered. And breach notification workflows differ in both timing and content.
A notification letter built for a German supervisory authority won't satisfy California's Attorney General's office, and vice versa. You need jurisdiction-specific templates, not one document with find-and-replace. In practice, the founders who get burned aren't the ones who ignore compliance entirely — they're the ones who did GDPR properly, felt confident, and assumed US obligations were basically the same shape. They're not.
The Strictest-Standard Framework: Build to Six Hours, Then Subtract
Here's the operational answer, and it's the one almost nobody states plainly: build your internal detection-to-decision workflow to the tightest deadline in your entire jurisdictional footprint, then have counsel remove obligations per incident rather than trying to assemble them under pressure.
Call it the 6-Hour Build: your goal isn't to notify every regulator in 6 hours — it's to have identified, triaged, and escalated internally within that window, every time, regardless of where the breach touches. That single internal habit satisfies CERT-In's 6-hour trigger, gives you 66 hours of runway before GDPR's 72-hour deadline, and leaves weeks of margin for US state deadlines and HIPAA's 30-day individual notice window.
Kiteworks' research found that 89% of organizations have never practiced incident response with their third-party vendors, and 87% lack joint incident response playbooks with partners at all. That's the gap the 6-Hour Build closes — you're not inventing a response from scratch mid-breach, you're executing a drill you've already run.
Who Notifies Whom: The Processor-Controller Trap
Most B2B SaaS companies are processors, not controllers, under GDPR — your customer holds the primary statutory notification obligation to their own regulator and users. But that doesn't let you off the hook. You still have to notify your customer fast enough for them to meet their 72-hour deadline, which in practice means your contractual SLA for breach notification to customers needs to be measured in hours, not days.
This is the contractual allocation problem that trips up lean teams: if your DPA says you'll notify customers "promptly" with no number attached, you've handed yourself a liability with no clear finish line. Put a number in the contract — 24 hours is a common, defensible standard — and build your internal process to beat it.
The same logic applies to US state deadlines: if your enterprise customer is the controller facing a 30-day California obligation, and you don't tell them about the breach until day 25, you've effectively broken their compliance for them, breach or no breach on your end.
A Lean Runbook: What to Automate, What Needs a Lawyer
You don't need an enterprise SOC to do this well. You need three things nailed down before you ever need them:
- Automate detection and escalation. Alerting rules that page a named human within minutes of anomalous access, not a ticket that sits in a queue.
- Template your notification letters per jurisdiction in advance. GDPR, California, New York, CERT-In, HIPAA — draft the skeletons now, while you're calm.
- Get counsel on retainer for the judgment calls. "Is this high-risk under Article 34?" and "does this trigger the 500-person HIPAA threshold?" are legal questions, not engineering ones. Don't make your head of product decide them at 1am.
Where startups get caught out isn't the big dramatic breach — it's the quiet one that nobody escalates for four days because the detection step was manual and nobody owned it.
Takeaway
Stop trying to track every state's deadline individually — build one workflow fast enough to satisfy the strictest rule you're exposed to (CERT-In's 6 hours if you've got Indian users, GDPR's 72 hours otherwise), then let a lawyer tell you what you can relax on per incident. Review your breach notification contracts with customers this quarter, especially the "promptly notify" clauses with no number attached — that's where the real exposure lives.
Frequently Asked Questions
Does GDPR's 72-hour deadline apply if my company is based in the US?
Yes, if you process personal data of people in the EU, GDPR's 72-hour notification obligation applies regardless of where your company is headquartered. Location of the data subject triggers the rule, not the location of your servers or your incorporation.
What happens if a breach hits both EU and US users at the same time?
You run all applicable clocks simultaneously — GDPR's 72-hour supervisory notice, any US state deadlines that apply to affected residents, and sectoral rules like CERT-In or HIPAA if relevant. There's no single combined deadline; you have to satisfy the fastest one first and keep working through the rest without treating the earlier notice as covering the later ones.
Is "without unreasonable delay" easier to comply with than a hard deadline?
No — it's often riskier, because there's no clear finish line to plan against. A hard deadline like 30 days gives you a target to build a workflow around; vague language invites panic decisions and after-the-fact arguments about what counts as reasonable.
Do I need a separate breach notification process for India?
Yes. India's CERT-In framework can require reporting within 6 hours for certain incident categories, which is faster than GDPR and most US state laws. If you have users or infrastructure in India, this needs its own line item in your runbook, not a footnote under GDPR.
As a SaaS processor, am I legally required to notify regulators directly?
Usually not — your customer, as the data controller, typically holds that statutory obligation. But your contract should require you to notify the customer fast enough that they can still meet their own deadline, and that internal SLA matters just as much as the regulatory one.