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

Schwan's Home Service — October 2015 breach

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

✓ data types agreeMerge100%

Determination

Confirmed

Members

4 filings

States

4

Affected · reported

213

First → last filing

Aug 4, 2016 → Aug 31, 2016

Merge confidence

100%

incident inc_33fa577b73fb43fa · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 4 regulatory filings. The filings describe a third-party compromise. Intrusion Oct 9, 2015–Aug 1, 2016, discovered Aug 1, 2016 — the first regulatory filing landed 3 days later. 213 individuals reported across the linked filings. Data reported: Identity (basic) and Financial account. Notifications rolled out on a 27-day schedule across 4 filings beginning Aug 4, 2016. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
3days

Discovered → first regulatory filing

Filing span
27days

Time between earliest and latest filing

Not recorded for this incident

Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.

Regulatory clocksOregon✓ OR AG ≤45dFull clock table in Litigation Timeline

Incident timeline

Oct 9, 2015breach begins
Aug 1, 2016discovered
notification delay · 3 days
Aug 4, 2016first filing
Aug 31, 2016most 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. AUG 4NH AGNH AG noticefirst filing · 78 NH residentsday 0
  2. AUG 15MT AGMT AG notice135 MT residents+11d
  3. AUG 22CA AGCA AG noticeno count stated+18d
  4. AUG 31OR AGOR AG noticemost recent · no count stated+27d
  5. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Oct 9, 2015
NH AG
Discovered
Aug 1, 2016· 297d undetected
OR AG
Data types
Financial account · Identity (basic)
NH AG + CA AG
Attack vector
Third-Party / Supply Chain
NH 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

27 days

Cadence

~1 / 9d

vs. multi-state median

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