Clustered 2 filings across 1 jurisdiction · filing window Jul 14, 2017 → Jul 31, 2017. View entity profile → Other incidents for this victim →
incident inc_415194e385b848b9 · merge_method deterministic · confidence 99%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Financial account · PII
Time between earliest and latest filing
Not recorded for this incident
Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.
CA
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Aug 10, 2016 → Mar 9, 2017
When the intrusion reportedly occurred, per the linked filings
Mar 9, 2017
Reported by CALIFORNIA AG filing
Jun 6, 2017
Reported by CALIFORNIA AG filing
Sabre Hospitality Solutions, a third-party provider for Two Roads Hospitality, experienced a data breach affecting guest reservation data. Unauthorized access occurred between August 10, 2016, and March 9, 2017, exposing payment card details and PII. Sabre engaged forensic investigators and notified law enforcement and card brands. Two Roads Hospitality is notifying affected guests.
Delaware North Companies, LLC. reported a data breach involving Sabre Hospitality Solutions, a third-party reservation system provider. Unauthorized access occurred between August 10, 2016, and March 9, 2017, exposing payment card information (card numbers, expiration dates, security codes) and guest PII (names, emails, phone numbers, addresses, reservation details). Delaware North notified law enforcement and payment card brands, retained a forensic investigator, and directed customers to a breach notification website. No SSNs or driver's licenses were exposed.
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.