Gonzales Park reported a data breach to the Montana Attorney General. The breach was reported on 2021-03-16. The breach occurred from 1/31/2021 to 2/10/2021. 5 Montana residents were affected.
Affected (this filing): 5
Clustered 2 filings across 2 jurisdictions · filed Mar 16, 2021. View entity profile → Other incidents for this victim →
incident inc_693deb4775544204 · 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.
ME MT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jan 31, 2021
When the intrusion reportedly occurred, per the linked filings
Feb 23, 2021
Reported by MAINE AG filing
Gonzales Park reported a data breach to the Montana Attorney General. The breach was reported on 2021-03-16. The breach occurred from 1/31/2021 to 2/10/2021. 5 Montana residents were affected.
Affected (this filing): 5
Gonzales Park, LLC reported a data breach affecting 1,334 individuals, which was discovered on February 23, 2021. The breach occurred between January 31, 2021, and February 10, 2021, and was described as an external system breach or hacking incident. The compromised data included names and financial account or credit/debit card numbers, along with security codes, access codes, passwords, or PINs. Affected individuals were notified on March 16, 2021, and offered 12 months of identity theft protection services.
Affected (this filing): 1,334
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.