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

Loews Hotels & Co — August 2016 breach

Clustered 4 filings across 4 jurisdictions · filing window Jul 5, 2017 → Aug 18, 2017. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

4 filings

States

4

Affected · reported

1,243

First → last filing

Jul 5, 2017 → Aug 18, 2017

Merge confidence

100%

incident inc_fde0e23ba8ca4ea8 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 4 regulatory filings. The filing describes a third-party compromise. Intrusion Aug 29, 2016–Mar 9, 2017, discovered Jun 6, 2017 — the first regulatory filing landed 29 days later (flagged late). 1,243 individuals reported across the linked filings. Data reported: PCI, Financial account, and Identity (basic). Notifications rolled out on a 44-day schedule across 4 filings beginning Jul 5, 2017. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
29days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
44days

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 clocksOregon✗ OR AG >45dFull clock table in Litigation Timeline

Incident timeline

Aug 29, 2016breach begins
Jun 6, 2017discovered
notification delay · 29 days
Jul 5, 2017first filing
Aug 18, 2017most 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 5MA AGMA AG noticefirst filing · 1,172 MA residentsday 0
  2. JUL 5CA AGCA AG noticeno count statedday 0
  3. JUL 6MT AGMT AG notice71 MT residents+1d
  4. AUG 18OR AGOR AG noticemost recent · no count stated+44d
  5. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Aug 29, 2016 – Mar 9, 2017
CA AG
Discovered
Jun 6, 2017· 281d undetected
MT AG + OR AG
Data types
Financial account · Identity (basic) · PCI
MA AG + MT AG
Attack vector
Third-Party / Supply Chain
MT AG

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

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

44 days

Cadence

~1 / 14.7d

vs. multi-state median

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