Wettermark Keith LLC reported a data breach to the Indiana Attorney General. The breach occurred on 2025-04-14 and was reported on 2025-10-01. 53 Indiana residents were affected.
Affected (this filing): 53
Clustered 2 filings across 2 jurisdictions · filing window Oct 1, 2025 → Oct 7, 2025. View entity profile → Other incidents for this victim →
incident inc_90c307e09f9c47d3 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
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.
IN NH
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Apr 14, 2025
When the intrusion reportedly occurred, per the linked filings
Apr 14, 2025
Reported by NEW HAMPSHIRE AG filing
Wettermark Keith LLC reported a data breach to the Indiana Attorney General. The breach occurred on 2025-04-14 and was reported on 2025-10-01. 53 Indiana residents were affected.
Affected (this filing): 53
Wettermark Keith LLC reported a cyber incident on April 14, 2025, involving unauthorized access to its internal computer system. The breach potentially exposed personal information of one New Hampshire resident, including names, SSNs, driver's license numbers, financial account numbers, and medical information. The firm engaged forensic investigators, contained the breach, and offered 12 months of credit monitoring to the affected individual. Notification was sent to the NH Attorney General on October 7, 2025.
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.