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

Nevada Restaurant Services Inc. — January 2021 breach

Clustered 11 filings across 8 jurisdictions · filing window Jul 1, 2021 → Sep 20, 2021. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

11 filings

States

8

Affected · reported

217,120

First → last filing

Jul 1, 2021 → Sep 20, 2021

Merge confidence

100%

incident inc_a338bb6e90f14821 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 11 regulatory filings. Intrusion Jan 16, 2021, discovered Jan 1, 2021 — the first regulatory filing landed 181 days later (flagged late). 217,120 individuals reported across the linked filings. Data reported: Government ID, PII, Identity (basic), and 3 more. Notifications rolled out on a 81-day schedule across 11 filings beginning Jul 1, 2021. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
181days

Discovered → first regulatory filing

Discovery variance
151days

Range of discovered_at dates across filings

Filing span
81days

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 >90dMaine⏱ ME AG >30d · 64dMassachusetts✓ MA credit monitoring dueOregon✓ OR AG ≤45dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jan 16, 2021breach begins
Jan 1, 2021discovered · members disagree
notification delay · 181 days
Jul 1, 2021first filing
Sep 20, 2021most 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. JUL 1CA AGCA AG noticefirst filing · no count statedday 0
  2. JUL 1MT AGMT AG notice743 MT residentsday 0
  3. JUL 1MA AGMA AG notice312 MA residentsday 0
  4. JUL 1ME AGME AG noticestates nationwide total 210,492day 0
  5. JUL 1WA AGWA AG notice3,241 WA residentsday 0
  6. JUL 1IN AGIN AG noticestates nationwide total 210,492day 0
  7. JUL 1OR AGOR AG noticestates nationwide total 210,492day 0
  8. JUL 6NH AGNH AG notice89 NH residents+5d
  9. AUG 2NH AGNH AG notice89 NH residents+32d
  10. AUG 4ME AGME AG noticestates nationwide total 217,120+34d
  11. SEP 20NH AGNH AG noticemost recent · 89 NH residents+81d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jan 16, 2021
CA AG
Discovered
Jan 1, 2021MT AG + WA AG + NH AGJun 1, 2021ME AG + OR AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
CA AG + MT AG + ME AG +3
Attack vector
Unauthorized Access
CA 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)

217,120

Sum of filed state slices

5,186· 2.4% of stated

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

US217,120
WA3,241
MT743
IN688
MA312
ME113
NH89

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

81 days

Cadence

~1 / 8.1d

vs. multi-state median

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