CR&R Incorporated reported a data breach to the Indiana Attorney General. The breach occurred on 2022-10-19 and was reported on 2024-12-26. 6 Indiana residents were affected. 9,895 individuals affected in total.
Affected (this filing): 9,895
Clustered 2 filings across 2 jurisdictions · filing window Dec 26, 2024 → Jan 23, 2025. View entity profile → Other incidents for this victim →
incident inc_ff5d9edafeb94e67 · merge_method deterministic · confidence 95%
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 · Financial account
CA IN
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Oct 19, 2022
When the intrusion reportedly occurred, per the linked filings
CR&R Incorporated reported a data breach to the Indiana Attorney General. The breach occurred on 2022-10-19 and was reported on 2024-12-26. 6 Indiana residents were affected. 9,895 individuals affected in total.
Affected (this filing): 9,895
CR&R Incorporated reported a data breach to the California Attorney General. Unauthorized access occurred between October 19, 2022, and December 18, 2022. The incident potentially exposed personal information, including Social Security numbers, for residents of California and several other states. The company offered credit monitoring services and established a call center for affected individuals. The specific method of unauthorized access was not disclosed in the provided notice.
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.