DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteState AGConfirmed6 filings · 4 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedavoslockerhigh sensitivity
Merged incident · 6 filings

Stratford University — August 2022 breach

Clustered 6 filings across 5 jurisdictions · filing window Dec 26, 2022 → Feb 9, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

6 filings

States

4

Affected · reported

78,894

First → last filing

Dec 26, 2022 → Feb 9, 2023

Merge confidence

100%

incident inc_48bc106accaa4921 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings and 1 unverified claim. Intrusion Aug 26, 2022–Aug 27, 2022, discovered Aug 27, 2022 — the first regulatory filing landed 152 days later (flagged late). 78,894 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PII, and 2 more. Notifications rolled out on a 45-day schedule across 5 filings beginning Dec 26, 2022. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
152days

Discovered → first regulatory filing

Discovery variance
124days

Range of discovered_at dates across filings

Leak precedence
31days before filing

Days between the first leak-site claim and the first regulatory filing. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.

Filing span
45days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksVermont✗ VT AG >45 bdayLeak gap✗ Leak >180dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Aug 26, 2022breach begins
Aug 27, 2022discovered · members disagree
notification delay · 152 days
Jan 26, 2023first filing
Feb 9, 2023most 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. DEC 26Leak siteavoslocker postfirst filing · attacker claim · unverifiedday 0
  2. JAN 26VT AGVT AG noticeno count stated+31d
  3. JAN 26ME AGME AG noticestates nationwide total 78,692+31d
  4. JAN 26MT AGMT AG notice7 MT residents+31d
  5. JAN 30NH AGNH AG notice17 NH residents+35d
  6. FEB 9ME AGME AG noticemost recent · states nationwide total 78,894+45d
  7. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Aug 26, 2022
VT AG
Discovered
Aug 27, 2022VT AG + MT AG + NH AGDec 29, 2022ME AGfilings disagree on discovery
Data types
Education · Employment · Identity (basic) · Government ID · PII
VT AG + ME AG + MT AG +1
Attack vector
Unauthorized Access
VT 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)

78,894

Sum of filed state slices

37· 0.0% of stated

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

US78,894
NH17
ME13
MT7

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 claim1 member

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

No press coverage linked yet.

State AG / regulator filing5 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 Aug 9, 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

45 days

Cadence

~1 / 9d

vs. multi-state median

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