Confirmed breach. Intrusion Jun 22, 2020, discovered Jun 22, 2020 — the first regulatory filing landed 130 days later (flagged late). 1 individuals reported across the linked filings.
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 clocksMaine✗ ME AG >90d · 130dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Affected (total reported)
1
Data types
3
Identity (basic) · Authentication · Health (basic)
Jurisdictions
1
ME
Linked filings
1
all State AG
Sensitive data
authentication
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Jun 22, 2020
When the intrusion reportedly occurred, per the linked filings
An unauthorized actor utilized credentials sourced from other data breaches to gain access to a user's account on the Castlight application. This breach resulted in the potential compromise of the user's first and last name, account password, and both personal health and health insurance information.
Affected (this filing): 1
ME AG >90d · 130d
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.