DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
State AGConfirmed4 filings · 4 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 4 filings

Any-Time Home Care, Inc. — March 2026 breach

Clustered 4 filings across 4 jurisdictions · filing window Jul 1, 2026 → Jul 21, 2026. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

4 filings

States

4

Affected · reported

11

First → last filing

Jul 1, 2026 → Jul 21, 2026

Merge confidence

100%

incident inc_e119e9086cb740e3 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 4 regulatory filings. The filing describes a ransomware attack. Intrusion Mar 17, 2026, discovered Apr 13, 2026 — the first regulatory filing landed 79 days later. 11 individuals reported across the linked filings. Data reported: Government ID, Health (basic), and Identity (basic). Notifications rolled out on a 20-day schedule across 4 filings beginning Jul 1, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
79days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
20days

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.

Sensitive data

identity_government

Incident timeline

Mar 17, 2026breach begins
Apr 13, 2026discovered
notification delay · 79 days
Jul 1, 2026first filing
Jul 21, 2026most 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. JUL 1IL AGIL AG noticefirst filing · no count statedday 0
  2. JUL 21NH AGNH AG notice2 NH residents+20d
  3. JUL 21MA AGMA AG notice8 MA residents+20d
  4. JUL 21VT AGVT AG noticemost recent · 1 VT residents+20d
  5. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Mar 17, 2026
NH AG
Discovered
Apr 13, 2026· 27d undetected
IL AG + NH AG
Data types
Health (basic) · Identity (basic) · Government ID
IL AG + VT AG + NH AG +1
Attack vector
Ransomware
NH AG

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

Affected residents by state

per-state reported counts

MA8
NH2
VT1

State AGs report only their own residents; teal bars show each state's reported slice.

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

20 days

Cadence

~1 / 6.7d

vs. multi-state median

2.5× 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.