A message about a Who Gives A Crap data incident has appeared in your inbox, text messages, or voicemail.
The fastest check: open the company’s official incident page independently. Its November 7, 2026 notice says some customer contact information and total-spend information were involved; it does not say that account passwords or payment information were involved. The company says it does not yet know whether the information was copied or downloaded, and reports no evidence of misuse. Those are the confirmed boundaries—not proof that no data left the system. Read the current official incident notice before acting on a message.
This guide is for people who received a message claiming to be from Who Gives A Crap, saw a report and want to separate confirmed facts from unknowns, or are deciding whether a temporary email would help with a future ordinary signup.
Last updated November 14, 2026. We checked the dates and incident details against the official incident page and the U.S. customer support notification. Check those pages again before relying on this summary; a later official update takes precedence.
Timeline: verify the message before responding
At first contact: treat the message as unverified
Do not decide that a message is genuine just because its display name says Who Gives A Crap, it mentions a real purchase, or it arrived around the time of public reporting. Display names can be misleading, and a scam message can borrow facts from an actual incident. The reverse is also true: not receiving a particular email does not establish that your information was outside the affected group.
How do you check whether the data breach email is genuine? Start from a source you reach independently. Type the company’s known official website address into your browser, then find its incident notice or use a support channel already listed on its site. Do not use a link, phone number, or reply address supplied by the message you are checking.
The U.S. Federal Trade Commission advises people to avoid using links in unexpected messages and instead contact the organization through a website or phone number they know to be genuine. Its guidance on protecting yourself from phishing scams also explains why an authentic-looking message is not enough to establish who sent it.
Before opening a suspicious message further, do not reply, download an attachment, submit a verification code, or enter a password or personal details. If you have already clicked a link, stop before entering information. Close the page and go to the official site independently. If you entered a password, secure that account through its official website, and change the password anywhere else you reused it. That precaution responds to what you did; it does not mean the incident notice says passwords were exposed.
November 7, 2026: compare the official notice with the claim
The incident page is dated November 7, 2026, and describes information associated with stores in Australia, the United Kingdom, and the United States. The company says it is notifying customers it believes may have been affected. A customer-support notice provides additional information for U.S. customers. These points should be checked against the pages themselves, since the company may revise its wording or add details. The U.S. support notice is a useful companion to the main incident page.
The notice identifies customer contact information and total spend as information involved. It distinguishes those categories from account credentials, order details, and payment information. Read the current wording on the official page rather than relying on a forwarded screenshot or a summary that may have compressed those distinctions.
| Source or message | What it can help establish | What it cannot establish by itself | Best next action |
|---|---|---|---|
| Official incident page | The company’s stated date, affected store regions, information categories, and current advice | Whether an individual message in your inbox was sent by the company | Open it independently from the company’s official site |
| Official customer-support notice | Region-specific explanation and customer guidance | Whether a separate text or email is authentic | Use the support page reached independently |
| Media report | Independent context about public reporting | A replacement for the company’s current description of affected data | Compare it with the official notice |
| Email, text, or voicemail you received | What the sender is claiming and what action it wants | The sender’s identity or your inclusion in the affected group | Do not use its links or contact details to verify the claim |
The ABC News report can help cross-check that the incident was publicly reported. It is still a media account, not the source of the company’s current statements about affected information or customer advice. If a report uses broader language than the official notice, do not treat that as confirmation that passwords, payment details, or other data were exposed.
After comparing sources: separate confirmed facts from unknowns
The company says it does not know whether the relevant information was copied or downloaded. It also says there is no evidence of misuse. These statements describe what the company currently knows; neither proves that no information was removed, nor establishes that the data has been published or used. “No evidence of misuse” is not the same as “there is no risk.”
Keep these categories separate when assessing a message:
- Confirmed by the company: the notice’s stated regions and the information categories it identifies.
- Not established by the notice: whether information was copied or downloaded.
- Not reported as known by the company: evidence of misuse.
- Not confirmed by an email’s wording alone: whether the recipient was affected or whether that particular email is genuine.
A message may quote accurate incident details and still be fraudulent. Scammers can use public reporting to make a request for a password, payment, or one-time code seem credible. The Cybersecurity and Infrastructure Security Agency’s phishing and spoofing tips recommend treating unexpected requests cautiously and checking the sender through a separate, trusted route.
As the notice changes: use the latest official wording
This article reflects the official notice available on November 14, 2026. If the company changes the affected regions, data categories, account-security guidance, or its assessment of possible copying and misuse, use the newer official statement instead. An earlier article, a search-result snippet, or a forwarded copy can lag behind an update.
When reviewing a later notice, check its publication or update date, then compare the exact statements on the official page. Avoid treating an undated screenshot as current. If you cannot find an update, contact the company through contact details listed on its official website—not through the message that raised your concern.
Timeline: decide what to do with your account
If your email address may be involved, do you need to change your password immediately? The official notice does not say that a password change is required because of this incident. It says account passwords were not involved. Do not present a password reset as a mandatory response to the notice alone.
That does not mean you should ignore a separate sign of account compromise. If you reused the same password elsewhere and entered it on a suspicious page, change it on the affected services using their official sites. If you receive an unexpected sign-in alert, check the account directly rather than following the alert’s link. The Associated Press’s password-protection guidance discusses password reuse and the value of using distinct credentials. Apply that general advice based on your circumstances; do not confuse it with a company instruction that this incident requires a reset.
What should you do with a text or email claiming to be from Who Gives A Crap? Keep the message as a record if you need to report it, but do not reply or provide information through it. Compare its claims with the official incident page, and use an independently found support channel if something remains unclear. A request for a verification code, password, payment, or extra identity details is a reason to stop and verify—not a reason to act faster.
Watch for follow-up contact that uses accurate personal details to sound convincing. That could arrive by email, text, phone, or letter. The fact that a sender knows a name, an email address, or a purchase-related detail does not prove that the sender is authorized. If a contact asks you to sign in, make a payment, or share a code, reach the organization through a known official route first.
A company incident notice and an individual phishing message are different questions. The notice may be genuine while a message using its name is not. Likewise, a message can be fraudulent even if it refers to a real event. Verify the event and verify the sender separately.
Timeline: limit future exposure without expecting a remedy
A temporary email can be a way to avoid giving your main email address to some future, low-stakes registration. It cannot remove information already provided to a retailer, recover data from a past incident, or conceal other details such as a phone number, delivery address, or payment information. This is the practical privacy boundary: it can change what address you use next time, not what an organization already holds.
For shopping accounts, order updates, returns, warranties, and customer support, a long-term email address you can reliably access is usually the safer choice. Those accounts may need a durable contact route. Use a temporary address only when the signup is ordinary and disposable, and you do not expect to depend on future access or replies. An alias or a separate email account may be a better fit when you want ongoing access while keeping your main address less exposed.
| Option | Main-email exposure | Long-term access | Better fit |
|---|---|---|---|
| Main email address | Gives the service your regular address | Usually suitable if you keep the account | Purchases, support, and accounts you may need to recover |
| Email alias | Can separate signups from your main inbox, depending on setup | Often useful for ongoing contact | Subscriptions or services where you want continuing access |
| Separate email account | Keeps the address distinct from your primary one | You control whether to maintain it | Longer-term registrations that need a separate inbox |
| Temporary email | Can keep your main address out of some low-stakes signups | Depends on the service and its current mailbox rules | One-off registrations where later access is not important |
This comparison is about the type of address, not a guarantee that every service will accept it or that every temporary inbox has the same privacy and retention behavior. Review the service’s current practices before using it. Our guide to choosing between a disposable address and other email options can help match the address to the account’s recovery and support needs. For a closer look at how to assess service handling, see Inboxtmp’s published data practices.
What does a temporary email protect in this situation? It may reduce exposure of your main address in a future signup if you choose it before submitting the form. It does not undo this event, prove whether your information was involved, or replace a long-term address for an account you may need to recover. That is the limit of temporary email privacy: it is a choice about future disclosure, not a breach-response tool.
For a future one-off registration, review the current options at Inboxtmp and decide whether a temporary address fits the account’s purpose. Keep an address you can access long term for orders, support, and recovery. For this incident, the reliable next step remains the same: verify the notice independently, follow the company’s latest official guidance, and do not let an unverified message collect more information from you.