Confirmed breach. Intrusion Oct 14, 2020, discovered Nov 18, 2020 — the first regulatory filing landed 175 days later (flagged late). 3,217 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 · 175dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Affected (total reported)
3,217
Data types
2
Government ID · Identity (basic)
Jurisdictions
1
ME
Linked filings
1
all State AG
Sensitive data
identity_government
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Oct 14, 2020
When the intrusion reportedly occurred, per the linked filings
Bridgewater College reported an internal system breach on 10/14/2020, discovered on 11/18/2020. The incident affected 3,217 individuals, including 4 Maine residents. Acquired data included names and Social Security Numbers. The College provided written notification and offered credit monitoring services through IDX.
Affected (this filing): 3,217
ME AG >90d · 175dME resident >60d · 160d
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.