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

KEMPER SPORTS MANAGEMENT, INC. — April 2024 breach

Clustered 10 filings across 10 jurisdictions · filed Sep 9, 2024 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

10 filings

States

10

Affected · reported

62,815

First → last dated filing

Sep 9, 2024

Merge confidence

100%

incident inc_cbfe79c431e646a8 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings. Intrusion Apr 1, 2024, discovered Apr 1, 2024. 62,815 individuals reported across the linked filings. Data reported: Government ID, PII, Identity (basic), and 5 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
0days

Range of discovered_at dates across filings

Filing span
0days

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 >45dWashington✗ WA AG >90dCalifornia✗ CA 60-day late · 161dVermont✗ VT AG >45 bdayMaine⏱ ME AG >30d · 161dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

authenticationidentity_government

Incident timeline

Apr 1, 2024breach begins
Apr 1, 2024discovered
Sep 9, 2024first dated filing
—watching for filings

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.

Member cascade — every filing about this breach

  1. SEP 1IL AGIL AG noticefiling day not on record · no count stated—
  2. SEP 9NH AGNH AG noticefirst filing · 11 NH residentsday 0
  3. SEP 9IN AGIN AG noticestates nationwide total 59,516day 0
  4. SEP 9ME AGME AG noticestates nationwide total 62,815day 0
  5. SEP 9OR AGOR AG noticestates nationwide total 62,815day 0
  6. SEP 9MT AGMT AG notice35 MT residentsday 0
  7. SEP 9WA AGWA AG notice1,929 WA residentsday 0
  8. SEP 9CA AGCA AG noticeno count statedday 0
  9. SEP 9VT AGVT AG noticeno count statedday 0
  10. SEP 9MA AGMA AG noticemost recent · 252 MA residentsday 0
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Apr 1, 2024
NH AG
Discovered
Apr 1, 2024
IL AG + NH AG + ME AG +5
Data types
Authentication · Employment · Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
NH AG + ME AG + MT AG +4
Attack vector
Unauthorized Access
ME AG

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

Count reconciliation

per-state reported counts

Nationwide (stated in a filing)

62,815

Sum of filed state slices

3,371· 5.4% of stated

95% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

US62,815
WA1,929
IN1,125
MA252
MT35
ME19
NH11

State AGs report only their own residents; teal bars show each state's reported slice. The gray US row is the nationwide total reported in a linked filing.

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

0 days

Cadence

~1 / 0d

vs. multi-state median

20.0× faster

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.