# Email clients about a security breach: template and timing

> Copy-paste email templates for telling customers your website was breached: what to say first, what to leave out, and which deadlines start when you find out.

Canonical: https://red.run.cloud/learn/email-customers-about-a-security-breach-template · By Timothy Lindblom · Published 2026-11-02 · Updated 2026-11-02

Send customers a short, factual email as soon as you know their data may be involved. Say what happened, which data, what you have done, what they should do and who to contact. State what you do not yet know and give a date for the next update. Do not write that data was unaffected until you hold evidence.

| Fact | Detail | Source |
|---|---|---|
| Who it is for | Site owners, shops and agencies who run a site that holds customer data | this page |
| Authority deadline (EU and UK) | 72 hours after becoming aware, where feasible | [GDPR Article 33](https://eur-lex.europa.eu/eli/reg/2016/679/oj), [ICO](https://ico.org.uk/for-organisations/report-a-breach/personal-data-breach/personal-data-breaches-a-guide/) |
| Individuals (EU and UK) | Without undue delay, when the breach is likely to be high risk | [ICO](https://ico.org.uk/for-organisations/report-a-breach/personal-data-breach/) |
| Individuals (New York) | Within thirty days of discovery | [NY GBS 899-aa](https://www.nysenate.gov/legislation/laws/GBS/899-AA) |
| Individuals (Florida) | No later than 30 days after determination of a breach | [Fla. Stat. 501.171](https://www.flsenate.gov/Laws/Statutes/2024/501.171) |
| Content the FTC expects | How it happened, what was taken, what you did, what people should do, contact details | [FTC guide](https://www.ftc.gov/business-guidance/resources/data-breach-response-guide-business) |
| Checked | 24 October 2026 | this page |

This page gives you wording and an order of work. Laws differ by country and by US state, and the one that applies is set by where your customers live. If your contract or your customers' data makes you a processor, read the processor section below before you send anything.

## What do I do before I write the email?

Work out four facts first. An email written before you know them tends to promise things you later retract.

1. **What the attacker could reach.** A defaced page, a planted script or an unfamiliar admin account can each sit next to a customer table. List what that account, file or access could read.
2. **When it started and when you knew.** Several deadlines run from the day you became aware, so write that date and time down now.
3. **Which customers and which data.** Names and emails, order history, addresses, passwords, payment details and uploaded documents carry different advice for the reader.
4. **What you have stopped.** Credentials changed, the hole closed, logs kept.

If you are still working out whether the site was hit at all, [the signs of a hacked website](/learn/how-to-tell-if-your-website-is-hacked) come first, and the [first 24 hours checklist](/learn/small-business-site-hacked-first-24-hours) covers the rest of the clean-up. Do not wipe evidence while you do this. The [FTC](https://www.ftc.gov/business-guidance/resources/data-breach-response-guide-business) says not to destroy forensic evidence during investigation and fix, and [CISA](https://www.cisa.gov/stopransomware/ransomware-guide) says to take system images and keep logs before rebuilding. Credentials come next: the FTC notes a system stays exposed until the credentials are changed, even after the attacker's tools are gone. Our [walkthrough for rotating keys and passwords](/learn/rotate-secrets-after-a-breach-guide) gives the order.

<figure class="ln-figure">
<svg viewBox="0 0 720 150" role="img" aria-labelledby="flow-title" xmlns="http://www.w3.org/2000/svg" font-family="Geist, sans-serif">
<title id="flow-title">Order of work before and after the customer email</title>
<rect x="6" y="35" width="124" height="80" rx="12" fill="#FFF1EF" stroke="#EAD3CF"/>
<text x="68" y="70" text-anchor="middle" font-size="13" font-weight="600" fill="#1A0F0F">Preserve</text>
<text x="68" y="90" text-anchor="middle" font-size="12" fill="#655553">logs and images</text>
<rect x="154" y="35" width="124" height="80" rx="12" fill="#FFFFFF" stroke="#EAD3CF"/>
<text x="216" y="70" text-anchor="middle" font-size="13" font-weight="600" fill="#1A0F0F">Scope</text>
<text x="216" y="90" text-anchor="middle" font-size="12" fill="#655553">data and dates</text>
<rect x="302" y="35" width="124" height="80" rx="12" fill="#FFFFFF" stroke="#EAD3CF"/>
<text x="364" y="70" text-anchor="middle" font-size="13" font-weight="600" fill="#1A0F0F">Decide</text>
<text x="364" y="90" text-anchor="middle" font-size="12" fill="#655553">who must be told</text>
<rect x="450" y="35" width="124" height="80" rx="12" fill="#C70500"/>
<text x="512" y="70" text-anchor="middle" font-size="13" font-weight="600" fill="#FFFFFF">Send</text>
<text x="512" y="90" text-anchor="middle" font-size="12" fill="#FFFFFF">first factual note</text>
<rect x="598" y="35" width="116" height="80" rx="12" fill="#FFFFFF" stroke="#B00500"/>
<text x="656" y="70" text-anchor="middle" font-size="13" font-weight="600" fill="#1A0F0F">Update</text>
<text x="656" y="90" text-anchor="middle" font-size="12" fill="#655553">on the date given</text>
<path d="M132 75 H152 M280 75 H300 M428 75 H448 M576 75 H596" stroke="#B00500" stroke-width="2" fill="none"/>
</svg>
<figcaption>Preserve, scope and decide come before the first email. The email promises an update date, and the update keeps that promise.</figcaption>
</figure>

## Who has to be told, and by when?

Three groups can have a claim on you, and each has its own clock. The email to customers is only one of them.

| Who | When | Source |
|---|---|---|
| Data protection authority (EU, UK, Sweden) | Within 72 hours of becoming aware, where feasible, unless a risk to people is unlikely. Late notice needs reasons | [GDPR Art. 33](https://eur-lex.europa.eu/eli/reg/2016/679/oj), [IMY](https://www.imy.se/en/organisations/data-protection/this-applies-accordning-to-gdpr/personal-data-breaches/) |
| Individuals (EU and UK) | Without undue delay when the breach is likely to be high risk, in clear and plain language | [GDPR Art. 34](https://eur-lex.europa.eu/eli/reg/2016/679/oj), [ICO](https://ico.org.uk/for-organisations/report-a-breach/personal-data-breach/) |
| Residents of New York | Within thirty days of discovery, plus state agencies | [NY GBS 899-aa](https://www.nysenate.gov/legislation/laws/GBS/899-AA) |
| Residents of Florida | No later than 30 days after determination; the state department when 500 or more are affected | [Fla. Stat. 501.171](https://www.flsenate.gov/Laws/Statutes/2024/501.171) |
| California Attorney General | A sample notice when more than 500 California residents are notified | [California AG](https://oag.ca.gov/privacy/databreach/reporting) |
| Police, FBI or CISA (US) | Report the incident; CISA lists its report page and the FBI field office | [CISA](https://www.cisa.gov/stopransomware/ransomware-guide) |

Checked 24 October 2026. Statutes get amended, and these rows are examples of the pattern and leave out many laws. Two points hold across them. Several clocks run from the day you became aware or determined a breach, and the ICO says to [report early and update later](https://ico.org.uk/for-organisations/report-a-breach/personal-data-breach/) instead of waiting for a full picture.

The FTC adds one more rule for US readers: ask your law enforcement contact about the timing of notification so it does not impede the investigation.

## What must a breach email contain?

Put the following in this order. Customers read the opening lines and forward the rest.

1. What happened, in one plain sentence.
2. Which kinds of data were involved, and which were not, as far as you know.
3. When it happened and when you found out.
4. What you have done.
5. What the reader should do, specific to the data type.
6. A named contact, a real address or phone line, and the date of the next update.

The [FTC guide](https://www.ftc.gov/business-guidance/resources/data-breach-response-guide-business) lists the same elements, and says not to make misleading statements and not to withhold key details. The [ICO](https://ico.org.uk/for-organisations/report-a-breach/personal-data-breach/personal-data-breaches-a-guide/) asks for a contact point, the likely consequences, the measures taken or proposed, and practical advice such as password resets. The GDPR calls for [clear and plain language](https://eur-lex.europa.eu/eli/reg/2016/679/oj) in the message to individuals.

## Which template should I send?

Pick by what you know today, not by how the news cycle feels.

| What you know | State | Template |
|---|---|---|
| Personal data was accessed or may have been, and you do not yet know how much | Detected, scope open | 1: first notice |
| Your review confirms which data and which customers | Confirmed by owner evidence | 2: full notification |
| An attacker was on the site, but the access could not reach customer data, shown by evidence | Detected, no data path found | 3: incident notice, no data involved |
| Time has passed since an earlier email | Any | 4: follow-up |

## Template 1: first notice, scope still open

Use this when you have reason to think personal data may be involved and the review is running. It tells the customer early and does not claim more than you know.

> **Subject:** Security incident at [company]: what we know so far
>
> Hello [first name], on [date] we found that someone gained unauthorised access to [the website / our online store]. We are writing now because information about you may have been involved: [kinds of data, for example names, email addresses and order history]. We do not yet know whether it was copied.
>
> What we have done: we closed the access we found on [date], changed the passwords and keys that could have been used, and kept the logs for review. What we do not know yet: how many customers are affected and whether payment details were reachable. We will write again by [date], whatever we have found.
>
> What you can do now: be careful with emails that mention your order or account, and do not click links in a message that asks you to log in. If you reused your [company] password elsewhere, change it there. Questions go to [named person, address, phone].

## Template 2: full notification, scope confirmed

Send this when the review has named the data and the customers. Open with the facts, not a reassurance.

> **Subject:** Notice of data breach affecting your [company] account
>
> Hello [first name], we are writing to tell you that between [start date] and [end date], an unauthorised person had access to [system]. We found it on [date] and stopped it on [date]. The information involved for your account was: [exact list]. The information that was not involved: [list, only what the review confirmed].
>
> We have [fixed the hole, replaced credentials, engaged a specialist, told the authority on date]. We do not know of any misuse so far, from the review of [logs and dates reviewed]. That is a statement about what we examined, and we will tell you if it changes.
>
> What to do: [step for each data type: change your password; watch your card statement and tell your bank; treat messages about your order with care]. Contact: [named person, address, phone, hours]. We will write again by [date].

## Template 3: incident notice, no customer data involved

Use this for a defaced page, a planted script or a hidden admin account where you hold evidence that customer data was out of reach. Write down how you decided.

> **Subject:** [company] website: an incident we found and fixed
>
> Hello [first name], on [date] we found that someone had changed [what: pages, a script, an admin account] on our website. We removed it on [date]. We reviewed [the database access logs and account permissions] for [date range] and found that the access could not reach customer records. We will tell you if that conclusion changes. No action is needed from you. Contact: [named person, address].

The test for this email is the evidence in the sentence. If you cannot name what you reviewed, send Template 1 instead. The ICO's [worked cases](https://ico.org.uk/for-organisations/report-a-breach/personal-data-breach/personal-data-breach-examples/) include credential theft that exposed customer data, where both the regulator and the clients were told, and a compromised account used for customer communications was part of the reasoning.

## Template 4: the follow-up

Send it on the date you promised, even when nothing has changed. A missed date reads as a second incident.

> **Subject:** Update on the incident at [company], [date]
>
> Hello [first name], an update to our email of [date]. Since then we have [what was reviewed, what was found]. This changes the picture in one way: [what changed, or "nothing has changed"]. Still open: [list]. Next update: [date]. Contact: [named person].

## What phrases should I leave out?

Customers have read many breach emails. Certain phrases signal that a company is managing perception.

| Avoid | Why | Write instead |
|---|---|---|
| "We take security seriously" | The reader has just been told otherwise | The steps you took, with dates |
| "A sophisticated attack" | Unknown until investigated; reads as an excuse | "Someone gained access using [credential / outdated component], as far as we know" |
| "No evidence of misuse" | True only if you looked | "We reviewed [logs] for [dates] and found [result]" |
| "Your data was not affected" | Cannot be known before scope is confirmed | The list of what was and was not involved, per your review |
| "Out of an abundance of caution" | Hides that the risk is real | "Your information may have been involved" |
| "Resolved" with no date | A hole closed and a password changed are different facts | "Access closed on [date]; credentials changed on [date]" |

Do not name a cause you have not confirmed. The FTC tells businesses to describe what they know about the compromise, not to speculate. For a third-party cause, such as a plugin or an agency login, say only what the evidence shows. If a service provider says the fault is fixed, the FTC says to [verify that they really fixed it](https://www.ftc.gov/business-guidance/resources/data-breach-response-guide-business). Our page on [patching duties split between host, agency and owner](/learn/who-is-responsible-for-patching-my-website) explains who owns which layer.

<div class="ln-selftest">
<h3>Am I affected? Which email can I send right now</h3>
<p>A scan from outside cannot see your database, your logs or which accounts were used. The state of your email depends on evidence you hold.</p>
<ol>
<li><span class="ln-state ln-state-detected">Detected</span> <strong>You found unauthorised access, a planted file or a rogue admin, and personal data may have been reachable.</strong> Send Template 1 now and keep the logs.</li>
<li><span class="ln-state ln-state-unknown">Unknown</span> <strong>Something looks wrong but you cannot yet say what the access could read.</strong> Do not send a no-impact email. Scope first, then choose Template 1 or 3.</li>
<li><span class="ln-state ln-state-confirmed">Confirmed by owner evidence</span> <strong>Your review names the data, the customers and the dates.</strong> Send Template 2, and tell the authority if the law that covers you requires it.</li>
</ol>
<p>No scan, ours included, moves you from "unknown" to "confirmed".</p>
</div>

## What if my agency or host had the breach, not me?

Then your first duty is to find out what they hold about your customers. The GDPR says a processor tells the controller [without undue delay](https://eur-lex.europa.eu/eli/reg/2016/679/oj) after becoming aware. Sweden's [IMY](https://www.imy.se/en/organisations/data-protection/this-applies-accordning-to-gdpr/personal-data-breaches/) says the controller stays responsible for reporting even when a processor had the breach. Under [Florida law](https://www.flsenate.gov/Laws/Statutes/2024/501.171) a third-party agent tells the covered entity within 10 days of determining a breach.

Ask the provider these questions in writing:

> On what date did you become aware of the incident affecting **[our site / our customers' data]**? Which of our customers' data categories could the access reach, and for which dates? What logs do you hold, and have they been preserved? What did you change, and at what time? Who is your named contact for the next update?

If you are the agency, and the client is the controller (see [who carries the liability when a client site is hacked](/learn/client-website-hacked-who-is-liable-contract-clauses)), send them the facts first and let them decide the customer wording. Our [ready-made client notification emails](/learn/are-we-affected-client-email-templates) cover the portfolio side. For the log review itself, the [first-hours response checklist](/learn/website-incident-response-playbook) lists what to preserve and rotate.

## How should I send it?

- [ ] Send one email per customer from a named person at a real address that can receive replies, not a no-reply address.
- [ ] Do not put the notice in a newsletter, a footer or a link to a blog post. Send the facts in the body.
- [ ] Do not ask the customer to click a link to log in. Breach emails are a favourite cover for phishing, so give the instruction in words.
- [ ] Put a plain version of the notice on your website for customers with no email on file.
- [ ] Keep a copy of every email, the send time and the list it went to.
- [ ] Write down the date you became aware, the date you decided, and the reason you did or did not notify each group.

The GDPR requires controllers to [document every breach](https://eur-lex.europa.eu/eli/reg/2016/679/oj), including the facts, effects and the action taken, and the ICO says to document and justify a decision not to report. Keep that record even if you choose not to notify. More guides like this sit with [the other incident response pages](/learn/topics/incident-response). The [NCSC](https://www.ncsc.gov.uk/collection/incident-management) says a well-prepared response helps limit public and media fallout, and its [small business guide](https://www.ncsc.gov.uk/collection/small-business-guidance--response-and-recovery) gives a 24-hour number, 0300 123 2040, for an active attack in the UK.

## Where does a scan fit?

After the incident, an outside view helps you see what your site shows to everyone. The Red free scan reads the stack your site serves and matches each version to known vulnerabilities. One scan per domain, no card. It is a lookup: it can say a version is affected, not whether your setup is exposed, and it cannot see your logs or what an attacker reached. See [the limits of a lookup-only scan](/learn/what-an-external-website-scan-cant-prove). Domain ownership is proved with one DNS TXT record before anything runs. The full scan costs $100 per scan and is ordered from your dashboard once the free scan is done. Neither gives you a "confirmed" for the email. That comes from your logs and your review.

## Questions people ask

### How soon do I have to tell customers my website was breached?

It depends on the law that covers your customers. Under the GDPR the authority is told within 72 hours where feasible, and individuals without undue delay when the risk to them is high. Some US states set a fixed limit, such as 30 days in New York and Florida. Ask a lawyer which laws apply, and send a first factual note early.

### What should a breach notification email say?

What happened, which kinds of data were involved, when, what you have done, what the customer should do, and who to contact. The FTC also says to describe what you know and avoid speculation. Add the date of your next update so the email does not read as the last word.

### Do I have to email customers if I am not sure their data was taken?

If the evidence says personal data may have been involved, send a short note saying so and say what you do not yet know. Silence while customers read the news is the worse option. If you hold no sign that customer data was reachable, you may not owe a notice. Write down why you decided that.

### Can I just say we take security seriously and no data was misused?

Avoid it. 'No evidence of misuse' is only true if you looked, and customers read it as a dodge. Say which logs and data you reviewed, for which dates, and what you found. If the review is not finished, say that.

### My agency or host had the breach, not me. Who emails the customers?

Usually the business that owns the customer relationship, which the GDPR calls the controller. A processor must tell the controller without undue delay. In Sweden's IMY guidance the controller stays responsible for reporting even when a processor had the breach. Your contract and a lawyer settle who sends what.

### Do I need to email customers about a breach that only defaced my site?

Only if personal data was reachable from what the attacker got to. A defaced page, a planted script or a hidden admin account can all sit next to a customer database. Find out what that account or file could read before you decide the notice is not needed.


## Sources

1. [FTC: Data Breach Response, A Guide for Business](https://www.ftc.gov/business-guidance/resources/data-breach-response-guide-business): What a notice should contain, describing what you know instead of speculating, evidence preservation, verifying a service provider's fix. Read 24 October 2026.
2. [Regulation (EU) 2016/679 (GDPR), Articles 33 and 34 (EUR-Lex)](https://eur-lex.europa.eu/eli/reg/2016/679/oj): 72 hours to the authority where feasible, processor to controller without undue delay, clear and plain language for individuals. Article text read via a reproduction on 24 October 2026.
3. [ICO: personal data breaches, a guide](https://ico.org.uk/for-organisations/report-a-breach/personal-data-breach/personal-data-breaches-a-guide/): Report within 72 hours where feasible; tell individuals when high risk is likely; what the message must contain. Read 24 October 2026.
4. [ICO: telling the ICO and individuals about a breach](https://ico.org.uk/for-organisations/report-a-breach/personal-data-breach/): Report early and update later; individuals must be told without undue delay when risk is high. Read 24 October 2026.
5. [ICO: personal data breach examples](https://ico.org.uk/for-organisations/report-a-breach/personal-data-breach/personal-data-breach-examples/): A worked case where credential theft exposed customer data and both the ICO and clients were told. Read 24 October 2026.
6. [IMY (Sweden): personal data breaches](https://www.imy.se/en/organisations/data-protection/this-applies-accordning-to-gdpr/personal-data-breaches/): 72-hour rule; the controller stays responsible for reporting even when a processor had the breach. Read 24 October 2026.
7. [New York General Business Law section 899-aa](https://www.nysenate.gov/legislation/laws/GBS/899-AA): Notice to residents within thirty days of discovery; required contents; notice to state agencies. Read 24 October 2026.
8. [Florida Statutes section 501.171](https://www.flsenate.gov/Laws/Statutes/2024/501.171): Notice no later than 30 days after determination; a third-party agent tells the covered entity within 10 days. Read 24 October 2026.
9. [California Attorney General: data security breach reporting](https://oag.ca.gov/privacy/databreach/reporting): A sample notice goes to the Attorney General when more than 500 California residents are notified. Read 24 October 2026.
10. [CISA: StopRansomware guide, response checklist](https://www.cisa.gov/stopransomware/ransomware-guide): Who to engage and report to; take system images and preserve logs before rebuilding. Read 24 October 2026.
11. [UK NCSC: small business guidance, response and recovery](https://www.ncsc.gov.uk/collection/small-business-guidance--response-and-recovery): Defines an incident and points to the response and recovery guide; reporting number for active attacks. Read 24 October 2026.
12. [UK NCSC: incident management](https://www.ncsc.gov.uk/collection/incident-management): A prepared response limits public and media fallout. Read 24 October 2026.
