Confirmed breach. Intrusion Jan 1, 2020–Apr 30, 2021, discovered Aug 11, 2021 — the first regulatory filing landed 121 days later (flagged late). 3 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 · 121dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Affected (total reported)
3
Data types
2
Identity (basic) · Government ID
Jurisdictions
1
ME
Linked filings
1
all State AG
Sensitive data
identity_government
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Jan 1, 2020 → Apr 30, 2021
When the intrusion reportedly occurred, per the linked filings
Valley County inadvertently disclosed personal information, including names and Social Security numbers. The breach occurred between January 2020 and April 2021, and was discovered in August 2021. Affected individuals were notified and offered 12 months of credit monitoring services from Experian.
Affected (this filing): 3
ME AG >90d · 121dME resident >60d · 121d
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.