XML 27 R12.htm IDEA: XBRL DOCUMENT
v3.21.1

Commitments and Contingencies | 3 Months Ended
--- | ---
Mar. 31, 2021
Commitments and Contingencies Disclosure [Abstract] |
Commitments and Contingencies | COMMITMENTS AND CONTINGENCIES Guarantees We present the maximum potential amount of our future guarantee fundings and the carrying amount of our liability for our debt service, operating profit, and other guarantees (excluding contingent purchase obligations) for which we are the primary obligor at March 31, 2021 in the following table:
($ in millions) Guarantee Type |  | Maximum Potential Amount of Future Fundings |  | Recorded Liability for Guarantees
Debt service |  | $ | 53 |  |  | $ | 6 |
Operating profit |  | 204 |  |  | 128 |
Other |  | 18 |  |  | 4 |
|  | $ | 275 |  |  | $ | 138 |
Our maximum potential guarantees listed in the preceding table include $93 million of guarantees that will not be in effect until the underlying properties open and we begin to operate the properties or certain other events occur. Contingent Purchase Obligation Sheraton Grand Chicago. In 2017, we granted the owner a one-time right, exercisable in 2022, to require us to purchase the leasehold interest in the land and the hotel for $300 million in cash (the “put option”). If the owner exercises the put option, we have the option to purchase, at the same time the put transaction closes, the fee simple interest in the underlying land for an additional $200 million in cash. We account for the put option as a guarantee, and our recorded liability at March 31, 2021 was $300 million. Starwood Data Security Incident Description of Event On November 30, 2018, we announced a data security incident involving unauthorized access to the Starwood reservations database (the “Data Security Incident”). Working with leading security experts, we determined that there was unauthorized access to the Starwood network since 2014 and that an unauthorized party had copied information from the Starwood reservations database and taken steps towards removing it. The Starwood reservations database is no longer used for business operations. Expenses and Insurance Recoveries In the 2021 first quarter, we recorded $5 million of expenses and $5 million of accrued insurance recoveries, and in the 2020 first quarter, we recorded $15 million of expenses and $17 million of accrued insurance recoveries, related to the Data Security Incident. We received insurance recoveries of $10 million in the 2021 first quarter and $24 million in the 2020 first quarter. The expenses for the 2021 first quarter primarily included legal costs. We recognize insurance recoveries when they are probable of receipt and present them in our Income Statements in the same caption as the related expense, up to the amount of total expense incurred in prior and current periods. We present expenses and insurance recoveries related to the Data Security Incident in either the “Reimbursed expenses” or “Restructuring and merger-related charges (recoveries)” captions of our Income Statements. Litigation, Claims, and Government Investigations Following our announcement of the Data Security Incident, approximately 100 lawsuits were filed by consumers and others against us in U.S. federal, U.S. state and Canadian courts related to the incident. All but one of the U.S. cases were consolidated and transferred to the U.S. District Court for the District of Maryland, pursuant to orders of the U.S. Judicial Panel on Multidistrict Litigation (the “MDL”). The plaintiffs in the U.S. and Canadian cases, who generally purport to represent various classes of consumers, generally claim to have been harmed by alleged actions and/or omissions by the Company in connection with the Data Security Incident and assert a variety of common law and statutory claims seeking monetary damages, injunctive relief, costs and attorneys’ fees, and other related relief. Among the U.S. cases consolidated in the MDL proceeding is a putative class action lawsuit that was filed on December 1, 2018 against the Company and certain of our current and former officers and directors, alleging violations of the federal securities laws in connection with statements regarding our cybersecurity systems and controls, and seeking certification of a class of affected persons, unspecified monetary damages, costs and attorneys’ fees, and other related relief. The MDL proceeding also includes two shareholder derivative complaints that were filed on February 26, 2019 and March 15, 2019, respectively, against the Company and certain of our current and former directors, alleging, among other claims, breach of fiduciary duty, corporate waste, unjust enrichment, mismanagement and violations of the federal securities laws, and seeking unspecified monetary damages and restitution, changes to the Company’s corporate governance and internal procedures, costs and attorneys’ fees, and other related relief. A separate shareholder derivative complaint was filed in the Delaware Court of Chancery on December 3, 2019 against the Company and certain of our current and former officers and directors, alleging claims and seeking relief generally similar to the claims made and relief sought in the other two derivative cases. This case will not be consolidated with the MDL proceeding. We have filed motions to dismiss in each of these cases, some of which have been denied in part or in whole and some of which are pending. A putative class action lawsuit brought on behalf of financial institutions has been voluntarily dismissed. The putative class action lawsuit alleging violations of the federal securities laws and the shareholder derivative lawsuits generally remain at an early stage. The other U.S. cases in the MDL proceeding are nearing completion of the discovery process. The Canadian cases have effectively been consolidated into a single case in the province of Ontario. We dispute the allegations in the lawsuits described above and are vigorously defending against such claims. In April 2019, we received a letter purportedly on behalf of a stockholder of the Company (also one of the named plaintiffs in the putative securities class action described above) demanding that our Board of Directors take action against certain of the Company’s current and former officers and directors to recover damages for alleged breaches of fiduciary duties and related claims arising from the Data Security Incident. The Board of Directors has constituted a demand review committee to investigate the claims made in the demand letter, and the committee has retained independent counsel to assist with the investigation. The committee’s investigation is ongoing. In addition, on August 18, 2020, a purported representative action was brought against us in the High Court of Justice for England and Wales on behalf of an alleged claimant class of English and Welsh residents alleging breaches of the General Data Protection Regulation and/or the U.K. Data Protection Act 2018 (the “U.K. DPA”) in connection with the Data Security Incident. We dispute all of the allegations in this purported action and will vigorously defend against any such claims. On November 5, 2020, the court issued an order with the consent of all parties staying this action pending resolution of another case raising similar issues, but not involving the Company, that is pending before the U.K. Supreme Court. In addition, numerous U.S. federal, U.S. state and foreign governmental authorities made inquiries, opened investigations, or requested information and/or documents related to the Data Security Incident and related matters, including Attorneys General offices from all 50 states and the District of Columbia, the Federal Trade Commission, the Securities and Exchange Commission, certain committees of the U.S. Senate and House of Representatives, the Information Commissioner’s Office in the United Kingdom (the “ICO”) as lead supervisory authority in the European Economic Area, and regulatory authorities in various other jurisdictions. With the exception of the ICO proceeding, which was resolved in October 2020, these matters generally remain open. We are in the early stages of discussions with the U.S. state Attorneys General and the Federal Trade Commission to resolve their investigations and requests. While we believe it is reasonably possible that we may incur additional losses associated with the above described proceedings and investigations related to the Data Security Incident, it is not possible to estimate the amount of loss or range of loss, if any, in excess of the amounts already incurred that might result from adverse judgments, settlements, fines, penalties or other resolution of these proceedings and investigations based on the current stage of these proceedings and investigations, the absence of specific allegations as to alleged damages, the uncertainty as to the certification of a class or classes and the size of any certified class, if applicable, and/or the lack of resolution of significant factual and legal issues.

X
- References No definition available. + Details
Name: | us-gaap_CommitmentsAndContingenciesDisclosureAbstract
Namespace Prefix: | us-gaap_
Data Type: | xbrli:stringItemType
Balance Type: | na
Period Type: | duration

X
- Definition The entire disclosure for commitments and contingencies. + References Reference 1: http://fasb.org/us-gaap/role/ref/legacyRef -Publisher FASB -Name Accounting Standards Codification -Topic 450 -URI http://asc.fasb.org/topic&trid=2127136 Reference 2: http://fasb.org/us-gaap/role/ref/legacyRef -Publisher FASB -Name Accounting Standards Codification -Topic 440 -URI http://asc.fasb.org/topic&trid=2144648 Reference 3: http://www.xbrl.org/2003/role/disclosureRef -Publisher FASB -Name Accounting Standards Codification -Topic 440 -SubTopic 10 -Section 50 -Paragraph 4 -Subparagraph (c) -URI http://asc.fasb.org/extlink&oid=121559207&loc=d3e25336-109308 Reference 4: http://www.xbrl.org/2003/role/disclosureRef -Publisher FASB -Name Accounting Standards Codification -Topic 440 -SubTopic 10 -Section 50 -Paragraph 4 -Subparagraph (a) -URI http://asc.fasb.org/extlink&oid=121559207&loc=d3e25336-109308 + Details
Name: | us-gaap_CommitmentsAndContingenciesDisclosureTextBlock
Namespace Prefix: | us-gaap_
Data Type: | nonnum:textBlockItemType
Balance Type: | na
Period Type: | duration