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

Francesca's Acquisition, LLC — January 2023 breach

Clustered 10 filings across 10 jurisdictions · filing window Sep 25, 2023 → Sep 26, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 filings

States

10

Affected · reported

58,387

First → last filing

Sep 25, 2023 → Sep 26, 2023

Merge confidence

100%

incident inc_31c97a09a8e2475d · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings. Intrusion Jan 1, 2023–Jan 31, 2023, discovered Jan 31, 2023 — the first regulatory filing landed 237 days later (flagged late). 58,387 individuals reported across the linked filings. Data reported: Government ID, Financial account, Identity (basic), and 3 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
237days

Discovered → first regulatory filing

Discovery variance
189days

Range of discovered_at dates across filings

Filing span
1days

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 clocksWashington✗ WA AG >90dVermont✗ VT AG >45 bdayCalifornia✗ CA 60-day late · 189dOregon✗ OR AG >45dMaine⏱ ME AG >30d · 48dMassachusetts✓ MA credit monitoring dueSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

financial_credentialsidentity_government

Incident timeline

Jan 1, 2023breach begins
Jan 31, 2023discovered · members disagree
notification delay · 237 days
Sep 25, 2023first filing
Sep 26, 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. SEP 25WA AGWA AG noticefirst filing · 805 WA residentsday 0
  2. SEP 25NH AGNH AG notice344 NH residentsday 0
  3. SEP 25VT AGVT AG noticeno count statedday 0
  4. SEP 25CA AGCA AG noticeno count statedday 0
  5. SEP 25ME AGME AG noticestates nationwide total 58,387day 0
  6. SEP 25MT AGMT AG notice152 MT residentsday 0
  7. SEP 25IN AGIN AG noticestates nationwide total 58,387day 0
  8. SEP 25OR AGOR AG noticestates nationwide total 58,387day 0
  9. SEP 26MA AGMA AG notice1,645 MA residents+1d
  10. SEP 26SC AGSC AG noticemost recent · 1,161 SC residents+1d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jan 12, 2023 – Jan 31, 2023
WA AG
Discovered
Jan 31, 2023WA AG + NH AG + VT AG +3Aug 8, 2023ME AG + OR AGfilings disagree on discovery
Data types
Financial account · Financial credentials · Health (basic) · Identity (basic) · Government ID · PHI
WA AG + ME AG + MA AG +5
Attack vector
Ransomware
WA 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)

58,387

Sum of filed state slices

5,585· 9.6% of stated

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

US58,387
MA1,645
IN1,269
SC1,161
WA805
NH344
ME209
MT152

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 filing10 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
Reviewed
operator-reviewed Jun 12, 2026 · at least one link edge was human-adjudicated
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

1 days

Cadence

~1 / 0.1d

vs. multi-state median

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

Francesca's Acquisition, LLC data breach (2023) · DisclosureLens