Where does the Discord Inc. case file come from?

Every entry is taken from the breach report Discord Inc. lodged with the Texas 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 December 5, 2025. The incident itself is dated September 20, 2025.

Timeline

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

September 20, 2025Incident dateWhen the filing says the breach took place.
December 5, 2025Report filed in TexasDate the notice was lodged with the Texas Attorney General.

Case facts

Filing state: Texas
Date reported: December 5, 2025
Incident date: September 20, 2025
Receiving office: Texas Attorney General

Case notes

Discord Inc. has officially reported a data security incident to regulators in Texas, with a public filing dated December 5, 2025. The report details that the breach event initially occurred on September 20, 2025. At the time of the filing, Discord Inc. noted that an investigation into the matter was ongoing.

The specific categories of personal information involved in this incident were not detailed within the public filing. However, the report confirms that individuals' personal information was exposed, leading to the regulatory notification process.

Public filings like this serve to formally inform state authorities about security incidents where personal data may have been compromised. They are a crucial step in transparency, signaling that a company is addressing a security event that could impact the privacy and security of those affected.

While details about the exposed data are general, individuals who receive direct notifications from Discord Inc. regarding this incident should carefully review them for specific instructions. As a general precaution, it is always advisable to remain vigilant for any unusual activity in personal accounts, exercise caution with unsolicited communications, and consider updating passwords for online services.

Monitoring financial statements and other personal accounts for any unauthorized activity can help detect potential misuse of exposed information. Staying informed and proactive with personal security measures is a recommended step in the wake of any data exposure.

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 Texas 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.

Texas data breaches

Filing source: Texas 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 Texas case files