All incidents View linkage analytics →Get the evidence package — $79 what’s inside →

Confirmed2 filings · 1 stateUnverified claimConfirmedEnforcedhigh sensitivity

Merged incident · 2 filings

North Gem School District No. 149 — December 2024 breach

Clustered 2 filings across 1 jurisdiction · filing window Jan 10, 2025 → Jan 15, 2025. View entity profile → Other incidents for this victim →

Agreement not assessableMerge61%

Determination

Confirmed

Members

2 filings

States

Affected · reported

—

First → last filing

Jan 10, 2025 → Jan 15, 2025

Merge confidence

61%

incident inc_61dafb93f94d4bed · merged by llm · confidence 61%

Part of the PowerSchool supply-chain incident (2025) — at least 65 organizations filed notifications naming this third party.

Confirmed breach. Merged as one breach: 2 regulatory filings. The filings describe a third-party compromise. Intrusion Dec 28, 2024, discovered Jan 10, 2025. Data reported: Government ID, PII, and Identity (basic). Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay

0days

Discovered → first regulatory filing

Filing span

5days

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.

Sensitive data

identity_government

Incident timeline

Dec 28, 2024breach begins

Jan 10, 2025discovered

notification delay · 0 days

Jan 10, 2025first filing

Jan 15, 2025most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

JAN 10ID AGID AG noticefirst filing · no count statedday 0
JAN 15ID AGID AG noticemost recent · no count stated+5d
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Dec 28, 2024
Discovered: Jan 10, 2025· 13d undetected
Data types: Identity (basic) · Government ID · PII
Attack vector: Third-Party / Supply Chain

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

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 filing2 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: llm
Confidence: 0.61 · below the 0.85 auto-merge floor
Audit: Every link edge records its method, confidence and model + prompt versions (61% is the strongest edge).

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

Filing velocity

Spread

5 days

vs. multi-state median

1.6× 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.