Confirmed breach. Intrusion Jan 19, 2024, discovered Apr 10, 2024 — the first regulatory filing landed 36 days later. 574 individuals reported across the linked filings.
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 · 36dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Affected (total reported)
574
Data types
2
Government ID · PII
Jurisdictions
2
ME NH
Linked filings
2
all State AG
Sensitive data
identity_government
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Jan 19, 2024
When the intrusion reportedly occurred, per the linked filings
82 days
Breach discoveredAG web form
Apr 10, 2024
Reported by MAINE AG filing
36 days
⛰️New Hampshire State AGFirst filinglinked via multistate filing link · 100%
Central Catholic High School of Lawrence, Inc. notified 134 New Hampshire residents of a data security event on May 16, 2024. The school notified federal law enforcement and is providing credit monitoring services through Kroll. The specific data types and cause of the breach were redacted in the public filing.
Central Catholic High School of Lawrence Inc. reported an external system breach (hacking) occurring on January 19, 2024, discovered on April 10, 2024. The incident affected 574 individuals, including 10 Maine residents. Compromised data included names and Social Security Numbers. The school provided written notification and offered 12 months of credit monitoring through Kroll.
Affected (this filing): 574
ME AG >30d · 36d
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.