BPG Real Estate Services reported a data breach to the Montana Attorney General. The breach was reported on 2021-11-04. The breach occurred from 8/29/2021 to 9/2/2021. 4 Montana residents were affected.
Affected (this filing): 4
Clustered 2 filings across 2 jurisdictions · filing window Nov 4, 2021 → Nov 5, 2021. View entity profile → Other incidents for this victim →
incident inc_a916d14aced747a6 · 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.
DE MT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Aug 29, 2021
When the intrusion reportedly occurred, per the linked filings
Sep 2, 2021
Reported by DELAWARE AG filing
BPG Real Estate Services reported a data breach to the Montana Attorney General. The breach was reported on 2021-11-04. The breach occurred from 8/29/2021 to 9/2/2021. 4 Montana residents were affected.
Affected (this filing): 4
BPG Real Estate Services notified affected individuals of a security incident detected on September 2, 2021, involving unauthorized network access between August 29 and September 2, 2021. The breach potentially exposed personal information including Social Security Numbers, credit/debit card numbers, and bank account numbers. BPG contained the threat, engaged outside cybersecurity professionals, notified law enforcement, and offered one year of complimentary Equifax Credit Watch Gold monitoring to affected individuals.
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.