Logit US Inc reported a data breach to the Indiana Attorney General. The breach occurred on 2024-08-18 and was reported on 2024-10-28. 102 Indiana residents were affected. 683 individuals affected in total.
Affected (this filing): 683
Clustered 2 filings across 2 jurisdictions · filing window Oct 28, 2024 → Oct 29, 2024. View entity profile → Other incidents for this victim →
incident inc_260a88bcbfd342a5 · 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
Aug 18, 2024
When the intrusion reportedly occurred, per the linked filings
Aug 19, 2024
Reported by MAINE AG filing
Logit US Inc reported a data breach to the Indiana Attorney General. The breach occurred on 2024-08-18 and was reported on 2024-10-28. 102 Indiana residents were affected. 683 individuals affected in total.
Affected (this filing): 683
Logit US, Inc. experienced an external system breach, described as a hacking incident, which occurred from August 18, 2024, to August 19, 2024. The breach was discovered on August 19, 2024. The incident affected 2 Maine residents. In response, the company offered twelve months of TransUnion Cyberscout identity theft and fraud monitoring services to those affected. Notification to consumers was sent on October 28, 2024.
Affected (this filing): 2
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.