Dassault Falcon Jet Corp. reported a data breach to the Montana Attorney General. The breach was reported on 2020-12-31. The breach occurred on 12/6/2020. 10 Montana residents were affected.
Affected (this filing): 10
Clustered 2 filings across 2 jurisdictions · filed Dec 31, 2020. View entity profile → Other incidents for this victim →
incident inc_e86dec50f4ed4243 · 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.
DE MT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Dec 6, 2020
When the intrusion reportedly occurred, per the linked filings
Dec 6, 2020
Reported by DELAWARE AG filing
Dassault Falcon Jet Corp. reported a data breach to the Montana Attorney General. The breach was reported on 2020-12-31. The breach occurred on 12/6/2020. 10 Montana residents were affected.
Affected (this filing): 10
Dassault Falcon Jet Corp. notified Delaware AG of a December 6, 2020 data security incident affecting systems and subsidiaries. Unauthorized access occurred to systems containing current and former employee PII, including SSNs, driver's licenses, passport info, and financial account numbers. Spouse/dependent data (name, address, DOB, SSN) was also potentially compromised. The company took systems offline, engaged forensic experts and law enforcement, and offered IDX identity protection services.
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.