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

Confirmed3 filings · 2 statesUnverified claimConfirmedEnforcedhigh sensitivity

Merged incident · 3 filings

Planned Parenthood of Northern New England, Inc. — February 2020 breach

Clustered 3 filings across 2 jurisdictions · filing window Nov 3, 2020 → Nov 16, 2020. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

3 filings

States

Affected · reported

First → last filing

Nov 3, 2020 → Nov 16, 2020

Merge confidence

100%

incident inc_3efea69ec8c3426f · merged by deterministic · confidence 100%

Part of the BLACKBAUD, INC. supply-chain incident (2020) — at least 175 organizations filed notifications naming this third party.

Confirmed breach. Merged as one breach: 3 regulatory filings. Intrusion Feb 7, 2020–May 20, 2020, discovered Jul 16, 2020 — the first regulatory filing landed 110 days later (flagged late). 10 individuals reported across the linked filings. Data reported: Identity (basic), Financial account, and Financial credentials. Notifications rolled out on a 13-day schedule across 3 filings beginning Nov 3, 2020. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Notification delay

110days

Discovered → first regulatory filing

Discovery variance

0days

Range of discovered_at dates across filings

Filing span

13days

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 clocksMaine✗ ME AG >90d · 110dFull clock table in Litigation Timeline

Sensitive data

financial_credentials

Incident timeline

Feb 7, 2020breach begins

Jul 16, 2020discovered

notification delay · 110 days

Nov 3, 2020first filing

Nov 16, 2020most recent filing

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

Member cascade — every filing about this breach

NOV 3ME AGME AG noticefirst filing · states nationwide total 10day 0
NOV 6NH AGNH AG notice2 NH residentsauto-linked+3d
NOV 16ME AGME AG noticemost recent · states nationwide total 10+13d
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Feb 7, 2020
Discovered: Jul 16, 2020· 160d undetected
Data types: Identity (basic) · Financial account · Financial credentials
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)

Sum of filed state slices

4· 40.0% of stated

60% 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

13 days

Cadence

~1 / 6.5d

vs. multi-state median

1.6× slower

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.