Confirmed breach. Intrusion Jan 18, 2025, discovered Jan 18, 2025 — the first regulatory filing landed 461 days later. 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.
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Affected (total reported)
1
Data types
2
Identity (basic) · Government ID
Jurisdictions
1
NH
Linked filings
1
all State AG
Sensitive data
identity_government
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Jan 18, 2025
When the intrusion reportedly occurred, per the linked filings
TechNH Inc. notified the New Hampshire Attorney General of a data event affecting one NH resident. Files containing names and SSNs were viewed/downloaded by an unknown actor on Jan 18, 2025. TechNH engaged cybersecurity specialists, notified federal law enforcement, and provided 12 months of credit monitoring. Incident status is contained.
Affected (this filing): 1
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.