Confirmed breach. Intrusion Feb 5, 2025, discovered Feb 21, 2025 — the first regulatory filing landed 41 days later. 554 individuals reported across the linked filings.
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.
Regulatory clocksMaine⏱ ME AG >30d · 41dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedlow sensitivity
Affected (total reported)
554
Data types
1
Identity (basic)
Jurisdictions
2
IN ME
Linked filings
2
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Feb 5, 2025
When the intrusion reportedly occurred, per the linked filings
Breach discovered
Feb 21, 2025
Reported by MAINE AG filing
41 days
🏎️Indiana State AGFirst filinglinked via multistate filing link · 100%
Belfair Property Owners' Association Inc reported a data breach to the Indiana Attorney General. The breach occurred on 2025-02-05 and was reported on 2025-04-03. 5 Indiana residents were affected. 554 individuals affected in total.
Belfair Property Owners' Association, Inc. experienced an external system breach (hacking) on February 5, 2025, which was discovered on February 21, 2025. The breach affected 554 individuals, including 3 Maine residents. In response, the association offered 24 months of identity theft protection services through Norton LifeLock Defender Preferred and began notifying affected consumers on April 3, 2025.
Affected (this filing): 3
ME AG >30d · 41d
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.