Where does the Discord Inc. case file come from?

Every entry is taken from the breach report Discord Inc. lodged with the California Attorney General. Nothing here is estimated.

Why do the incident date and the report date differ?

Companies usually investigate before they report. The gap between the two dates shows how long that took.

What does the records-affected figure count?

It is the number the company gave the state. It can cover residents of that state only, so the national total may be higher.

Does this case file change over time?

Yes. When a company files an update or a new state publishes its copy of the report, the dates and counts here are refreshed.

Case file

Case File: Discord Inc. Data Breach

This file collects the dated facts on record for the Discord Inc. incident. The state report is dated November 26, 2025. The incident itself is dated September 20, 2025.

Timeline

67 days separate the incident date from the date it was reported.

September 20, 2025Incident dateWhen the filing says the breach took place.
November 26, 2025Report filed in CaliforniaDate the notice was lodged with the California Attorney General.

Case facts

Filing state: California
Date reported: November 26, 2025
Incident date: September 20, 2025
Receiving office: California Attorney General

Case notes

Discord Inc. has officially reported a data breach, confirming that a security incident took place on September 20, 2025. The California-headquartered company subsequently filed notice of this event with regulators on November 26, 2025, as documented in public records.

The nature of the breach itself has not been specified in the available public filings. Similarly, the exact categories of personal information involved in the incident and the number of individuals potentially affected remain undisclosed at this time. Discord Inc. has indicated that a thorough investigation into the matter is actively in progress.

For users of Discord's services, this reported incident means there is a possibility that some of your personal information may have been exposed. While specific details regarding the compromised data are not yet public, it is important to be aware of the potential implications of any data security event.

In light of this report, individuals who may be affected are advised to take general precautionary measures. This includes remaining vigilant for any unusual activity across your online accounts and being cautious of unexpected communications, particularly those that request personal or sensitive details. Such caution is a widely recommended step following any data security incident.

These facts are based solely on information provided by Discord Inc. in their public regulatory filings concerning this security breach.

Questions about this case file

Where does the Discord Inc. case file come from?: Every entry is taken from the breach report Discord Inc. lodged with the California Attorney General. Nothing here is estimated.
Why do the incident date and the report date differ?: Companies usually investigate before they report. The gap between the two dates shows how long that took.
What does the records-affected figure count?: It is the number the company gave the state. It can cover residents of that state only, so the national total may be higher.
Does this case file change over time?: Yes. When a company files an update or a new state publishes its copy of the report, the dates and counts here are refreshed.

California data breaches

Filing source: California Attorney General

Named in the Discord Inc. breach?

Attach your notice and a short note. An attorney checks it against this case file at no cost.

Timeline

Case facts

Case notes

Questions about this case file

More California case files