Resort Data Processing — January 2019 breach

Clustered 10 filings across 8 jurisdictions · filing window Jul 14, 2021 → Jul 27, 2021. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

10 filings

States

Affected · reported

10,210

First → last filing

Jul 14, 2021 → Jul 27, 2021

Merge confidence

100%

incident inc_450e4fc149364a3a · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings. The filings describe unauthorized access. Intrusion Jan 1, 2019–Jun 14, 2021, discovered Jun 14, 2021 — the first regulatory filing landed 30 days later. 10,210 individuals reported across the linked filings. Data reported: Identity (basic), Financial account, PII, and 3 more. Notifications rolled out on a 13-day schedule across 10 filings beginning Jul 14, 2021. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay

30days

Discovered → first regulatory filing

Discovery variance

0days

Range of discovered_at dates across filings

Filing span

13days

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 clocksMaine✓ ME AG ≤30d · 30dWashington✓ WA AG ≤30dOregon✓ OR AG ≤45dCalifornia✓ CA 60-day OK · 39dFull 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.