Confirmed breach. Intrusion Feb 6, 2022–Feb 11, 2022, discovered Aug 9, 2022 — the first regulatory filing landed 23 days later (flagged late). 15 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 clocksLeak gap✗ Leak >180dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Affected (total reported)
15
Data types
2
Government ID · Identity (basic)
Jurisdictions
1
NH
Linked filings
1
all State AG
Sensitive data
identity_government
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Feb 6, 2022 → Feb 11, 2022
When the intrusion reportedly occurred, per the linked filings
San Francisco 49ers notified NH AG of unauthorized access to corporate IT network files between Feb 6-11, 2022. Incident involved names and SSN/driver's license data for 15 NH residents. Discovered Aug 9, 2022. Notifications mailed Sept 1, 2022. Response included forensic engagement, law enforcement notification, and credit monitoring offers.
Affected (this filing): 15
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.