All incidents View linkage analytics →Get the evidence package — $79

Confirmed2 filings · 1 stateUnverified claimConfirmedEnforcedmoderate sensitivity

Merged incident · 2 filings

Redwood Coast Regional Center — June 2023 breach

Clustered 2 filings across 1 jurisdiction · filing window Aug 7, 2023 → Aug 8, 2023. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

2 filings

States

Affected · reported

1,347

First → last filing

Aug 7, 2023 → Aug 8, 2023

Merge confidence

100%

incident inc_f6ef7358561c4a1a · merged by deterministic · confidence 100%

Confirmed breach. One breach, 2 legal records. Intrusion Jun 14, 2023–Jun 15, 2023, discovered Jun 14, 2023 — the first regulatory filing landed 54 days later. 1,347 individuals reported across the linked filings. This page is the deduped roll-up; each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay

54days

Discovered → first regulatory filing

Filing span

1days

Time between earliest and latest filing

Not recorded for this incident

Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.

Regulatory clocksHIPAA✓ HHS notifiedFull clock table in Litigation Timeline

Incident timeline

Jun 14, 2023breach begins

Jun 14, 2023discovered

notification delay · 54 days

Aug 7, 2023first filing

Aug 8, 2023most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

AUG 7HHS OCRHHS OCR noticefirst filing · states nationwide total 1,345auto-linkedday 0
AUG 8CA AGCA AG noticemost recent · 1,347 CA residentsauto-linked+1d
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Jun 14, 2023 – Jun 15, 2023
Discovered: Jun 14, 2023
Data types: Health (basic) · Identity (basic)
Attack vector: Unauthorized Access
Response: Notified HHS, affected individuals, and media · Revised policies and procedures · Retrained workforce members

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 filing2 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
Reviewed: operator-confirmed · at least one link edge was human-adjudicated
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

1 days

vs. multi-state median

5.0× faster

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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.