DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
SEC 8-KState AGConfirmed12 filings · 12 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 12 filings

CAESARS ENTERTAINMENT, INC. — August 2023 breach

Clustered 12 filings across 12 jurisdictions · filing window Sep 14, 2023 → Oct 18, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

12 filings

States

12

Affected · reported

3,703,286

First → last filing

Sep 14, 2023 → Oct 18, 2023

Merge confidence

100%

incident inc_ec5dd59d1e0e42a4 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 12 regulatory filings. The filings describe a third-party compromise. Intrusion Aug 18, 2023–Sep 6, 2023, discovered Aug 19, 2023 — the first regulatory filing landed 26 days later. 3,703,286 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), and PII. Notifications rolled out on a 34-day schedule across 12 filings beginning Sep 14, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
26days

Discovered → first regulatory filing

Discovery variance
19days

Range of discovered_at dates across filings

Filing span
34days

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.

Regulatory clocksWashington⏱ WA AG >30dMaine✓ ME AG ≤30d · 29dHawaii✓ HI CRA notice dueMassachusetts✓ MA credit monitoring dueSouth Carolina✓ SC CRA notice dueOregon✓ OR AG ≤45dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Aug 18, 2023breach begins
Aug 19, 2023discovered · members disagree
notification delay · 26 days
Sep 14, 2023first filing
Oct 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. SEP 14SEC 8-KSEC 8-K noticefirst filing · no count statedday 0
  2. OCT 6IN AGIN AG notice1,662,718 IN residents+22d
  3. OCT 6ME AGME AG notice41,397 affected+22d
  4. OCT 6DE AGDE AG noticeno count stated+22d
  5. OCT 6MT AGMT AG notice56,879 MT residents+22d
  6. OCT 6NH AGNH AG notice59,221 NH residents+22d
  7. OCT 6WA AGWA AG notice784,234 WA residents+22d
  8. OCT 11CA AGCA AG noticeno count stated+27d
  9. OCT 11HI AGHI AG notice165,271 HI residents+27d
  10. OCT 11MA AGMA AG notice327,948 MA residents+27d
  11. OCT 12SC AGSC AG notice605,618 SC residents+28d
  12. OCT 18OR AGOR AG noticemost recent · states nationwide total 271,637+34d
  13. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Aug 18, 2023
IN AG
Discovered
Aug 19, 2023NH AG + WA AGSep 7, 2023ME AG + OR AGfilings disagree on discovery
Data types
Identity (basic) · Government ID · PII
SEC 8-K + ME AG + WA AG +7
Attack vector
Third-Party / Supply Chain
SEC 8-K

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Affected residents by state

per-state reported counts

US271,637
IN1,662,718
WA784,234
SC605,618
MA327,948
HI165,271
NH59,221
MT56,879
ME41,397

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

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

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

34 days

Cadence

~1 / 3.1d

vs. multi-state median

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