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

Classic Residence Management — March 2023 breach

Clustered 11 filings across 6 jurisdictions · filing window Sep 29, 2023 → Mar 6, 2024. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

11 filings

States

6

Affected · reported

61,425

First → last filing

Sep 29, 2023 → Mar 6, 2024

Merge confidence

100%

incident inc_0609263aa6ec420e · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 11 regulatory filings. The filings describe unauthorized access. Intrusion Mar 1, 2023–Mar 31, 2023, discovered Mar 13, 2023 — the first regulatory filing landed 200 days later (flagged late). 61,425 individuals reported across the linked filings. Data reported: Government ID, Financial account, Identity (basic), and 1 more. Notifications rolled out on a 159-day schedule across 11 filings beginning Sep 29, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
200days

Discovered → first regulatory filing

Discovery variance
134days

Range of discovered_at dates across filings

Filing span
159days

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 clocksMaine✗ ME AG >90d · 149dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Mar 1, 2023breach begins
Mar 13, 2023discovered · members disagree
notification delay · 200 days
Sep 29, 2023first filing
Mar 6, 2024most 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. SEP 29MA AGMA AG noticefirst filing · 17 MA residentsday 0
  2. SEP 29MT AGMT AG notice3 MT residentsday 0
  3. SEP 29CA AGCA AG noticeno count statedday 0
  4. SEP 29IN AGIN AG noticestates nationwide total 61,425day 0
  5. SEP 29ME AGME AG noticestates nationwide total 61,425day 0
  6. SEP 29NH AGNH AG notice4 NH residentsday 0
  7. DEC 21NH AGNH AG notice2 NH residents+83d
  8. DEC 21CA AGCA AG noticeno count stated+83d
  9. DEC 21ME AGME AG noticestates nationwide total 61,425+83d
  10. MAR 6CA AGCA AG noticeno count stated+159d
  11. MAR 6NH AGNH AG noticemost recent · 22 NH residents+159d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Mar 1, 2023 – Mar 31, 2023
MT AG
Discovered
Mar 13, 2023MT AG + CA AG + NH AGJul 25, 2023ME AGfilings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID · PII
MA AG + ME AG + MT AG +2
Attack vector
Unauthorized Access
MT 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)

61,425

Sum of filed state slices

66· 0.1% of stated

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

US61,425
NH22
IN20
MA17
ME4
MT3

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

159 days

Cadence

~1 / 15.9d

vs. multi-state median

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