General Fasteners Company reported a data breach to the Indiana Attorney General. The breach occurred on 2024-05-24 and was reported on 2024-07-08. 23 Indiana residents were affected. 984 individuals affected in total.
Affected (this filing): 984
Clustered 2 filings across 2 jurisdictions · filed Jul 8, 2024. View entity profile → Other incidents for this victim →
incident inc_95753e1890b74bec · 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
May 24, 2024
When the intrusion reportedly occurred, per the linked filings
May 24, 2024
Reported by NEW HAMPSHIRE AG filing
General Fasteners Company reported a data breach to the Indiana Attorney General. The breach occurred on 2024-05-24 and was reported on 2024-07-08. 23 Indiana residents were affected. 984 individuals affected in total.
Affected (this filing): 984
General Fasteners Company notified the NH Attorney General of a data breach discovered on May 24, 2024. An unauthorized actor accessed files on GFC's servers containing the name of one New Hampshire resident. GFC secured the network, investigated, and mailed notification letters on July 8, 2024, offering one year of credit monitoring via NortonLifeLock.
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.