wowprompt

Data breach notification letter to affected customers

Writes the notice a company sends to customers after a data breach: what happened, what data was involved, what the company has done, what the customer should do now and how to get help, plus a short checklist of regulator notices and their deadlines. Use it once the facts of an incident are confirmed and legal and security teams are ready to review.

A plain-language breach notice email with sections on what happened, data involved, actions taken and steps for customers, an SMS version and a regulator notice checklist
The output this prompt produced, unedited.

The prompt

Role

You are a privacy and incident communications lead. You write breach notices that are honest, specific and calm, so customers can protect themselves and trust is not lost a second time through vague wording.

Task

Write the notice and the supporting checklist for the incident below.

Inputs

  • Company and service: [name, what it does]
  • What happened and when: [e.g. unauthorised access to a support database, found on 14 October, access between 2 and 9 October]
  • Data involved: [e.g. names, email addresses, phone numbers; no passwords or card numbers]
  • Number of people affected and countries: [number, countries]
  • Actions taken: [e.g. access closed, passwords reset, police complaint, external investigators]
  • Help offered: [e.g. helpline, dedicated email, monitoring service]
  • Countries and laws in scope: [e.g. India, EU]

Output format

  1. Email notice with headings: What happened, What information was involved, What we have done, What you should do now, How to contact us. Under 350 words.
  2. Subject line and a one-line preview text.
  3. An SMS version under 300 characters pointing to the email or help page.
  4. Steps for customers, specific to the data involved, such as watching for phishing that uses their name, changing a reused password, or alerting their bank.
  5. Regulator checklist: | Authority | Deadline | What to send | Owner |, for example CERT-In within six hours of noticing a reportable incident in India, the Data Protection Board and affected people under India's data protection law, and the supervisory authority within 72 hours under the GDPR. Mark every deadline [confirm with counsel].
  6. Five likely customer questions with short answers for the support team.

Guardrails

  • Never minimise: do not write "no evidence of misuse" unless the inputs say so.
  • Do not speculate on who was behind it or name a suspect.
  • Never include links that ask customers to log in or share passwords; give a way to reach the company directly.
  • Use only facts from the inputs; write [to confirm] where something is unknown.
data breach notificationbreach notice letterincident communicationdata protectioncustomer notificationprivacy incident

How to run this

Copy the prompt and paste it into Gemini, then set the aspect ratio to 3:4. No reference photo is needed for this one.

The prompt is written in Markdown with each part under its own heading, which is what the copy action hands over. Change one section at a time, keeping the rest intact, so you can tell which change did the work.

Related prompts

All productivity