IN RE ONIX GROUP, LLC DATA BREACH LITIGATION

CourtDistrict Court, E.D. Pennsylvania
DecidedJune 14, 2024
Docket2:23-cv-02288
StatusUnknown

This text of IN RE ONIX GROUP, LLC DATA BREACH LITIGATION (IN RE ONIX GROUP, LLC DATA BREACH LITIGATION) is published on Counsel Stack Legal Research, covering District Court, E.D. Pennsylvania primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
IN RE ONIX GROUP, LLC DATA BREACH LITIGATION, (E.D. Pa. 2024).

Opinion

IN THE UNITED STATES DISTRICT COURT FOR THE EASTERN DISTRICT OF PENNSYLVANIA

CIVIL ACTION

IN RE ONIX GROUP, LLC DATA BREACH LITIGATION NO. 23-2288-KSM

MEMORANDUM

Marston, J. June 14, 2024

This is a putative class action brought by Plaintiffs Eric Meyers, Donald Owens, Aida Albina Wimbush, Ashtyn Mark, Leah Simione, Melissa Lyston, and Angela Haynie (“Plaintiffs”). (See Doc. No. 18.) Plaintiffs allege that Defendant Onix Group, LLC (“Defendant”) failed to adequately safeguard sensitive personal information entrusted to it by its customers, despite the foreseeability of a data breach. (Doc. No. 29-1 at 8.) Presently before the Court is Plaintiffs’ Unopposed Motion for Preliminary Approval of the Class Action Settlement (the “Motion”) and revised Settlement Agreement, Notices, and Claim Form. (Doc. Nos. 29, 35, 37, 42, 43.1) For the reasons below, the Motion is granted, and the Court will schedule a final approval hearing. I. BACKGROUND

Beginning in June 2023, numerous class actions were filed in this Court on behalf of consumers whose information was stolen following a third party cyberattack against Defendant, a conglomerate operating in the hospitality, commercial real estate development, and healthcare industries. (See, e.g., Doc. No. 1, Owens v. Onix Group, LLC, Civil Action No. 2:23-cv-2301-

1 The operative Settlement Agreement is incorporated as Doc. No. 43, and the operative Claim Form, short-form notice, and long-form notice are incorporated as Doc. Nos. 43-2, 43-3, and 43-4 respectively. KSM; Doc. No. 1, Bernard v. Onix Group, LLC, Civil Action No. 5:23-cv-02556-KSM; Doc. No. 18 at ¶ 2.) On July 19, 2023, this Court consolidated these class actions under the new case name “In re Onix Group, LLC Data Breach Litigation.” (Doc. No. 14.) On September 15, 2023, Plaintiffs filed a consolidated complaint asserting claims for negligence, negligence per se,

breach of implied contract, breach of fiduciary duty, unjust enrichment, and violations of state consumer protection and privacy statutes. (Doc. No. 18.) Plaintiffs alleged that they entrusted Defendant with their sensitive personal information, such as name, address, social security number, medication information, health insurance information, and other clinical information, but that Defendant failed to implement adequate security practices to protect the information from cybercriminals. (Id. at ¶¶ 20–24.) Plaintiffs argued that a large depository of highly valuable health care information is a foreseeable target for cybercriminals, and that Defendant should have known that its repository of information for hundreds of thousands of patients posed a significant risk of being targeted for a data breach. (Id. at ¶ 223.) On December 1, 2023, following mediation with an experienced mediator, Bennett G. Picker, Esquire of Stradley

Ronon Stevens & Young LLP, the parties agreed to a settlement in principle, and on February 20, 2024, Plaintiffs filed an initial unopposed Motion for preliminary approval of the class action settlement. (Doc. No. 29; Doc. No. 29-1 at 9.) On May 15, 2024, the Court held a hearing on the Motion, and on May 21, 2024, at the Court’s direction, the parties filed a revised settlement agreement, short-form notice, long-form notice, and Claim Form. (Doc. Nos. 34, 35.) On May 31, 2024, at the Court’s further direction to provide additional clarity in the settlement notices and Claim Form, the parties filed second amended settlement documents.2 (Doc. No. 37.)

2 In addition, on June 13, 2024, at the Court’s direction to ensure that deadlines in the Settlement Agreement were more certain, the parties filed a second amended Settlement Agreement. (Doc. No. 42.) The parties refiled the Settlement Agreement on June 14, 2024 to correct a clerical error. (Doc. No. 43.) II. Preliminary Certification of the Class for Settlement Purposes

a. Legal Standard

The Court may certify class actions for the sole purpose of settlement. In re CertainTeed Corp. Roofing Shingle Prods. Liab. Litig., 269 F.R.D. 468, 476 (E.D. Pa. 2010) (citing In re GMC Pick-Up Truck Fuel Tank Prods. Liab. Litig., 55 F.3d 768, 786 (3d Cir. 1995)). In these situations, the court provisionally certifies the class, but reserves “[f]inal certification” until it “rules on whether the final settlement agreement is to be approved.” Id. When a court certifies a class for settlement, “it must first find that the class satisfies all the requirements of Rule 23,” and in particular Rule 23(a) and 23(b). In re Cmty. Bank of N. Va., 418 F.3d 277, 300 (3d Cir. 2005). Under Rule 23(a), a class action is allowable only if: (1) the class is so numerous that joinder of all members is impracticable; (2) there are questions of law or fact common to the class; (3) the claims or defenses of the representative parties are typical of the claims or defenses of the class; and (4) the representative parties will fairly and adequately protect the interests of the class. Fed. R. Civ. P. 23(a); see also Reyes v. Netdeposit, LLC, 802 F.3d 469, 482 (3d Cir. 2015) (“All potential classes must initially satisfy four prerequisites to be certified: (1) numerosity, (2) commonality, (3) typicality, and (4) adequacy of representation.”). Additionally, the class must be currently and readily ascertainable based on objective criteria. Marcus v. BMW of N. Am. LLC, 687 F.3d 583, 593 (3d Cir. 2012). If the Rule 23(a) and ascertainability conditions are met, then a case may proceed as a class action if one of the conditions of Rule 23(b) is also satisfied. Here, Plaintiff seeks certification for a class under Rule 23(b)(3), which requires that “the court find[] that the questions of law or fact common to class members predominate over any questions affecting only individual members, and that a class action is superior to other available methods for fairly and efficiently adjudicating the controversy.” Fed. R. Civ. P. 23(b)(3); see also Reyes, 802 F.3d at 482 (explaining that plaintiff must demonstrate “predominance and superiority” for certification under Rule 23(b)(3)).

b. Analysis Plaintiff proposes a class of: All 308,942 natural persons whose Private Information was compromised in the Data Breach and who have not been confirmed to be deceased. Excluded from the Settlement Class are: (1) the Judges presiding over the Action and members of their immediate families and their staff; (2) Onix, its subsidiaries, parent companies, successors, predecessors, and any entity in which Onix or its parents, have a controlling interest, and its current or former officers and directors; (3) natural persons who properly execute and submit a Request for Exclusion prior to the expiration of the Opt-Out Period; and (4) the successors or assigns of any such excluded natural person.

(Doc. No. 29-1 at 10; Doc. No. 43-1 at ¶ 1.42.) This class is ascertainable and meets all six requirements of Rules 23(a) and 23(b). We will address each in turn. i. Ascertainability The plaintiff has the burden of showing, by a preponderance of the evidence, that “(1) the class is ‘defined with reference to objective criteria’; and (2) there is ‘a reliable and administratively feasible mechanism for determining whether putative class members fall within the class definition.’” Byrd v. Aaron’s Inc., 784 F.3d 154, 163 (3d Cir.

Free access — add to your briefcase to read the full text and ask questions with AI

Related

Mullane v. Central Hanover Bank & Trust Co.
339 U.S. 306 (Supreme Court, 1950)
Amchem Products, Inc. v. Windsor
521 U.S. 591 (Supreme Court, 1997)
In Re Pet Food Products Liability Litigation
629 F.3d 333 (Third Circuit, 2010)
Dewey v. Volkswagen Aktiengesellschaft
681 F.3d 170 (Third Circuit, 2012)
Marcus v. BMW of North America, LLC
687 F.3d 583 (Third Circuit, 2012)
In Re Baby Products Antitrust Litigation
708 F.3d 163 (Third Circuit, 2013)
John Rodriguez v. Natl City Bank
726 F.3d 372 (Third Circuit, 2013)
Gabriel Carrera v. Bayer Corp
727 F.3d 300 (Third Circuit, 2013)
United States v. Richardson
521 F.3d 149 (Second Circuit, 2008)
Reibstein v. RITE AID CORPORATION
761 F. Supp. 2d 241 (E.D. Pennsylvania, 2011)
Crystal Byrd v. Aaron's Inc
784 F.3d 154 (Third Circuit, 2015)
Reynaldo Reyes v. Netdeposit
802 F.3d 469 (Third Circuit, 2015)
In Re: Google Inc. Cookie Plac v.
934 F.3d 316 (Third Circuit, 2019)
Sullivan v. DB Investments, Inc.
667 F.3d 273 (Third Circuit, 2011)

Cite This Page — Counsel Stack

Bluebook (online)
IN RE ONIX GROUP, LLC DATA BREACH LITIGATION, Counsel Stack Legal Research, https://law.counselstack.com/opinion/in-re-onix-group-llc-data-breach-litigation-paed-2024.