Clustered 3 filings across 2 jurisdictions · filing window Sep 28, 2021 → Nov 1, 2021. View entity profile → Other incidents for this victim →
incident inc_c1edfede965c49e4 · merge_method human · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
ME MT
Time between earliest and latest filing
Not recorded for this incident
Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.
all State AG
per-filing reported counts
State AGs report only their own residents; bars show per-filing counts.
Earliest sighting first · deep chronology in Litigation Timeline
May 17, 2021
When the intrusion reportedly occurred, per the linked filings
Sep 9, 2021
Reported by MAINE AG filing
Layman, Diener, and Borntrager Insurance Agency reported a data breach to the Montana Attorney General. The breach was reported on 2021-09-28. The breach occurred on 5/17/2021. 7 Montana residents were affected.
Affected (this filing): 7
Oct 21, 2021
Reported by MAINE AG filing
Layman, Diener, and Borntrager Insurance Agency reported an internal system breach occurring on May 17, 2021, discovered on September 9, 2021. The incident compromised the names and driver's license numbers of 7,909 individuals, including 7 Maine residents. The agency provided 12 months of credit monitoring and identity protection services to affected parties.
Affected (this filing): 7,909
Layman, Diener, and Borntrager Insurance Agency reported a data breach affecting 7,909 individuals. The breach, which occurred on May 17, 2021, and was discovered on October 21, 2021, was described as an internal system breach. Compromised information included names and driver's license or non-driver identification card numbers. The company began notifying affected individuals in writing on October 29, 2021, and offered 12 months of credit monitoring and identity theft protection services through IDX.
Affected (this filing): 7,909
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.