DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
State AGConfirmed9 filings · 8 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedcritical sensitivity
Merged incident · 9 filings

Restaurant Management Company of Wichita, Inc. — October 2025 breach

Clustered 9 filings across 8 jurisdictions · filing window Apr 17, 2026 → May 11, 2026. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

9 filings

States

8

Affected · reported

120,426

First → last filing

Apr 17, 2026 → May 11, 2026

Merge confidence

100%

incident inc_f04ee8792e3e4974 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings. The filings describe unauthorized access. Intrusion Oct 4, 2025–Oct 13, 2025, discovered Oct 13, 2025 — the first regulatory filing landed 186 days later (flagged late). 120,426 individuals reported across the linked filings. Data reported: Government ID, Minor, PII, and 4 more. Notifications rolled out on a 24-day schedule across 9 filings beginning Apr 17, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
186days

Discovered → first regulatory filing

Discovery variance
164days

Range of discovered_at dates across filings

Filing span
24days

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 · 189dMassachusetts✗ MA AG >90dTexas✓ TX AG ≤30dFull clock table in Litigation Timeline

Sensitive data

identity_governmentminor

Incident timeline

Oct 4, 2025breach begins
Oct 13, 2025discovered · members disagree
notification delay · 186 days
Apr 17, 2026first filing
May 11, 2026most 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. APR 17VT AGVT AG noticefirst filing · 9 VT residentsday 0
  2. APR 20IN AGIN AG noticestates nationwide total 120,416+3d
  3. APR 20IN AGIN AG noticestates nationwide total 120,416+3d
  4. APR 20ME AGME AG noticestates nationwide total 120,426+3d
  5. APR 20MT AGMT AG notice9,922 MT residents+3d
  6. APR 20NH AGNH AG notice20 NH residents+3d
  7. APR 20NE AGNE AG noticeno count stated+3d
  8. APR 22TX AGTX AG noticestates nationwide total 120,426+5d
  9. MAY 11MA AGMA AG noticemost recent · 40 MA residents+24d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Oct 4, 2025
IN AG
Discovered
Oct 13, 2025ME AG + MT AG + NH AG +2Mar 26, 2026TX AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · Minor · PHI · PII
VT AG + MT AG + NH AG +4
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)

120,426

Sum of filed state slices

62,146· 51.6% of stated

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

US120,426
TX52,017
MT9,922
IN112
MA40
ME26
NH20
VT9

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

24 days

Cadence

~1 / 3d

vs. multi-state median

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