Freedom Square of Seminole notified consumers of a data breach involving unauthorized access to personal information. Affected data included names, addresses, Social Security numbers, dates of birth, and financial account numbers. The organization is offering 12 months of credit monitoring and identity theft recovery services through IDX. The incident is contained.
🏎️Indiana State AGlinked via same-victim cross-source · 100%
Freedom Square of Seminole reported a data breach to the Indiana Attorney General. The breach occurred on 2024-09-09 and was reported on 2025-07-11. 15 Indiana residents were affected. 5,849 individuals affected in total.
Affected (this filing): 5,849
🇺🇸FLHHS OCRlinked via same-victim cross-source · 100%
Freedom Square of Seminole, a healthcare organization in Seminole, FL, reported an external system breach (hacking) that occurred on September 9, 2024 but was not discovered until May 13, 2025. A total of 5,849 individuals were affected, including 5 Maine residents. Affected individuals were notified in writing on July 11, 2025 and offered 12 months of IDX credit and CyberScan monitoring services.
Affected (this filing): 5
ME AG >30d · 60d
⛰️New Hampshire State AGMost recentlinked via same-victim cross-source · 100%
Freedom Square of Seminole reported unauthorized access to employee email accounts between Sept 9-12, 2024, following suspicious activity detected on Sept 16, 2024. The incident involved phishing leading to credential compromise. Data at risk included names and SSNs for 3 New Hampshire residents. The company engaged forensic specialists, secured accounts, and offered 12 months of credit monitoring.
Affected (this filing): 3
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.