DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
HHS OCRState AGConfirmed11 filings · 9 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 11 filings

Sound Generations — July 2021 breach

Clustered 11 filings across 9 jurisdictions · filing window Nov 29, 2021 → Dec 15, 2021 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

11 filings

States

9

Affected · reported

600,605

First → last dated filing

Nov 29, 2021 → Dec 15, 2021

Merge confidence

100%

incident inc_9fee40c31f244aea · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 11 regulatory filings. Intrusion Jul 18, 2021–Sep 18, 2021, discovered Jul 18, 2021. 600,605 individuals reported across the linked filings. Data reported: Government ID, PHI, Health (basic), and 5 more. Notifications rolled out on a 16-day schedule across 9 dated filings beginning Nov 29, 2021. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
0days

Range of discovered_at dates across filings

Filing span
16days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.

Regulatory clocksWashington✗ WA AG >90dMaine⏱ ME AG >30d · 150dHIPAA✓ HHS notifiedMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jul 18, 2021breach begins
Jul 18, 2021discovered
Nov 29, 2021first dated filing
Dec 15, 2021most recent dated filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.

Member cascade — every filing about this breach

  1. JAN 1IL AGIL AG noticefiling day not on record · no count stated—
  2. JAN 1IL AGIL AG noticefiling day not on record · no count stated—
  3. NOV 29HHS OCRHHS OCR noticefirst filing · states nationwide total 456,243day 0
  4. DEC 13MT AGMT AG notice280 MT residents+14d
  5. DEC 13MA AGMA AG notice3,248 MA residents+14d
  6. DEC 13OR AGOR AG noticestates nationwide total 600,605+14d
  7. DEC 13WA AGWA AG notice211,097 WA residents+14d
  8. DEC 13IN AGIN AG noticestates nationwide total 600,605+14d
  9. DEC 14NH AGNH AG noticestates nationwide total 600,605+15d
  10. DEC 15ME AGME AG noticestates nationwide total 600,605+16d
  11. DEC 15CA AGCA AG noticemost recent · no count stated+16d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jul 18, 2021 – Sep 18, 2021
MT AG
Discovered
Jul 18, 2021
IL AG + MT AG + WA AG +2
Data types
Credentials · Employment · Financial · Financial account · Health (basic) · Identity (basic) · Government ID · PHI
HHS OCR + NH AG + MT AG +4
Attack vector
Unauthorized Access
HHS OCR

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Count reconciliation

per-state reported counts

Nationwide (stated in a filing)

600,605

Sum of filed state slices

217,770· 36.3% of stated

64% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

US600,605
WA211,097
MA3,248
IN2,135
ME943
MT280
NH67

State AGs report only their own residents; teal bars show each state's reported slice. The gray US row is the nationwide total reported in a linked filing.

Evidence ladder — rungs this incident occupies

Leak-site claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing11 members

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

No SEC filing or victim statement yet.

Merge provenance

Method
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Aug 23, 2026 · at least one link edge was human-adjudicated
Audit
Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).

Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.

Filing velocity

Spread

16 days

Cadence

~1 / 2d

vs. multi-state median

2.7× slower

About this clustering

DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.

The weekly clock on records like this one

The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.

Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.