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

Welk Resort Group, Inc. — November 2017 breach

Clustered 4 filings across 4 jurisdictions · filing window Jul 25, 2018 → Aug 1, 2018. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

4 filings

States

4

Affected · reported

1,040

First → last filing

Jul 25, 2018 → Aug 1, 2018

Merge confidence

100%

incident inc_4aee0e4814d847f6 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 4 regulatory filings. Intrusion Nov 29, 2017–Dec 4, 2017, discovered Dec 4, 2017 — the first regulatory filing landed 233 days later; 1 later filing was flagged late. 1,040 individuals reported across the linked filings. Data reported: Government ID, Financial account, PCI, and 5 more. Notifications rolled out on a 7-day schedule across 4 filings beginning Jul 25, 2018. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
233days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
7days

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 clocksCalifornia✗ CA 60-day late · 233dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Nov 29, 2017breach begins
Dec 4, 2017discovered
notification delay · 233 days
Jul 25, 2018first filing
Aug 1, 2018most 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 25MA AGMA AG noticefirst filing · 3 MA residentsday 0
  2. JUL 25NH AGNH AG notice2 NH residentsday 0
  3. JUL 25MT AGMT AG notice1 MT residentsday 0
  4. AUG 1CA AGCA AG noticemost recent · 1,034 CA residents+7d
  5. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Nov 29, 2017 – Dec 4, 2017
NH AG
Discovered
Dec 4, 2017· 5d undetected
NH AG + MT AG + CA AG
Data types
Credentials · Employment · Financial account · Health (basic) · Identity (basic) · Government ID · PCI · PII
MA AG + NH AG + CA AG +1
Attack vector
Phishing
NH AG

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

CA1,034
MA3
NH2
MT1

State AGs report only their own residents; teal bars show each state's reported slice.

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

7 days

Cadence

~1 / 2.3d

vs. multi-state median

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