The Biltmore Company, LLC reported a data breach to the Montana Attorney General. The breach was reported on 2024-03-15. The breach occurred from 2/16/2024 to 2/23/2024. 10 Montana residents were affected.
Affected (this filing): 10
Clustered 2 filings across 2 jurisdictions · filed Mar 15, 2024. View entity profile → Other incidents for this victim →
incident inc_3328682494be4e0f · 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.
ME MT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Feb 16, 2024
When the intrusion reportedly occurred, per the linked filings
Feb 16, 2024
Reported by MAINE AG filing
The Biltmore Company, LLC reported a data breach to the Montana Attorney General. The breach was reported on 2024-03-15. The breach occurred from 2/16/2024 to 2/23/2024. 10 Montana residents were affected.
Affected (this filing): 10
The Biltmore Company, LLC experienced an external system breach (hacking) on 12/05/2023, discovered on 02/16/2024. Approximately 11,530 individuals were affected, including 35 Maine residents. Acquired data included names and financial account/credit card numbers. The company provided written notification on 03/15/2024 and offered 24 months of Equifax Credit WatchTM Gold services.
Affected (this filing): 11,530
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.