Clustered 2 filings across 1 jurisdiction · filing window Mar 6, 2020 → Apr 23, 2020. View entity profile → Other incidents for this victim →
incident inc_9cd70b777add455d · merge_method deterministic · confidence 89%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Identity (basic) · Government ID · Financial account
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.
CA
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jul 1, 2019 → Sep 17, 2019
When the intrusion reportedly occurred, per the linked filings
Sep 17, 2019
Reported by CALIFORNIA AG filings
Athens Insurance Services, Inc. reported a data breach involving unauthorized access to an employee email account between July 1, 2019, and September 17, 2019. The incident potentially exposed personal information including names, SSNs, DOBs, driver's license numbers, financial account numbers, and health information. Athens engaged forensic investigators, secured the account, and offered one year of credit monitoring.
Athens Insurance Services, Inc. reported a cybersecurity incident involving unauthorized access to an employee email account between July 1, 2019, and September 17, 2019. The breach potentially exposed personal information including names, SSNs, driver's license numbers, financial account numbers, and health information. Athens engaged forensic investigators, secured the account, and offered one year of 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.