DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
SEC 8-KState AGConfirmed15 filings · 15 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 15 filings

The University of Phoenix, Inc. — August 2025 breach

Clustered 15 filings across 15 jurisdictions · filing window Nov 21, 2025 → Jan 1, 2026. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

15 filings

States

15

Affected · reported

3,669,567

First → last filing

Nov 21, 2025 → Jan 1, 2026

Merge confidence

100%

incident inc_7944c7952c2b41d0 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 15 regulatory filings. The filings describe unauthorized access. Intrusion Aug 1, 2025–Aug 22, 2025, discovered Nov 21, 2025. 3,669,567 individuals reported across the linked filings. Data reported: Government ID, Financial account, Identity (basic), and 1 more. Notifications rolled out on a 41-day schedule across 15 filings beginning Nov 21, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
0days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
41days

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.

Regulatory clocksMassachusetts✓ MA credit monitoring dueWashington✓ WA AG ≤30dMaine✓ ME AG ≤30d · 30dIowa✓ IA AG ≤5 bdayOregon✓ OR AG ≤45dCalifornia✓ CA 60-day OK · 31dTexas✓ TX CRA notice dueSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Aug 1, 2025breach begins
Nov 21, 2025discovered
notification delay · 0 days
Nov 21, 2025first filing
Jan 1, 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. NOV 21WI AGWI AG noticefirst filing · 3,500,000 affectedday 0
  2. DEC 2SEC 8-KSEC 8-K noticeno count stated+11d
  3. DEC 21MA AGMA AG notice23,769 MA residents+30d
  4. DEC 21WA AGWA AG notice64,796 WA residents+30d
  5. DEC 21ME AGME AG noticestates nationwide total 3,489,274+30d
  6. DEC 21IA AGIA AG noticeno count stated+30d
  7. DEC 21OR AGOR AG noticestates nationwide total 3,489,274+30d
  8. DEC 21CA AGCA AG noticeno count stated+30d
  9. DEC 22NH AGNH AG notice6,661 NH residents+31d
  10. DEC 22IN AGIN AG noticestates nationwide total 3,489,274+31d
  11. DEC 22TX AGTX AG noticestates nationwide total 3,489,274+31d
  12. DEC 22NE AGNE AG notice10,180 NE residents+31d
  13. DEC 22DE AGDE AG noticeno count stated+31d
  14. DEC 22SC AGSC AG notice64,161 SC residents+31d
  15. JAN 1IL AGIL AG noticemost recent · no count stated+41d
  16. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Aug 1, 2025
SEC 8-K
Discovered
Nov 21, 2025· 112d undetected
SEC 8-K + WA AG + ME AG +9
Data types
Education · Financial account · Identity (basic) · Government ID
WI AG + SEC 8-K + MA AG +10
Attack vector
Unauthorized Access
SEC 8-K

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

US3,489,274
WI3,500,000
TX304,393
WA64,796
SC64,161
IN56,568
MA23,769
NE10,180
ME9,131
NH6,661

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 filing14 members

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

SEC 8-K / victim statement1 member

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

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

41 days

Cadence

~1 / 2.9d

vs. multi-state median

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