DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
State AGConfirmed5 filings · 5 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 5 filings

Dassault Falcon Jet — June 2020 breach

Clustered 5 filings across 5 jurisdictions · filing window Dec 31, 2020 → Jan 6, 2021. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

5 filings

States

5

Affected · reported

94

First → last filing

Dec 31, 2020 → Jan 6, 2021

Merge confidence

100%

incident inc_e86dec50f4ed4243 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings. Intrusion Jun 19, 2020–Dec 7, 2020, discovered Dec 6, 2020 — the first regulatory filing landed 25 days later. 94 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 2 more. Notifications rolled out on a 6-day schedule across 5 filings beginning Dec 31, 2020. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
25days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
6days

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.

Regulatory clocksMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jun 19, 2020breach begins
Dec 6, 2020discovered
notification delay · 25 days
Dec 31, 2020first filing
Jan 6, 2021most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. DEC 31MT AGMT AG noticefirst filing · 10 MT residentsday 0
  2. DEC 31IN AGIN AG notice42 IN residentsday 0
  3. DEC 31DE AGDE AG noticeno count statedday 0
  4. JAN 5NH AGNH AG notice11 NH residents+5d
  5. JAN 6MA AGMA AG noticemost recent · 31 MA residents+6d
  6. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jun 19, 2020
IN AG
Discovered
Dec 6, 2020· 170d undetected
MT AG + DE AG + NH AG
Data types
Employment · Financial account · Identity (basic) · Government ID · PII
MT AG + DE AG + NH AG +1
Attack vector
Unauthorized Access
MT AG

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Affected residents by state

per-state reported counts

IN42
MA31
NH11
MT10

State AGs report only their own residents; teal bars show each state's reported slice.

Evidence ladder — rungs this incident occupies

Leak-site claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing5 members

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

No SEC filing or victim statement yet.

Merge provenance

Method
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Audit
Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).

Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.

Filing velocity

Spread

6 days

Cadence

~1 / 1.5d

vs. multi-state median

1.3× faster

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. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.

The weekly clock on records like this one

The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.

Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.