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

Aspen Education Group, Inc. — August 2020 breach

Clustered 10 filings across 10 jurisdictions · filing window Jan 1, 2021 → May 11, 2021. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 filings

States

10

Affected · reported

57,763

First → last filing

Jan 1, 2021 → May 11, 2021

Merge confidence

100%

incident inc_593e3bb7f5f64bd9 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings. Intrusion Aug 23, 2020–Dec 13, 2020, discovered Dec 13, 2020 — the first regulatory filing landed 19 days later (flagged late). 57,763 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Health (basic), and 2 more. Notifications rolled out on a 130-day schedule across 10 filings beginning Jan 1, 2021. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
19days

Discovered → first regulatory filing

Discovery variance
88days

Range of discovered_at dates across filings

Filing span
130days

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 >90dMaine⏱ ME AG >30d · 60dMassachusetts✓ MA credit monitoring dueSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Aug 23, 2020breach begins
Dec 13, 2020discovered · members disagree
notification delay · 19 days
Jan 1, 2021first filing
May 11, 2021most 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. JAN 1IL AGIL AG noticefirst filing · no count statedday 0
  2. MAY 10ME AGME AG noticestates nationwide total 57,763+129d
  3. MAY 10OR AGOR AG noticestates nationwide total 57,763+129d
  4. MAY 10WA AGWA AG notice1,958 WA residents+129d
  5. MAY 10MT AGMT AG notice263 MT residents+129d
  6. MAY 10NH AGNH AG notice377 NH residents+129d
  7. MAY 10CA AGCA AG noticeno count stated+129d
  8. MAY 10IN AGIN AG noticestates nationwide total 57,763+129d
  9. MAY 10MA AGMA AG notice1,684 MA residents+129d
  10. MAY 11SC AGSC AG noticemost recent · 1,060 SC residents+130d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 13, 2020
ME AG
Discovered
Dec 13, 2020IL AG + WA AG + MT AG +3Mar 11, 2021ME AG + OR AGfilings disagree on discovery
Data types
Health (basic) · Identity (basic) · Government ID · PHI · PII
ME AG + WA AG + MT AG +4
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)

57,763

Sum of filed state slices

6,303· 10.9% of stated

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

US57,763
WA1,958
MA1,684
SC1,060
IN682
NH377
ME279
MT263

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 filing10 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
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

130 days

Cadence

~1 / 14.4d

vs. multi-state median

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