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

City of Whitehall — December 2021 breach

Clustered 3 filings across 3 jurisdictions · filing window Oct 8, 2022 → Dec 8, 2022. View entity profile → Other incidents for this victim →

✓ affected count, data types agreeMerge100%

Determination

Confirmed

Members

3 filings

States

3

Affected · reported

36,694

First → last filing

Oct 8, 2022 → Dec 8, 2022

Merge confidence

100%

incident inc_20bdb8c816e04204 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 3 regulatory filings. The filing describes unauthorized access. Intrusion Dec 27, 2021, discovered Oct 12, 2022. 36,694 individuals reported across the linked filings. Data reported: Government ID. Notifications rolled out on a 61-day schedule across 3 filings beginning Oct 8, 2022. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Filing span
61days

Time between earliest and latest filing

Not recorded for this incident

Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.

Regulatory clocksMaine⏱ ME AG >30d · 57dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Dec 27, 2021breach begins
Oct 12, 2022discovered
Oct 8, 2022first filing
Dec 8, 2022most 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. OCT 8IN AGIN AG noticefirst filing · states nationwide total 36,694day 0
  2. DEC 8ME AGME AG noticestates nationwide total 36,694+61d
  3. DEC 8MA AGMA AG noticemost recent · 11 MA residents+61d
  4. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 27, 2021
IN AG
Discovered
Oct 12, 2022· 289d undetected
ME AG
Data types
Government ID
ME AG + MA AG
Attack vector
Unauthorized Access
ME AG

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)

36,694

Sum of filed state slices

123· 0.3% of stated

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

US36,694
IN107
MA11
ME5

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

61 days

Cadence

~1 / 30.5d

vs. multi-state median

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