Discovery variance · Leak precedence · Materiality delta · SEC filing delay · Filing span — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Regulatory clocksCalifornia✓ CA 60-day OK · 0dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Affected (total reported)
—
Data types
2
Credentials · Authentication
Jurisdictions
1
CA
Linked filings
1
all State AG
Sensitive data
authentication
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
May 7, 2017 → Jul 22, 2017
When the intrusion reportedly occurred, per the linked filings
Sprint notified California residents of a security incident where a fraudulent device insurance claim was attempted on accounts between May 7 and July 22, 2017. The incident compromised customer Sprint account PINs and security questions/answers. Sprint sent SMS notifications and reset credentials for affected users. No financial cost was incurred by customers.
CA 60-day OK · 0d
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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.