Hamilton Zanze & Company — June 2017 breach

Clustered 5 filings across 4 jurisdictions · filing window Jul 25, 2017 → Aug 8, 2017. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

5 filings

States

Affected · reported

not comparable

First → last filing

Jul 25, 2017 → Aug 8, 2017

Merge confidence

100%

incident inc_6adc0d92e19948da · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings. The filings describe a physical incident. Intrusion Jun 29, 2017, discovered Jun 29, 2017 — the first regulatory filing landed 26 days later. Data reported: Government ID and Identity (basic). Notifications rolled out on a 14-day schedule across 5 filings beginning Jul 25, 2017. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Notification delay

26days

Discovered → first regulatory filing

Discovery variance

0days

Range of discovered_at dates across filings

Filing span

14days

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 clocksCalifornia✓ CA 60-day OK · 28dFull 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.