Personal & Life
Data Breach Notice for Beginners: Change Passwords, Check Reuse, Watch for Suspicious Charges
Beginner | 4 whiteboard pages · Task board: 5 columns (4 parent tasks, 12 subtasks)
Beginner: No technical terms. Just answer the whiteboard's questions, following the examples, and it takes shape.
When a service says your personal data may have leaked, check the notice without clicking its links, act on what was exposed, and watch your accounts for months. What to do depends on whether your email, password, card number, address and phone, or birth date leaked. A leaked password must change everywhere you reused it. For a card number, call the number on the back of the card and ask about stopping or reissuing it. Breaches bring scams, so reopen the service from a bookmark or the official app, never from the notice. On day one, look for the same announcement on the official site's news page and, if found, note its date and content. Common slips are using the notice's link, forgetting reused services, delaying a card reissue, and missing odd charges or contacts months later. Passwords need no scheduled changes, and an authenticator app or passkey beats SMS codes. The whiteboard has 4 pages and the task board 5 columns, with 4 parent tasks of 3 subtasks each.
Once you have a free account, you can copy this template from the marketplace
Whiteboard preview
Read the whiteboard text as plain text
Data Breach Response Board
How to use (4 pages): ① On page 1, confirm the notice on the official site and record it (boards①–③) → ② On page 2, list the to-dos and pitfalls for each leaked item (boards④–⑦) → ③ On page 3, sort by urgency and harm and set deadlines (boards⑧⑨) → ④ On page 4, plan the 3-month watch and note who to call (boards⑩–⑫)
1/4 Check the notice
① Goal and the notice you received (start writing here)
- What you are doing this for e.g. Keep the leaked data from being used against your money or contacts
- The notice you received e.g. Email from online shop A. Member data may have leaked
- What you will finish by when e.g. Check today, and finish the password and card steps this week
② Four steps to check the notice is real (do not click its links)
- Open the official site Do not use the notice's link e.g. Opened shop A from a bookmark or the official app
- Read the news page See if the same announcement is there e.g. The news page had an announcement with the same date and content
- Ask the help desk Ask the contact point listed on the official site e.g. Asked whether my data was affected. Did not use the number in the notice
- Record it Write down what you saw and heard e.g. Wrote the date received, the announcement title, and the answer in table ③
③ Record of notices received
| Date and channel received | What it said | Check on the official site | |
|---|---|---|---|
| Notice 1 | e.g. Day 1, email | e.g. Member email, address, phone, birth date, and card number may have leaked | e.g. Same announcement on the news page = the breach is real. Proceed from the official site |
| Notice 2 | e.g. Day 3, SMS | e.g. "Identity check needed" with a link | e.g. No announcement on the news page = do not click the link, delete it |
| Notice 3 | e.g. Week 2, postal mail | e.g. An apology and next steps | e.g. Called the help desk on the official site and confirmed the same content |
2/4 Sort out what leaked
④ From the notices checked in ③, what to do for each leaked item
| Leaked? (yes, no, unsure) | What could happen | What to do | |
|---|---|---|---|
| Email address | e.g. Yes | e.g. More lookalike emails arrive | e.g. Do not click email links, and reopen the service from the official app |
| Password | e.g. Unsure | e.g. Someone else logs in | e.g. Change it on that service and on any other service with the same password. Also set up an authenticator app or passkey (signing in by face, fingerprint, or PIN, like your phone's screen lock) for sign-in checks |
| Card number | e.g. Yes (number and expiry date) | e.g. Charges you do not recognize appear | e.g. Call the number on the back of the card and ask about stopping or reissuing it |
| Address and phone | e.g. Yes | e.g. Suspicious calls or mail arrive | e.g. Do not answer on the spot, and call back on the official number yourself |
| Date of birth | e.g. Yes | e.g. Used for identity-check questions | e.g. If you used your birth date in a PIN or passphrase, change it |
⑤ Pitfall: starting from the notice's link
- What happens: if the notice is fake, the password or card number you enter goes to the attacker
- How to check: recall whether you opened the screen from a bookmark or the official app
- Safeguard: do not click the link, reopen the service with the 4 steps in ②, and then proceed
- e.g. Entered my password on a screen opened from the link → change it from the official site right away
⑥ Pitfall: forgetting services with the same password
- What happens: the leaked password also opens the other services where you reused it
- How to check: list the services you use often and recall one by one whether the password is the same
- Safeguard: change every reused service to its own separate password
- e.g. Email, online bank, and shop B were the same → change all three this week
⑦ Pitfall: hesitating to reissue the card
- What happens: you keep using a card whose number leaked, and unauthorized charges arrive later
- How to check: ask the card company whether you are affected and how many days a reissue takes
- Safeguard: if unsure, ask for a reissue and move your automatic payments to the new number
- e.g. Wrote a plan to move utility and video-service payments to the new card
3/4 Set the order
⑧ Sort the to-dos from ④ and ⑤ to ⑦ by urgency and size of harm
Vertical axis: Size of harm (higher = bigger) / Horizontal axis: Urgency (further right = more urgent)
- Plan it Big harm but not needed today. e.g. Change the passwords of the remaining reused services this week
- Do today Big harm and urgent. e.g. Change the leaked service's password and call the card company
- Do when convenient Small harm and not urgent. e.g. Change a passphrase based on your birth date
- Do soon Small harm but urgent. It takes little effort, so clear it fast. e.g. Delete a suspicious email without opening it
⑨ In the order of ⑧, the to-do, deadline, and done
| To-do | Deadline | Done (date finished) | |
|---|---|---|---|
| First | e.g. Change shop A's password | e.g. Night of day 1 | e.g. Done, day 1 |
| Second | e.g. Call the card company and ask for a reissue | e.g. Within day 1 | e.g. Done, day 1 |
| Third | e.g. Change the 3 services that had the same password | e.g. Weekend of week 1 | e.g. Not yet |
| Fourth | e.g. Set up an authenticator app or passkey | e.g. Week 2 | e.g. Not yet |
4/4 Watch for months
⑩ Timeline (including ⑨, from day one to 3 months later)
- Start (day one) e.g. Check the notice and handle the password and card
- Phase 1 (week 1) e.g. Every day, check card use and incoming email
- Phase 2 (weeks 2 to 4) e.g. Once a week, review statements and sign-in records
- Phase 3 (month 2) e.g. Check that all payments have moved to the new card
- Phase 4 (month 3) e.g. Keep the monthly statement check and look for suspicious contacts
- Goal (3 months later) e.g. If nothing looks wrong, go back to your usual checks
⑪ Pitfall: missing suspicious contact months later (what to watch and how often)
| What happens | How to check and how often | Safeguard | |
|---|---|---|---|
| Card statements | e.g. Small charges you do not recognize slip in | e.g. Check usage in the card company's app daily in week 1, then weekly | e.g. If you find one, call the number on the back of the card |
| Email and SMS | e.g. Messages using the breach as a pretext arrive | e.g. Each time, check the official app for the same notice | e.g. If there is no notice, delete it without clicking the link |
| Sign-in records | e.g. Sign-ins from unfamiliar places or devices | e.g. Check sign-in records in account settings weekly until week 4, then monthly (where the service offers them, and check each service's guide for where to look) | e.g. If you do not recognize one, change the password and tell the help desk |
| Phone and mail | e.g. Calls or mail from someone claiming to be the company | e.g. When one arrives, check whether the number matches the official site | e.g. Do not answer on the spot, and call back on the official number |
⑫ Who to ask for help (copy numbers from the official site or the back of your card)
- The service's help desk e.g. Shop A's support desk, found through Contact on the official site
- Your card company e.g. The number on the back of the card, for unauthorized charges or reissue questions
- Local consumer advice office and police e.g. Ask if you lose money or get threatening contact. Check the latest guidance for the office's name and number
Task board contents
Not started 16 items
Check the notice
On page 1, confirm the notice is real through the official site, not its links, and record it. Once you know, you can decide what to do on the later pages. Press Ctrl+F (⌘F on Mac) and type "3/4" to jump to page 3.
Open the real site
Do this the day the notice arrives. Close the notice email, open the service from a bookmark or the official app, and look for the same announcement in its news page (board ②, steps 1 and 2). Write what you saw in row 1 of the table on board ③ to finish.
Set goal, deadline
On the three sticky notes of board ①, write why you are doing this, the notice you received, and what you will finish by when. With a deadline written down, it is easier to set the order on page 3.
Ask the help desk
If you cannot tell whether your data is affected, ask the contact point listed on the official site (board ②, steps 3 and 4). Write the answer in the table on board ③ to finish.
Sort what leaked
On page 2, write what could happen and what to do for each type of leaked information, then check the common pitfalls against your own case. The actions you list here are the material for setting the order on page 3.
Mark what leaked
In the table on board ④, write yes, no, or unsure for each of the five types, then read the to-do in the yes and unsure rows. For an unsure row, act as if it leaked.
List reused logins
Using the pitfall on board ⑥, list every service where you used the same password that leaked. Those services are what you change on page 3.
Check the pitfalls
Rewrite the e.g. examples on the sticky notes of boards ⑤ and ⑦ for your own case, and add the safeguard for each pitfall that applies to the to-dos in ④.
Set the order
On page 3, sort the actions from page 2 by urgency and size of harm, give each a deadline, and finish them one at a time. Move finished ones to the Done column of the task board.
Sort into four
On the four areas of board ⑧, place one sticky note for each action from ④ and ⑤ to ⑦. Start with whatever lands in Do today.
Add deadlines
In the table on board ⑨, write the actions in the order from ⑧ with their deadlines. You are done when all four rows have a deadline.
Log finish dates
In the Done (date finished) column of board ⑨, write the day you finished, like day 2. If any row is still open, revisit its deadline.
Watch for months
On page 4, decide what to check and how often from the day of the notice up to three months later, and note who to ask for help. Even after the steps are done, suspicious contacts can arrive months later.
Plan the watch
On the timeline of board ⑩, write what to check in each period from day one to three months later. You are done when the check-ins are on your calendar.
Watch for red flags
Follow the frequencies in the table on board ⑪ for card statements, email and SMS, sign-in records, and phone calls and mail. If something looks wrong, act as the safeguard column says.
Note who to call
On board ⑫, write the numbers for the service's help desk, your card company, and a local consumer advice office. Copy numbers from the official site or the back of your card, not from the notice.