← All articles

What to Tell Customers After Your Website Was Hacked

A small-business owner preparing a clear update for customers after a website security incident

A website hack can create two urgent problems: securing your site and deciding what to tell the people who use it. That second question can feel difficult, especially when you’re still working out what happened.

The right message depends on the facts. You don’t need to guess or share technical details you haven’t confirmed. You do need to take possible privacy obligations seriously, communicate clearly, and give affected customers useful next steps.

Do I have to tell customers if my website was hacked?

It depends on where your business operates, where affected customers live, what personal information may have been involved, the risk to those people, and what your contracts require. A hack alone does not automatically mean customer data was accessed. But if personal information may have been exposed, notification rules could apply.

Many jurisdictions require organizations to notify affected people in certain circumstances. The rules may have thresholds, exceptions, or different requirements for notifying privacy regulators. Contracts with payment providers, booking platforms, suppliers, or other service providers may also set their own expectations.

For example, Canada’s Office of the Privacy Commissioner explains when organizations covered by federal privacy law need to report a breach and notify affected individuals. The UK’s Information Commissioner’s Office provides guidance for organizations dealing with personal data breaches. These are examples, not a complete guide to every place your business or customers may be located.

This is not legal advice. If personal information may have been involved, get a qualified professional’s opinion rather than relying on a general article. The Hack Remover’s legal associate can help if you need support finding the right next steps.

Should you tell customers if you’re not legally required to?

Legal requirements are only one part of the decision. Customers may need to know if they received suspicious email from your domain, if their account or booking could be affected, or if an incident disrupted an order.

Silence can also create a trust problem. If customers discover the issue through a browser warning, a strange message, or a public notice before hearing from you, they may wonder why you didn’t contact them. On the other hand, sending an alarming message before you have reliable information can create confusion. Aim for a prompt, factual update based on what you know, and get professional guidance about who needs to receive it.

If the hack affected your online store, start with the immediate response steps in our guide to what to do first after a WordPress store is hacked. That can help you address the site while you assess the customer impact.

What should I say to customers after a hack?

A useful message is direct, calm, and specific. It should separate confirmed facts from what is still under investigation. Customers don’t need a technical incident report, but they do need enough information to understand whether they might be affected and what they can do.

Include these points where relevant:

  • What happened: Describe the security issue in plain language, and say when it occurred or when you discovered it if you know.
  • What information may have been involved: Be clear about the categories you have confirmed or are investigating. Don’t claim data was safe if you haven’t established that.
  • What you’ve done: Explain the practical actions taken, such as temporarily disabling a feature, securing the website, or bringing in specialists.
  • What customers should do: Give steps that fit the situation. If accounts were involved, for instance, advise customers to change their password, and to change it anywhere else they reused it. Don’t ask them to send passwords or payment details to you.
  • Where to get help: Provide a contact method customers can use to ask questions, and tell them when you expect to share another update if you know.

A small-business owner and colleague reviewing an incident response plan and customer update

A simple customer message template

Adapt this example to the facts. Remove anything that doesn’t apply, and have a qualified professional review it if personal information may have been affected.

Subject: Update about a security issue with our website

We recently identified a security issue affecting our website. We have taken steps to secure the site and are investigating what happened.

We are reviewing whether customer information was involved. At this time, [state only what you have confirmed; if you do not yet know, say so plainly].

If your website account may be involved, please change your password and avoid reusing it on other sites. We will contact you directly if we confirm that further action is needed.

We’re sorry for the concern. If you have questions, contact us at [verified email address or phone number]. We’ll share another update [when you have a realistic update time, if known].

This is a starting point, not a one-size-fits-all notice. The message may need different information depending on the incident, applicable rules, and advice from your legal or privacy professional.

When and how should you contact customers?

Sooner is generally better than waiting for a perfect explanation. But “sooner” doesn’t mean sending unverified details. Make an initial assessment, preserve relevant evidence, and get help understanding what systems and information may have been affected. If you have a notification obligation, follow professional advice on timing and requirements rather than waiting until every technical question is answered.

Use a channel customers actually check and can recognize as yours. Depending on your business, that might mean email, phone, or a direct message through an established customer account. Verify the contact list and sender details first. If you also post an update on your website, don’t assume that a public notice replaces direct communication where direct notice is required or appropriate.

A short, plain-language update is easier to understand than a long technical explanation. If you don’t yet know the full impact, say what is known, what is not known, and how you’ll share further information. Avoid making customers search for a hidden notice on your site.

A customer reading a straightforward security update on a phone

What should you avoid saying?

Don’t guess about the cause. You may not know whether the incident involved an outdated plugin, a compromised password, a hosting issue, or another route. An early assumption can mislead customers and distract from the facts.

Don’t minimise the issue. Avoid phrases such as “nothing to worry about” unless you can support that conclusion. Acknowledge the concern without exaggerating it.

Don’t promise it can never happen again. No business can guarantee that. Explain the steps you’re taking to secure the site and reduce the chance of a repeat incident.

Don’t blame an employee, vendor, or service provider publicly. Focus on confirmed information and actions. You can investigate responsibility through the appropriate channels without turning a customer notice into an accusation.

Don’t bury practical advice in technical language. Customers need to know what to do, not the names of malware files or server settings. Keep detailed technical explanations for the people handling the investigation.

Keep communicating as you learn more

A customer update is not a substitute for securing the website or investigating the incident. It is one part of a responsible response. Keep a record of what you know, when you learned it, who you contacted, and what you told them. Coordinate messages with your hosting provider, payment provider, insurer, and legal or privacy professional as needed.

If the investigation changes what you understand about the incident, correct or update the message rather than leaving customers with an outdated impression. A clear, timely update cannot undo a hack, but it can help people take sensible steps, and show that your business is taking the incident seriously.

Talk with RachelAI receptionist · 613 706 8145