Carl's Golfland, Inc reported a data breach to the Montana Attorney General. The breach was reported on 2019-08-30. The breach occurred from 3/25/2019 to 7/14/2019. 80 Montana residents were affected.
Affected (this filing): 80
Clustered 2 filings across 2 jurisdictions · filed Aug 30, 2019. View entity profile → Other incidents for this victim →
incident inc_621e1362f1604ed8 · 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.
CA MT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Mar 25, 2019
When the intrusion reportedly occurred, per the linked filings
Jun 30, 2019
Reported by CALIFORNIA AG filing
Carl's Golfland, Inc reported a data breach to the Montana Attorney General. The breach was reported on 2019-08-30. The breach occurred from 3/25/2019 to 7/14/2019. 80 Montana residents were affected.
Affected (this filing): 80
Carl's Golfland, Inc. disclosed a cybersecurity incident affecting its online shopping website. Between March 25 and July 14, 2019, an unauthorized party accessed customer data including credit card numbers, expiration dates, CVVs, names, addresses, emails, and phone numbers. The breach was discovered via a bank inquiry in late June 2019. Carl's Golfland cooperated with the Secret Service, conducted a forensic audit, and offered one year of credit monitoring to affected customers.
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.