Gemini Industries Inc reported a data breach to the Indiana Attorney General. The breach occurred on 2024-10-15 and was reported on 2025-04-02. 2 Indiana residents were affected. 557 individuals affected in total.
Affected (this filing): 557
Clustered 2 filings across 2 jurisdictions · filed Apr 2, 2025. View entity profile → Other incidents for this victim →
incident inc_72cba8d31dbf4d98 · 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.
PII
IN VT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Oct 15, 2024
When the intrusion reportedly occurred, per the linked filings
Oct 26, 2024
Reported by VERMONT AG filing
Gemini Industries Inc reported a data breach to the Indiana Attorney General. The breach occurred on 2024-10-15 and was reported on 2025-04-02. 2 Indiana residents were affected. 557 individuals affected in total.
Affected (this filing): 557
Gemini Industries, Inc. notified consumers of unauthorized access to its network between Oct 15 and Nov 14, 2024. Suspicious activity was detected on Oct 26, 2024. Files were taken without authorization. Personal information was contained in affected files. The company engaged forensic specialists, secured the network, and is offering complimentary credit monitoring via Experian.
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.