Clustered 2 filings across 2 jurisdictions · filed Dec 28, 2023. View entity profile → Other incidents for this victim →
incident inc_89af30f3ed2d4c41 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
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.
IN NH
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Oct 16, 2023
When the intrusion reportedly occurred, per the linked filings
Oct 27, 2023
Reported by NEW HAMPSHIRE AG filing
St. Lucie County Tax Collector's Office reported a data breach to the Indiana Attorney General. The breach occurred on 2023-10-16 and was reported on 2023-12-28. 24 Indiana residents were affected. 22,406 individuals affected in total.
Affected (this filing): 22,406
St. Lucie County Tax Collector’s Office (SLCTC) disclosed a cybersecurity incident affecting New Hampshire residents. Unauthorized access occurred between October 16 and October 27, 2023. SLCTC discovered unusual activity on October 27, 2023, and engaged third-party forensic specialists. The incident involved the acquisition of certain files by an unknown actor. SLCTC notified 15 New Hampshire residents on December 28, 2023, and reported the event to law enforcement. Additional safeguards were implemented.
Affected (this filing): 15
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.