A mid-sized SaaS company detects unusual database activity at 02:40 on a Tuesday. By 06:00, the security team has confirmed that customer records were accessed. At 09:00, the first customer asks whether their data is safe, and at noon a journalist emails three questions and a deadline.
The technical response is running well, and legal has started counting hours. Nobody has decided what to tell customers, regulators or the press, or in which order. Most incident response playbooks cover containment in detail and leave communication to a single line that reads "inform stakeholders". Disclosure needs the same planning.
Four Clocks Start At Once
One incident starts several regulatory clocks, each with its own starting point. In the EU, GDPR Article 33 requires the controller to notify the supervisory authority "without undue delay and, where feasible, not later than 72 hours after having become aware" of a personal data breach; a later notification has to carry the reasons for the delay. Under Article 34, affected individuals are informed without undue delay when the breach is likely to put them at high risk. The UK GDPR keeps the same 72-hour deadline.
In the United States, a public company files Form 8-K Item 1.05 within four business days of determining that a cybersecurity incident is material, so that decision itself needs an owner and a time stamp. In Canada, PIPEDA requires a report to the Privacy Commissioner when a breach creates a real risk of significant harm, notification of affected individuals as soon as feasible, and breach records kept for two years.
A regulatory notification stays confidential on paper. In practice, the chance that the story gets out grows the moment it is filed, so the public statement is planned for the same day as the first notification. The stakes are known: IBM's Cost of a Data Breach Report 2026 puts the global average cost of a breach at 4.99 million USD, a 12 percent increase on the previous year.
Hour 0 to 24: The Holding Statement
The first statement goes out before the investigation is complete, so it says four things and nothing else: what the company knows, what it does not yet know, what it has done, and when the next update follows. It gives no number of affected people until that number is verified; a corrected figure costs more trust than a delayed one.
One named spokesperson owns every quote, in every market, for the whole incident. B2Press's Press Release Content Analysis 2026, covering 2,150 distributions in 83 countries and 32 languages between May 2025 and June 2026 and the 125,412 news items they generated, found that releases with a spokesperson quote received 41 percent more coverage in the global market than releases without one. In a crisis the named spokesperson also carries the credibility of the news; a statement with nobody behind it reads as evasion.
Hour 24 to 72: Regulators, customers, press, in that order
The order of disclosure follows one rule: nobody learns about the incident from a party further down the list. Regulators first, directly affected customers next through the channel they already use, employees before it appears in the media, and the general public last. "Last" here means the same day.
A statement published in one country is read everywhere within minutes. If the Canadian office has issued a notice while German customers see silence, they draw their own conclusion, and so does the German regulator. The practical answer is one master text, a localised version for each market, and a single release time. B2Press, an online PR platform that distributes press releases in 75+ countries and 24 languages, exists for that kind of simultaneous release in the local language of each market.
Writing the Release Itself
The headline shapes the perception of an event. If customer data was taken, it says data breach, and the word "incident" is kept for cases where that is all the company knows. Journalists notice the softer word, and the softer word becomes the story.
Every number comes from the forensic team; anything still estimated is labelled as such or left out. One paragraph tells affected people what to do now: reset passwords, watch for the phishing that follows this kind of theft, enrol in the monitoring service the company is paying for. The release closes with a short company description, because a reader who meets the company for the first time in a breach story has no other context.
After 72 hours: Keep the Cadence
The holding statement promised an update, so it goes out at the promised time even if the only news is that the investigation continues. A second release follows the end of the forensic work with the confirmed scope, the cause in plain terms and the measures taken. A closing statement marks the return to normal operations.
Markets that received the first statement receive every later one, in the same language and through the same channel. Using country-specific press release packages for each affected market keeps that repetition manageable when the communications team is at its most stretched.