One linked filing — more sources may join as they report · filed Aug 8, 2025. View entity profile → Other incidents for this victim →
incident inc_fa2639b3b58d42e8 · merge_method deterministic
Discovered → first regulatory filing
Not recorded for this incident
Discovery variance · Leak precedence · Materiality delta · SEC filing delay · Filing span — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
PII · Identity (basic)
CA
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Mar 2, 2025 → Mar 3, 2025
When the intrusion reportedly occurred, per the linked filings
Mar 3, 2025
Reported by CALIFORNIA AG filing
Renkim Corporation detected suspicious network activity on March 3, 2025, which investigation traced back to March 2, 2025. An unauthorized third party may have obtained files containing personal information used for print and electronic communications solutions. The company engaged third-party experts, notified law enforcement, and is offering credit monitoring to affected individuals.
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.