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

SPRINT LLC — account takeover notices

Clustered 5 filings across 5 jurisdictions · filing window Jul 3, 2019 → Aug 9, 2019 (dated filings only). View entity profile → Other incidents for this victim →

✓ data types, discovery date agreeMerge100%

Determination

Confirmed

Members

5 filings

States

5

Affected · reported

35

First → last dated filing

Jul 3, 2019 → Aug 9, 2019

Merge confidence

100%

incident inc_c995a6c62cdc4979 · merged by deterministic · confidence 100%

Account takeover notices. SPRINT LLC notified customers of unauthorized access to their accounts. Merged as one incident: 5 regulatory filings. Account access Jun 8, 2019–Jun 23, 2019, discovered Jun 22, 2019. 35 individuals reported across the linked filings. Data reported: Identity (basic) and Financial account. Notifications rolled out on a 37-day schedule across 4 dated filings beginning Jul 3, 2019. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
37days

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.

Incident timeline

Jun 8, 2019account access begins
Jun 22, 2019discovered
Jul 3, 2019first dated filing
Aug 9, 2019most recent dated filing

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 access they report began, are not placed on this rail.

Member cascade — every filing in this incident

  1. JAN 1IL AGIL AG noticefiling day not on record · no count stated—
  2. JUL 3CA AGCA AG noticefirst filing · no count statedday 0
  3. JUL 11DE AGDE AG notice1 affected+8d
  4. JUL 11MT AGMT AG notice1 MT residents+8d
  5. AUG 9SC AGSC AG noticemost recent · 34 SC residents+37d
  6. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Account access window
Jun 8, 2019 – Jun 23, 2019
CA AG
Discovered
Jun 22, 2019· 14d undetected
IL AG + CA AG + DE AG +2
Data types
Financial account · Identity (basic)
CA AG + DE AG + MT AG +1
Attack vector
Unauthorized Access
CA 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

SC34
DE1
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 filing5 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

37 days

Cadence

~1 / 12.3d

vs. multi-state median

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