Confirmed breach. Intrusion Feb 2, 2020, discovered May 1, 2020 — the first regulatory filing landed 168 days later (flagged late). 3,178 individuals reported across the linked filings.
Discovery variance · Leak precedence · Materiality delta · SEC filing delay · Filing span — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Regulatory clocksMaine✗ ME AG >90d · 168dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Affected (total reported)
3,178
Data types
2
Identity (basic) · Government ID
Jurisdictions
1
ME
Linked filings
1
all State AG
Sensitive data
identity_government
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Feb 2, 2020
When the intrusion reportedly occurred, per the linked filings
Columbus City Schools experienced a phishing attack that was discovered on May 1, 2020. The breach, which occurred on February 2, 2020, compromised the names and Social Security numbers of 3,178 individuals. Affected parties were notified on October 16, 2020, and offered 12 months of credit monitoring and identity protection services.
Affected (this filing): 3,178
ME AG >90d · 168dME resident >60d · 168d
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.