Confirmed breach. Intrusion Apr 29, 2023–May 30, 2023, discovered May 30, 2023 — the first regulatory filing landed 184 days later. 2 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.
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Affected (total reported)
2
Data types
3
Identity (basic) · Government ID · Health (basic)
Jurisdictions
2
CA MT
Linked filings
2
all State AG
Sensitive data
identity_government
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Apr 29, 2023 → May 30, 2023
When the intrusion reportedly occurred, per the linked filings
Livermore Amador Valley Transit Authority (LAVTA) notified individuals that unauthorized access occurred between April 29, 2023, and May 30, 2023. The incident, discovered on May 30, 2023, involved the potential exfiltration of names, addresses, dates of birth, and medical information. The investigation is ongoing. LAVTA secured systems and is reviewing security policies.
🦬Montana State AGMost recentlinked via multistate filing link · 100%
Livermore Amador Valley Transit Authority reported a data breach to the Montana Attorney General. The breach was reported on 2023-11-30. The breach occurred from 4/29/2023 to 5/30/2023. 2 Montana residents were affected.
Affected (this filing): 2
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.