Drury Hotels Company, LLC
ent_effee1b861ce120dee4f911a
Disclosures
5
State AG · 5 jurisdictions
Incidents
1
filings grouped by incident
Max affected reported
109,000
as filed · State AG OR
Leak-site claims
0
none in sample
Identity resolution
- Canonical name
- Drury Hotels Company, LLC
- Normalized
- drury hotels— dedupe via name-norm; Microsoft / MSFT collapse to one row
- GLEIF LEI
- No match
- SEC EDGAR CIK
- None — not an SEC registrant
- Domain
- None on record
Disclosure history (5)newest first
- 🐻California State AGas victim2019-10-01
Drury Hotels Company, LLC reported a data breach involving a third-party technology service provider used for third-party online booking reservations. Unauthorized access occurred between December 28, 2017, and June 2, 2019. The incident exposed guest names, addresses, payment card numbers, expiration dates, and verification codes. Drury notified 359 California residents via mail, email, and a press release/website notice. The service provider engaged a cybersecurity firm to investigate and implement security enhancements.
- 🦬Montana State AGas victim2019-05-30
Drury Hotels Company, LLC reported a data breach to the Montana Attorney General. The breach was reported on 2019-05-30. The breach occurred from 12/28/2017 to 6/2/2019. 17 Montana residents were affected.
- 🌴South Carolina State AGas reporting2019-05-28
State AG breach notification from South Carolina regarding Drury Hotels Company, LLC. The attached PDF document contains only page separators and no extractable breach narrative, dates, data types, or response actions. No specific incident details could be extracted from the provided source.
- 🦫Oregon State AGas victim2019-05-24
Drury Hotels Company, LLC reported a data breach to the Oregon Attorney General. The breach was reported on 2019-05-24. The breach occurred during 1/1/0001. The breach was discovered on 5/15/2019. 109,000 individuals were affected. Notice was sent on 5/24/2019.
- 🌲Washington State AGas victim2019-05-24
Drury Hotels Company, LLC, a business sector entity reported a unclear/unknown incident to the Washington Attorney General. The organization became aware of the incident on 2019-03-26 and filed notice on 2019-05-24. 59 days elapsed between awareness and notification. 452 days to identify the breach. 0 days to contain the breach.