Other Articles
- Getting Started with the Organization Setup
- How to add employee details step by step?
- Getting Started with Policies
- Getting Started with Trainings
- Getting Started with Vendor Management
- Risk Module – User Help Guide
- Pentest Flow – Adding and Managing Penetration Test Findings
- Controls Module – Step-by-Step User Guide
- Privacy and Data Governance: A Comprehensive Guide for Modern Organizations
- Guide to Hiring Assessment: Referral-Based and Standard Hiring
- Guide to Background Verification: Referral-Based and Standard Hiring
- Employee Performance Review: A Complete Guide
- Succession Planning: How to Prepare Your Business for Key Employee Changes
- Incident Response Plan: Steps to Prepare Your Business for Security Incidents
- Business Continuity Planning: A Practical Guide for Startups
- Guide to Vendor Risk Assessment and Management
- Guide to Vendor Questionnaire: Assessment and Due Diligence
Data Breach Communication: What Should You Tell Affected Customers?
5 November, 2026
Introduction
A company discovers that an employee's account has been compromised. The investigation suggests that customer email addresses and contact details may have been accessed. While the technical team works to secure the account, the company faces another decision: who needs to be informed, what should the message say, and how quickly should it be sent?
Data breach communication is how a company informs affected customers, employees or other individuals about a breach involving their information. It explains what happened, what information may have been exposed, what the company is doing and what recipients can do to protect themselves.
The challenge is to communicate clearly without making assumptions or sharing details that have not been verified.
When should a company communicate a data breach?
A data breach can involve personal information being accessed, disclosed, altered, lost or exposed without authorization. It may result from a cyberattack, compromised account, configuration error or human mistake.
Common examples include:
- Customer records exposed through a misconfigured cloud storage folder.
- An attacker accessing customer correspondence through a compromised employee account.
- Personal information sent to an unintended recipient.
- A ransomware incident involving the theft of customer or employee information.
Not every security incident requires notifying every customer. The company should first establish what information may have been affected, who could be impacted and which legal or contractual requirements apply.
What should the communication include?
A useful data breach communication should answer five questions:
- What happened? Describe the incident and when it was discovered, if known.
- What information was involved? Identify the categories of information that may have been affected.
- What does this mean for the recipient? Explain realistic risks without exaggerating or minimizing the impact.
- What has the company done? Describe the actions taken to contain the incident, investigate it and prevent further exposure.
- What should the recipient do? Provide relevant protective steps and a contact for questions.
If the investigation is ongoing, explain what is still being examined. Do not claim that information was misused—or that it was not misused—unless the findings support that statement.
How should a company prepare and send the communication?
A small business does not need a complicated approval structure, but it should know who is responsible for each decision.
- Establish the facts. Work with the technical or incident response team to confirm what happened, when it was detected, which systems were affected and what information may have been exposed. Keep confirmed findings separate from assumptions.
- Identify affected recipients. Determine which customers, employees, partners or other individuals may be affected. Check customer agreements and data processing agreements for additional communication requirements.
- Prepare the message. Use plain language and focus on what recipients need to know. Avoid unnecessary technical explanations. Include protective steps only when they are relevant to the information involved.
- Review and approve. Have the appropriate security, privacy, management and legal representatives review the message. Confirm that the facts, recipient list and communication method are correct. Assign a clear approval owner.
- Send and retain a record. Use an appropriate communication channel. Keep a copy of the final message, recipient list, date and time sent, delivery information and follow-up correspondence.
Global data breach notification requirements
A company serving customers in multiple countries may need to comply with more than one data breach notification law. Requirements depend on where affected individuals are located, the information involved and the circumstances of the breach.
Some important regulations include:
| Country / Region | Regulation | Key requirement |
|---|---|---|
| European Union | GDPR | Notify the supervisory authority within 72 hours where the breach is likely to pose a risk to individuals. Inform affected individuals without undue delay if there is a high risk. |
| United Kingdom | UK GDPR | Similar to GDPR: report qualifying breaches within 72 hours, where feasible, and inform individuals if there is a high risk. |
| United States | State breach notification laws | All 50 states have notification laws. Requirements and deadlines vary. HIPAA-covered organisations have additional requirements for breaches involving protected health information. |
| Canada | PIPEDA | Report and notify affected individuals as soon as feasible when there is a real risk of significant harm. |
| Australia | Privacy Act – NDB Scheme | Notify the regulator and affected individuals as soon as practicable when an eligible data breach occurs. |
| Singapore | PDPA | Notify the regulator within three calendar days after determining that a breach is notifiable. Inform affected individuals where required. |
| India | CERT-In Directions and DPDP Rules | Report specified cyber incidents to CERT-In within six hours. DPDP Rule 7 provides for individual and Board notification but is scheduled to take effect on 13 May 2027. |
These are high-level summaries, not deadlines that apply to every incident. For example, the GDPR's 72-hour period applies to qualifying regulator notifications, not automatically to every customer communication. HIPAA's 60-day limit applies to specified breaches involving unsecured protected health information.
Before sending a communication, identify the affected individuals, determine which laws apply and check the relevant deadlines. Customer contracts may also contain additional reporting obligations.
Official references:
- European Commission – Data protection obligations
- UK ICO – Personal data breaches
- US FTC – Data breach response guide
- US HHS – HIPAA Breach Notification Rule
- Canada – PIPEDA
- Australia OAIC – Notifiable Data Breaches
- Singapore PDPC – Data Breach Notification Guide
- India CERT-In Directions
- India MeitY – DPDP Rules, 2025
Data Breach Communication Template
Preparing a message from scratch during an incident can lead to delays and inconsistent communication. A reusable template gives the team a starting point while allowing the message to be adapted to the incident and applicable requirements.
The downloadable template includes:
- Incident description and timeline.
- Information that may have been affected.
- Actions taken by the company.
- Recommended steps for affected individuals.
- Contact details for questions and assistance.
- An internal review checklist to complete before sending.
Download the Data Breach Communication Template (.docx)
The template is a general communication aid, not a legally compliant notice for every jurisdiction. Verify the incident details, adapt the content to the affected recipients and obtain appropriate approval before sending.
A company does not need a dedicated communications department to handle a breach responsibly. It needs accurate incident information, a designated approval owner, a reliable way to reach affected individuals and a record of what was communicated. These arrangements are easier to establish before an incident than while customers are waiting for answers.