Ty Inc. reported a data breach to the Montana Attorney General. The breach was reported on 2023-09-15. The breach occurred on 4/26/2023. 2 Montana residents were affected.
Affected (this filing): 2
Clustered 2 filings across 2 jurisdictions · filing window Sep 15, 2023 → Sep 18, 2023. View entity profile → Other incidents for this victim →
incident inc_2dce1132a8e444d3 · merge_method llm · confidence 44%
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
ME MT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Apr 26, 2023
When the intrusion reportedly occurred, per the linked filings
Aug 28, 2023
Reported by MAINE AG filing
Ty Inc. reported a data breach to the Montana Attorney General. The breach was reported on 2023-09-15. The breach occurred on 4/26/2023. 2 Montana residents were affected.
Affected (this filing): 2
Ty Inc. experienced an external system breach (hacking) that occurred from April 21, 2023, to April 26, 2023. The breach was discovered on August 28, 2023. The personal information of 5 Maine residents was affected, including their names and Social Security numbers. Ty Inc. provided written notification to the affected individuals on September 15, 2023, and offered one year of credit monitoring and identity theft protection services through Kroll.
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.