Clustered 2 filings across 2 jurisdictions · filed Oct 29, 2024. View entity profile → Other incidents for this victim →
incident inc_d74341f721b44d07 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Identity (basic)
Time between earliest and latest filing
Not recorded for this incident
Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.
NH VT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jul 3, 2024 → Jul 11, 2024
When the intrusion reportedly occurred, per the linked filings
Jul 9, 2024
Reported by VERMONT AG, NEW HAMPSHIRE AG filings
Horizontal Integration, Inc. notified consumers of a data breach where unauthorized access occurred between July 3-11, 2024. The incident involved the exfiltration of personal information, including names. The company engaged third-party cybersecurity specialists, secured systems, and offered 24 months of credit monitoring via Experian. The investigation was determined to be contained as of September 17, 2024.
Horizontal Integration, Inc. reported unauthorized access to its network systems between July 3 and July 11, 2024. The company identified unexpected network activity on July 9, 2024, and engaged third-party cybersecurity specialists. Personal information of residents in New Hampshire and Rhode Island was potentially impacted. The company is offering 24 months of credit monitoring and identity restoration services through Experian.
Affected (this filing): 5
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.