The Gill Corporation reported a data breach to the Indiana Attorney General. The breach occurred on 2024-06-23 and was reported on 2024-09-16. 2 Indiana residents were affected. 3,232 individuals affected in total.
Affected (this filing): 3,232
Clustered 2 filings across 2 jurisdictions · filing window Sep 16, 2024 → Sep 19, 2024. View entity profile → Other incidents for this victim →
incident inc_9772e59176644994 · 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 ME
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jun 23, 2024
When the intrusion reportedly occurred, per the linked filings
Jun 23, 2024
Reported by MAINE AG filing
The Gill Corporation reported a data breach to the Indiana Attorney General. The breach occurred on 2024-06-23 and was reported on 2024-09-16. 2 Indiana residents were affected. 3,232 individuals affected in total.
Affected (this filing): 3,232
The Gill Corporation, a commercial entity, experienced an external system breach (hacking) on June 23, 2024, which was discovered the same day. The breach affected 3,232 individuals in total, including one resident of Maine. The company notified the affected Maine resident on September 16, 2024, and offered 12 months of identity theft protection services through Experian IdentityWorks.
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.