Ryman Hospitality Properties reported a data breach to the Montana Attorney General. The breach was reported on 2016-04-01. The breach occurred on 3/23/2016. 2 Montana residents were affected.
Affected (this filing): 2
Clustered 2 filings across 2 jurisdictions · filed Apr 1, 2016. View entity profile → Other incidents for this victim →
incident inc_d6a6cae822f3472c · 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
Mar 23, 2016
When the intrusion reportedly occurred, per the linked filings
Mar 23, 2016
Reported by NEW HAMPSHIRE AG filing
Ryman Hospitality Properties reported a data breach to the Montana Attorney General. The breach was reported on 2016-04-01. The breach occurred on 3/23/2016. 2 Montana residents were affected.
Affected (this filing): 2
Ryman Hospitality Properties, Inc. notified the New Hampshire Attorney General of a March 23, 2016 phishing incident. Employees received a spoofed email impersonating an executive, resulting in the unauthorized disclosure of W-2 forms containing names, addresses, and Social Security numbers. The company notified affected individuals and offered credit monitoring.
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.