Clustered 2 filings across 2 jurisdictions · filing window Apr 30, 2025 → May 1, 2025. View entity profile → Other incidents for this victim →
incident inc_2a267584a12c45ee · 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)
CA IN
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Nov 12, 2024
When the intrusion reportedly occurred, per the linked filings
Nov 13, 2024
Reported by CALIFORNIA AG filing
Conrey Insurance Brokers & Risk Managers reported a data breach to the Indiana Attorney General. The breach occurred on 2024-11-12 and was reported on 2025-04-30. 8 Indiana residents were affected. 8,759 individuals affected in total.
Affected (this filing): 8,759
Conrey Insurance Brokers & Risk Managers notified the California Attorney General of an unauthorized access incident. The breach occurred between November 12 and November 13, 2024, and was discovered on November 13, 2024. The company identified unusual activity and investigated, determining that unauthorized access occurred. Affected data includes names and potentially other personal information. The company notified law enforcement, changed network passwords, reviewed policies, and offered complimentary credit monitoring and identity protection services to affected individuals. The investigation and data review were completed on April 10, 2025.
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.