Kimpton Hotels & Restaurants — February 2016 breach

Clustered 9 filings across 7 jurisdictions · filing window Aug 31, 2016 → Sep 16, 2016. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

9 filings

States

Affected · reported

12,810

First → last filing

Aug 31, 2016 → Sep 16, 2016

Merge confidence

100%

incident inc_18344a7c441a4b48 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings. The filing describes unauthorized access. Intrusion Feb 16, 2016–Jul 7, 2016, discovered Jul 15, 2016 — the first regulatory filing landed 47 days later (flagged late). 12,810 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Employment, and 3 more. Notifications rolled out on a 16-day schedule across 9 filings beginning Aug 31, 2016. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Notification delay

47days

Discovered → first regulatory filing

Discovery variance

28days

Range of discovered_at dates across filings

Filing span

16days

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 >45dCalifornia✓ CA 60-day OK · 47dFull clock table in Litigation Timeline

No cross-filing comparison data available for this incident.

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.