In re Target Corp. Customer Data Security Breach Litigation

309 F.R.D. 482, 2015 WL 5432115
CourtDistrict Court, D. Minnesota
DecidedSeptember 15, 2015
DocketMDL No. 14-2522 (PAM/JJK)
StatusPublished
Cited by6 cases

This text of 309 F.R.D. 482 (In re Target Corp. Customer Data Security Breach Litigation) is published on Counsel Stack Legal Research, covering District Court, D. Minnesota primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
In re Target Corp. Customer Data Security Breach Litigation, 309 F.R.D. 482, 2015 WL 5432115 (mnd 2015).

Opinion

MEMORANDUM AND ORDER

PAUL A. MAGNUSON, District Judge.

This matter is before the Court on Plaintiffs’ Motion for Class Certification and Appointment of Class Representatives and Class Counsel. For the reasons that follow, the Motion is granted.

BACKGROUND

This case arises out of a massive breach of the computer network of one of the nation’s largest retailers, Defendant Target Corporation. In late 2013, unidentified computer hackers gained virtually unfettered access to Target’s computer system, ultimately extracting the financial information of more than 40 million consumers. That the breach occurred during the holiday shopping season served to increase its severity.

After the Judicial Panel on Multidistrict Litigation consolidated lawsuits regarding [485]*485the breach in this Court, the case was separated into two “tracks”: one for consumers and one for financial institutions.1 The consumer action has settled, pending final court approval. (Mar. 19, 2015, Order Preliminarily Approving Settlement (Docket No. 364).) Thus, only the instant “track” of financial-institution eases remains.

Plaintiffs in the financial-institution “track” issued payment cards such as credit and debit cards to consumers who, in turn, used those cards at Target stores during the period of the 2013 data breach. The Consolidated Amended Class Action Complaint (Docket No. 163) raises three claims2 against Target. Count One contends that Target was negligent in failing to provide sufficient security to prevent the hackers from accessing customer data. Count Two asserts that Target violated Minnesota’s Plastic Security Card Act, and Count Three alleges that this violation constitutes negligence per se. The putative class representative Plaintiffs allege that they suffered injury in the form of replacing cards for their customers, reimbursing fraud losses, and taking various other remedial steps in response to the Target data breach.

Plaintiffs now seek the certification of a Rule 23(b)(3) class “of all entities in the United States and its Territories that issued payment cards compromised in the payment card data breach that was publicly disclosed by Target on December 19, 2013.” (Pis.’ Supp. Mem. (Docket No. 474) at 21.) Target opposes the certification request. DISCUSSION

Rule 23(a) sets out the preliminary requirements for the certification of a class action. According to the Rule, a plaintiff seeking class certification must establish that:

(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). These requirements are commonly expressed as numerosity, commonality, typicality, and adequacy of representation.

In addition, because Plaintiffs request certification under Rule 23(b)(3), they must demonstrate that “questions of law or fact common to the class predominate over any questions affecting only individual members, and that a class action is superior to other available methods for the fair and efficient adjudication of the controversy.” Again, in common parlance, these requirements are known as predominance and superiority. Although Target also challenges Plaintiffs’ ability to establish every class certification requirement with the exception of numerosity, Target focuses its argument on the related issues of commonality and predominance.

The Court does not consider the merits of Plaintiffs’ substantive claims in assessing a motion for class certification, but Plaintiffs bear the burden to establish each element listed above. Gen. Tel. Co. v. Falcon, 457 U.S. 147, 161, 102 S.Ct. 2364, 72 L.Ed.2d 740 (1982). In rigorously analyzing whether Plaintiffs have met their burden, the Court “may look past the pleadings ... [to] understand the claims, defenses, relevant facts, and applicable substantive law____” Thompson v. Am. Tobacco Co., 189 F.R.D. 544, 549 (D.Minn.1999) (quotation omitted). Indeed, the class-certification “determination generally involves considerations that are enmeshed in the factual and legal issues comprising the plaintiffs cause of action.” Comcast Corp. v. Behrend, — U.S. -, 133 S.Ct. 1426, 1429, 185 L.Ed.2d 515 (2013). Because of the fact-specific quality of the analysis, the Court exercises broad discretion [486]*486in determining whether to certify a particular class under Rule 23. Reiter v. Sonotone Corp., 442 U.S. 330, 345, 99 S.Ct. 2326, 60 L.Ed.2d 931 (1979).

A. Commonality and Predominance

As Target notes, Rule 23(a)’s commonality requirement and Rule 23(b)(3)’s predominance requirement are related and somewhat interdependent concepts. Rule 23(a) requires that there are common questions of law or fact among class members’ claims, and Rule 23(b)(3) requires that those common questions predominate over individual issues. According to Target, any common questions among Plaintiffs do not predominate, making class certification inappropriate.

When determining whether common questions predominate, the Court’s “inquiry should be limited to determining whether, if the plaintiffs’ ‘general allegations are true, common evidence could suffice to make out a prima facie case for the class.’ ” In re Zurn Pex Plumbing Prods. Liab. Litig., 644 F.3d 604, 618 (8th Cir.2011) (quoting Blades v. Monsanto Co., 400 F.3d 562, 566 (8th Cir.2005)). A common question is one whose determination “will resolve an issue that is central to the validity of each one of the claims in one stroke.” Wal-Mart Stores v. Dukes, 564 U.S. 338, 131 S.Ct. 2541, 2551, 180 L.Ed.2d 374 (2011).

Target attacks Plaintiffs’ Motion on multiple fronts, but Target’s arguments are essentially two overarching challenges. First, Target contends that no classwide proof supports Plaintiffs’ negligence claims or Plaintiffs’ PCSA claims. Part of this argument is Target’s contention that the negligence claims are subject to the laws of different states, making class treatment of those claims inappropriate. Second, Target contends that damages must be calculated on a bank-by-bank basis, meaning that individual damages issues predominate over any potential class-wide issues.

1. Choice of Law

Target contends that Plaintiffs’ claims have only a “slight nexus” to Minnesota, making the wholesale application of Minnesota law inappropriate. According to Target, the Court must conduct a choice-of-law analysis with regard to each putative Plaintiffs claim to determine which state’s negligence law applies. And indeed, Target argues the Court must evaluate each potential jurisdiction’s choice-of-law rules to even conduct the choice-of-law analysis. Such a complicated undertaking renders class treatment unworkable, Target insists.

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

Related

Cite This Page — Counsel Stack

Bluebook (online)
309 F.R.D. 482, 2015 WL 5432115, Counsel Stack Legal Research, https://law.counselstack.com/opinion/in-re-target-corp-customer-data-security-breach-litigation-mnd-2015.