Confirmed breach. Intrusion Jul 9, 2024–Jul 16, 2024, discovered Oct 22, 2024 — the first regulatory filing landed 29 days later. 37,064 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 · 29dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Affected (total reported)
37,064
Data types
2
PII · Government ID
Jurisdictions
2
IN ME
Linked filings
2
all State AG
Sensitive data
identity_government
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Jul 9, 2024
When the intrusion reportedly occurred, per the linked filings
105 days
Breach discovered
Oct 22, 2024
Reported by MAINE AG filing
🏎️Indiana State AGFirst filinglinked via multistate filing link · 100%
Saint Thomas Aquinas High School Inc reported a data breach to the Indiana Attorney General. The breach occurred on 2024-07-09 and was reported on 2024-11-20. 13 Indiana residents were affected. 37,064 individuals affected in total.
Saint Thomas Aquinas High School Inc. (Fort Lauderdale, FL) suffered an external system breach (hacking) between July 9–16, 2024, discovered on October 22, 2024. A total of 37,064 individuals were affected, including 6 Maine residents. Affected data included personal identifiers and Social Security numbers. Notifications were sent electronically on November 20, 2024. Twelve-month credit monitoring and identity theft protection were offered through CyberScout/TransUnion.
Affected (this filing): 6
ME AG ≤30d · 29d
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.