Clustered 2 filings across 2 jurisdictions · filing window Jan 13, 2025 → Nov 13, 2025. View entity profile → Other incidents for this victim →
incident inc_f665ebfaa28b4a2d · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
PII · 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.
MD NH
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Sep 17, 2024
When the intrusion reportedly occurred, per the linked filings
Oct 3, 2024
Reported by NEW HAMPSHIRE AG, MARYLAND AG filings
HCF of Sweden Valley Inc. reported a data security incident affecting one New Hampshire resident. Unauthorized access to the management company's computer systems occurred on September 17, 2024, and was discovered on October 3, 2024. Personal information was accessed. The company engaged forensic investigators, notified law enforcement, and offered credit monitoring.
Affected (this filing): 1
HCF of Sweden Valley Inc. reported a data breach affecting 2 Maryland residents. An unauthorized third party accessed the management company's computer systems starting September 17, 2024. The incident involved personal information including names, SSNs, DOBs, financial account numbers, and medical/insurance data. Notifications were mailed on January 9, 2025, offering credit monitoring. The incident was discovered on October 3, 2024.
Affected (this filing):
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.