DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
State AGConfirmed17 filings · 15 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedcritical sensitivity
Merged incident · 17 filings

PowerSchool — December 2024 breach

Clustered 17 filings across 15 jurisdictions · filing window Jan 27, 2025 → Jan 29, 2025 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

17 filings

States

15

Affected · reported

2,572,517

First → last dated filing

Jan 27, 2025 → Jan 29, 2025

Merge confidence

100%

incident inc_696ae92aa5e64f46 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 17 regulatory filings. The filings describe unauthorized access. Intrusion Dec 19, 2024–Dec 28, 2024, discovered Dec 19, 2024. 2,572,517 individuals reported across the linked filings. Data reported: Government ID, Minor, Identity (basic), and 4 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
9days

Range of discovered_at dates across filings

Filing span
2days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.

Regulatory clocksVermont⏱ VT AG >14 bdayWashington✓ WA AG ≤30dOregon✓ OR AG ≤45dMaine✓ ME AG ≤30d · 30dRhode Island✓ RI AG ≤45dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_governmentminor

Incident timeline

Dec 19, 2024breach begins
Dec 19, 2024discovered · members disagree
Jan 27, 2025first dated filing
Jan 29, 2025most recent dated filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.

Member cascade — every filing about this breach

  1. JAN 1IL AGIL AG noticefiling day not on record · no count stated—
  2. JAN 27ID AGID AG noticefirst filing · no count statedday 0
  3. JAN 27VT AGVT AG noticeno count statedday 0
  4. JAN 27ID AGID AG notice29,074 ID residentsday 0
  5. JAN 27CA AGCA AG noticeno count statedday 0
  6. JAN 27NH AGNH AG notice9,384 NH residentsday 0
  7. JAN 27WA AGWA AG notice314,107 WA residentsday 0
  8. JAN 27OR AGOR AG noticeno count statedday 0
  9. JAN 27MT AGMT AG notice41,520 MT residentsday 0
  10. JAN 27IA AGIA AG notice49,921 IA residentsday 0
  11. JAN 27ME AGME AG noticeno count statedday 0
  12. JAN 28RI AGRI AG notice6,766 RI residents+1d
  13. JAN 28RI AGRI AG noticeno count stated+1d
  14. JAN 28MA AGMA AG notice18,476 MA residents+1d
  15. JAN 29IN AGIN AG notice2,103,269 IN residents+2d
  16. JAN 29DE AGDE AG noticemost recent · no count stated+2d
  17. JAN 29NE AGNE AG noticefiling day not on record · no count stated—
  18. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 19, 2024 – Dec 28, 2024
ID AG
Discovered
Dec 19, 2024IL AGDec 28, 2024ID AG + VT AG + CA AG +9filings disagree on discovery
Data types
Education · Health (basic) · Identity (basic) · Government ID · Minor · PHI · PII
ID AG + VT AG + CA AG +9
Attack vector
Unauthorized Access
ID AG

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Affected residents by state

per-state reported counts

IN2,103,269
WA314,107
IA49,921
MT41,520
ID29,074
MA18,476
NH9,384
RI6,766

State AGs report only their own residents; teal bars show each state's reported slice.

Evidence ladder — rungs this incident occupies

Leak-site claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing17 members

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

No SEC filing or victim statement yet.

Merge provenance

Method
human
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Oct 22, 2026 · at least one link edge was human-adjudicated
Audit
Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).

Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.

Filing velocity

Spread

2 days

Cadence

~1 / 0.1d

vs. multi-state median

3.0× faster

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. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.

The weekly clock on records like this one

The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.

Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.