DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79
State AGConfirmed2 filings · 2 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 2 filings

Staten Island Academy — May 2020 breach

Clustered 2 filings across 2 jurisdictions · filing window Jan 19, 2021 → Jan 25, 2021. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

2 filings

States

2

Affected · reported

3

First → last filing

Jan 19, 2021 → Jan 25, 2021

Merge confidence

100%

incident inc_9e47f412bdee4636 · 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, 2 legal records. Intrusion May 1, 2020–May 20, 2020, discovered Jul 16, 2020 — the first regulatory filing landed 187 days later. 3 individuals reported across the linked filings. This page is the deduped roll-up; each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
187days

Discovered → first regulatory filing

Filing span
6days

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.

Sensitive data

identity_government

Incident timeline

May 1, 2020breach begins
Jul 16, 2020discovered
notification delay · 187 days
Jan 19, 2021first filing
Jan 25, 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. JAN 19MA AGMA AG noticefirst filing · 2 MA residentsday 0
  2. JAN 25NH AGNH AG noticemost recent · 1 NH residents+6d
  3. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 1, 2020 – May 20, 2020
NH AG
Discovered
Jul 16, 2020· 76d undetected
NH AG
Data types
Government ID · Identity (basic) · Financial account
MA AG + NH AG
Attack vector
Ransomware
NH AG
Response
Engaged forensic investigators · Notified law enforcement · Provided notice to potentially affected individuals
NH AG

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

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

vs. multi-state median

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