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

Bailey Cavalieri LLC — November 2022 breach

Clustered 7 filings across 7 jurisdictions · filing window Jan 1, 2023 → Aug 18, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

7 filings

States

7

Affected · reported

203,136

First → last filing

Jan 1, 2023 → Aug 18, 2023

Merge confidence

100%

incident inc_1e73f1303ce24e51 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 7 regulatory filings. The filings describe unauthorized access. Intrusion Nov 22, 2022–Dec 13, 2022, discovered Dec 13, 2022 — the first regulatory filing landed 19 days later (flagged late). 203,136 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PII, and 1 more. Notifications rolled out on a 229-day schedule across 7 filings beginning Jan 1, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
19days

Discovered → first regulatory filing

Discovery variance
212days

Range of discovered_at dates across filings

Filing span
229days

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 clocksVermont✗ VT AG >45 bdayMaine⏱ ME AG >30d · 35dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Nov 22, 2022breach begins
Dec 13, 2022discovered · members disagree
notification delay · 19 days
Jan 1, 2023first filing
Aug 18, 2023most 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. JAN 1IL AGIL AG noticefirst filing · no count statedday 0
  2. AUG 17IN AGIN AG noticestates nationwide total 203,136+228d
  3. AUG 17VT AGVT AG noticeno count stated+228d
  4. AUG 17NH AGNH AG notice22 NH residents+228d
  5. AUG 17ME AGME AG noticestates nationwide total 203,136+228d
  6. AUG 17MT AGMT AG notice32 MT residents+228d
  7. AUG 18MA AGMA AG noticemost recent · 152 MA residents+229d
  8. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Nov 22, 2022
IN AG
Discovered
Dec 13, 2022IL AG + VT AG + NH AG +1Jul 13, 2023ME AGfilings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID · PII
VT AG + NH AG + ME AG +2
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)

203,136

Sum of filed state slices

622· 0.3% of stated

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

US203,136
IN393
MA152
MT32
ME23
NH22

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

229 days

Cadence

~1 / 38.2d

vs. multi-state median

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