Clustered 2 filings across 2 jurisdictions · filing window Jan 7, 2025 → Jan 14, 2025. View entity profile → Other incidents for this victim →
incident inc_0fae77905b284a69 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
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.
NH WI
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Dec 28, 2024
When the intrusion reportedly occurred, per the linked filings
Dec 28, 2024
Reported by NEW HAMPSHIRE AG filing
PowerSchool reported a data breach to the Wisconsin DATCP. The public was notified on 2025-01-07. The incident occurred on Between December 19 and December 28, 2024. Data accessed: Individuals' names, contact information, dates of birth, limited medical alert information, Social Security numbers, and other related information.
Perkins School for the Blind notified the New Hampshire Attorney General of a data security incident involving PowerSchool, a third-party data management provider. On December 28, 2024, PowerSchool discovered unauthorized access to its Student Information System (SIS) via a compromised credential. The breach affected 3 New Hampshire residents, involving parent and student contact information and Social Security Numbers. PowerSchool contained the incident, deactivated credentials, reset passwords, and engaged law enforcement (FBI). Perkins is offering credit monitoring to affected individuals.
Affected (this filing): 3
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.