Ascentia Real Estate reported a data breach to the Montana Attorney General. The breach was reported on 2023-12-14. The breach occurred on 5/23/2023. 8 Montana residents were affected.
Affected (this filing): 8
Clustered 2 filings across 2 jurisdictions · filing window Dec 14, 2023 → Dec 15, 2023. View entity profile → Other incidents for this victim →
incident inc_f44256debc654922 · 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.
MT NH
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
May 23, 2023
When the intrusion reportedly occurred, per the linked filings
May 23, 2023
Reported by NEW HAMPSHIRE AG filing
Ascentia Real Estate reported a data breach to the Montana Attorney General. The breach was reported on 2023-12-14. The breach occurred on 5/23/2023. 8 Montana residents were affected.
Affected (this filing): 8
Ascentia Real Estate Holding Company, LLC reported a data security incident to the New Hampshire Attorney General on December 14, 2023. The company discovered unauthorized access to its systems on May 23, 2023. The incident affected one New Hampshire resident, whose personal information (identity_basic) may have been accessed. Ascentia engaged forensic experts, reported the incident to the FBI, and sent notification letters offering credit monitoring and identity protection services.
Affected (this filing): 1
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.