DisclosureLens
State AGConfirmed2 filings · 2 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 2 filings

Codal

Clustered 2 filings across 2 jurisdictions · filing window Jun 30, 2020 → Jul 6, 2020. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

2 filings

States

2

Affected · reported

33

First → last filing

Jun 30, 2020 → Jul 6, 2020

Merge confidence

100%

incident inc_db37bd6d4b584ee7 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 2 regulatory filings. The filing describes unauthorized access. Discovered Jan 24, 2020 — the first regulatory filing landed 158 days later. 33 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

Supplemental
Notification delay
158days

Discovered → first regulatory filing

Filing span
6days

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.

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.

Codal data breach (2020) — Massachusetts and New Hampshire filings, June 2020 · DisclosureLens