All incidents View linkage analytics →Get the evidence package — $79 what’s inside →

Confirmed3 filings · 3 statesUnverified claimConfirmedEnforcedcritical sensitivity

Merged incident · 3 filings

Town of Concord — October 2019 breach

Clustered 3 filings across 3 jurisdictions · filing window Sep 16, 2021 → Sep 22, 2021. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

3 filings

States

Affected · reported

57,116

First → last filing

Sep 16, 2021 → Sep 22, 2021

Merge confidence

100%

incident inc_5d998220aa094cc1 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 3 regulatory filings. The filings describe a physical incident. Intrusion Oct 17, 2019, discovered Oct 17, 2019 — the first regulatory filing landed 700 days later (flagged late). 57,116 individuals reported across the linked filings. Data reported: Government ID, Biometric, PII, and 4 more. Notifications rolled out on a 6-day schedule across 3 filings beginning Sep 16, 2021. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Notification delay

700days

Discovered → first regulatory filing

Discovery variance

0days

Range of discovered_at dates across filings

Filing span

6days

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 clocksMaine✗ ME AG >90d · 701dFull 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.