Confirmed breach. Intrusion Nov 7, 2022–Nov 28, 2022, discovered Nov 25, 2022 — the first regulatory filing landed 41 days later. 1 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 clocksMaine⏱ ME AG >30d · 41dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Affected (total reported)
1
Data types
2
Identity (basic) · Government ID
Jurisdictions
2
ME NH
Linked filings
2
all State AG
Sensitive data
identity_government
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Nov 7, 2022 → Nov 28, 2022
When the intrusion reportedly occurred, per the linked filings
Breach discovered
Nov 25, 2022
Reported by MAINE AG filing
41 days
⛰️New Hampshire State AGFirst filinglinked via multistate filing link · 100%
State AG breach notification filed by Vision Technologies in New Hampshire. The document provided is a consumer notification letter detailing identity theft protection resources, including credit monitoring, credit freezes, and fraud alerts. The specific incident details, dates, and data types are not present in this attachment.
Vision Technologies experienced an external system breach from November 7, 2022, to November 28, 2022, discovered on November 25, 2022. The breach compromised names and Social Security Numbers, affecting one Maine resident out of 2,111 total individuals. In response, the company offered 12 months of complimentary credit monitoring and identity theft protection services through Experian IdentityWorks.
Affected (this filing): 1
ME AG >30d · 41d
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.