Seattle University — March 2019 breach

Clustered 2 filings across 2 jurisdictions · filing window Apr 23, 2019 → Apr 25, 2019. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

2 filings

States

Affected · reported

2,065

First → last filing

Apr 23, 2019 → Apr 25, 2019

Merge confidence

100%

incident inc_504f024d7ff6439b · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 2 regulatory filings. The filing describes a physical incident. Intrusion Mar 26, 2019, discovered Mar 28, 2019 — the first regulatory filing landed 26 days later. 2,065 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

26days

Discovered → first regulatory filing

Filing span

2days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

No cross-filing comparison data available for this incident.

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.