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

Confirmed2 filings · 2 statesUnverified claimConfirmedEnforcedmoderate sensitivity

Merged incident · 2 filings

Wakefield Terrace Associates Limited Partnership — March 2025 breach

Clustered 2 filings across 2 jurisdictions · filed Jan 30, 2026. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

2 filings

States

Affected · reported

31,751

First → last filing

Jan 30, 2026

Merge confidence

100%

incident inc_eb3dee98f8dc4014 · merged by deterministic · confidence 100%

Confirmed breach. One breach, 2 legal records. Intrusion Mar 2, 2025, discovered Mar 3, 2025 — the first regulatory filing landed 333 days later (flagged late). 31,751 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

333days

Discovered → first regulatory filing

Filing span

0days

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 clocksLeak gap✗ Leak >180dCalifornia✗ CA 60-day late · 333dFull clock table in Litigation Timeline

Incident timeline

Mar 2, 2025breach begins

Mar 3, 2025discovered

notification delay · 333 days

Jan 30, 2026first filing

—watching for filings

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

Member cascade — every filing about this breach

JAN 30HHS OCRHHS OCR noticefirst filing · states nationwide total 31,751auto-linkedday 0
JAN 30CA AGCA AG noticemost recent · no count statedauto-linkedday 0
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Mar 2, 2025
Discovered: Mar 3, 2025· 1d undetected
Data types: PHI · Identity (basic) · Financial account
Attack vector: Unauthorized Access
Response: Renkim immediately responded to terminate that activity and secure its network environment · Renkim launched an investigation with the assistance of third-party experts · Renkim notified law enforcement of the incident

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

0 days

vs. multi-state median

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