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

Imhoff and Associates, PC — June 2014 breach

Clustered 4 filings across 3 jurisdictions · filing window Aug 26, 2014 Sep 29, 2014. View entity profile → Other incidents for this victim →

1 cross-filing discrepancyMerge100%

Determination

Confirmed

Members

4 filings

States

3

Affected · reported

not comparable

First → last filing

Aug 26, 2014 Sep 29, 2014

Merge confidence

100%

incident inc_62e068b28a7d4f0f · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 4 regulatory filings. The filings describe a physical incident. Intrusion Jun 27, 2014–Jun 27, 2014, discovered Jun 27, 2014 — the first regulatory filing landed 60 days later. Data reported: Government ID, Identity (basic), and Financial account. Notifications rolled out on a 34-day schedule across 4 filings beginning Aug 26, 2014. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
60days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
34days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delayno leak-site claim in this cluster; no SEC 8-K in this cluster.

Regulatory clocksCalifornia CA 60-day OK · 60dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jun 27, 2014breach begins
Jun 27, 2014discovered
notification delay · 60 days
Aug 26, 2014first filing
Sep 29, 2014most 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. AUG 26NH AGNH AG noticefirst filing · 5 NH residentsday 0
  2. AUG 26CA AGCA AG noticeno count statedday 0
  3. AUG 28MA AGMA AG notice12 MA residents+2d
  4. SEP 29NH AGNH AG noticemost recent · 17 NH residents+34d
  5. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jun 27, 2014
NH AG
Discovered
Jun 27, 2014
NH AG + CA AG
Data types
Financial account · Identity (basic) · Government ID
NH AG + CA AG + MA AG

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

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

34 days

Cadence

~1 / 11.3d

vs. multi-state median

4.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.

Imhoff and Associates, PC data breach (2014) · DisclosureLens