All incidents View linkage analytics →Get the evidence package — $79 what’s inside →

Confirmed3 filings · 3 statesUnverified claimConfirmedEnforcedhigh sensitivity

Merged incident · 3 filings

THE NEMOURS FOUNDATION — August 2011 breach

Clustered 3 filings across 3 jurisdictions · filing window Oct 6, 2011 → Oct 11, 2011. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

3 filings

States

Affected · reported

1,055,489

First → last filing

Oct 6, 2011 → Oct 11, 2011

Merge confidence

100%

incident inc_36e10658573f494b · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 3 regulatory filings. The filing describes unauthorized access. Intrusion Aug 1, 2011–Aug 31, 2011. 1,055,489 individuals reported across the linked filings. Data reported: Government ID, PHI, Health (basic), and 2 more. Notifications rolled out on a 5-day schedule across 3 filings beginning Oct 6, 2011. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Filing span

5days

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.

Regulatory clocksHIPAA✓ HHS notifiedFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Aug 1, 2011breach begins

Oct 6, 2011first filing

Oct 11, 2011most recent filing

No discovery date is recorded on any filing in this cluster, so the notification delay is not computable. Dashed segments fill in as filings merge.

Member cascade — every filing about this breach

OCT 6NH AGNH AG noticefirst filing · no count statedauto-linkedday 0
OCT 7HHS OCRHHS OCR noticestates nationwide total 1,055,489auto-linked+1d
OCT 11MA AGMA AG noticemost recent · 804 MA residentsauto-linked+5d
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Aug 1, 2011 – Aug 31, 2011
Discovered: —
Data types: Financial account · Health (basic) · Identity (basic) · Government ID · PHI
Attack vector: Unauthorized Access

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

Count reconciliation

per-state reported counts

Nationwide (stated in a filing)

1,055,489

Sum of filed state slices

804· 0.1% of stated

100% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

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 filing3 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

5 days

Cadence

~1 / 2.5d

vs. multi-state median

1.6× 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.