Ganesh Sankar, et al. v. California Northstate University, LLC

CourtDistrict Court, E.D. California
DecidedDecember 10, 2025
Docket2:24-cv-00473
StatusUnknown

This text of Ganesh Sankar, et al. v. California Northstate University, LLC (Ganesh Sankar, et al. v. California Northstate University, LLC) is published on Counsel Stack Legal Research, covering District Court, E.D. California primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Ganesh Sankar, et al. v. California Northstate University, LLC, (E.D. Cal. 2025).

Opinion

1 2 3 4 5 6 7 8 UNITED STATES DISTRICT COURT 9 FOR THE EASTERN DISTRICT OF CALIFORNIA 10 11 GANESH SANKAR, et al., No. 2:24-cv-00473-DAD-JDP 12 Plaintiffs, 13 v. ORDER GRANTING PLAINTIFFS’ MOTION FOR PRELIMINARY APPROVAL OF 14 CALIFORNIA NORTHSTATE CLASS ACTION SETTLEMENT UNIVERSITY, LLC, 15 (Doc. No. 42) Defendant. 16

17 18 This matter is before the court on plaintiffs’ motion for preliminary approval of class 19 action settlement of their data breach class action lawsuit brought against defendant California 20 Northstate University, LLC. (Doc. No. 42.) On March 24, 2025, plaintiffs’ motion was taken 21 under submission on the papers pursuant to Local Rule 230(g). (Doc. No. 43.) For the reasons 22 explained below, the court will grant plaintiffs’ motion. 23 BACKGROUND 24 On February 15, 2024, plaintiffs filed this data breach class action. (Doc. No. 1.) On June 25 14, 2024, plaintiffs filed an amended complaint. (Doc. No. 20.) Defendant filed a motion to 26 dismiss on July 15, 2024, which the court administratively terminated after the parties filed their 27 notice of settlement. (Doc. Nos. 22, 32.) Plaintiffs represent that they engaged in the following 28 discovery efforts prior to settlement. 1 Before reaching a settlement, the Parties engaged in both formal and informal discovery to assess the merits of their respective claims and 2 defenses. Plaintiffs propounded written discovery, including interrogatories and requests for production, while Defendant 3 provided information regarding the scope and impact of the Data Incident. In addition, the Parties exchanged informal discovery, 4 including discussions about Defendant’s data security practices, remedial measures taken following the incident, and the potential 5 risks and damages associated with the alleged breach. 6 (Doc. No. 42 at 10) (citations omitted). 7 To facilitate resolution, the Parties agreed to participate in private mediation with an experienced data breach mediator, which was 8 scheduled for December 12, 2024. However, through continued negotiations and a thorough evaluation of the relevant facts and legal 9 issues, the Parties were able to reach a Settlement before the scheduled mediation date, avoiding the time and expense of further 10 litigation. By November 27, 2024, the Parties reached an agreement on the material terms of the Settlement[.] 11 12 (Id.) 13 On March 4, 2025, plaintiffs filed a motion for preliminary approval of the class action 14 settlement. (Doc. No. 42.) The parties attached thereto their executed Settlement Agreement. 15 (Doc. No. 42-1.) In their pending motion plaintiffs seek an order from this court: 16 (1) provisionally certifying the settlement class, for settlement purposes only, with appointment 17 of plaintiffs as class representatives, appointment of plaintiffs’ counsel as class counsel, and 18 approval of Kroll Settlement Administration, LLC (“Kroll”) as the Settlement Administrator; 19 (2) preliminarily approving the parties’ proposed settlement; (3) approving and directing the 20 mailing of the proposed Notices and the Notice Program and approving the Claim Form and the 21 Claim process; (4) establishing procedures and deadlines for Settlement Class members to opt-out 22 and object; and (5) scheduling the hearing date for the final approval of the class settlement. 23 (Doc. No. 42 at 8–9.) On August 23, 2025, defendant filed a statement of non-opposition to the 24 granting of plaintiff’s motion. (Doc. No. 44.) On October 1, 2025, the court ordered that 25 plaintiffs file supplemental briefing addressing areas of concern to the court. (Doc. No. 45.) On 26 October 21, 2025, plaintiffs filed their supplemental briefing. (Doc. No. 46.) 27 ///// 28 ///// 1 THE PROPOSED SETTLEMENT 2 A. The Class 3 For settlement purposes, the parties request approval of the following class (the “Class,” 4 “Class Members,” or “Settlement Class”): “All persons in the United States whose Private 5 Information was potentially accessible as a result of the Data Incident, including those who were 6 sent notification from Defendant that their Private Information was potentially accessible as a 7 result of the Data Incident.” (Doc. No. 42 at 11.) “Excluded from the Settlement Class are: (a) 8 all persons who are governing board members of the Defendant; (b) governmental entities; and 9 (c) the Court, the Court’s immediate family, and Court staff.” (Id.) “‘Data Incident’ means the 10 cybersecurity incident involving Defendant resulting in the unauthorized access to or acquisition 11 of Settlement Class Members’ Private Information between February 12, 2023, and February 13, 12 2023.” (Doc. No. 42-1 at 7.) “‘Private Information’ means information collected by Defendant 13 pertaining to Settlement Class members, including, but not limited to, names and Social Security 14 numbers.” (Id. at 9.) 15 B. Class Period 16 The Class period is February 12, 2023 to the present. (Doc. No. 46 at 10.) 17 C. The Release of Claims 18 Released Parties means “Defendant, and its present and former parents, subsidiaries, 19 divisions, departments, affiliates, predecessors, successors and assigns, and any and all of its past, 20 present, and future directors, officers, executives, officials, principals, stockholders, heirs, agents, 21 insurers, reinsurers, members, attorneys, accountants, actuaries, fiduciaries, advisors, consultants, 22 representatives, partners, joint venturers, licensees, licensors, independent contractors, subrogees, 23 trustees, executors, administrators, clients, customers, data owners, associated third parties, 24 predecessors, successors and assigns, and any other person acting on Defendant’s behalf and/or in 25 their capacity as such.” (Doc. No. 42-1 at 10.) 26 Releasing Parties means “(i) Plaintiffs and all Settlement Class Members, (ii) each of their 27 respective executors, representatives, heirs, predecessors, assigns, beneficiaries, affiliates, 28 successors, bankruptcy trustees, guardians, joint tenants, tenants in common, tenants by the 1 entireties, agents, attorneys, (iii) any entities in which a Plaintiff and/or other participating 2 Settlement Class Member has or had a controlling interest or that has or had a controlling interest 3 in him or her, (iv) any other person or entity (including any governmental entity) claiming by or 4 through, on behalf of, for the benefit of, derivatively for, or as representative of a Plaintiff and/or 5 any other Settlement Class Member, and all those who claim through them or on their behalf, and 6 (v) the respective past and present directors, governors, executive-committee members, officers, 7 officials, employees, members, partners, principals, agents, attorneys, advisors, trustees, 8 administrators, fiduciaries, consultants, service providers, representatives, successors in interest, 9 assigns, beneficiaries, heirs, executors, accountants, accounting advisors, and auditors of any or 10 all of the above persons or entities identified in (i)-(iv).” (Id. at 10–11.) 11 “As of the Effective Date, the Releasing Parties shall automatically be deemed to have 12 fully, finally, and irrevocably released and forever discharged the Released Parties of, and shall 13 be forever barred from instituting, maintaining, or prosecuting, any and all liabilities, rights, 14 claims, actions, causes of action, demands, damages, costs, attorneys’ fees, losses and remedies, 15 whether known or unknown, asserted or unasserted, existing or potential, suspected or 16 unsuspected, liquidated or unliquidated, legal, statutory, or equitable, based on contract, tort or 17 any other theory, whether on behalf of themselves or others, that result from, arise out of, are 18 based upon, or relate to (a) the Data Incident; (b) the Action; or (c) any of the alleged violations 19 of laws or regulations cited in the Complaint.” (Id.

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

Related

Amchem Products, Inc. v. Windsor
521 U.S. 591 (Supreme Court, 1997)
Wolin v. Jaguar Land Rover North America, LLC
617 F.3d 1168 (Ninth Circuit, 2010)
United States v. Ortiz-Graulau
526 F.3d 16 (First Circuit, 2008)
In Re Bluetooth Headset Products Liability
654 F.3d 935 (Ninth Circuit, 2011)
Mazza v. American Honda Motor Co., Inc.
666 F.3d 581 (Ninth Circuit, 2012)
United States v. Dennis Veal
23 F.3d 985 (Sixth Circuit, 1994)
Powers v. Eichen
229 F.3d 1249 (Ninth Circuit, 2000)
Staton v. Boeing Co.
327 F.3d 938 (Ninth Circuit, 2003)
Ginger McCall v. Facebook, Inc.
696 F.3d 811 (Ninth Circuit, 2012)
Comcast Corp. v. Behrend
133 S. Ct. 1426 (Supreme Court, 2013)
Robert Radcliffe v. Experian Information Solutions
715 F.3d 1157 (Ninth Circuit, 2013)
Martin Gonzalez, Sr. v. City of Maywood
729 F.3d 1196 (Ninth Circuit, 2013)
Hesse v. Sprint Corp.
598 F.3d 581 (Ninth Circuit, 2010)
Rodriguez v. West Publishing Corp.
563 F.3d 948 (Ninth Circuit, 2009)

Cite This Page — Counsel Stack

Bluebook (online)
Ganesh Sankar, et al. v. California Northstate University, LLC, Counsel Stack Legal Research, https://law.counselstack.com/opinion/ganesh-sankar-et-al-v-california-northstate-university-llc-caed-2025.