In Re JetBlue Airways Corp. Privacy Litigation

379 F. Supp. 2d 299, 2005 U.S. Dist. LEXIS 16002, 2005 WL 1813273
CourtDistrict Court, E.D. New York
DecidedJuly 29, 2005
Docket1:04-cv-01587
StatusPublished
Cited by48 cases

This text of 379 F. Supp. 2d 299 (In Re JetBlue Airways Corp. Privacy Litigation) is published on Counsel Stack Legal Research, covering District Court, E.D. New York primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
In Re JetBlue Airways Corp. Privacy Litigation, 379 F. Supp. 2d 299, 2005 U.S. Dist. LEXIS 16002, 2005 WL 1813273 (E.D.N.Y. 2005).

Opinion

MEMORANDUM & ORDER

AMON, District Judge.

INTRODUCTION

A nationwide class of plaintiffs brings this action against JetBlue Airways Corporation (“JetBlue”), Torch Concepts, Inc. (“Torch”), Acxiom Corporation (“Acxiom”), and SRS Technologies (“SRS”) for alleged violations of the Electronic Communications Privacy Act of 1986 (“ECPA”), 18 U.S.C. § 2701, et seq. (1986), and violations of state and common law. Plaintiffs claim that defendants violated their privacy rights by unlawfully transferring their personal information to Torch for use in a federally-funded study on military base security. Plaintiffs seek a minimum of $1,000 in damages per class member, or injunctive relief to the extent that damages are unavailable, as well as a declaratory judgment. Defendants have moved to dismiss the Amended Complaint pursuant to Rule 12(b)(6) of the Federal Rules of Civil Procedure on the grounds that plaintiffs have failed to state a federal cause of action under the ECPA, that plaintiffs’ state law claims are federally preempted, and that plaintiffs have failed to state any claim under state law.

PROCEDURAL HISTORY

This case is a multidistrict consolidated class action. Initially, a total of nine putative class actions were brought, eight in the Eastern District of New York and one in the Central District of California, 1 on behalf of persons allegedly injured by Jet-Blue’s unauthorized disclosure of personally identifiable travel information. On February 24, 2004, the Judicial Panel on Multidistrict Litigation ordered, pursuant to 28 U.S.C. § 1407, that the action pending in the Central District of California be

*304 transferred to this Court for coordinated or consolidated pretrial proceedings with the actions already pending in this district. Since that time, five more cases have been joined in the action. 2 The consolidated class filed its Amended Complaint in this Court on May 7, 2004.

STATEMENT OF FACTS

Unless otherwise indicated, the following facts set forth in plaintiffs’ Amended Complaint are presumed to be true for purposes of defendants’ motions to dismiss. JetBlue has a practice of compiling and maintaining personal information, known in the airline industry as Passenger Name Records (“PNRs”), on each of its adult and minor passengers. Information contained in PNRs includes, for example, passenger names, addresses, phone numbers, and travel itineraries. (Am. Compl. ¶ 38; PL’s Mem. at 4-5.) The PNRs are maintained, or temporarily stored, on JetBlue’s computer servers, and passengers are able to modify their stored information. (Am. Comply 39.) Acxiom, a world leader in customer and information management solutions, maintains personally-identifiable information on almost eighty percent of the U.S. population, including many Jet-Blue passengers, which it uses to assist companies such as JetBlue in customer and information management solutions. (Id. ¶ 22; PL’s Mem. at 4.)

The personal information that forms the basis of JetBlue’s PNRs is obtained from its passengers over the telephone and through its Internet website during the selection and purchase of travel arrangements. In order to encourage the provision of personal information in this manner, JetBlue created a privacy policy which provided that the company would use computer IP addresses only to help diagnose server problems, cookies to save consumers’ names, e-mail addresses to alleviate consumers from having to re-enter such data on future occasions, and optional passenger contact information to send the user updates and offers from JetBlue. (Am.Compl^ 36.) The JetBlue privacy policy specifically represented that any financial and personal information collected by JetBlue would not be shared with third parties and would be protected by secure servers. JetBlue also purported to have security measures in place to guard against the loss, misuse, or alteration of consumer information under its control. (Id. ¶ 37.)

In the wake of September 11, 2001, Torch, a data mining company similar to Acxiom, presented the Department of Defense (“DOD”) with a data pattern analysis proposal geared toward improving the security of military installations in the United States and possibly abroad. Torch suggested that a rigorous analysis of personal characteristics of persons who sought access to military installations might be used to predict which individuals pose a risk to the security of those installations. (Id. ¶ 42.) DOD showed interest in Torch’s proposal and added Torch as a subcontractor to an existing contract with SRS so that Torch could carry out a limited initial test of its proposed study. The SRS contract was amended to include airline PNRs as a possible data source in connection with Torch’s study. (Id. ¶ 43.) Because Torch needed access to a large national-level database of personal information and because no federal agencies approached by Torch would grant access to their own governmental databases, Torch indepen *305 dently contacted a number of airlines in search of private databases that might contain adequate information tp serve its requirements. (Id. ¶¶ 43-^16.) These airlines declined to share their passengers’ personal information unless the Department of Transportation (“DOT”) and/or the Transportation Security Administration (“TSA”) were involved and approved of such data sharing. (Id. ¶ 46.)

Unable to obtain the data through its own devices, Torch asked members of Congress to intervene on its behalf with the airlines or federal agencies. (Id. ¶ 47.) Torch also contacted the DOT directly. (Id. ¶ 48.) Following a series of meetings, the DOT and the TSA agreed to assist Torch in obtaining consent from a national airline to share its passenger information. (Id. ¶ 51.) On July 30, 2002, the TSA sent JetBlue a written request to supply its data to the DOD, and JetBlue agreed to cooperate. (Id. ¶¶ 53-54.) In September 2002, JetBlue and Acxiom collectively transferred approximately five million electronically-stored PNRs to Torch" in connection with the SRS/DOD contract. (Id. ¶¶ 53, 55.) Then, in October 2002, Torch separately purchased additional data from Acxiom for use in connection with the SRS contract. This data was merged with the September 2002 data to create a single database of JetBlue passenger information including each passenger’s name, address, gender, home ownership or rental status, economic status, social security number, occupation, and the number of adults and children in the passenger’s family as well as the number of vehicles owned or leased. (Id. ¶ 56.) Using this data, Torch began its data analysis and created a customer profiling scheme designed to identify high-risk passengers among those traveling on JetBlue. (Id. ¶¶ 57-58.)

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

Related

In re: NOVANT HEALTH, INC.
M.D. North Carolina, 2023
Meyer v. Mittal
D. Oregon, 2023
Leitner v. Morsovillo
W.D. Missouri, 2022
Moore v. Centrelake Medical Group, Inc.
California Court of Appeal, 2022
Garner v. Amazon.com Inc
W.D. Washington, 2022
Abudayyeh v. Envoy Air, Inc.
N.D. Illinois, 2021
Conlan Abu v. Dickson
E.D. Michigan, 2021
Kornotzki v. Jawad
S.D. New York, 2020
DOE v. Patrick
N.D. New York, 2020
Dolan v. Jetblue Airways Corp.
385 F. Supp. 3d 1338 (S.D. Florida, 2019)
Corley v. Vance
365 F. Supp. 3d 407 (S.D. Illinois, 2019)
In re Equifax, Inc.
362 F. Supp. 3d 1295 (N.D. Georgia, 2019)
Cox v. Spirit Airlines, Inc.
340 F. Supp. 3d 154 (E.D. New York, 2018)

Cite This Page — Counsel Stack

Bluebook (online)
379 F. Supp. 2d 299, 2005 U.S. Dist. LEXIS 16002, 2005 WL 1813273, Counsel Stack Legal Research, https://law.counselstack.com/opinion/in-re-jetblue-airways-corp-privacy-litigation-nyed-2005.