Great Star Tools USA reported a data breach to the Indiana Attorney General. The breach occurred on 2023-08-02 and was reported on 2024-11-12. 2 Indiana residents were affected. 4,472 individuals affected in total.
Affected (this filing): 4,472
Clustered 2 filings across 2 jurisdictions · filed Nov 12, 2024. View entity profile → Other incidents for this victim →
incident inc_c30ee24722ce4cdf · 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.
Identity (basic) · Government ID
CA IN
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Aug 2, 2023
When the intrusion reportedly occurred, per the linked filings
Aug 17, 2023
Reported by CALIFORNIA AG filing
Great Star Tools USA reported a data breach to the Indiana Attorney General. The breach occurred on 2023-08-02 and was reported on 2024-11-12. 2 Indiana residents were affected. 4,472 individuals affected in total.
Affected (this filing): 4,472
Great Star Tools USA, Inc. reported an incident where an unauthorized actor accessed certain systems between August 2 and August 17, 2023. The company detected suspicious activity on August 17, 2023. The investigation determined that name and other data elements were present in the accessible data. The company secured its systems, engaged third-party specialists, notified law enforcement, and is offering credit monitoring services.
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.