XML 42 R14.htm IDEA: XBRL DOCUMENT
v3.23.1

Commitments and Contingencies | 3 Months Ended
--- | ---
Mar. 31, 2023
Commitments and Contingencies Disclosure [Abstract] |
Commitments and Contingencies |
8. Commitments and Contingencies
Leases We have operating leases for corporate offices, subleased offices and certain equipment and furniture. As of March 31, 2023, we did not have any operating leases that had not yet commenced. The following table summarizes the components of our lease expense:
|  |  | Three months ended March 31,
(dollars in thousands) |  |  |  | 2023 | 2022
Operating lease cost(1) |  |  |  | $ | 2,385 |  | $ | 2,532 |
Variable lease cost |  |  |  | 432 |  | 437 |
Sublease income |  |  |  | (811) |  | (431) |
Net lease cost |  |  |  | $ | 2,006 |  | $ | 2,538 |
(1)Includes short-term lease costs, which were immaterial. Other commitments The term loans under the 2020 Credit Facility require periodic principal payments. The balance of the term loans and any amounts drawn on the revolving credit loans are due upon maturity of the 2020 Credit Facility in October 2025. The Real Estate Loans also require periodic principal payments and the balance of the Real Estate Loans are due upon maturity in April 2038. We have contractual obligations for third-party technology used in our solutions and for other services we purchase as part of our normal operations. In certain cases, these arrangements require a minimum annual purchase commitment by us. As of March 31, 2023, the remaining aggregate minimum purchase commitment under these arrangements was approximately $280.7 million through 2027. Solution and service indemnifications In the ordinary course of business, we provide certain indemnifications of varying scope to customers against claims of intellectual property infringement made by third parties arising from the use of our solutions or services. We have not identified any losses that might be covered by these indemnifications. Legal proceedings We are subject to legal proceedings and claims that arise in the ordinary course of business, as well as certain other non-ordinary course proceedings, claims and investigations, as described below. We make a provision for a loss contingency when it is both probable that a material liability has been incurred and the amount of the loss can be reasonably estimated. If only a range of estimated losses can be determined, we accrue an amount within the range that, in our judgment, reflects the most likely outcome; if none of the estimates within that range is a better estimate than any other amount, we accrue the low end of the range. For proceedings in which an unfavorable outcome is reasonably possible but not probable and an estimate of the loss or range of losses arising from the proceeding can be made, we disclose such an estimate, if material. If such a loss or range of losses is not reasonably estimable, we disclose that fact. We review any such loss contingency provisions at least quarterly and adjust them to reflect the impacts of negotiations, settlements, rulings, advice of legal counsel and other information and events pertaining to a particular case. We recognize insurance recoveries, if any, when they are probable of receipt. All associated costs due to third-party service providers and consultants, including legal fees, are expensed as incurred. Legal proceedings are inherently unpredictable. However, we believe that we have valid defenses with respect to the legal matters pending or threatened against us and intend to defend ourselves vigorously against all claims asserted. It is possible that our consolidated financial position, results of operations or cash flows could be materially negatively affected in any particular period by an unfavorable resolution of one or more of such legal proceedings. Security incident As previously disclosed, we are subject to risks and uncertainties as a result of a ransomware attack against us in May 2020 in which a cybercriminal removed a copy of a subset of data from our self-hosted environment (the "Security Incident"). Based on the nature of the Security Incident, our research and third party (including law enforcement) investigation, we do not believe that any data went beyond the cybercriminal, has been misused, or has been disseminated or otherwise made available publicly. Our investigation into the Security Incident by our cybersecurity team and third-party forensic advisors remains ongoing. As a result of the Security Incident, we are currently subject to certain legal proceedings, claims and investigations, as discussed below, and could be the subject of additional legal proceedings, claims, inquiries and investigations in the future that might result in adverse judgments, settlements, fines, penalties or other resolution. To limit our exposure to losses related to claims against us, including data breaches such as the Security Incident, we maintain $50 million of insurance above a $250 thousand deductible payable by us. As noted below, this coverage has reduced our financial exposure related to the Security Incident. We recorded expenses and offsetting probable insurance recoveries related to the Security Incident as follows:
|  |  | Three months ended March 31,
(dollars in thousands) |  |  |  | 2023 | 2022
Gross expense |  |  |  | $ | 17,783 |  | $ | 9,005 |
Offsetting probable insurance recoveries |  |  |  | — |  | (1,804) |
Net expense |  |  |  | $ | 17,783 |  | $ | 7,201 |
The following summarizes our cumulative expenses, insurance recoveries recognized and insurance recoveries paid as of:
(dollars in thousands) | March 31, 2023 | December 31, 2022
Cumulative gross expense | $ | 125,788 |  | $ | 108,005 |
Cumulative offsetting insurance recoveries recognized | (50,000) |  | (50,000) |
Cumulative net expense | $ | 75,788 |  | $ | 58,005 |
Cumulative offsetting insurance recoveries paid | $ | (50,000) |  | $ | (50,000) |
Recorded expenses have consisted primarily of payments to third-party service providers and consultants, including legal fees, as well as settlement of the previously disclosed SEC investigation (as discussed below), settlements of customer claims and accruals for certain loss contingencies. Not included in the expenses discussed above were costs associated with enhancements to our cybersecurity program. We present expenses and insurance recoveries related to the Security Incident in general and administrative expense on our consolidated statements of comprehensive loss and as operating activities on our consolidated statements of cash flows. Total costs related to the Security Incident exceeded the limit of our insurance coverage during the first quarter of 2022. We expect to continue to experience significant expenses related to our response to the Security Incident, resolution of legal proceedings, claims and investigations, including those discussed below, and our efforts to further enhance our cybersecurity measures. For the three months ended March 31, 2023, we incurred net pre-tax expense of $17.8 million related to the Security Incident, which included $7.6 million for ongoing legal fees and an additional accrual for loss contingencies of $10.2 million. During the three months ended March 31, 2023, we had net cash outlays of $9.2 million related to the Security Incident, which included ongoing legal fees and the $3.0 million civil penalty paid related to the SEC settlement (as discussed below). In line with our policy, legal fees are expensed as incurred. For full year 2023, we currently expect net pre-tax expense of approximately $20.0 million to $30.0 million and net cash outlays of approximately $25.0 million to $35.0 million for ongoing legal fees related to the Security Incident. Not included in these ranges are our previous settlements or current accruals for loss contingencies related to the matters discussed below. As of March 31, 2023, we have recorded approximately $30.2 million in aggregate liabilities for loss contingencies based primarily on recent negotiations with certain governmental agencies related to the Security Incident that we believe we can reasonably estimate in accordance with our loss contingency procedures described above. It is reasonably possible that our estimated or actual losses may change in the near term for those matters and be materially in excess of the amounts accrued, but we are unable at this time to reasonably estimate the possible additional loss. There are other Security Incident-related matters, including customer claims, customer constituent class actions and governmental investigations, for which we have not recorded a liability for a loss contingency as of March 31, 2023 because we are unable at this time to reasonably estimate the possible loss or range of loss. Each of these matters could, separately or in the aggregate, result in an adverse judgment, settlement, fine, penalty or other resolution, the amount, scope and timing of which we are currently unable to predict, but could have a material adverse impact on our results of operations, cash flows or financial condition. Customer claims. To date, we have received approximately 260 specific requests for reimbursement of expenses, approximately 205 (or 79%) have been fully resolved and closed. We have also received approximately 400 reservations of the right to seek expense recovery in the future from customers or their attorneys in the U.S., U.K. and Canada related to the Security Incident. We have also received notices of proposed claims on behalf of a number of U.K. data subjects, which we are reviewing. In addition, insurance companies representing various customers’ interests through subrogation claims have contacted us, and certain insurance companies have filed subrogation claims in court. Customer and insurer subrogation claims generally seek reimbursement of their costs and expenses associated with notifying their own customers of the Security Incident and taking steps to assure that personal information has not been compromised as a result of the Security Incident. Our review of customer and subrogation claims includes analyzing individual customer contracts into which we have entered, the specific claims made and applicable law. Customer constituent class actions. Presently, we are a defendant in 19 putative consumer class action cases [17 in U.S. federal courts (which have been consolidated under multi district litigation to a single federal court) and 2 in Canadian courts] alleging harm from the Security Incident. The plaintiffs in these cases, who purport to represent various classes of individual constituents of our customers, generally claim to have been harmed by alleged actions and/or omissions by us in connection with the 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. Lawsuits that are putative class actions require a plaintiff to satisfy a number of procedural requirements before proceeding to trial. These requirements include, among others, demonstration to a court that the law proscribes in some manner our activities, the making of factual allegations sufficient to suggest that our activities exceeded the limits of the law and a determination by the court—known as class certification—that the law permits a group of individuals to pursue the case together as a class. If these procedural requirements are not met, the lawsuit cannot proceed as a class action and the plaintiff may lose the financial incentive to proceed with the case. We are currently engaged in court proceedings to determine whether this will proceed as a class action. Frequently, a court’s determination as to these procedural requirements is subject to appeal to a higher court. As a result of these uncertainties, we may be unable to determine the probability of loss until, or after, a court has finally determined that a plaintiff has satisfied the applicable class action procedural requirements. Furthermore, for putative class actions, it is often not possible to reasonably estimate the possible loss or a range of loss amounts, even where we have determined that a loss is reasonably possible. Generally, class actions involve a large number of people and raise complex legal and factual issues that result in uncertainty as to their outcome and, ultimately, making it difficult for us to estimate the amount of damages that a plaintiff might successfully prove. This analysis is further complicated by the fact that the plaintiffs lack contractual privity with us. Governmental investigations. To date, we have received a consolidated, multi-state Civil Investigative Demand issued on behalf of 49 state Attorneys General and the District of Columbia, a separate Civil Investigative Demand from the office of the Indiana Attorney General and a separate Civil Investigative Demand from the office of the California Attorney General relating to the Security Incident. We have been in discussions, directly with certain Attorneys General or indirectly through an executive committee of the multi-state group of Attorneys General, about potential resolution of issues arising from these investigations. Although we are hopeful that we can resolve these matters on acceptable terms, there is no assurance that we will be able to do so on terms acceptable to us and to any or all such states. We also are subject to the following pending governmental actions: •an investigation by the U.S. Federal Trade Commission; •an investigation by the U.S. Department of Health and Human Services; •an investigation by the Office of the Australian Information Commissioner; and •an investigation by the Office of the Privacy Commissioner of Canada. As previously disclosed, on March 9, 2023, the Company reached a settlement with the SEC in connection with the Security Incident. This settlement fully resolves the previously disclosed SEC investigation of the Security Incident and is further described in an SEC cease-and-desist order (the “SEC Order”). Under the terms of the SEC Order, the Company has agreed to cease-and-desist from committing or causing any violations or any future violations of Sections 17(a)(2) and (3) of the Securities Act of 1933, as amended (the “Securities Act”), and Section 13(a) of the Securities Exchange Act of 1934, as amended (the “Exchange Act”), and Rules 12b-20, 13a-13 and 13a-15(a) thereunder. No other violations of the securities laws are alleged in the SEC Order. As part of the SEC Order, the Company also agreed to pay, and has paid, a civil penalty in the amount of $3.0 million. The Company consented to the entry of the SEC Order without admitting or denying the findings of the SEC Order, other than with respect to the SEC’s jurisdiction over the Company and the subject matter of the SEC Order. The SEC Order describing the settlement was furnished as Exhibit 99.1 and the SEC’s press release announcing this resolution is furnished as Exhibit 99.2 to the Company’s Current Report on Form 8-K filed with the SEC on March 9, 2023. On September 28, 2021, the Information Commissioner’s Office in the United Kingdom under the U.K. Data Protection Act 2018 (the "ICO") notified us that it has closed its investigation of the Security Incident. Based on its investigation and having considered our actions before, during and after the Security Incident, the ICO issued our European subsidiary a reprimand in accordance with Article 58(2)(b) of the U.K. General Data Protection Regulation ("U.K. GDPR") due to our non-compliance, in the ICO's view, with the requirements set out in Article 32 of the U.K. GDPR regarding the processing of personal data. The ICO did not impose a penalty related to the Security Incident, nor did it impose any requirements for further action by us. On September 24, 2021, we received notice from the Spanish Data Protection Authority that it has concluded its investigation of the Security Incident, pursuant to which our European subsidiary paid a penalty of €60,000 in relation to the alleged late notification of two Spanish data controllers regarding the Security Incident. On January 15, 2021, we were notified by the Data Protection Commission of Ireland that it has concluded its investigation of the Security Incident without taking any action against us. We continue to cooperate with all ongoing investigations, which include various requests for documents, policies, narratives and communications, as well as requests to interview or depose various Company-related personnel. As noted above, each of these separate governmental investigations could result in adverse judgments, settlements, fines, penalties or other resolution, the amount, scope and timing of which we are currently unable to predict, but could have a material adverse impact on our results of operations, cash flows or financial condition.

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://www.xbrl.org/2003/role/disclosureRef -Topic 440 -SubTopic 10 -Name Accounting Standards Codification -Section 50 -Paragraph 4 -Subparagraph (a) -Publisher FASB -URI https://asc.fasb.org//1943274/2147482648/440-10-50-4 Reference 2: http://www.xbrl.org/2009/role/commonPracticeRef -Topic 450 -Name Accounting Standards Codification -Publisher FASB -URI https://asc.fasb.org//450/tableOfContent Reference 3: http://www.xbrl.org/2003/role/disclosureRef -Topic 954 -SubTopic 440 -Name Accounting Standards Codification -Section 50 -Paragraph 1 -Subparagraph (a) -Publisher FASB -URI https://asc.fasb.org//1943274/2147480327/954-440-50-1 Reference 4: http://www.xbrl.org/2003/role/disclosureRef -Topic 440 -SubTopic 10 -Name Accounting Standards Codification -Section 50 -Paragraph 4 -Subparagraph (c) -Publisher FASB -URI https://asc.fasb.org//1943274/2147482648/440-10-50-4 Reference 5: http://fasb.org/us-gaap/role/ref/legacyRef -Topic 440 -Name Accounting Standards Codification -Publisher FASB -URI https://asc.fasb.org//440/tableOfContent + Details
Name: | us-gaap_CommitmentsAndContingenciesDisclosureTextBlock
Namespace Prefix: | us-gaap_
Data Type: | dtr-types:textBlockItemType
Balance Type: | na
Period Type: | duration