DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
State AGConfirmed13 filings · 13 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 13 filings

STRATEGIC EDUCATION, INC. — February 2026 breach

Clustered 13 filings across 13 jurisdictions · filing window May 29, 2026 → Jun 2, 2026. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

13 filings

States

13

Affected · reported

1,513,518

First → last filing

May 29, 2026 → Jun 2, 2026

Merge confidence

100%

incident inc_997e4dfab9174675 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 13 regulatory filings. The filings describe unauthorized access. Intrusion Feb 23, 2026–Feb 25, 2026, discovered Feb 25, 2026 — the first regulatory filing landed 93 days later (flagged late). 1,513,518 individuals reported across the linked filings. Data reported: Government ID and Identity (basic). Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
93days

Discovered → first regulatory filing

Discovery variance
85days

Range of discovered_at dates across filings

Filing span
4days

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 clocksOregon✗ OR AG >45dWashington✗ WA AG >90dCalifornia✓ CA AG copy ≤15d · 11dMaine✓ ME AG ≤30d · 11dIowa✓ IA AG ≤5 bdayTexas✓ TX AG ≤30dSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Feb 23, 2026breach begins
Feb 25, 2026discovered · members disagree
notification delay · 93 days
May 29, 2026first filing
Jun 2, 2026most 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 29IN AGIN AG noticefirst filing · states nationwide total 1,513,518day 0
  2. MAY 29DE AGDE AG noticeno count statedday 0
  3. JUN 1CA AGCA AG noticeno count stated+3d
  4. JUN 1VT AGVT AG notice1,065 VT residents+3d
  5. JUN 1IL AGIL AG noticeno count stated+3d
  6. JUN 1OR AGOR AG noticestates nationwide total 1,513,518+3d
  7. JUN 1ME AGME AG notice2,673 ME residents+3d
  8. JUN 1IA AGIA AG notice7,157 IA residents+3d
  9. JUN 1MA AGMA AG notice8,188 MA residents+3d
  10. JUN 1WA AGWA AG notice14,112 WA residents+3d
  11. JUN 1NH AGNH AG notice2,274 NH residents+3d
  12. JUN 2TX AGTX AG noticestates nationwide total 1,513,518+4d
  13. JUN 2SC AGSC AG noticemost recent · 63,272 SC residents+4d
  14. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 23, 2026
IN AG
Discovered
Feb 25, 2026OR AG + WA AG + SC AGMay 21, 2026IL AG + ME AG + TX AGfilings disagree on discovery
Data types
Identity (basic) · Government ID
DE AG + CA AG + ME AG +8
Attack vector
Unauthorized Access
ME AG

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

Count reconciliation

per-state reported counts

Nationwide (stated in a filing)

1,513,518

Sum of filed state slices

221,450· 14.6% of stated

85% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

US1,513,518
TX100,845
SC63,272
IN21,864
WA14,112
MA8,188
IA7,157
ME2,673
NH2,274
VT1,065

State AGs report only their own residents; teal bars show each state's reported slice. The gray US row is the nationwide total reported in a linked filing.

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 filing13 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
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Jun 12, 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

4 days

Cadence

~1 / 0.3d

vs. multi-state median

2.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.