Noble House Hotels & Resorts Data Breach (August 2016)
Noble House Hotels & Resorts reported a data breach to the California Attorney General on Jul 28, 2017. It was also reported to the Washington State Attorney General. The filing says the breach happened between Aug 10, 2016 and Mar 9, 2017, 352 days before it was reported. It affected 523 Washington residents (Washington only counts its own residents).
What Happened
- Cause: Unauthorized access or disclosure (someone saw or shared information they should not have, including insiders and mistakes).
- Industry: Hotels, restaurants and travel.
- From breach to filing took 352 days, longer than the typical 126 days across all breaches on this site.
“The Sabre Hospitality Solutions SynXis Central Reservations system (Sabre) facilitates the booking of hotel reservations made by consumers through hotels, online travel agencies, and similar booking services. These services include reservations for Noble House Hotels & Resorts (Noble House).”
From the sample notice letter Noble House Hotels & Resorts filed with the California Attorney General (read the full letter)
What Was Exposed
The filings and notice letter mention these kinds of information:
Not everyone affected had every item exposed. Your letter says which of your details were involved.
What to Do Now
If Payment Card Details Were Exposed
- Ask your card issuer for a replacement card with a new number.
- Check recent statements and dispute any charge you don't recognize. Card fraud protection usually covers you.
- Update the card on subscriptions only after the new one arrives.
If a Password Was Exposed
- Change that password, and anywhere else you used the same one.
- Turn on two-step verification (an app or security key is better than texts).
- Use a password manager so every site gets a different password.
For Everyone Affected
- Watch for phishing that mentions the breach. Contact the organization only through phone numbers or websites you find yourself.
- Keep the letter: you may need it for a claim, a settlement or a dispute later.
Official Filings
| Filed With | Date | People Affected | Source |
|---|---|---|---|
| California Attorney General | Jul 28, 2017 | – | Notice and sample letter |
| Washington State Attorney General | Jul 28, 2017 | 523 (WA residents) | Washington AG list |
Other Breaches Reported by Noble House Hotels & Resorts
| Reported | Organization | People Affected |
|---|---|---|
| Sep 2, 2016 | Noble House Hotels & Resorts | – |
| Nov 13, 2015 | Noble House Hotels & Resorts | 4,555 in WA |
All Noble House Hotels & Resorts breaches ›
Similar Breaches Reported Around the Same Time
| Reported | Organization | People Affected | Industry |
|---|---|---|---|
| Jul 28, 2017 | Kimpton Hotels & Restaurants | – | Hotels, restaurants and travel |
| Jul 26, 2017 | Al J. Schneider Company (Galt House Hotel) | 791 in WA | Hotels, restaurants and travel |
| Jul 26, 2017 | Woodside Hotels and Resorts | – | Hotels, restaurants and travel |
| Aug 3, 2017 | Silver Cloud Inns & Hotels | 1,382 in WA | Hotels, restaurants and travel |
| Aug 11, 2017 | Pacifica Hotel Management, LLC | – | Hotels, restaurants and travel |
| Jul 14, 2017 | Two Roads Hospitality, LLC | 5,401 in WA | Hotels, restaurants and travel |
Questions
- Is the Noble House Hotels & Resorts data breach letter legitimate?
- Noble House Hotels & Resorts filed a breach notice with the California Attorney General and Washington State Attorney General on Jul 28, 2017. If your letter matches those details, it is likely genuine. Still, don't use phone numbers or links from an email you weren't expecting; look up the organization yourself.
- Can I sue Noble House Hotels & Resorts or claim compensation?
- It depends on what was exposed, whether you lost money or time because of it, and the laws where you live. Large breaches sometimes lead to class actions and settlements, which are announced by a court-appointed administrator. A lawyer can tell you where you stand.
- How many people were affected?
- Noble House Hotels & Resorts told the Washington Attorney General that 523 Washington residents were affected. The total across all states is usually higher.