DisclosureLens
State AGConfirmed2 filings · 1 stateLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedcritical sensitivity
Merged incident · 2 filings

Rocklin Unified School District — December 2021 breach

Clustered 2 filings across 1 jurisdiction · filing window May 4, 2022 May 13, 2022. View entity profile → Other incidents for this victim →

Determination

Confirmed

Members

2 filings

States

1

Affected · reported

First → last filing

May 4, 2022 May 13, 2022

Merge confidence

89%

incident inc_e83f9107be8e48c4 · merged by deterministic · confidence 89%

Confirmed breach. Merged as one breach: 2 regulatory filings. The filing describes hacking. Intrusion Dec 28, 2021–Jan 8, 2022, discovered Jan 8, 2022 — the first regulatory filing landed 116 days later. Data reported: Minor, PII, Identity (basic), and 1 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
116days

Discovered → first regulatory filing

Filing span
9days

Time between earliest and latest filing

Not recorded for this incident

Discovery variance · Leak precedence · Materiality delta · SEC filing delayno leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.

Sensitive data

minor

Incident timeline

Dec 28, 2021breach begins
Jan 8, 2022discovered
notification delay · 116 days
May 4, 2022first filing
May 13, 2022most recent filing

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

Member cascade — every filing about this breach

  1. MAY 4CA AGCA AG noticefirst filing · no count statedday 0
  2. MAY 13CA AGCA AG noticemost recent · no count stated+9d
  3. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 28, 2021Jan 8, 2022
CA AG
Discovered
Jan 8, 2022· 11d undetected
CA AG
Data types
Education · Identity (basic) · Minor · PII
CA AG

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
deterministic
Confidence
0.89 · above the 0.85 auto-merge floor
Audit
Every link edge records its method, confidence and model + prompt versions (89% is the strongest edge).

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

Filing velocity

Spread

9 days

vs. multi-state median

1.1× slower

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.