Confirmed breach. Intrusion Feb 7, 2020–May 20, 2020, discovered Dec 5, 2020 — the first regulatory filing landed 30 days later. 5,492 individuals reported across the linked filings.
incident inc_ca7e7c52ce444be1 · merge_method human · confidence 100%
Litigation Timing
Notification delay
30days
Discovered → first regulatory filing
Filing span
0days
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 clocksMaine✓ ME AG ≤30d · 30dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced
Affected (total reported)
5,492
Data types
—
Jurisdictions
2
ME MT
Linked filings
2
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Feb 7, 2020
When the intrusion reportedly occurred, per the linked filings
Florida Gulf Coast University Foundation, Inc. (Blackbaud) reported a data breach to the Montana Attorney General. The breach was reported on 2021-01-04. The breach occurred from 2/7/2020 to 5/20/2020. 3 Montana residents were affected.
Affected (this filing): 3
🦞Maine State AGMost recentlinked via operator-confirmed · 100%
Florida Gulf Coast University Foundation, Inc. reported a ransomware incident involving its vendor, Blackbaud, occurring between May 14 and May 20, 2020. The breach was discovered on December 5, 2020, affecting 5,489 individuals, including 26 Maine residents. Personal information and financial account numbers were compromised. The Foundation provided 12 months of credit monitoring and identity restoration services through TransUnion to affected individuals.
Affected (this filing): 5,489
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.