Remington Lodging & Hospitality reported a data breach to the Montana Attorney General. The breach was reported on 2017-07-17. The breach occurred from 8/10/2016 to 3/9/2017. 22 Montana residents were affected.
Affected (this filing): 22
Clustered 2 filings across 2 jurisdictions · filing window Jul 17, 2017 → Jul 18, 2017. View entity profile → Other incidents for this victim →
incident inc_370832f79cb346c6 · 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
Aug 10, 2016
When the intrusion reportedly occurred, per the linked filings
Jun 6, 2017
Reported by CALIFORNIA AG filing
Remington Lodging & Hospitality reported a data breach to the Montana Attorney General. The breach was reported on 2017-07-17. The breach occurred from 8/10/2016 to 3/9/2017. 22 Montana residents were affected.
Affected (this filing): 22
Remington Lodging & Hospitality, LLC reported a data breach affecting its Sabre Hospitality Solutions reservation system. Unauthorized access occurred between August 10, 2016, and March 9, 2017, via stolen account credentials. Payment card data (including CVV) and guest PII were accessed. Sabre engaged forensic investigators and notified law enforcement.
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.