# We had a breach. Who do we notify, and by when? GDPR and Florida, one answer in twenty minutes

> Who do we notify after a data breach, and by when? GDPR: the regulator within 72 hours, customers without undue delay. Florida: within 30 days. One answer.

URL: https://pilot5.ai/blog/data-breach-notification-deadlines-gdpr-florida
Category: use-case
Published: 2026-11-20
Read time: 10 min
Keywords: data breach notification deadlines GDPR and Florida, who do we notify after a data breach and by when, GDPR Article 33, 72 hours, GDPR Article 34, Florida Statute 501.171, 30 days, in-house counsel, Pilot5 Legal, legal AI, privacy law

---

Watch the film on YouTube (2:26): [youtu.be/fyxZxJ4dmRI](https://youtu.be/fyxZxJ4dmRI)

After a data breach, the answer to “who do we notify, and by when?” depends on where the customers are, which company holds their data, and the moment the company learned. In the film, in-house counsel puts a real case to Pilot5 Legal, one of the workflows of Pilot5, with IT’s incident report and the customer figures: a backup of the booking database downloaded, with names, dates of birth and passport numbers, nine thousand customers in the EU and two thousand in Florida. Five AI models from five companies deliberate, and the memo comes back in about twenty minutes: the regulator within seventy-two hours, EU customers without undue delay, Florida customers within thirty days. Two clocks, both started the moment she learned. For in-house counsel, and for the lawyers who advise them.

**In one look: data breach notification deadlines under the GDPR and Florida law**

- EU customers, GDPR Article 33: the supervisory authority within 72 hours of becoming aware of the breach, unless the breach is unlikely to result in a risk. The notification can be made in phases.

- EU customers, GDPR Article 34: the people concerned without undue delay when the breach is likely to result in a high risk to them. Passport numbers in an unencrypted backup, public for thirteen days, is that kind of case.

- Florida customers, Florida Statute 501.171: the people concerned as expeditiously as practicable and no later than 30 days after the breach is determined; the Florida Department of Legal Affairs within the same 30 days when 500 or more Florida residents are affected.

- Both clocks start when the company learns of the breach. Investigating does not stop them.

## What is the case in the film?

Thursday 19 November, 5:40 p.m. IT Security confirms that a full backup of the booking database sat in a publicly readable cloud folder from 6 to 19 November, unencrypted, and was downloaded twice from unknown addresses. It holds names, email addresses, dates of birth, passport numbers and trip itineraries, no card data. About 9,400 customers booked with the European company in Paris, so French law and the GDPR apply; about 2,400 booked with the US company in Miami, so Florida law applies. In-house counsel wants to notify the regulator within seventy-two hours. The CEO wants to wait until forensics are done. The companies, the people and the facts are invented for the demonstration.

## How does Pilot5 Legal answer a data breach question?

- Counsel opens [legal.pilot5.ai](https://legal.pilot5.ai), writes the question as she would put it to a colleague, and attaches IT’s incident report and the file of affected customers by country.

- Pilot5 reads the files first, then asks only what they do not say: which law governs each company, the strongest fact a regulator would point to, and whether she already has a view.

- She reviews the brief Pilot5 built from her answers: the question, the governing law for each company, and the hypothesis to challenge, notify the CNIL within 72 hours against the CEO’s wish to wait.

- She launches the deliberation. Five AI models from five companies work the case separately. Three say notify now; the Contrarian argues the bigger risk is notifying too early.

- The panel stops once to ask the one question a regulator would ask: before 19 November, did anyone get an alert that the backup was public? No. That one answer sets the clock.

- The five then challenge each other’s work without knowing whose it is. Even the Contrarian concedes that notifying promptly is legally sound.

- The memo comes back: both deadlines counted from the moment she learned, every option compared, the dissent on the record, and every source listed, down to her own files.

## What does the law require after a data breach, in the EU and in Florida?

Two clocks, both started the moment the company learned. In the EU, the supervisory authority within seventy-two hours, here the CNIL, by Sunday 22 November at 23:40 Paris time; the people concerned without undue delay, because passport data in a public, unencrypted backup is a high-risk case. In Florida, the people concerned within thirty days, by 19 December, and the Department of Legal Affairs within the same thirty days.

The European clock is shorter, that is all. Nothing stops a company from telling its Florida customers at the same time as its EU customers, and in practice most companies send all customer notices at once. The memo gives the legal deadline for each, not an instruction to wait.

## What did the panel answer, and what did the Contrarian argue?

Notify now. File with the CNIL within seventy-two hours. Tell EU customers without undue delay. In Florida, notify within thirty days. Investigate in parallel, not first: a short forensic sprint helps accuracy, but not past the seventy-two-hour filing.

The Contrarian argued for waiting: Article 33 contains an exception for breaches unlikely to result in a risk, passport data does not automatically mean a high risk under Article 34, and a short forensic sprint could reduce inaccurate or unnecessarily alarming communications. The panel answered, and the Contrarian conceded that prompt notification is legally sound, while keeping its view on timing. That view is in the memo, in the section called Dissenting view, with the facts that would make it right: reliable evidence that the downloads did not happen, or that the exposed data was narrower than reported. Counsel walks into the CEO’s office with the answer and the objection already tested.

## Why a deliberation, and not a lookup?

Everyone knows the seventy-two hours. What takes time at 5:40 p.m. on a Thursday is the rest: which entity holds which customers, which law applies to each, when the clock started, what to tell the CEO who wants to wait, and a memo with sources that can go to the board. For a single statute, Pilot5 Legal’s statutory lookup quotes the text in seconds, free. For two jurisdictions, a clock to set and an objection to answer, the deliberation is the right tool: about twenty minutes, a few dollars.

## Questions in-house counsel ask us

**Who do we notify after a data breach, and by when?** It depends on where the people concerned are and which company holds their data. For EU customers: the supervisory authority within 72 hours of becoming aware, and the people concerned without undue delay when the risk is high. For Florida customers: the people concerned within 30 days, and the Florida Department of Legal Affairs within 30 days when 500 or more Florida residents are affected. Both clocks start when the company learns of the breach.

**What are the data breach notification deadlines under the GDPR and Florida law?** GDPR: 72 hours to the supervisory authority (Article 33), without undue delay to the people concerned when the risk is high (Article 34). Florida Statute 501.171: no later than 30 days to the people concerned and, above 500 Florida residents, to the Department of Legal Affairs. The film shows both deadlines computed from the moment of awareness.

**When does the 72-hour clock start?** When the company becomes aware of the breach with a reasonable degree of certainty. In the film, the panel asks whether anyone received an alert before 19 November; the answer, no, sets the clock at 19 November, 5:40 p.m. Eastern, 11:40 p.m. Paris.

**Do we have to wait for forensics before notifying?** No. The GDPR allows notification in phases: file what you know within 72 hours, complete it as the investigation goes on. The memo’s recommendation is to investigate in parallel, not first.

**Does Pilot5 Legal work for a law firm advising the company?** Yes. The question, the brief and the memo are the same whether in-house counsel or outside counsel puts the case. The memo is written to be sent: to the CEO, to the board, to the regulator’s file.

**Where do the sources come from, and are the citations checked?** From official sources: the GDPR, the EDPB guidelines on breach notification, the Florida statute, and the documents counsel attached. The memo lists every source it relied on, down to her own files, and marks what it could check against the source text.

**Is this legal advice?** No. Pilot5 Legal is a legal research and decision-support tool. Counsel reads the memo, opens the sources that matter, decides, and notifies.

## What we are not claiming

No tool replaces the lawyer’s judgment on a breach, and no memo knows what the forensics will find. Pilot5 Legal deliberates, sets the clock from the facts counsel gives it, shows its sources and keeps the argument against. Counsel reviews the sources that matter most to the case, and signs. Verification remains the user’s responsibility.

## Sources

- Regulation (EU) 2016/679 (GDPR), Articles 33 and 34: [EUR-Lex](https://eur-lex.europa.eu/eli/reg/2016/679/oj)

- EDPB Guidelines 9/2022 on personal data breach notification under the GDPR: [edpb.europa.eu](https://www.edpb.europa.eu/our-work-tools/our-documents/guidelines/guidelines-92022-personal-data-breach-notification-under-gdpr_en)

- Florida Statutes, section 501.171, Security of confidential personal information: [leg.state.fl.us](https://www.leg.state.fl.us/statutes/index.cfm?App_mode=Display_Statute&URL=0500-0599/0501/Sections/0501.171.html)

*A real Pilot5 run on a test case, November 2026; screens simplified for the film. All companies, people and facts are fictional. Pilot5 Legal is a legal research and decision-support tool. It does not provide legal advice. Outputs must be reviewed by a qualified professional before use.*

## Transcript of the film

Counsel: IT just confirmed a breach. Someone downloaded a backup of our booking database: names, dates of birth, passport numbers. Nine thousand customers in the EU, two thousand in Florida. Who do we notify, and by when?

Narrator: Two companies, two laws, and the clocks are already running. She puts it to Pilot5 Legal, with IT’s report and the customer figures. Pilot5 reads her files first, then asks only what they don’t say. Which law governs each company?

Counsel: Paris: French law and the GDPR. Miami: Florida law.

Narrator: What is the strongest fact against you?

Counsel: The backup sat unencrypted in a public cloud folder for thirteen days. We only learned of it today, at five forty.

Narrator: Do you already have a view?

Counsel: Notify the regulator within seventy-two hours. But our CEO wants to wait for forensics.

Narrator: Then five AI models, from five different companies, work the case separately. Three say notify now. The Contrarian argues the bigger risk is notifying too early. Before the nineteenth of November, did anyone get an alert that the backup was public?

Counsel: No. Nothing before today.

Narrator: That one answer sets the clock. Then they challenge each other’s work, without knowing whose it is. Even the Contrarian concedes that notifying promptly is legally sound. Notify now. File with the CNIL within seventy-two hours: by Sunday the twenty-second, at eleven forty at night, Paris time. Tell EU customers without undue delay. In Florida, notify by the nineteenth of December. Investigate in parallel, not first. The Contrarian still disagrees. Their view is kept. What comes back is a memo she can work from: both deadlines, counted from the moment she learned; every option compared; the dissent on the record; and every source listed, down to her own files. Two jurisdictions, one answer, in about twenty minutes, for a few dollars. You review, and notify.