Clustered 2 filings across 2 jurisdictions · filed May 29, 2025. View entity profile → Other incidents for this victim →
incident inc_ecd41edb0f1e4abd · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Identity (basic)
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.
NH VT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Mar 17, 2024 → Mar 25, 2024
When the intrusion reportedly occurred, per the linked filings
Mar 25, 2024
Reported by NEW HAMPSHIRE AG, VERMONT AG filings
City of St. Cloud, Florida reported unauthorized access to systems between March 17-25, 2024, discovered on March 25, 2024. The breach potentially impacted personal information of New Hampshire residents. The City notified federal law enforcement, implemented additional safeguards, and provided credit monitoring services through IDX.
Affected (this filing): 6
The City of St. Cloud, Florida, notified consumers of a data breach occurring between March 17-25, 2024. An unauthorized actor gained access to systems, potentially impacting names and variable data. The City engaged third-party cybersecurity specialists, secured systems, and reported the incident to regulators. Credit monitoring services are offered. A Vermont filing specifically notes approximately 4 Rhode Island residents may be impacted.
Affected (this filing): 4
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.