All incidents View linkage analytics →Get the evidence package — $79

Confirmed3 filings · 3 statesUnverified claimConfirmedEnforcedhigh sensitivity

Merged incident · 3 filings

Stetson — February 2020 breach

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

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

3 filings

States

Affected · reported

1,158

First → last filing

Oct 8, 2020 → Nov 3, 2020

Merge confidence

100%

incident inc_7e75d3e2c0d24ee2 · merged by deterministic · confidence 100%

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

Confirmed breach. One breach, 3 legal records. Intrusion Feb 7, 2020–May 20, 2020, discovered Jul 16, 2020 — the first regulatory filing landed 84 days later. 1,158 individuals reported across the linked filings. Notifications rolled out on a 26-day schedule across 3 filings beginning Oct 8, 2020. This page is the deduped roll-up; each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Notification delay

84days

Discovered → first regulatory filing

Discovery variance

0days

Range of discovered_at dates across filings

Filing span

26days

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.

Sensitive data

identity_government

Incident timeline

Feb 7, 2020breach begins

Jul 16, 2020discovered

notification delay · 84 days

Oct 8, 2020first filing

Nov 3, 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

OCT 8NH AGNH AG noticefirst filing · 198 NH residentsday 0
NOV 3MA AGMA AG notice845 MA residentsauto-linked+26d
NOV 3CA AGCA AG noticemost recent · 115 CA residentsauto-linked+26d
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Feb 7, 2020 – May 20, 2020
Discovered: Jul 16, 2020· 160d undetected
Data types: Identity (basic) · Government ID
Attack vector: Third-Party / Supply Chain
Response: Commenced an investigation · Engaged external cybersecurity professionals · Providing the affected residents with written notification

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

MA845

NH198

CA115

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

26 days

Cadence

~1 / 13d

vs. multi-state median

5.2× 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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.