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

Access TeleCare — November 2023 breach

Clustered 6 filings across 4 jurisdictions · filing window Dec 23, 2024 → Mar 14, 2025. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

6 filings

States

4

Affected · reported

736

First → last filing

Dec 23, 2024 → Mar 14, 2025

Merge confidence

100%

incident inc_647420b58d9d4e47 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 6 regulatory filings. Intrusion Nov 6, 2023–Jan 8, 2024, discovered Jan 8, 2024 — the first regulatory filing landed 350 days later (flagged late). 736 individuals reported across the linked filings. Data reported: Government ID, PII, Identity (basic), and 2 more. Notifications rolled out on a 81-day schedule across 6 filings beginning Dec 23, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
350days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
81days

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 clocksVermont✗ VT AG >45 bdayMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Nov 6, 2023breach begins
Jan 8, 2024discovered
notification delay · 350 days
Dec 23, 2024first filing
Mar 14, 2025most 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. DEC 23CA AGCA AG noticefirst filing · no count statedday 0
  2. DEC 23VT AGVT AG noticeno count statedday 0
  3. DEC 23MA AGMA AG notice681 MA residentsday 0
  4. DEC 23NH AGNH AG notice55 NH residentsday 0
  5. MAR 14CA AGCA AG noticeno count stated+81d
  6. MAR 14VT AGVT AG noticemost recent · no count stated+81d
  7. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Nov 6, 2023 – Jan 8, 2024
CA AG
Discovered
Jan 8, 2024· 63d undetected
VT AG + NH AG
Data types
Health (basic) · Identity (basic) · Government ID · PHI · PII
CA AG + NH AG + VT AG +1
Attack vector
Unauthorized Access
CA 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 filing6 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

81 days

Cadence

~1 / 16.2d

vs. multi-state median

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