Case file: Discord Inc.
Every government filing on this incident, the dates as stated, and the days to notice against each state's statute. Built from the records on Nov 9, 2026, agency link on every row. Not legal advice.
The incident
- Breach window
- Sep 20, 2025 to Sep 22, 2025
- Discovered
- Sep 25, 2025, as stated in the California letter
- State and federal records
- 3 filings, Nov 26, 2025 to Feb 6, 2026
- Residents counted
- 1,748 in 2 states (MA, TX), latest filing per state
- Everyone affected
- 74,729, as reported to Texas AG on Dec 5, 2025
- Information exposed
- Driver's license / state ID, Passport number, Date of birth, Postal address, Financial / bank account, Usernames / passwords, Email address, Phone number
- Offered to those affected
- 12 months of credit or identity monitoring through Experian
- Third party named
- Yes, the letter attributes the incident to a vendor or service provider
- Days to notice
- Past the statutory period in all 2 states that set one, counted from discovery to each state's first record
The letter: "On September 25, 2025, Discord Inc. ( We or the Company ) discovered that your data was impacted when a third party obtained unauthorized access to our customer service platform through a compromised vendor device."
Filings
| Agency | Record date | People | In total | Days to notice | Links |
|---|---|---|---|---|---|
| Massachusetts Massachusetts OCABR | Feb 6, 2026 | 283 | 134 days, statute no fixed period | Record | |
| Texas Texas AG | Dec 5, 2025 | 1,465 | 74,729 | 71 days, statute 60 days, over | Record |
| California California AG | Nov 26, 2025 | Not published | 62 days, statute 30 days, over | Letter Record |
People is the count the filing gives, residents of the state unless marked total. Days to notice runs from the discovery date the letter states, or from the end of the breach window when no letter states one, to the date on the state's first record of the incident. "Over" marks a count past the days the state's statute allows for notice to residents. The statute's trigger is a question of fact, the days are arithmetic.
Notice timing, state by state
- 134 days from discovery (Sep 25, 2025) to the Massachusetts record (Feb 6, 2026). Statute: no fixed period from knowledge or reason to know of the breach (Mass. Gen. Laws ch. 93H, § 3).
- 71 days from discovery (Sep 25, 2025) to the Texas record (Dec 5, 2025). Statute: 60 days from determination that the breach occurred (Tex. Bus. & Com. Code § 521.053).
- 62 days from discovery (Sep 25, 2025) to the California record (Nov 26, 2025). Statute: 30 days from discovery or notification of the breach (Cal. Civ. Code § 1798.82).
The statutes
- Massachusetts: no fixed period to notify residents from knowledge or reason to know of the breach, Mass. Gen. Laws ch. 93H, § 3. Attorney General and OCABR as soon as practicable and without unreasonable delay, every breach.
- Texas: 60 days to notify residents from determination that the breach occurred, Tex. Bus. & Com. Code § 521.053. Attorney General within 30 days of determination when 250 or more Texas residents are affected.
- California: 30 days to notify residents from discovery or notification of the breach, Cal. Civ. Code § 1798.82. Sample notice to the Attorney General when more than 500 Californians are notified, within 15 days of the consumer notice (effective 2026).
Filings by others that name Discord Inc.
Clients of a breached vendor often file under their own names and name the vendor.
- 5CA (a third-party service provider for Discord), Wisconsin, Oct 3, 2025, 70,000
Sources and method
Records as published by Massachusetts OCABR, Texas AG, California AG. Letter facts (discovery date, monitoring, third party) are read from the consumer letter the agency posted, 1 letter read for this incident, and quoted so you can check them. Texas and HHS publish no letters. First-seen times on each record page. Spot an error? Email support@breachtally.com with this page link.