Clustered 2 filings across 2 jurisdictions · filing window Sep 16, 2025 → Sep 18, 2025. View entity profile → Other incidents for this victim →
incident inc_4ebd07d03d604663 · 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.
Government ID · PHI · PII
MT TX
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Oct 25, 2024
When the intrusion reportedly occurred, per the linked filings
Jan 16, 2025
Reported by TEXAS AG filing
Insight Partners reported a data breach to the Montana Attorney General. The breach was reported on 2025-09-16. The breach occurred on 10/25/2024. 20 Montana residents were affected.
Affected (this filing): 20
Insight Partners based in New York, New York, a financial services entity reported a data breach to the Texas Attorney General. The breach was discovered on 2025-01-16 and reported on 2025-09-18. 542 Texas residents were affected. 12,657 individuals affected in total. Types of information involved: Name of individual;Address;Social Security Number Information;Driver’s License number;Government-issued ID number (e.g. passport, state ID card);Financial Information (e.g. account number, credit or debit card number);Medical Information;Health Insurance Information;Date of Birth. Consumers were notified via U.S. Mail.
Affected (this filing): 542
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.