DisclosureLens
HHS OCRState AGConfirmed5 filings · 5 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedcritical sensitivity
Merged incident · 5 filings

Onondaga County Chapter NYSARC, Inc. — August 2021 breach

Clustered 5 filings across 5 jurisdictions · filing window Nov 19, 2021 Nov 30, 2021. View entity profile → Other incidents for this victim →

Determination

Confirmed

Members

5 filings

States

5

Affected · reported

8,566

First → last filing

Nov 19, 2021 Nov 30, 2021

Merge confidence

100%

incident inc_9b519c8c28de41b7 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings. The filings describe unauthorized access. Intrusion Aug 15, 2021, discovered Sep 21, 2021 — the first regulatory filing landed 59 days later. 8,566 individuals reported across the linked filings. Data reported: Government ID, Minor, PHI, and 2 more. Notifications rolled out on a 11-day schedule across 5 filings beginning Nov 19, 2021. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
59days

Discovered → first regulatory filing

Discovery variance
56days

Range of discovered_at dates across filings

Filing span
11days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksHIPAA HHS notifiedMassachusetts MA credit monitoring dueMaine ME AG ≤30d · 14dFull clock table in Litigation Timeline

Sensitive data

identity_governmentminor

Incident timeline

Aug 15, 2021breach begins
Sep 21, 2021discovered · members disagree
notification delay · 59 days
Nov 19, 2021first filing
Nov 30, 2021most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. NOV 19HHS OCRHHS OCR noticefirst filing · states nationwide total 5,425day 0
  2. NOV 30MA AGMA AG notice7 MA residents+11d
  3. NOV 30MT AGMT AG noticestates nationwide total 8,520+11d
  4. NOV 30ME AGME AG noticestates nationwide total 8,566+11d
  5. NOV 30IN AGIN AG noticemost recent · states nationwide total 8,566+11d
  6. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Aug 15, 2021
MT AG
Discovered
Sep 21, 2021MT AGNov 16, 2021ME AGfilings disagree on discovery
Data types
Health (basic) · Identity (basic) · Government ID · Minor · PHI
HHS OCR + MT AG + ME AG +1
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)

8,566

Sum of filed state slices

11· 0.1% of stated

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

US8,566
MA7
ME2
MT1
IN1

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 filing5 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
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

11 days

Cadence

~1 / 2.8d

vs. multi-state median

1.4× 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.