Brodsky v. Apple Inc.

• Court: District Court, N.D. California
• Decided: April 7, 2020
• Docket: 5:19-cv-00712
• Status: Unknown

Opinion

8 UNITED STATES DISTRICT COURT

9 NORTHERN DISTRICT OF CALIFORNIA 10 SAN JOSE DIVISION 11

12 JAY BRODSKY, et al., Case No. 19-CV-00712-LHK

13 Plaintiffs, ORDER GRANTING MOTION TO DISMISS WITH PREJUDICE 14 v. Re: Dkt. No. 46 15 APPLE INC., 16 Defendant. 17 18 Plaintiffs Jay Brodsky, Brian Tracey, Alex Bishop, Brendan Schwartz, William 19 Richardson, and John Kyslowsky (“Plaintiffs”) bring this putative class action against Defendant 20 Apple Inc. (“Apple”) for alleged privacy and property violations based on Apple’s two-factor 21 authentication login tool. The Court previously granted Apple’s motion to dismiss the First 22 Amended Complaint (“FAC”), but granted Plaintiffs leave to amend. ECF No. 40 (“Order”). 23 Currently before the Court is Apple’s motion to dismiss Plaintiffs’ Second Amended Complaint 24 (“SAC”). ECF No. 46 (“Mot.”).1 Because the SAC fails to cure deficiencies previously identified 25

26 1 Apple’s motion to dismiss contains a notice of motion that is separately paginated from the memorandum of points and authorities in support of the motion. Civil Local Rule 7-2(b) provides 27 that the notice of motion and points and authorities should be contained in one document with a combined limit of 25 pages. See Civ. Loc. R. 7-2(b). Additionally, Apple’s statement of the 1 in the Court’s prior Order, the Court GRANTS Apple’s motion to dismiss with prejudice. 2 I. BACKGROUND 3 A. Factual Background 4 Plaintiffs are residents of New York, California, Ohio, Pennsylvania, Colorado, and Texas. 5 ECF No. 43 ¶ 8 (“SAC”). Apple is a California corporation that designs and sells products 6 including iPhones, iPads, Macbooks, Apple TVs, and Apple Watches. Id. ¶¶ 9, 17. Once a 7 consumer buys an Apple product, the Apple product is associated with the consumer’s Apple ID, 8 which is an individual’s email address. Id. ¶¶ 20, 34. An Apple ID is required to use Apple 9 services, such as FaceTime and iMessage. Id. ¶ 20. 10 Plaintiffs allege that Apple’s provision of two-factor authentication (“2FA”) as an Apple 11 ID login process violates Plaintiffs’ right to privacy. Id. ¶ 1. As in the FAC, the SAC identically 12 alleges that 2FA is enabled in three instances: “(i) a software update occurs on one of the Apple 13 devices; (ii) on creation of a new Apple ID; or (iii) owner of the Apple device turns on two-factor 14 authentication in the Settings.” Id. ¶ 35; see also FAC ¶ 16. 15 When enabled, 2FA requires a multi-step login process before a user can access Apple 16 services. First, the user must enter his Apple ID password on the Apple device on which the user 17 wishes to use Apple services. SAC ¶ 42. Second, the user must enter his Apple ID password on a 18 second trusted Apple device and wait to receive a six-digit verification code on the second Apple 19 device. Id. Third, the user must enter the six-digit verification code on the first Apple device. Id. 20 According to Plaintiffs, 2FA takes “2-5 or more minutes” than other login processes. Id.; see also 21 FAC ¶ 17 (pleading identical allegations). 22 After 2FA is enabled, Apple will sometimes send an email to the user that explains that the 23 user can disable 2FA: “If you didn’t enable two-factor authentication and believe someone else 24 has access to your account, you can return to your previous security settings. This link and your 25 26 issues to be decided must similarly be included in the motion’s pagination. See Civ. Loc. R. 7- 27 2(b)(4); 7-4(a)(3). Apple’s motion to dismiss also includes excessively long footnotes. One spans half a page. See Mot. at 10 n.5. 1 Apple ID security questions will expire on October 15, 2018.” SAC ¶ 61; FAC ¶ 18. Plaintiffs 2 allege that the link allowing a user to disable 2FA expires within 14 days after 2FA’s enablement, 3 and that afterwards, Plaintiffs cannot disable 2FA. SAC ¶¶ 2, 3, 61. The email also explains that 4 2FA “is an additional layer of security designed to ensure that you’re the only person who can 5 access your account, even if someone knows your password” and that 2FA “significantly 6 improves the security of your Apple ID and helps protect the photos, documents, and other data 7 you store with Apple.” Id. ¶ 61. 8 Plaintiff Brodsky alleges that in September 2015, a software update enabled 2FA for 9 Plaintiff Brodsky’s Apple ID. Id. ¶ 37. As in the FAC, the SAC includes the exact same 10 allegations that “Plaintiff Brodsky’s Apple devices had a software update that enabled 2FA for 11 Apple ID without his knowledge or consent on or around September of 2015.” Id.; see also FAC 12 ¶ 19. 13 Plaintiff Tracey alleges that “[o]n or around September 2017, 2FA was turned on for 14 Plaintiff Tracey’s Apple ID after a software update on his Apple devices.” SAC ¶ 38. 15 Specifically, Plaintiff Tracey alleges that “[h]e needs access to the latest software updates for his 16 work,” but that “Apple does not provide an option to upgrade software without 2FA.” Id. 17 Plaintiff Tracey, however, does not allege that he did not voluntarily consent to the software 18 update that included enabling 2FA. 19 The SAC alleges that the remaining four Named Plaintiffs—Plaintiffs Bishop, Schwartz, 20 Richardson, and Kyslowsky—“do not remember when 2FA was enabled for them.” Id. ¶ 39. 21 Instead, the SAC alleges the following as to the remaining four Named Plaintiffs. As to Plaintiff 22 Bishop, the SAC alleges that on or around January 2019, “based on an unforeseen consequence 23 outside of his control,” Plaintiff Bishop “lost access to his trusted device to receive his 2FA 24 passcode.” Id. ¶ 48. Plaintiff Bishop could not access Apple services using Apple ID “for days.” 25 Id. 26 As to Plaintiff Schwartz, the SAC alleges that Plaintiff Schwartz lost his second trusted 27 Apple device “based on events outside of his control.” Id. ¶ 49. Then, Apple placed Plaintiff 1 Schwartz in its account recovery process and Plaintiff Schwartz could not use his Apple ID “for 2 months.” Id. 3 As to Plaintiff Richardson, the SAC alleges that Plaintiff Richardson “was locked out of 4 [his devices] when he could not recollect offhand his password on one of the devices on or around 5 April 2019.” Id. ¶ 50. Plaintiff Richardson allegedly lost access to his downloaded and purchased 6 data and spent $219.94 installing new hardware and software. Id. 7 As to Plaintiff Kyslowsky, the SAC does not include any details about when, how, or why 8 he was locked out of his Apple devices. 9 Plaintiffs, however, do assert that they paid for third-party apps in “monthly, yearly, or 10 one-time subscription[s]” and that 2FA “intercepts access to Third-Party Apps” and Apple 11 services. Id. ¶¶ 21, 46, 51. According to Plaintiffs, 2FA thereby “virtually dispossesse[s]” 12 Plaintiffs of their access to these third-party apps and Apple services for the duration of time 13 necessary to login through 2FA. Id. ¶¶ 44, 46. 14 B. Procedural History 15 On February 8, 2019, Plaintiff Brodsky filed the instant case against Apple. ECF No. 1. 16 On March 29, 2019, Plaintiffs filed the FAC, which added Tracey, Bishop, and Schwartz as 17 named Plaintiffs. The FAC alleged five causes of action: (1) trespass to chattels, FAC ¶¶ 47-52; 18 (2) violation of the California Invasion of Privacy Act (“CIPA”), California Penal Code § 631, id. 19 ¶¶ 53-56; (3) violation of the California Computer Crime Law (“CCCL”), California Penal Code 20 § 502, id. ¶¶ 57-69; (4) violation of the Computer Fraud and Abuse Act (“CFAA”), 18 U.S.C. 21 § 1030, id. ¶¶ 70-78; and (5) unjust enrichment, id. ¶¶ 79-81. Plaintiffs brought suit on behalf of 22 the following putative class: 23 All persons or entities in the United States who own or owned an Apple Watch, iPhone, iPad, MacBook, or iMac or use Apple Services that have enabled two-factor 24 authentication (“2FA”), subsequently want to disable 2FA, and are not allowed to disable 2FA. 25 Id. ¶ 29. The class period began “when Apple introduced 2FA in 2015.” Id. ¶ 28. 26 On May 1, 2019, Apple filed a motion to dismiss Plaintiffs’ FAC. ECF No. 32. On May 27 1 15, 2019, Plaintiffs filed an opposition. On May 22, 2019, Apple filed a reply in support of its 2 motion to dismiss. ECF No. 37. 3 On May 15, 2019, the parties filed a joint case management statement. ECF No. 35. In the 4 joint case management statement, Apple asked the Court to stay discovery until after the Court 5 determines whether Plaintiffs can state a claim. Id. at 6. On May 16, 2019, the Court stayed 6 discovery “until the Court orders otherwise.” ECF No. 36. 7 On August 30, 2019, the Court granted Apple’s motion to dismiss all five of Plaintiffs’ 8 causes of action. ECF No. 40 (“Order”). First, the Court dismissed Plaintiffs’ claim for trespass 9 to chattels for two reasons. Id. at 5-8. Plaintiffs did not adequately allege a claim for trespass to 10 chattels because “Plaintiff [did] not allege facts to indicate that Plaintiffs failed to authorize the 11 enablement of 2FA.” Id. at 6. Specifically, the Court concluded that the FAC “allege[d] that 2FA 12 is enabled when an Apple ID user voluntarily turn[ed] on 2FA, install[ed] a software update, or 13 create[d] a new Apple ID,” but that “[n]one of those means to enable 2FA permit[ted] Apple to 14 enable 2FA unilaterally and without Plaintiffs’ authorization.” Id. Plaintiff Brodsky did not 15 allege whether he read or reviewed the software update or “whether the message disclosed that the 16 update would enable 2FA.” Id. at 7. Additionally, the Court held that Plaintiffs had not alleged 17 that any trespass harmed Plaintiffs as required under binding California Supreme Court precedent. 18 Id. Rather, Plaintiffs only pleaded that “each login process [took] an additional estimated 2-5 19 more minutes with 2FA,” and such allegations were “plainly insufficient to allege the requisite 20 showing of harm.” Id. In situations where Plaintiffs argued that they “suffer[ed] longer 21 dispossessions,” the Court nonetheless concluded that Apple did not proximately cause Plaintiffs’ 22 dispossession from their Apple devices or services because the FAC “d[id] not allege that Apple 23 or 2FA led Plaintiffs to lose access to their trusted devices.” Id. at 8. Rather, the FAC simply 24 alleged that Plaintiffs lost access based on events “outside of [their] control.” Id. Accordingly, 25 the Court granted Apple’s motion to dismiss Plaintiffs’ trespass to chattels claim under California 26 law. Id. 27 Second, the Court dismissed Plaintiffs’ claim for violating the CIPA, again for two 1 reasons. The Court noted that “[t]he CIPA is an anti-wiretapping statute that is violated when a 2 person, without authorization, ‘reads, or attempts to read, or to learn the contents or meaning of 3 any message, report, or communication while the same is in transit or passing over any wire, line, 4 or cable.’” Id. at 9 (quoting Cal. Penal Code § 631(a)). The CIPA, however, “prohibit[s] only 5 third party access to ongoing communications,” and “the only communications that Plaintiffs 6 allege Apple ‘intercepted’ are Plaintiff’s communications to Apple.” Id. at 9-10 (quotation marks 7 omitted). Furthermore, the Court concluded that Plaintiffs “also failed to identify the contents of 8 any communication that Apple allegedly intercepted, as required to state a claim under the CIPA” 9 because Plaintiffs’ “login activities,” such as usernames and passwords, did not qualify as 10 “contents” under prevailing law. Id. at 10-11. As a result, the Court granted Apple’s motion to 11 dismiss Plaintiffs’ CIPA claim. 12 Third, the Court addressed Plaintiffs’ claims under the federal CFAA. Id. at 11-14. 13 Relying on binding Ninth Circuit precedent, the Court concluded that “the plain language of the 14 CFAA target[s] the unauthorized procurement or alteration of information not its misuse or 15 misappropriation,” and that under the CFAA, “Plaintiffs must also plead that Apple’s actions 16 caused loss of more than $5,000 during any one-year period.” Id. at 12 (quotation marks omitted). 17 On this basis, the Court dismissed Plaintiffs’ CFAA claims because Plaintiffs authorized 2FA 18 through voluntary software updates. Id. at 13. Insofar as Plaintiffs “attempt[ed] to allege that 19 Apple exceeded Plaintiffs’ authorization,” this argument also failed because Plaintiffs had not 20 alleged that they “revoked any consent for Apple’s servers to receive Plaintiffs’ login activities.” 21 Id. at 13. Importantly, the Court noted that “Plaintiffs also d[id] not explain how Apple’s access 22 to Plaintiffs’ ‘login activities’ via 2FA [was] at all different from Apple’s access to such login 23 activities when Plaintiffs employ a different Apple ID login method.” Id. Finally, the Court also 24 disposed of Plaintiffs’ CFAA claims because Plaintiffs failed to plead $5,000 in damages over a 25 one-year period. Id. at 14. Therefore, the Court granted Apple’s motion to dismiss Plaintiffs’ 26 CFAA claims. 27 Fourth, the Court dismissed Plaintiffs’ claims under the CCCL. Id. at 14-16. The Court 1 held that “the CCCL prohibits only access or disruptions to a computer system that are ‘without 2 permission,’” and that “a defendant acted without permission . . . [when] the offending software 3 was designed in such a way to render ineffective any barriers the Plaintiffs must wish to use to 4 prevent access to their information.” Id. at 15 (quotation marks omitted). Because Plaintiffs did 5 not offer any allegations about how Plaintiffs attempted to prevent 2FA’s access to their 6 information, Plaintiffs’ CCCL claims failed. Id. Additionally, Plaintiffs’ CCCL claims failed 7 because the FAC “merely parrot[ed] the language of the CCCL,” and such “boilerplate allegations 8 also provide[d] a reason to dismiss Plaintiffs’ CCCL claims.” Id. at 15-16. As a result, the Court 9 granted Apple’s motion to dismiss Plaintiffs’ CCCL claims. 10 Fifth, the Court analyzed Plaintiffs’ unjust enrichment claim under California law. Id. at 11 16-17. California law, however, “does not recognize a separate cause of action for unjust 12 enrichment.” Id. at 16 (citation omitted). Though “courts have [sometimes] construed purported 13 claims for unjust enrichment as quasi-contract claims seeking restitution,” “Plaintiffs’ FAC 14 include[d] no allegation that Apple is liable in quasi-contract.” Id. at 16-17. Therefore, the Court 15 granted Apple’s motion to dismiss Plaintiff’s unjust enrichment claims. 16 Sixth, in the alternative, the Court found that Plaintiffs’ claims under the CIPA, CFAA, 17 and CCCL were time-barred. Id. at 17-19. “The longest applicable statute of limitations [was] 18 three years,” but Plaintiffs only brought suit “approximately three and a half years after Plaintiff 19 Brodsky alleges that he enabled 2FA on his Apple devices.” Id. at 17. Additionally, the 20 continuous accrual doctrine, the continuing violation doctrine, and the delayed discovery rule did 21 not apply and thus did not save Plaintiffs’ CIPA, CFAA, and CCCL claims. Id. at 18-19. 22 Finally, as to Plaintiffs’ common law claims—namely the trespass to chattels and unjust 23 enrichment claims—the Court found that the FAC failed to satisfy Rule 8. Id. at 20. Specifically, 24 Plaintiffs had not alleged their states of residence or which state’s law applied to each of Plaintiffs’ 25 common law claims such that “Apple [could not] adequately defend itself, nor [could] the Court 26 assess the sufficiency of Plaintiffs’ claims.” Id. The Court directed Plaintiffs to “amend their 27 pleading to specify their states of residence and clarify under which state’s common law Plaintiffs 1 bring their trespass to chattels and unjust enrichment claims.” Id. The Court also noted that 2 “[f]ailure to cure the deficiencies identified herein or in Apple’s motion to dismiss will result in 3 dismissal with prejudice. Id. 4 On September 26, 2019, Plaintiffs filed the SAC. ECF No. 43. The SAC adds two new 5 Named Plaintiffs, William Richardson and John Kyslowsky, who are residents of Colorado and 6 Texas respectively. Id. ¶ 8. The SAC also alleges that Plaintiff Brodsky is a New York resident, 7 Plaintiff Tracey is a California resident, Plaintiff Bishop is an Ohio resident, and Plaintiff 8 Schwartz is a Pennsylvania resident. Id. Additionally, the SAC alleges that California law applies 9 to all of Plaintiffs’ claims based on a choice of law provision in Apple’s terms and use 10 agreements. Id. ¶ 15; see also id. ¶ 76 (“California’s substantive laws including common law 11 apply to every member of the Class, regardless of where in the United States the Class Member 12 resides based on Apple’s ‘Controlling Law’ provisions in its Terms and Conditions agreements for 13 all of its products and services.”). The SAC also alleges that Plaintiffs’ states of residence “have 14 the substantively same laws for common law claims at issue here, i.e., trespass of [sic] chattels and 15 unjust enrichment claims,” such that “applying California law for common law claims is 16 appropriate here because the differences of application will not be substantive.” Id. ¶ 77. 17 Additionally, the SAC now pleads that Plaintiffs pay for third-party apps in “monthly, 18 yearly, or one-time subscription[s].” Id. ¶ 21. Plaintiffs also assert that 2FA “intercepts access to 19 Third-Party Apps” and Apple services, id. ¶¶ 46, 51, just as Plaintiffs previously argued that 20 “Apple has ‘intercepted’ the user’s communication with the Apple service,” Order at 11; see id. 21 (“However, if a user cannot access an Apple service like FaceTime due to 2FA, as Plaintiffs 22 allege, the user cannot create any communication over FaceTime for Apple to ‘intercept.’”). The 23 SAC also adds a new allegation that “[b]y filing . . . this lawsuit, Plaintiffs hereby revoke any 24 authorization Apple may have to continue to operate 2FA on Apple Devices.” Id. ¶ 65. 25 Based on these allegations, the SAC realleges the same five causes of action as the FAC: 26 (1) trespass to chattels, id. ¶¶ 94-100; (2) violation of the California Invasion of Privacy Act 27 (“CIPA”), California Penal Code § 631, id. ¶¶ 101-05; (3) violation of the California Computer 1 Crime Law (“CCCL”), California Penal Code § 502, id. ¶¶ 106-18; (4) violation of the Computer 2 Fraud and Abuse Act (“CFAA”), 18 U.S.C. § 1030, id. ¶¶ 119-128; and (5) unjust enrichment, id. 3 ¶¶ 129-33. Plaintiffs again bring suit on behalf of the following putative class: 4 All persons or entities in the United States who own or owned an Apple Watch, iPhone, iPad, MacBook, or iMac or use Apple Services that have enabled two-factor 5 authentication (“2FA”), subsequently want to disable 2FA, and are not allowed to disable 2FA. 6 Id. ¶ 71. The class period began “when Apple introduced 2FA in 2015.” Id. ¶ 70. In the SAC, 7 Plaintiffs again seek to represent subclasses as in the FAC. Id. ¶¶ 72-73. The SAC, however, 8 includes a new subclass whereby Plaintiffs Richardson and Kyslowsky seek to represent an 9 analogous subclass of “senior persons in the United States.” Id. ¶ 74. 10 On October 22, 2019, Apple filed the instant motion to dismiss Plaintiff’s SAC. ECF No. 11 46 (“Mot.”). On November 5, 2019, Plaintiffs filed an opposition. ECF No. 47 (“Opp.”). On 12 November 19, 2019, Apple filed a reply. ECF No. 50 (“Reply”). 13 II. LEGAL STANDARD 14 A. Motion to Dismiss Under Federal Rule of Civil Procedure 12(b)(6) 15 Rule 8(a)(2) of the Federal Rules of Civil Procedure requires a complaint to include “a 16 short and plain statement of the claim showing that the pleader is entitled to relief.” A complaint 17 that fails to meet this standard may be dismissed pursuant to Federal Rule of Civil Procedure 18 12(b)(6). The United States Supreme Court has held that Rule 8(a) requires a plaintiff to plead 19 “enough facts to state a claim to relief that is plausible on its face.” Bell Atlantic Corp. v. 20 Twombly, 550 U.S. 544, 570 (2007). “A claim has facial plausibility when the plaintiff pleads 21 factual content that allows the court to draw the reasonable inference that the defendant is liable 22 for the misconduct alleged.” Ashcroft v. Iqbal, 556 U.S. 662, 678 (2009). “The plausibility 23 standard is not akin to a probability requirement, but it asks for more than a sheer possibility that a 24 defendant has acted unlawfully.” Id. (internal quotation marks omitted). For purposes of ruling 25 on a Rule 12(b)(6) motion, the Court “accept[s] factual allegations in the complaint as true and 26 construe[s] the pleadings in the light most favorable to the nonmoving party.” Manzarek v. St. 27 1 Paul Fire & Marine Ins. Co., 519 F.3d 1025, 1031 (9th Cir. 2008). The Court, however, need not 2 “assume the truth of legal conclusions merely because they are cast in the form of factual 3 allegations.” Fayer v. Vaughn, 649 F.3d 1061, 1064 (9th Cir. 2011) (per curiam) (internal 4 quotation marks omitted). Additionally, mere “conclusory allegations of law and unwarranted 5 inferences are insufficient to defeat a motion to dismiss.” Adams v. Johnson, 355 F.3d 1179, 1183 6 (9th Cir. 2004). 7 B. Leave to Amend 8 If the Court determines that a complaint should be dismissed, it must then decide whether 9 to grant leave to amend. Under Rule 15(a) of the Federal Rules of Civil Procedure, leave to 10 amend “shall be freely given when justice so requires,” bearing in mind “the underlying purpose 11 of Rule 15 to facilitate decisions on the merits, rather than on the pleadings or technicalities.” 12 Lopez v. Smith, 203 F.3d 1122, 1127 (9th Cir. 2000) (en banc) (alterations and internal quotation 13 marks omitted). When dismissing a complaint for failure to state a claim, “a district court should 14 grant leave to amend even if no request to amend the pleading was made, unless it determines that 15 the pleading could not possibly be cured by the allegation of other facts.” Id. at 1130 (internal 16 quotation marks omitted). Accordingly, leave to amend generally shall be denied only if allowing 17 amendment would unduly prejudice the opposing party, cause undue delay, or be futile, or if the 18 moving party has acted in bad faith. Leadsinger, Inc. v. BMG Music Publ’g, 512 F.3d 522, 532 19 (9th Cir. 2008). At the same time, a court is justified in denying leave to amend when a plaintiff 20 “repeated[ly] fail[s] to cure deficiencies by amendments previously allowed.” See Carvalho v. 21 Equifax Info. Servs., LLC, 629 F.3d 876, 892 (9th Cir. 2010). Indeed, a “district court’s discretion 22 to deny leave to amend is particularly broad where plaintiff has previously amended the 23 complaint.” Cafasso, U.S. ex rel. v. Gen. Dynamics C4 Sys., Inc., 637 F.3d 1047, 1058 (9th Cir. 24 2011) (quotation marks omitted). 25 III. DISCUSSION 26 Apple moves to dismiss each of Plaintiffs’ claims for failure to state a claim. Apple also 27 contends that certain claims are fail to satisfy Rule 8’s pleading standard or are barred by the 1 statute of limitations. The Court first addresses the sufficiency of each of Plaintiffs’ individual 2 claims before turning to Apple’s other arguments. 3 A. Claim for Trespass to Chattels 4 Plaintiffs allege that Apple committed trespass to chattels because Apple “interfered with 5 Plaintiffs and Class Members’ possessory interest of their one or more Apple devices by requiring 6 an extraneous login process through two-factor authentication that is imposed on Plaintiffs and 7 Class members without authorization or consent.” SAC ¶ 96. 8 As an initial matter, the Court notes that the SAC alleges that California law applies to all 9 of Plaintiffs’ claims based on a choice of law provision in Apple’s terms and use agreements. Id. 10 ¶ 15; see also id. ¶ 76 (“California’s substantive laws including common law apply to every 11 member of the Class, regardless of where in the United States the Class Member resides based on 12 Apple’s ‘Controlling Law’ provisions in its Terms and Conditions agreements for all of its 13 products and services.”). 14 For Plaintiffs’ common law claims—namely their claims for trespass to chattels and unjust 15 enrichment—Plaintiffs allege that they bring those claims under the common law of New York, 16 Ohio, Pennsylvania, Colorado, and Texas “[i]n the alternative.” Id. ¶¶ 95, 130. However, the 17 SAC also alleges that Plaintiffs’ states of residence “have the substantively same laws for common 18 law claims at issue here, i.e., trespass of [sic] chattels and unjust enrichment claims,” such that 19 “applying California law for common law claims is appropriate here because the differences of 20 application will not be substantive.” Id. ¶ 77. 21 Furthermore, in any event, Apple argues in its motion to dismiss that Plaintiffs’ common 22 law claims must be dismissed insofar as those claims rely on non-California law. See Mot. at 10 23 n.5, 24 n.7. Plaintiffs do not respond to Apple’s arguments, and as such, Plaintiffs have 24 abandoned their common law claims premised on non-California law. Moore v. Apple, Inc., 73 F. 25 Supp. 3d 1191, 1205 (N.D. Cal. 2014) (stating that a failure in an opposition to address arguments 26 raised in a motion to dismiss constitutes abandonment of the claim, which results in dismissal with 27 prejudice). Accordingly, the Court proceeds to analyze Plaintiffs’ common law claims under 1 California law. 2 Under California law, trespass to chattels “lies where an intentional interference with the 3 possession of personal property has proximately caused injury.” Intel Corp. v. Hamidi, 30 Cal. 4 4th 1342, 1350-51 (2003). To state a trespass to chattels claim, a plaintiff must plead that “(1) the 5 defendant intentionally and without authorization interfered with plaintiff’s possessory interest in 6 the computer system; and (2) defendant’s unauthorized use[] proximately caused damage.” In re 7 Facebook Internet Tracking Litig., 263 F. Supp. 3d 836, 842 (N.D. Cal. 2017) (quoting eBay, Inc. 8 v. Bidder’s Edge, Inc., 100 F. Supp. 2d 1058, 1069-70 (N.D. Cal. 2000)). 9 As with the previous motion to dismiss, Apple argues that (1) Apple did not enable 2FA 10 without Plaintiffs’ authorization; and (2) Plaintiffs have not alleged that Apple damaged Plaintiffs. 11 The Court addresses each argument in turn. 12 1. Plaintiffs Have Not Alleged that 2FA was Enabled Without Plaintiffs’ Authorization 13 First, Apple contends that Plaintiffs consented to 2FA, and thus, that any interference with 14 possession was authorized. Under Hamidi, a trespass only occurs where an interference is 15 “unauthorized.” 30 Cal. 4th at 1350. Plaintiffs make much of their new allegation that “[b]y 16 filing . . . this lawsuit, Plaintiffs hereby revoke any authorization Apple may have to continue to 17 operate 2FA on Apple Devices.” Id. ¶ 65. However, as the Court noted in its prior Order, courts 18 consistently hold that in the context of a software update and digital trespass, “[v]oluntary 19 installation runs counter to the notion that the alleged act was a trespass.” In re Apple & ATTM 20 Antitrust Litig., 2010 WL 3521965 (N.D. Cal. July 8, 2010), vacated in part sub nom. on other 21 grounds In re Apple & AT & TM Antitrust Litig., 826 F. Supp. 2d 1168 (N.D. Cal. 2011); see 22 Order at 6. Plaintiffs do not point to any case law or authority to the contrary. 23 As a result, what the Court is left with are the same allegations that were previously found 24 wanting in the Court’s prior Order. Here, Plaintiffs again do not allege facts that Plaintiffs failed 25 to authorize the enablement of 2FA. Rather, just like the FAC, the SAC identically alleges that 26 2FA is enabled in three instances: when an Apple ID user voluntarily turns on 2FA, installs a 27 1 software update, or creates a new Apple ID. SAC ¶ 35; FAC ¶ 16. As the Court previously 2 concluded, “[n]one of those means to enable 2FA permits Apple to enable 2FA unilaterally and 3 without Plaintiffs’ authorization.” Id. at 6. 4 Plaintiffs nevertheless persist and argue that they had “no notice of [the] 2FA feature 5 upgrade.” Opp. at 6. To be sure, as the Court noted in its prior Order, courts have recognized that 6 “consent to enter may be limited and that a trespass claim may lie when the scope of consent is 7 exceeded.” In re Apple Inc. Device Performance Litig. (“In re Apple”), 347 F. Supp. 3d 434, 455 8 (N.D. Cal. 2018). However, in In re Apple, the plaintiffs’ complaint quoted the message that 9 accompanied Apple’s software update and explained how the message failed to identify additional 10 effects of the software update. Id. The In re Apple plaintiffs did not consent to those additional 11 effects of the software update. 12 Here, as before, the SAC offers no information about Plaintiff Brodsky’s 2015 software 13 update that allegedly enabled 2FA on his phone, nor about whether Plaintiff Brodsky read or 14 reviewed the message that accompanied the update and whether the message disclosed that the 15 update would enable 2FA. Id. ¶ 37. Nor has Plaintiff Tracey alleged any facts related to his 16 alleged involuntary enablement of 2FA through voluntary software updates. Id. ¶ 38. Plaintiffs’ 17 bald assertions in the SAC that they did not consent to enabling 2FA is a legal conclusion not 18 entitled to the presumption of truth. See In re Gilead Scis. Sec. Litig., 536 F.3d 1049, 1055 (9th 19 Cir. 2008) (holding that a court need not accept as true “allegations that are merely conclusory”). 20 Indeed, none of the remaining Named Plaintiffs—Plaintiffs Bishop, Schwartz, Richardson, and 21 Kyslowsky—even specify how they enabled 2FA on their Apple devices. Id. ¶ 39. Accordingly, 22 Plaintiffs have not alleged that 2FA was enabled without Plaintiffs’ authorization. 23 2. Plaintiffs Have Not Alleged That Any Trespass Harmed Them 24 Second, Plaintiffs’ claim for trespass to chattels fails because Plaintiffs have again failed to 25 allege that Apple harmed Plaintiffs through 2FA. The California Supreme Court has explained 26 that, “while a harmless use or touching of personal property may be a technical trespass (see Rest. 27 2d of Torts, § 217), an interference (not amounting to dispossession) is not actionable under 1 modern California and broader American law without a showing of harm.” Intel Corp., 30 Cal. 2 4th at 1350-51. In the context of a trespass to a computer system, a plaintiff must allege “that the 3 purported trespass: (1) caused physical damage to the personal property, (2) impaired the 4 condition, quality, or value of the personal property, or (3) deprived plaintiff of the use of personal 5 property for a substantial time.” Fields v. Wise Media, LLC, 2013 WL 5340490, at *4 (N.D. Cal. 6 Sept. 24, 2013). 7 Plaintiffs argue that the SAC adequately alleges harm because Plaintiffs are “blocked 8 100%” for “ongoing short periods of time when 2FA is triggered” or “when not connected to the 9 internet” and because they are “lock[ed] out for days . . . when access to a trusted device to receive 10 2FA is lost.” Opp. at 8. However, as in the FAC, the SAC only alleges that 2FA takes “2-5 or 11 more minutes” than other login processes. SAC ¶ 42. 12 Plaintiffs’ allegations are insufficient to allege the requisite showing of harm. In In re 13 iPhone Application Litigation, this Court concluded that Apple programs that consumed the 14 devices’ memory and “shortened the[ir] battery life” were insufficient to state a claim. 844 F. 15 Supp. 2d 1040, 1069 (N.D. Cal. 2012). The allegations did not suggest that Apple’s trespass 16 “caused an interference with the intended functioning” of the devices. Id.; see also Hamidi, 30 17 Cal. 4th at 1347 (holding that trespass to chattels “does not encompass, and should not be 18 extended to encompass, an electronic communication that neither damages the recipient computer 19 system nor impairs its functioning”). 20 In the instant case, as the Court previously held, a delay of 2-5 minutes does not impair the 21 functioning of Plaintiffs’ Apple devices or Apple IDs. Order at 7; In re iPhone Application Litig., 22 844 F. Supp. 2d at 1069; Hamidi, 30 Cal. 4th at 1347. Plaintiffs do not allege that 2FA prevents 23 Plaintiffs from logging in after that delay, or that Plaintiffs’ devices are “damaged” by the delay. 24 See Engle v. Unified Life Ins. Co., Inc., 2014 WL 12508347, at *7 (S.D. Cal. Oct. 27, 2014) 25 (concluding that impairment of devices for the “duration of a phone call” did not qualify as harm 26 sufficient to state a trespass to chattels claim). 27 Furthermore, as recognized in the Court’s earlier Order, insofar as Plaintiffs contend that 1 Plaintiffs suffer longer dispossessions, any such allegations fail to adequately allege proximate 2 causation. Order at 8. Plaintiffs offer no new argument as to how their pleading adequately 3 alleges proximate causation. Instead, the SAC includes the same or nearly identical allegations as 4 the FAC, and Plaintiffs fail to allege that Apple or 2FA led Plaintiffs to lose access to their trusted 5 devices. Rather, Plaintiff Bishop lost access to his trusted device “based on an unforeseen 6 consequence outside of his control,” and Plaintiff Schwartz lost access to his trusted device “based 7 on events outside of his control.” SAC ¶¶ 48-49. As to Plaintiff Richardson, the SAC alleges that 8 he “was locked out of [his devices] when he could not recollect offhand his password on one of 9 the devices on or around April 2019.” Id. ¶ 50. In none of these instances did Apple or 2FA cause 10 Plaintiffs’ dispossession from their Apple devices and Apple services. See Thrifty-Tel, Inc. v. 11 Bezenek, 46 Cal. App. 4th 1559, 1566 (1996) (holding that a trespass to chattels occurs only where 12 the interference “has proximately caused injury”). Thus, Plaintiffs have not adequately alleged a 13 claim for trespass to chattels. 14 Therefore, the Court GRANTS Apple’s motion to dismiss Plaintiffs’ claim for trespass to 15 chattels. Plaintiffs failed to cure the same deficiencies the Court previously identified in its prior 16 Order, and the SAC offers no new facts to justify a different conclusion. Order at 5-8. As the 17 Court previously warned, “failure to cure the deficiencies identified herein or in Apple’s motion to 18 dismiss will result in dismissal with prejudice.” Id. at 20. Furthermore, courts are justified in 19 denying leave to amend when a plaintiff “repeated[ly] fail[s] to cure deficiencies by amendments 20 previously allowed.” Carvalho, 629 F.3d at 892. This is precisely the situation here, as the 21 Court’s prior Order put Plaintiffs on notice that Plaintiffs’ claim for trespass to chattels was 22 deficient for the same exact reasons as stated in this Order. Accordingly, the Court GRANTS 23 Apple’s motion to dismiss Plaintiffs’ claim for trespass to chattels with prejudice. 24 B. Claim for Violation of the California Information Privacy Act (“CIPA”) 25 The Court next addresses Plaintiffs’ CIPA claim. Plaintiffs allege that Apple violated the 26 CIPA because via 2FA, “Apple, by injecting itself in the process by requiring extra logging [sic] 27 steps, has acquired without authorization confidential electronic communication owned by 1 Plaintiffs and Class Members.” SAC ¶ 102. 2 The CIPA is an anti-wiretapping statute that is violated when a person, without 3 authorization, “reads, or attempts to read, or to learn the contents or meaning of any message, 4 report, or communication while the same is in transit or passing over any wire, line, or cable.” 5 Cal. Penal Code § 631(a). The CIPA was “passed to protect against the invasion of privacy,” 6 Matera v. Google Inc., 2016 WL 5339806, at *10 (N.D. Cal. Sept. 23, 2016), and requires the 7 “interception of an electronic communication,” Bradley v. Google, Inc., 2006 WL 3798134, at *5- 8 6 (N.D. Cal. Dec. 22, 2006). 9 In the instant case, Plaintiffs contend that 2FA violates Plaintiffs’ privacy rights under the 10 CIPA. Apple responds that (1) the CIPA prohibits only a third party’s interceptions and that 11 Apple is not a third party; and (2) Plaintiffs fail to allege the contents of any communications that 12 Apple intercepted. The Court addresses each argument in turn. 13 1. Plaintiffs Have Failed To Allege That Apple Was Not A Party To The Communications 14 Courts have interpreted the CIPA to prohibit only “third party access to ongoing 15 communications.” In re Facebook Internet Tracking Litig., 263 F. Supp. 3d 836, 845 (N.D. Cal. 16 2017). In In re Facebook, the district court held that Facebook could not “intercept” 17 communications to which Facebook was already a party. Id. at 844-45; see Thomasson v. GC 18 Servs. Ltd. P’Ship, 321 F. App’x 557, 559 (9th Cir. 2008) (explaining that California courts 19 interpret the anti-eavesdropping provision of the CIPA “to refer to a third party secretly listening 20 to a conversation between two other parties”). 21 Plaintiffs disagree and argue that CIPA liability attaches “irrespective of whether Apple is 22 a party.” Opp. at 11. Plaintiffs again rely on Ramos v. Capitol One, N.A., 2017 WL 3232488 23 (N.D. Cal. July 27, 2017), id. at 12, which the Court previously distinguished, Order at 10. In 24 Ramos, the district court concluded that a defendant could be liable for intercepting a 25 communication between two other parties on the defendant’s phone lines. 2017 WL 3232488, at 26 *9. Ramos is inapplicable to the instant case, in which Plaintiffs’ “login activities” are 27 1 communications that Plaintiffs send to Apple’s servers. 2 In the alternative, Plaintiffs contend that Apple is not a party to Plaintiffs’ 3 communications. /d. Plaintiffs, however, do not cite to any allegations in the SAC for this 4 argument. Instead, Plaintiffs simply point to two tables that appear only in their opposition brief. 5 Opp. at 11-12. Plaintiffs assert that these two tables allegedly demonstrate that Apple is not a 6 || party to Plaintiffs’ communications. The tables are reproduced below: 7 = = * Table 2: Steps showing Plaintiff access Google Drive Server with Apple 2FA Enabled 8 ee eee 9 User taps on the Google Apple Operating System 10S on the Apple Drive App on his Apple a Device intercepts and blocks that request 10 Device to access files User Request and tiggers 2FA 11

13 = Apple 2FA server on the intemet receives 14 user identification. device originating from. 6 time request made, third-party App Google Drive access requested 2 15 User receives login Apple 2FA Code to Trusted Device verification Es

16 User inputs code from > Apple 2FA server on the internet verifies trusted device code is accurate 2 17 User receives valid (ee Apple confirms user identification, Apple Google Drive Server Receives confirmation forwards user request to Third-party Server —_—_—_—_— > access request O User Request □ 18 User connects with Google Drive Server connects with Third-Party Server a User and shares content 19 20 Table 3: Steps showing Plaintiff access Google Drive Server with Apple 2FA Disabled User taps on the Google Apple Operatmg System 10S on the Apple Google Drive Server Receives 92 Drive App on his Apple serena Device passes through the request to the > access request Device to access files . intemet server User Request User Request 23 24 : 25 26 User connects with 4 Google Drive Server connects with Third-Party Server User and shares content 27 28 17 Case No. 19-CV-00712-LHK

1 Even if the Court considers Tables 2 and 3, which are not pleaded in the SAC, the Court 2 nonetheless concludes that Plaintiffs fail to allege that Apple was a third party to Plaintiffs’ 3 communications. Table 2 allegedly shows what happens when users attempt to access a third- 4 party app with 2FA enabled. Table 3 purportedly shows what happens when users attempt to 5 access a third-party app with 2FA disabled. However, regardless of whether 2FA is enabled or 6 disabled, users must still communicate with Apple, who “passes through the [user’s] request” to 7 the third-party app. Opp. at 12 (Table 3). Nothing in Tables 2 or 3 suggest that Apple is a third 8 party to communications. Instead, Tables 2 and 3 confirm that the only communications that 9 Plaintiffs argue Apple “intercepted” are Plaintiffs’ communications to Apple. As in In re 10 Facebook, Apple cannot intercept communications to which Apple is already a party. Thus, 11 Plaintiffs have not alleged a violation of the CIPA. 12 2. Plaintiffs Have Failed To Allege The Contents Of Any Intercepted Communication 13 Second, Plaintiffs have also failed to identify the contents of any communication that 14 Apple allegedly intercepted, as required to state a claim under the CIPA. See Cal. Penal Code 15 § 631(a) (prohibiting unauthorized access of the “contents” of any communication). “The analysis 16 for a violation of CIPA is the same as that under the federal Wiretap Act.” Cline v. Reetz-Laiolo, 17 329 F. Supp. 3d 1000, 1051 (N.D. Cal. 2018) (citation omitted). 18 Under the Wiretap Act, the term “contents” is defined as “any information concerning the 19 substance, purport, or meaning of that communication.” 18 U.S.C. § 2510. The Ninth Circuit has 20 held that “record information regarding the characteristics of the message that is generated in the 21 course of the communication” does not qualify as “contents.” In re Zynga Privacy Litig., 750 F.3d 22 1098, 1106 (9th Cir. 2014). Record information, the Ninth Circuit explained, “includes the name, 23 address, and subscriber number or identity of a subscriber or customer.” Id. (quotation marks 24 omitted). Accordingly, text messages qualify as contents under the Wiretap Act. In re Carrier 25 IQ, Inc., 78 F. Supp. 3d 1051, 1083 (N.D. Cal. 2015). However, user names, passwords, and 26 geographic location information are not contents. Id. at 1082, 1084. 27 1 In the instant case, Plaintiffs allege that Apple intercepted Plaintiffs’ “requests” to “access 2 to Third-Party Apps” or presumably Plaintiffs’ user names and passwords. SAC ¶¶ 51-52. 3 However, as the Ninth Circuit has concluded, a CIPA claim cannot be predicated on such record 4 information. In re Zynga Privacy Litig., 750 F.3d 1098 at 1106 (holding that “record information 5 regarding the characteristics of the message that is generated in the course of the communication” 6 does not qualify as “contents”). Indeed, In re Carrier IQ explicitly held that user names and 7 passwords do not constitute “contents” under the Wiretap Act. 78 F. Supp. 3d at 1082, 1084. 8 Additionally, in the Court’s prior Order, the Court rejected Plaintiffs’ argument that when 9 2FA prevents a user from accessing his Apple ID or services (such as when the user has lost his 10 trusted device), Apple has “intercepted” the user’s communication with the Apple service. Order 11 at 11. The Court explained that “if a user cannot access an Apple service like FaceTime due to 12 2FA, as Plaintiffs allege, the user cannot create any communication over FaceTime for Apple to 13 ‘intercept.’” Order at 11. Plaintiffs recycle that same argument in the SAC, but also allege that 14 “[o]n information and belief, Apple also uses its 2FA to intercept content, such as photos, music 15 and other files on Apple devices stored locally” and on third-party apps. SAC ¶ 51. This 16 allegation, however, contradicts the other allegations in the SAC. 17 First, the SAC’s allegation that Apple “uses its 2FA to intercept content, such as photos, 18 music and other files on Apple devices stored locally” is incorrect. The SAC alleges that 2FA is 19 simply a process for logging into an Apple ID, which is a separate process from accessing “files 20 on Apple devices stored locally.” Id. ¶¶ 3, 51. 21 Second, in any event, Plaintiffs clarify in their opposition brief that the “photos, music[,] 22 and other files . . . stored locally” are not in fact stored locally. Instead, Plaintiffs clarify that 23 “photos, music[,] and other files . . . stored locally” actually refers to content in Apple Services 24 and third-party apps. See Opp. at 12 (“SAC lists out and gives examples of different Apple 25 Services and Third-Party Apps used by Plaintiffs. Undisputedly, these Apps and Services include 26 Content. For example, Google drive includes files, photos with content hosted by third party, 27 Google Servers.” (citations omitted)). However, as the SAC alleges elsewhere, Apple’s 1 “intercepts access to Third-Party Apps” and Apple Services and “intercepts such requests and 2 communications by interjecting 2FA in the process . . . when opening a Third-Party App” or 3 Apple Services. Id. ¶¶ 51-52. As the Court previously held, “if a user cannot access a [service] 4 like FaceTime [or other third-party apps] due to 2FA, as Plaintiffs allege, the user cannot create 5 any communication . . . for Apple to ‘intercept.’” Order at 11. Therefore, just as in the FAC, the 6 SAC fails to allege the contents of any communication that Apple intercepted. 7 Accordingly, the Court GRANTS Apple’s motion to dismiss Plaintiffs’ CIPA claim. 8 Plaintiffs failed to cure the same deficiencies the Court previously identified in its prior Order, and 9 any new allegations fail to justify a different conclusion. Order at 9-11. As the Court previously 10 warned, “failure to cure the deficiencies identified herein or in Apple’s motion to dismiss will 11 result in dismissal with prejudice.” Id. at 20. Furthermore, courts are justified in denying leave to 12 amend when a plaintiff “repeated[ly] fail[s] to cure deficiencies by amendments previously 13 allowed.” Carvalho, 629 F.3d at 892. This is precisely the situation here, as the Court’s prior 14 Order put Plaintiffs on notice that Plaintiffs’ CIPA claim was deficient for the same exact reasons 15 as stated in this Order. Accordingly, the Court GRANTS Apple’s motion to dismiss Plaintiffs’ 16 CIPA claim with prejudice. 17 C. Claims for Violation of the Computer Fraud and Abuse Act (“CFAA”) 18 Next, the Court discusses Plaintiffs’ claims under the federal CFAA. Plaintiffs allege that 19 Apple “intentionally accessed through the 2FA feature Plaintiffs’ and Class Members’ computers” 20 and that Apple “knowingly caused the transmission of information, i.e. sending and receiving of 21 six-digit verification code [sic] on another device.” SAC ¶¶ 120-21. Plaintiffs bring claims under 22 two provisions of the CFAA, 18 U.S.C. § 1030(a)(2) and 18 U.S.C. § 1030(a)(5). Id. 23 The CFAA is an anti-hacking statute that creates liability where a defendant “intentionally 24 accesses a computer without authorization or exceeds authorized access,” and thus obtains 25 “information from any protected computer” or financial records. 18 U.S.C. § 1030(a)(2). The 26 CFAA also creates liability for “knowingly caus[ing] the transmission of a program, information, 27 code, or command, and as a result of such conduct, intentionally caus[ing] damage without 1 authorization, to a protected computer.” Id. § 1030(a)(5)(A)(i). Thus, “the plain language of the 2 CFAA target[s] the unauthorized procurement or alteration of information, not its misuse or 3 misappropriation.” United States v. Nosal, 676 F.3d 854, 863 (9th Cir. 2012) (en banc) (alteration 4 in original) (citation omitted). Based on the SAC’s allegations, the CFAA requires that Plaintiffs 5 also plead that Apple’s actions caused a loss of more than $5,000 during any one-year period. 6 LVRC Holdings LLC v. Brekka, 581 F.3d 1127, 1131-32 (9th Cir. 2009) (citing 18 U.S.C. 7 § 1030(a)). 8 Finally, the CFAA was enacted “primarily to address the growing problem of computer 9 hacking,” such that the en banc Ninth Circuit has favored an interpretation of the statute that 10 “maintains the CFAA’s focus on hacking rather than turning it into a sweeping Internet-policing 11 mandate.” Nosal, 676 F.3d at 858. Given that instruction, the Court previously noted that it was 12 “exceedingly skeptical of Plaintiffs’ theory that 2FA—an Apple login method that according to 13 Plaintiffs’ FAC ‘significantly improves the security of [a user’s] Apple ID’—can render Apple 14 liable under the CFAA, particularly given Plaintiffs’ vague and conclusory allegations.” Order at 15 12. 16 Plaintiffs’ amendments in the SAC have done little to dispel that skepticism. At base, 17 Plaintiffs’ SAC alleges a claim that 2FA slows down the login process, not a hacking claim. As 18 the Court previously noted, “[a]llowing CFAA claims to proceed on such conclusory, thin 19 allegations ‘would expand the CFAA too far.’” Order at 13-14 (quoting In re Apple, 347 F. Supp. 20 3d at 453)). As a result, the Court again agrees with Apple that Plaintiffs have failed to plead that 21 (1) Apple hacked into Plaintiffs’ devices without authorization; and (2) any Apple actions caused 22 $5,000 in damages in any given one-year period. The Court addresses each argument in turn. 23 1. Plaintiffs Have Not Alleged That Any Access Was Unauthorized 24 First, both CFAA provisions under which Plaintiffs bring their claims apply only where a 25 defendant accesses or transmits a program to a computer “without authorization” or by “exceeding 26 authorized access.” “‘[A]uthorization,’” however, in the CFAA context, “is most naturally read in 27 reference to the identity of the person accessing the computer or website, not how access occurs.” 1 hiQ Labs, Inc. v. LinkedIn Corp., 273 F. Supp. 3d 1099, 1113 (N.D. Cal. 2017), aff’d and 2 remanded, 938 F.3d 985 (9th Cir. 2019) (emphasis in original). Therefore, if a plaintiff authorizes 3 an individual to access the plaintiff’s computer, the plaintiff’s CFAA claim cannot be based 4 simply on the manner or means by which the individual accesses the computer. See id.; see also 5 Ticketmaster L.L.C. v. Prestige Entm’t, Inc., 306 F. Supp. 3d 1164, 1176-77 (C.D. Cal. 2018) 6 (dismissing CFAA and CCCL claims because Ticketmaster “never withdrew” authorization to 7 access its website where “Ticketmaster’s cease-and-desist letter only expressed its disapproval of 8 the method by which Defendants accessed the website”). In situations where a plaintiff clearly 9 revokes access to a party and not simply the means, manner, or method for such access, that party 10 may be liable under the CFAA. Facebook, Inc. v. Power Ventures, Inc., 844 F.3d 1058, 1068-69 11 (9th Cir. 2016) (affirming CFAA liability because “Facebook explicitly revoked authorization for 12 any access” (emphasis in original)). 13 Plaintiffs do not offer any response to this argument in their opposition brief. See Opp. at 14 13-14. As such, Plaintiffs have abandoned their CFAA claims. Moore, 73 F. Supp. 3d at 1205 15 (stating that a failure in an opposition to address arguments raised in a motion to dismiss 16 constitutes abandonment of the claim, which results in dismissal with prejudice). Even had 17 Plaintiffs responded, the SAC only purports to revoke Apple’s authorization for the method of 18 access, 2FA, but does not disclaim Apple’s access through other Apple ID login methods. SAC 19 ¶ 65; hiQ Labs, 273 F. Supp. 3d at 1113 (“‘[A]uthorization,’ . . . is most naturally read in reference 20 to the identity of the person accessing the computer or website, not how access occurs.”); 21 Ticketmaster, 306 F. Supp. 3d at 1176-77 (dismissing CFAA and CCCL claims because 22 Ticketmaster “never withdrew” authorization to access its website where “Ticketmaster’s cease- 23 and-desist letter only expressed its disapproval of the method by which Defendants accessed the 24 website”). Indeed, the Court previously recognized that Plaintiffs were simply attempting to 25 challenge Apple’s method of access to Plaintiffs’ login activities. Order at 13 (“Plaintiffs also do 26 not explain how Apple’s access to Plaintiffs’ ‘login activities’ via 2FA is at all different from 27 Apple’s access to such login activities when Plaintiffs employ a different Apple ID login 1 method.”); id. at 10 (“[O]ther Apple ID login methods presumably also require Plaintiffs to 2 communicate with Apple’s servers.”). Therefore, beyond Plaintiffs’ failure to respond to Apple’s 3 argument, the SAC only challenges how access occurs through 2FA and still permits Apple to 4 access Plaintiffs’ login activities through other means, which Plaintiffs authorized. Accordingly, 5 Plaintiffs’ CFAA claims fail. 6 2. Plaintiffs Have Also Failed to Plead $5,000 in Damages 7 Second, Plaintiffs have again failed to plead the requisite damages under the CFAA. 8 Plaintiffs contend that the SAC adequately alleges damages to satisfy the CFAA’s $5,000 9 requirement by “list[ing] the number of [A]pple devices owned, [A]pple services subscriptions[,] 10 and access to third-party apps that are constructively disp[ossessed].” Opp. at 14. However, 11 Plaintiffs cannot rely on these allegations regarding the full cost of their devices and services 12 subscriptions because the gravamen of the SAC is that 2FA adds only an “additional estimated 2-5 13 or more minutes” to log in with Apple ID. SAC ¶ 42. Insofar as the SAC alleges that some 14 Plaintiffs could not access Apple services or third-party apps for longer periods of time, Plaintiffs 15 acknowledge that they either forgot their passwords or that they were locked out based on “events 16 outside [their] control,” which cannot be attributed to Apple. Id. ¶¶ 48-50. Without more, the 17 SAC does not adequately plead how Plaintiffs’ damages based on their devices, Apple services 18 subscriptions, or third-party apps for 2-5 minutes satisfy the CFAA’s $5,000 loss during a one- 19 year period requirement. 20 Plaintiffs’ only remaining damages allegation is that “Apple has collected personal 21 information that has economic value to the Plaintiffs and Class Members, the unauthorized 22 collection of which resulted in the deprivation or diminution of such economic value, causing 23 Plaintiffs and Class Members to sustain . . . economic loss with an aggregated value of at least 24 $5,000 during a one-year period.” Id. ¶ 126. Plaintiffs, however, do not rely on this allegation in 25 their opposition, and for good reason. See Opp. at 13-14. 26 Recently, the Ninth Circuit decided a CFAA case where Plaintiffs’ “theory of loss [was] 27 that he and his fellow class members were denied the profits they might have received from 1 commodifying the personal information that [the defendant] allegedly obtained through unlawful 2 means.” Andrews v. Sirius XM Radio Inc., 932 F.3d 1253, 1262 (9th Cir. 2019). The plaintiff in 3 Andrews argued that because the defendant “allegedly stole the personal information without 4 compensating [him], he lost the value of that information and the opportunity to sell it.” Id. The 5 Ninth Circuit rejected Plaintiff’s theory of loss because the CFAA’s “narrow conception of ‘loss’ 6 . . . does not include a provision that aligns with [plaintiff’s] theory.” Id. Andrews therefore 7 forecloses Plaintiffs’ theory that Apple caused Plaintiffs’ and Class Members damages in the form 8 of lost economic value in their personal information. As a result, Plaintiffs have failed to plead 9 $5,000 in damages. 10 Accordingly, the Court GRANTS Apple’s motion to dismiss Plaintiffs’ CFAA claims. 11 Plaintiffs failed to cure the same or similar deficiencies the Court previously identified in its prior 12 Order, and the SAC offers no new facts to justify a different conclusion. Order at 11-14. As the 13 Court previously warned, “failure to cure the deficiencies identified herein or in Apple’s motion to 14 dismiss will result in dismissal with prejudice.” Id. at 20. Furthermore, courts are justified in 15 denying leave to amend when a plaintiff “repeated[ly] fail[s] to cure deficiencies by amendments 16 previously allowed.” Carvalho, 629 F.3d at 892. This is precisely the situation here, as the 17 Court’s prior Order put Plaintiffs on notice that Plaintiffs’ CFAA claims were deficient for the 18 same or similar reasons as stated in this Order. Accordingly, the Court GRANTS Apple’s motion 19 to dismiss Plaintiffs’ CFAA claims with prejudice. 20 D. Claims for Violation of the California Computer Crime Law (“CCCL”) 21 Next, the Court discusses Plaintiffs’ claims under the CCCL, Cal. Penal Code § 502. The 22 CCCL is also sometimes referred to as the California Comprehensive Computer Data Access and 23 Fraud Act and abbreviated as “CDAFA.” Facebook, Inc. v. Grunin, 77 F. Supp. 3d 965, 971 24 (N.D. Cal. 2015); Oracle USA, Inc. v. Rimini St., Inc., 879 F.3d 948, 952 (9th Cir.), cert. granted, 25 139 S. Ct. 52 (2018), and rev’d in part, 139 S. Ct. 873 (2019). 26 Plaintiffs bring claims under five provisions of the CCCL, Cal. Penal Code §§ 502(c)(1), 27 (3)-(5), and (7). SAC ¶¶ 109-13. For each claim, Plaintiff alleges that Apple “knowingly and 1 without permission” accessed, altered, or otherwise disrupted Plaintiffs’ Apple devices. Id. Case 2 law suggests that Plaintiffs’ CCCL claims rise or fall with Plaintiffs’ CFAA claims because “the 3 necessary elements of Section 502 do not differ materially from the necessary elements of the 4 CFAA,” except in terms of damages. Multiven, Inc. v. Cisco Sys., Inc., 725 F. Supp. 2d 887, 895 5 (N.D. Cal. 2010). Unlike the CFAA, the CCCL does not impose a minimum of $5,000 in 6 damages. Cline, 329 F. Supp. 3d at 1052. 7 Like the CFAA, the CCCL prohibits only access or disruptions to a computer system that 8 are “without permission.” This means that, like a CFAA claim, a CCCL claim cannot be based 9 simply on the method by which a defendant accesses a computer if the defendant otherwise has 10 authorization to access the computer. As the Ninth Circuit held, “taking data using a method 11 prohibited by the applicable terms of use, when the taking itself generally is permitted, does not 12 violate the [CCCL].” Oracle USA, 879 F.3d at 962 (emphasis in original). In Oracle USA, the 13 Ninth Circuit noted that “Oracle obviously disapproved of the method . . . by which Rimini took 14 Oracle’s proprietary information. But the key to the [CCCL] is whether Rimini was authorized in 15 the first instance to take and use the information that it downloaded.” Id.; see also Ticketmaster 16 L.L.C. v. Prestige Entm’t, Inc., 306 F. Supp. 3d 1164, 1176-77 (C.D. Cal. 2018) (dismissing 17 CFAA and CCCL claims because Ticketmaster “never withdrew” authorization to access its 18 website where “Ticketmaster’s cease-and-desist letter only expressed its disapproval of the 19 method by which Defendants accessed the website”). As the Court noted previously, see supra 20 Part III.C.1, the SAC only purports to revoke Apple’s authorization for the method of access 21 through 2FA without disclaiming Apple’s access to Plaintiffs’ login activities through other 22 means. SAC ¶ 65. In addition, the Court’s prior Order also explained that Plaintiffs’ CCCL 23 claims failed in part because “Plaintiffs offer no allegations about . . . how 2FA offers Apple 24 access to Plaintiffs’ information that is somehow different from Apple’s access through other 25 Apple ID login methods.” Order at 15. As a result, because the SAC only challenges the login 26 method of 2FA without alleging that Apple is otherwise accessing Plaintiffs’ login activities 27 without authorization, Plaintiffs’ CCCL claims fail. 1 Furthermore, Plaintiffs’ CCCL claims fail for an additional reason. As the Court 2 previously held, “Plaintiffs’ specific CCCL claims all merely parrot the language of the CCCL.” 3 Order at 15. As before, the SAC includes the same exact allegations that the Court previously 4 found insufficient in the FAC. Plaintiffs allege that “Apple knowingly and without permission has 5 used and caused to be used Plaintiffs’ and Class Members’ Apple Services and Third-Party Apps 6 configured on their Apple devices.” SAC ¶ 110; FAC ¶ 61. This allegation mirrors the language 7 of California Penal Code § 502(c)(5), which renders liable a defendant who “[k]nowingly and 8 without permission uses or causes to be used computer services.” Cal. Penal Code § 502(c)(5). 9 Plaintiffs have simply inserted their Apple services and third-party apps in place of “computer 10 services.” For example, the SAC includes no factual allegations about how it is even possible for 11 Apple to “use” a third-party app on Plaintiffs’ devices—particularly if Plaintiffs’ are “locked” out 12 of their devices. These boilerplate allegations also provide a reason to dismiss Plaintiffs’ CCCL 13 claims. See Gonzales v. Uber Techs., Inc., 305 F. Supp. 3d 1078, 1090 (N.D. Cal. 2018) (granting 14 a motion to dismiss where plaintiffs made only “boilerplate allegations” of CCCL violations). 15 Accordingly, the Court GRANTS Apple’s motion to dismiss Plaintiffs’ CCCL claims. 16 Plaintiffs failed to cure the same or similar deficiencies the Court previously identified in its prior 17 Order, and the SAC offers no new facts to justify a different conclusion. Order at 14-16. As the 18 Court previously warned, “failure to cure the deficiencies identified herein or in Apple’s motion to 19 dismiss will result in dismissal with prejudice.” Id. at 20. Furthermore, courts are justified in 20 denying leave to amend when a plaintiff “repeated[ly] fail[s] to cure deficiencies by amendments 21 previously allowed.” Carvalho, 629 F.3d at 892. This is precisely the situation here, as the 22 Court’s prior Order put Plaintiffs on notice that Plaintiffs’ CCCL claims were deficient for the 23 same or similar reasons as stated in this Order. Accordingly, the Court GRANTS Apple’s motion 24 to dismiss Plaintiffs’ CCCL claims with prejudice. 25 E. Claim for Unjust Enrichment 26 Plaintiffs’ fifth and final claim is for unjust enrichment. SAC ¶¶ 129-33. However, 27 California does not recognize a separate cause of action for unjust enrichment. See Hill v. Roll 1 Int’l Corp., 195 Cal. App. 4th 1295, 1307 (2011) (“Unjust enrichment is not a cause of action, just 2 a restitution claim.”). As a result, courts have consistently dismissed stand-alone claims for unjust 3 enrichment. See, e.g., Low v. LinkedIn Corp., 900 F. Supp. 2d 1010, 1031 (N.D. Cal. 2012); 4 Robinson v. HSBC Bank USA, 732 F. Supp. 2d 976, 987 (N.D. Cal. 2010). 5 In some circumstances, courts have construed purported claims for unjust enrichment as 6 quasi-contract claims seeking restitution. Astiana v. Hain Celestial Grp., Inc., 783 F.3d 753, 762 7 (9th Cir. 2015); see also Swafford v. Int’l Bus. Mach. Corp., 383 F. Supp. 3d 916, 931-32 (N.D. 8 Cal. 2019) (construing unjust enrichment cause of action as a quasi-contract claim). A quasi- 9 contract cause of action seeks “to prevent unjust enrichment in the absence of a true contract or 10 where the contract was obtained by fraud.” Fowler v. Wells Fargo Bank, N.A., 2017 WL 11 3977385, at *5 (N.D. Cal. Sept. 11, 2017) (citing McBride v. Boughton, 123 Cal. App. 4th 379, 12 388 (2004)). However, “an action based on an implied-in-fact or quasi-contract cannot lie where 13 there exists between the parties a valid express contract covering the same subject matter.” Tsai v. 14 Wang, 2017 WL 2587929, at *7 (N.D. Cal. June 14, 2017) (quoting Rutherford Holdings, LLC v. 15 Plaza Del Rey, 223 Cal. App. 4th 221, 231 (2014)); see also Klein v. Chevron U.S.A., Inc., 202 16 Cal. App. 4th 1342, 1388 (2012) (“A plaintiff may not . . . pursue or recover on a quasi-contract if 17 the parties have an enforceable agreement regarding a particular subject matter.”). 18 Plaintiffs now contend that they adequately plead a quasi-contract claim seeking restitution 19 for unjust enrichment. Opp. at 15. They are mistaken. Courts have repeatedly held that “a 20 plaintiff may not plead the existence of an enforceable contract and simultaneously maintain a 21 quasi-contract claim unless the plaintiff also pleads facts suggesting that the contract may be 22 unenforceable or invalid.” Tsai, 2017 WL 2587929, at *7; Adtrader, Inc. v. Google LLC, 2018 23 WL 3428525, at * 11 (N.D. Cal. July 13, 2018) (“[T]o assert such a claim [for unjust enrichment], 24 Plaintiffs must allege that the parties do not have an enforceable contract pertaining to Google’s 25 advertisement services.”); Deras v. Volkswagen Grp. of Am., Inc., 2018 WL 2267448, at *3 (N.D. 26 Cal. May 17, 2018) (“[A] quasi-contract action for unjust enrichment does not lie where express 27 binding agreements exist and define the parties’ rights.” (quoting Gerstle v. Am. Honda Motor 1 Co., 2017 WL 2797810, at *14 (N.D. Cal. June 28, 2017))). 2 Here, the SAC alleges that “Plaintiffs have a contract with Apple pursuant to the Terms of 3 Use of Apple Devices and Services that is breached by Apple’s interference as alleged,” SAC 4 ¶ 131, but the SAC does not plead any allegations suggesting that this contract is unenforceable or 5 invalid. Plaintiffs, however, contend that they are entitled to plead alternative or inconsistent 6 theories of recovery under Federal Rule of Civil Procedure 8(d)(2). Opp. at 15. 7 To be sure, Rule 8 allows a party to set out two or more claims hypothetically and 8 regardless of consistency. Fed. R. Civ. P. 8(e)(2)-(3). However, “[e]ven though [Rule 8] of the 9 Federal Rules of Civil Procedure allows a party to state multiple, even inconsistent claims, it does 10 not alter a substantive right between the parties and accordingly does not allow a plaintiff invoking 11 state law to an unjust enrichment claim while also alleging an express contract.” Deras, 2018 WL 12 2267448, at *3 (quoting Gerlinger v. Amazon.com, Inc., 311 F. Supp. 2d 838, 856 (N.D. Cal. 13 2004)). Indeed, “[a] plaintiff may assert inconsistent theories of recovery at the pleading stage, 14 including inconsistent claims alleging both the existence and the absence of an enforceable 15 contract. However, a plaintiff may not plead the existence of an enforceable contract and 16 simultaneously maintain a quasi-contract claim unless the plaintiff also pleads facts suggesting 17 that the contract may be unenforceable or invalid.” Tsai, 2017 WL 2587929, at *7 (citations 18 omitted). As a result, because Plaintiffs fail to allege that their contract with Apple is 19 unenforceable or invalid, the SAC fails to state a quasi-contract claim for unjust enrichment. 20 Accordingly, the Court GRANTS Apple’s motion to dismiss Plaintiffs’ unjust enrichment 21 claim. Plaintiffs failed to cure similar deficiencies the Court previously identified in its prior 22 Order, and the SAC offers no new facts to justify a different conclusion. Order at 16-17. As the 23 Court previously warned, “failure to cure the deficiencies identified herein or in Apple’s motion to 24 dismiss will result in dismissal with prejudice.” Id. at 20. Furthermore, courts are justified in 25 denying leave to amend when a plaintiff “repeated[ly] fail[s] to cure deficiencies by amendments 26 previously allowed.” Carvalho, 629 F.3d at 892. This is precisely the situation here, as the 27 Court’s prior Order put Plaintiffs on notice that Plaintiffs’ unjust enrichment claim was deficient 1 for similar reasons as stated in this Order. Accordingly, the Court GRANTS Apple’s motion to 2 dismiss Plaintiffs’ unjust enrichment claim with prejudice. 3 F. Rule 8 and Statutes of Limitations 4 Finally, the Court addresses Apple’s Rule 8 and statute of limitations argument. Apple 5 notes that “[n]otwithstanding the opportunity to amend their Complaint, the SAC is silent as to 6 when the Plaintiffs [Bishop, Schwartz, Richardson, and Kyslowsky] first enabled 2FA.” Mot. at 7 8, n.4. Additionally, Apple contends that Plaintiff Brodsky’s CIPA, CFAA, and CCCL claims are 8 time-barred and that Plaintiff Tracey’s CIPA claim is time-barred. Mot. at 8-9. 9 Plaintiff Brodsky alleges that he enabled 2FA on his Apple devices in September 2015. 10 SAC ¶ 37. Plaintiff Tracey now alleges that he enabled 2FA on his Apple devices in September 11 2017. Id. ¶ 38. Plaintiff Brodsky did not file the instant putative class action until February 8, 12 2019, approximately three and a half years after Plaintiff Brodsky alleges that he enabled 2FA on 13 his Apple devices and more than sixteen months after Plaintiff Tracey alleges that he enabled 2FA 14 on his Apple devices. ECF No. 1. As before, the remaining Named Plaintiffs—Plaintiffs Bishop, 15 Schwartz, Richardson, and Kyslowsky—do not allege when 2FA was enabled on their devices. 16 SAC ¶ 39; see Order at 17 (“However, in line with the overall vagueness of Plaintiffs’ FAC, [some 17 Named] Plaintiffs . . . do not allege when 2FA was enabled on their Apple devices.”). 18 The longest applicable statute of limitations is three years. Under the CIPA, the applicable 19 statute of limitations is one year. Ion Equip. Corp. v. Nelson, 110 Cal. App. 3d 868, 880 (1980) 20 (“The statute of limitations in which to commence an action for invasion of privacy is one year.”). 21 Under the CFAA, the statute of limitations is two years from “the date of the act complained of or 22 the date of the discovery of the damage.” 18 U.S.C. § 1030(g). Under the CCCL, the statute of 23 limitations is three years. Cal. Penal Code § 502(e)(5). The Court first addresses Rule 8’s 24 pleading standard as to Plaintiffs Bishop, Schwartz, Richardson, and Kyslowsky before turning to 25 the statutes of limitations argument as to Plaintiffs Brodsky and Tracey. 26 1. Plaintiffs Bishop, Schwartz, Richardson, and Kyslowsky Fail to Satisfy Rule 8 For Their CIPA, CFAA, and CCCL Claims 27 1 At the outset, the Court acknowledges that Apple has the burden of proof to support its 2 statute of limitations defenses as to Plaintiffs Bishop, Schwartz, Richardson, and Kyslowsky. 3 Opp. at 5. However, the issue with the SAC with regard to Plaintiffs Bishop, Schwartz, 4 Richardson, and Kyslowsky is not a statute of limitations problem, but rather, a Rule 8 problem. 5 Courts often dismiss claims under Rule 8 when plaintiffs fail to allege approximately when 6 the actionable misconduct occurred. See Mir v. City of Torrance, 2018 WL 6133712, at *1 (C.D. 7 Cal. Oct. 17, 2018) (“Although twice directed to do so by the Court, Plaintiff has not attributed 8 most of the alleged acts to any Defendant nor alleged when most of them occurred, leaving the 9 Court and Defendants to attempt to parse out who is accused of doing what and when. This is 10 improper.” (citations omitted)); Vasconcellos v. Sara Lee Bakery, 2013 WL 4014520, at *2 (N.D. 11 Cal. Aug. 5, 2013) (concluding plaintiffs’ claims were “insufficiently pled” in part because “[t]he 12 complaint d[id] not allege when plaintiff worked for defendants, when plaintiff became injured or 13 engaged in protected activity, or when the alleged misconduct occurred”); O’Donnell v. U.S. 14 Bancorp Equip. Fin., Inc., 2010 WL 2198203, at *3 (N.D. Cal. May 28, 2010) (“However, the 15 Court finds that O’Donnell has nonetheless failed to satisfy the pleading requirements of Federal 16 Rule of Civil Procedure 8 because she has not alleged any dates in her complaint. See, e.g., 17 Swierkiewicz, 534 U.S. at 514 (finding complaint to be sufficient in part because it “provided 18 relevant dates”). Without any reference to when the alleged misconduct occurred, O’Donnell's 19 allegations fail to state a plausible claim for relief.”). 20 This is especially true here because Plaintiffs Bishop, Schwartz, Richardson, and 21 Kyslowsky do not allege when 2FA was enabled on their devices, and Apple has raised the non- 22 frivolous possibility of multiple statute of limitations defenses. The Court notes that a failure to 23 plead when any alleged misconduct occurred will not necessarily be fatal under Rule 8. However, 24 where, as here, an applicable statute of limitations defense has been raised and is non-frivolous, 25 Plaintiffs’ repeated failure to plead the approximate date of alleged misconduct fails to satisfy 26 Rule 8’s requirement to “contain sufficient allegations of underlying facts to give fair notice and to 27 enable the opposing party to defend itself effectively.” Starr v. Baca, 652 F.3d 1202, 1216 (9th 1 Cir. 2011); see also Calip v. M.E.I.C., 2015 WL 5996365, at *6 (N.D. Cal. Oct. 15, 2015) (“Nor 2 does Plaintiff state when she was in the hospital and when her child passed away, without which 3 the Court cannot determine whether Plaintiff brought her claims within the applicable statute of 4 limitations period.”). Indeed, the Court previously cautioned Plaintiffs that the FAC was vague as 5 to multiple Plaintiffs’ allegations regarding when 2FA was enabled on their Apple devices. Order 6 at 17. Nonetheless, Plaintiffs largely failed to cure those same defects in the SAC. 7 As a result, because the SAC does not plead when 2FA was enabled for Plaintiffs Bishop, 8 Schwartz, Richardson, and Kyslowsky and therefore fails to satisfy Rule 8’s pleading standard, the 9 Court dismisses Plaintiffs Bishop’s, Schwartz’s, Richardson’s, and Kyslowsky’s CIPA, CFAA, 10 and CCCL claims. These Plaintiffs failed to cure similar deficiencies the Court previously 11 identified in its prior Order, and the SAC offers no new facts to justify a different conclusion. 12 Order at 17-20. As the Court previously warned, “failure to cure the deficiencies identified herein 13 or in Apple’s motion to dismiss will result in dismissal with prejudice.” Id. at 20. Furthermore, 14 courts are justified in denying leave to amend when a plaintiff “repeated[ly] fail[s] to cure 15 deficiencies by amendments previously allowed.” Carvalho, 629 F.3d at 892. This is precisely 16 the situation here, as the Court’s prior Order put Plaintiffs on notice that Plaintiffs Bishop’s, 17 Schwartz’s, Richardson’s, and Kyslowsky’s CIPA, CFAA, and CCCL claims were deficient for 18 similar reasons as stated in this Order. Accordingly, the Court dismisses these claims with 19 prejudice. 20 2. The Statute of Limitations Bars Plaintiff Brodsky’s CIPA, CFAA, and CCCL Claims and Plaintiff Tracey’s CIPA Claim 21 As noted previously, the CIPA’s statute of limitations is one year, the CFAA’s statute of 22 limitations is two years, and the CCCL’s statute of limitations is three years. Therefore, because 23 Plaintiff Brodsky enabled 2FA in September 2015, the statute of limitations ran for Plaintiff 24 Brodsky’s CIPA claim in September 2016, his CFAA claims in September 2017, and his CCCL 25 claims in September 2018. Thus, Plaintiff Brodsky’s CIPA, CFAA, and CCCL claims are time- 26 barred. Similarly, because Plaintiff Tracey enabled 2FA in September 2017, the statute of 27 1 limitations ran for Plaintiff Tracey’s CIPA claim in September 2018 such that Plaintiff Tracey’s 2 CIPA claim is also time-barred. 3 Acknowledging this, Plaintiffs contend that Plaintiff Brodsky’s CIPA, CFAA, and CCCL 4 claims and Plaintiff Tracey’s CIPA claim are nonetheless timely pursuant to the continuous 5 accrual doctrine, the continuing violation doctrine, and the delayed discovery rule. Opp. at 4-5. 6 However, none of these doctrines apply to toll the relevant statutes of limitations. 7 a. The Continuous Accrual Doctrine Does Not Apply 8 Under California law, the continuous accrual doctrine recognizes that “a series of wrongs 9 or injuries may be viewed as each triggering its own limitations period, such that a suit for relief 10 may be partially time-barred as to older events . . . but timely as to those within the applicable 11 limitations period.” Wolf v. Travolta, 167 F. Supp. 3d 1077, 1104 (C.D. Cal. 2016) (quoting 12 Aryeh v. Canon Bus. Solutions, Inc., 55 Cal. 4th 1185, 1192 (2013)). “Generally speaking, 13 continuous accrual applies whenever there is a continuing or recurring obligation: When an 14 obligation or liability arises on a recurring basis, a cause of action accrues each time a wrongful 15 act occurs, triggering a new limitations period.” Aryeh, 55 Cal. 4th at 1199 (quotation marks 16 omitted). In Aryeh v. Canon Business Solutions, Inc., the question before the California Supreme 17 Court was “when a UCL claim accrues.” Id. at 1192. The California Supreme Court found that 18 the continuous accrual doctrine can apply to UCL claims when the claims involved unlawful 19 charges in monthly bills, but also explained that “[t]o determine whether the continuous accrual 20 doctrine applies here,” courts “look not to the claim’s label as a UCL claim but to the nature of the 21 obligation allegedly breached.” Aryeh, 55 Cal. 4th at 1200. 22 California courts have largely confined the application of the continuing accrual theory to 23 “a limited category of cases, including installment contracts, leases with periodic rental payments, 24 and other types of periodic contracts that involve no fixed or total payment amount.” Lamont v. 25 Time Warner, Inc., 2012 WL 6146681, at *5 (C.D. Cal. Dec. 11, 2012). This court has repeatedly 26 noted that when an alleged duty “bears little relation to the monthly payments or monthly bills that 27 California courts have found to be periodic, recurring obligations,” applying the continuous 1 accrual doctrine is unwarranted. See Garrison v. Oracle Corp., 159 F. Supp. 3d 1044, 1083-84 2 (N.D. Cal. 2016); see also State ex rel. Metz v. CCC Info. Servs., Inc., 149 Cal. App. 4th 402, 418 3 (2007) (holding that the continuous accrual doctrine does not apply where “[the plaintiff’s] action 4 does not involve a recurring obligation or any such period payment obligations”); Tsemetzin v. 5 Coast Fed’l Sav. & Loan Ass’n, 57 Cal. App. 4th 1334, 1344 (1997) (applying the continuous 6 accrual doctrine to a dispute over monthly rent payments); Armstrong Petroleum Corp. v. Tri- 7 Valley Oil & Gas Co., 116 Cal. App. 4th 1375, 1388-89 (2004) (applying the continuous accrual 8 doctrine to a dispute over monthly lease payments). Indeed, a “continuing obligation to avoid 9 anticompetitive behavior is not a periodic, recurring obligation such as a monthly payment or 10 monthly bill, and as such, the continuous accrual doctrine does not apply.” Ryan v. Microsoft 11 Corp., 147 F. Supp. 3d 868, 896 (N.D. Cal. 2015). 12 Here, Plaintiffs attempt to conform the SAC to the Court’s prior Order by alleging that 13 Plaintiffs made periodic payments for Apple Services and third-party apps. Plaintiffs, however, 14 do not argue that Apple breached a continuing duty by unlawfully charging them for payments for 15 their Apple Services or third-party apps. Order at 18 (“The continuous accrual doctrine applies 16 where the defendant owes the plaintiff a continuing duty ‘susceptible to recurring breaches.’” 17 (quoting Aryeh, 55 Cal. 4th at 1200)). Rather, the gravamen of the SAC is that Apple unlawfully 18 upgraded Plaintiffs’ Apple devices to 2FA, which occurs at a discrete point in time. SAC ¶¶ 1-4, 19 37-38. Therefore, the SAC’s description of the alleged duty that Apple owed and breached is best 20 characterized as an obligation not to unlawfully force Plaintiffs to use 2FA. But just as this Court 21 previously concluded that a “continuing obligation to avoid anticompetitive behavior is not a 22 periodic, recurring obligation such as a monthly payment or monthly bill,” Apple’s “continuing 23 obligation” to avoid forcing Plaintiffs to use 2FA is also not a periodic, recurring obligation. See 24 Ryan, 147 F. Supp. 3d at 896; see also Factory Direct Wholesale, LLC v. iTouchless Housewares 25 & Prod., Inc., 411 F. Supp. 3d 905, 918 (N.D. Cal. 2019) (“Defendant’s continuing obligation to 26 avoid illegal behavior that violates the UCL is also not a periodic, recurring obligation.”). “[A]s 27 such, the continuous accrual doctrine does not apply.” Ryan, 147 F. Supp. 3d at 896. b. The Continuing Violation Doctrine Does Not Apply 1 Plaintiffs next argue that the continuing violation doctrine applies and thus tolls the 2 relevant statutes of limitations. Unlike the continuous accrual doctrine, the continuing violation 3 doctrine “renders an entire course of conduct actionable,” including wrongful acts that would 4 otherwise be untimely. Aryeh, 5 Cal. 4th at 1199. The continuing violation doctrine applies when 5 “a wrongful course of conduct [becomes] apparent only through the accumulation of a series of 6 harms” but not when a plaintiff experiences “a series of discrete, independently actionable alleged 7 wrongs.” Id. at 1198. The complaint must feature “[a]llegations of a pattern of reasonably 8 frequent and similar acts.” Id. 9 The Court previously concluded that the continuing violation doctrine did not save 10 Plaintiffs’ claims because “the continuing violation doctrine applies only where ‘a wrongful 11 course of conduct [becomes] apparent only through the accumulation of a series of harms.’” 12 Order at 19 (quoting Aryeh, 55 Cal. 4th at 1198). Because “[a]ny user allegedly injured by 2FA 13 would doubtless be aware of that injury on the user’s first attempt to log in to his Apple ID via 14 2FA,” “the continuing violation doctrine does not apply.” Id. 15 That same conclusion applies again here. The SAC alleges that “2FA increases the 16 complexity of using the Apple devices, Services[,] and Third-Party Apps for Plaintiffs and Class, 17 especially for Senior Plaintiffs and Senior Class Members,” SAC ¶ 41, but that allegation does not 18 indicate that users would not “be aware of their injury on the user’s first attempt to log in to [their] 19 Apple ID via 2FA,” Order at 19. In fact, the SAC’s allegations include figures that prominently 20 display 2FA covering a device’s entire screen, and the SAC alleges that 2FA delays Plaintiffs’ 21 ability to log in to Apple ID or their Apple devices as soon as 2FA is enabled. SAC ¶¶ 35-36, 38- 22 41. In short, none of the SAC’s allegations alter the Court’s previous conclusion that “[a]ny user 23 allegedly injured by 2FA would doubtless be aware of that injury on the user’s first attempt to log 24 in to his Apple ID via 2FA.” Order at 19. Thus, the alleged wrongful course of conduct does not 25 become apparent only through the accumulation of a series of harms as required by the continuing 26 violation doctrine. Accordingly, the continuing violation doctrine does not apply to rescue the 27 1 time-barred claims. 2 c. The Delayed Discovery Rule Does Not Apply 3 Finally, as before, Plaintiffs cannot rely on the delayed discovery rule. Under the delayed 4 discovery rule, “the accrual of the action may be postponed and the running of the limitations 5 period tolled until the plaintiff discovers, or has reason to discover the cause of action.” Quarry v. 6 Doe I, 53 Cal. 4th 945, 960 (2012) (citation omitted). “A plaintiff has reason to discover a cause 7 of action when he or she has reason to at least suspect a factual basis for its elements.” Id. 8 Plaintiffs’ SAC includes no allegations of delayed discovery, and Plaintiff’s opposition brief 9 recycles the exact same arguments from Plaintiffs’ prior opposition brief that the Court previously 10 rejected. Compare Opp. at 5, with ECF No. 34 at 6. Plaintiffs’ SAC alleges that 2FA delays 11 Plaintiffs’ ability to log in to Apple ID or their Apple devices as soon as 2FA is enabled. SAC 12 ¶¶ 35, 38-39. Therefore, any user allegedly injured by 2FA would be aware of that injury on the 13 user’s first attempt to log in via 2FA. As a result, the delayed discovery rule does not apply. 14 Accordingly, the statute of limitations bars Plaintiff Brodsky’s CIPA, CFAA, and CCCL 15 claims and Plaintiff Tracey’s CIPA claim. Therefore, the Court GRANTS Apple’s motion to 16 dismiss Plaintiff Brodsky’s CIPA, CFAA, and CCCL claims and Plaintiff Tracey’s CIPA claim on 17 that ground. Plaintiffs failed to cure the same deficiencies the Court previously identified in its 18 prior Order, and the SAC offers no new facts to justify a different conclusion. Order at 17-19. As 19 the Court previously warned, “failure to cure the deficiencies identified herein or in Apple’s 20 motion to dismiss will result in dismissal with prejudice.” Id. at 20. Furthermore, courts are 21 justified in denying leave to amend when a plaintiff “repeated[ly] fail[s] to cure deficiencies by 22 amendments previously allowed.” Carvalho, 629 F.3d at 892. This is precisely the situation here, 23 as the Court’s prior Order put Plaintiffs on notice that many of their claims were time-barred. 24 Accordingly, the Court GRANTS Apple’s motion to dismiss Plaintiff Brodsky’s CIPA, CFAA, 25 and CCCL claims and Plaintiff Tracey’s CIPA claim with prejudice. 26 IV. CONCLUSION 27 For the foregoing reasons, the Court GRANTS Apple’s motion to dismiss with prejudice. 1 IT IS SO ORDERED. 2 Dated: April 7, 2020 3 ______________________________________ LUCY H. KOH 4 United States District Judge

6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27