GLOBALClaimed by AbyssFirst sighting
Posted to leak site Jun 25, 2024bd_59e23dda4f5b9ef6
tpocc.org 570Gb uncompressed data
Clustered 3 filings across 3 jurisdictions · filing window Jun 25, 2024 → Aug 30, 2024. View entity profile → Other incidents for this victim →
incident inc_0ed1d41e458c478d · merge_method human · confidence 100%
Discovered → first regulatory filing
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.
CA IN
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Apr 30, 2024
When the intrusion reportedly occurred, per the linked filings
May 1, 2024
Reported by CALIFORNIA AG filing
tpocc.org 570Gb uncompressed data
Turning Point of Central California reported a data breach to the Indiana Attorney General. The breach occurred on 2024-04-30 and was reported on 2024-08-30. 1 Indiana residents were affected. 2,684 individuals affected in total.
Turning Point of Central California, Inc. (TPOCC) experienced a data security incident in May 2024, with unauthorized access occurring on April 30, 2024. An unauthorized user gained access to the system, potentially compromising names, social security numbers, and addresses of current and former employees. TPOCC disconnected systems, engaged forensic experts, and reset passwords. Identity theft protection services were offered 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.
Affected (this filing): 2,684