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

Crystal Bay Casino — November 2022 breach

Clustered 12 filings across 10 jurisdictions · filing window Feb 24, 2023 → Apr 3, 2023 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

12 filings

States

10

Affected · reported

93,950

First → last dated filing

Feb 24, 2023 → Apr 3, 2023

Merge confidence

100%

incident inc_3d850ce664f34d71 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 12 regulatory filings. Intrusion Nov 27, 2022–Jan 25, 2023, discovered Nov 1, 2022. 93,950 individuals reported across the linked filings. Data reported: Government ID, PII, and Identity (basic). Notifications rolled out on a 38-day schedule across 11 dated filings beginning Feb 24, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
85days

Range of discovered_at dates across filings

Filing span
38days

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 · 63dMassachusetts✓ MA credit monitoring dueDate basis✓ Clock withheld · confirmation dateFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Nov 27, 2022breach begins
Nov 1, 2022discovered · members disagree
Feb 24, 2023first dated filing
Apr 3, 2023most recent dated filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.

Member cascade — every filing about this breach

  1. JAN 1IL AGIL AG noticefiling day not on record · no count stated—
  2. FEB 24MA AGMA AG noticefirst filing · 476 MA residentsday 0
  3. FEB 24OR AGOR AG noticestates nationwide total 86,291day 0
  4. FEB 24MT AGMT AG notice143 MT residentsday 0
  5. FEB 24WA AGWA AG notice1,480 WA residentsday 0
  6. FEB 24ME AGME AG noticestates nationwide total 86,291day 0
  7. FEB 24CA AGCA AG noticeno count statedday 0
  8. FEB 24VT AGVT AG noticeno count statedday 0
  9. FEB 24IN AGIN AG noticestates nationwide total 86,291day 0
  10. MAR 29ME AGME AG noticestates nationwide total 93,950+33d
  11. MAR 29CA AGCA AG noticeno count stated+33d
  12. APR 3NH AGNH AG noticemost recent · 128 NH residents+38d
  13. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Nov 27, 2022
OR AG
Discovered
Nov 1, 2022MT AG + CA AG + VT AG +1Nov 27, 2022IL AGJan 25, 2023OR AG + WA AG + ME AGfilings disagree on discovery
Data types
Identity (basic) · Government ID · PII
MA AG + WA AG + ME AG +4
Attack vector
Unauthorized Access
MT 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)

93,950

Sum of filed state slices

2,548· 2.7% of stated

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

US93,950
WA1,480
MA476
IN255
MT143
NH128
ME66

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 filing12 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 Oct 22, 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

38 days

Cadence

~1 / 3.8d

vs. multi-state median

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