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

San Diego Family Care — November 2020 breach

Clustered 7 filings across 6 jurisdictions · filing window May 7, 2021 → May 18, 2021. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

7 filings

States

6

Affected · reported

154,513

First → last filing

May 7, 2021 → May 18, 2021

Merge confidence

100%

incident inc_e44c5f69c9ac418f · merged by deterministic · confidence 100%

Part of the Netgain Networks supply-chain incident (2021) — at least 15 organizations filed notifications naming this third party.
Confirmed breach. Merged as one breach: 7 regulatory filings. Intrusion Nov 22, 2020–Dec 3, 2020, discovered Dec 1, 2020 — the first regulatory filing landed 157 days later (flagged late). 154,513 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Health (basic), and 2 more. Notifications rolled out on a 11-day schedule across 7 filings beginning May 7, 2021. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
157days

Discovered → first regulatory filing

Discovery variance
132days

Range of discovered_at dates across filings

Filing span
11days

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 late · 157dMaine✓ ME AG ≤30d · 27dMassachusetts✓ MA credit monitoring dueHIPAA✓ HHS notifiedFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Nov 22, 2020breach begins
Dec 1, 2020discovered · members disagree
notification delay · 157 days
May 7, 2021first filing
May 18, 2021most 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. MAY 7MT AGMT AG noticefirst filing · 16 MT residentsday 0
  2. MAY 7IN AGIN AG noticestates nationwide total 125,530day 0
  3. MAY 9CA AGCA AG noticeno count stated+2d
  4. MAY 9ME AGME AG noticestates nationwide total 125,530+2d
  5. MAY 10NH AGNH AG notice6 NH residents+3d
  6. MAY 10MA AGMA AG notice34 MA residents+3d
  7. MAY 18HHS OCRHHS OCR noticemost recent · states nationwide total 154,513+11d
  8. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Nov 22, 2020
IN AG
Discovered
Dec 1, 2020MT AG + CA AG + NH AGApr 12, 2021ME AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI
MT AG + CA AG + ME AG +3
Attack vector
Third-Party / Supply Chain
MT AG

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

Count reconciliation

per-state reported counts

Nationwide (stated in a filing)

154,513

Sum of filed state slices

98· 0.1% of stated

100% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

US154,513
IN36
MA34
MT16
ME6
NH6

State AGs report only their own residents; teal bars show each state's reported slice. The gray US row is the nationwide total reported in a linked filing.

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

11 days

Cadence

~1 / 1.8d

vs. multi-state median

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