Confirmed breach. Intrusion Apr 15, 2025–Apr 21, 2025, discovered Apr 15, 2025 — the first regulatory filing landed 238 days later (flagged late). 340,101 individuals reported across the linked filings.
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Regulatory clocksVermont✗ VT AG >45 bdayLeak gap✗ Leak >180dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Affected (total reported)
340,101
Data types
2
Identity (basic) · Government ID
Jurisdictions
2
IN VT
Linked filings
2
all State AG
Sensitive data
identity_government
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Apr 15, 2025 → Apr 21, 2025
When the intrusion reportedly occurred, per the linked filings
Pierce County Library System notified consumers of unauthorized access to its systems between April 15-21, 2025. Personal information, including names and government identifiers, was copied. PCLS offered complimentary credit monitoring and identity protection services through IDX.
VT AG >45 bdayLeak >180d
🏎️Indiana State AGMost recentlinked via multistate filing link · 100%
Pierce County Library System reported a data breach to the Indiana Attorney General. The breach occurred on 2025-04-15 and was reported on 2025-12-09. 10 Indiana residents were affected. 340,101 individuals affected in total.
Affected (this filing): 340,101
Leak >180d
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.