DisclosureLens
State AGConfirmed5 filings · 5 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 5 filings

William Doyle Galleries, Inc. — October 2024 breach

Clustered 5 filings across 5 jurisdictions · filing window Dec 9, 2025 Dec 11, 2025. View entity profile → Other incidents for this victim →

1 cross-filing discrepancyMerge100%

Determination

Confirmed

Members

5 filings

States

5

Affected · reported

2,123

First → last filing

Dec 9, 2025 Dec 11, 2025

Merge confidence

100%

incident inc_3d22a02998704292 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings. The filings describe unauthorized access. Intrusion Oct 24, 2024–Feb 18, 2025, discovered Feb 18, 2025 — the first regulatory filing landed 294 days later (flagged late). 2,123 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 1 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
294days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
2days

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 clocksVermont VT AG >45 bdayMaine ME AG >90d · 296dMassachusetts MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Oct 24, 2024breach begins
Feb 18, 2025discovered
notification delay · 294 days
Dec 9, 2025first filing
Dec 11, 2025most 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. DEC 9VT AGVT AG noticefirst filing · no count statedday 0
  2. DEC 10IN AGIN AG noticestates nationwide total 2,123+1d
  3. DEC 11ME AGME AG notice11 ME residents+2d
  4. DEC 11NH AGNH AG notice7 NH residents+2d
  5. DEC 11MA AGMA AG noticemost recent · 99 MA residents+2d
  6. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Oct 24, 2024Feb 18, 2025
VT AG
Discovered
Feb 18, 2025· 117d undetected
VT AG + ME AG + NH AG
Data types
Financial account · Identity (basic) · Government ID · PCI
VT AG + ME AG + NH AG +1
Attack vector
Unauthorized Access
VT 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)

2,123

Sum of filed state slices

120· 5.7% of stated

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

US2,123
MA99
ME11
NH7
IN3

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

2 days

Cadence

~1 / 0.5d

vs. multi-state median

4.0× faster

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.