ORDER GRANTING MOTION TO DISMISS

CHARLES R. BREYER, District Judge.

This is a putative class action brought by James Gross against computer security software maker Symantec and its subsidiary PC Tools, Ltd. Gross alleges the companies fraudulently induced him to buy security software through a free trial that was supposed to identify weaknesses in his computer's security. He alleges that the free trial was essentially a scam, and that the software does not increase security. He claims (1) a violation of California's Unfair Competition Law, Cal Bus. & Prof. Code § 17200; (2) fraudulent inducement; (3) breach of express warranties, Cal. Com. Code § 2312; (4) breach of contract; (5) breach of the implied covenant of good faith and fair dealing; and (6) unjust enrichment. PC Tools, Ltd., an Irish company, has yet to be served. Symantec moves to dismiss all causes of action on the grounds that Plaintiff Gross fails to state a claim upon which relief can be granted.

I. BACKGROUND1

Founded in 1982, Symantec has become a household name for its anti-virus and other security-related software. First Amended Complaint (dkt. 33) ¶ 13. In 1992, Symantec merged with Peter Norton Computing, Inc. and has continued to sell products, such as Norton Antivirus and Norton Utilities, under the Norton brand name. Id. ¶ 13. In August 2008, Symantec acquired an Australian PC utilities software company called PC Tools, Ltd. Id. ¶ 15. Symantec has since taken over the operations of PC Tools, but continues to sell software under the PC Tools name. Id. ¶ 16.

Through its websites and marketing materials, Symantec represents that its software protects users' privacy, improves the efficiency and performance of a computer, increases PC stability, repairs the hard drive, and cures other common computer errors and problems. Id. ¶ 38. To demonstrate its software's supposed utility, Symantec recommends that consumers download a free version of the software and conduct a "free diagnostic" scan, which purports to detect errors and other problems existing on a user's computer. Id. ¶¶ 39-40. After the user downloads the software and performs the free scan, the software allegedly invariably reports that there are numerous — often "high priority" — errors and other problems on the computer and represents that the software can "fix" the supposed problems, but only if the consumer registers and pays for the full price version of the software. Id. ¶¶ 41-45.

Despite Symantec's representations, Plaintiff alleges that the software is not designed to accurately identify and fix computer errors and improve PC performance. Id. ¶¶ 44-46. Rather, Plaintiff alleges Symantec intentionally designed the software to misrepresent and exaggerate the severity and existence of errors and the overall "System," "Privacy" and "Disk" health of consumers' PCs, thereby inducing them, like Gross, to register and pay for a full version of the software. Id.

In April 2011, Plaintiff Gross searched the Internet for software that would enhance the performance of his PC, and viewed an advertisement for Symantec's "Registry Mechanic" software. Id. ¶ 48. After reading representations in Symantec's advertisement and on its website that the software would accurately detect, report and repair errors and enhance the performance of his PC, Plaintiff downloaded a trial version of the software to run a "free scan." Id. ¶¶ 48-49. Plaintiff then ran Registry Mechanic's free diagnostic scan on his PC, which, to his chagrin, reported that his PC had numerous "High Priority" errors and other problems, and that his "System Health" was "LOW." Id. ¶ 50. The software further reported that in order to "fix all detected issues," Plaintiff would have to purchase a full version of Registry Mechanic. Id. Based on these representations, Plaintiff clicked on the "Purchase Online" button within the software and was directed to a website where he purchased the full version of Registry Mechanic for $29.99. Id. ¶ 51.

Plaintiff, acting through his counsel, later engaged a computer forensic expert to examine the functionality of the software. Id. ¶ 45. The expert ran a series of diagnostic tests in a controlled environment and determined that Symantec had deceptively designed its software to invariably report that the computer's "System Health," "Privacy Health," and "Disk Health" are "LOW," and that "High Priority" errors exist on the system. Id. ¶ 45. Plaintiff's expert further found that the software is designed to identify problems on a user's computer (even where none actually exist), and artificially inflate the number of errors detected, all without performing any actual assessment of these issues and regardless of the actual status of the system. Id. ¶ 46.

On January 10, 2012, Plaintiff Gross filed his original class action complaint against Symantec alleging claims for violations of California's Unfair Competition Law, fraudulent inducement, breach of express warranties, breach of contract, breach of the implied covenant of good faith and fair dealing, and unjust enrichment. Complaint (dkt. 1). Plaintiff also filed his Motion for Class Certification at that time. (Dkt. 2). On March 12, 2012, Symantec filed its motion to dismiss Plaintiff's complaint pursuant to Federal Rule Civil Procedure 12(b)(6). (Dkt. 28). In lieu of responding to Symantec's motion, Gross filed his First Amended Complaint, which alleged identical claims against Symantec and named as a party-defendant Symantec's subsidiary, PC Tools, Ltd. FAC (dkt. 33). Thereafter, Symantec again moved to dismiss each of Plaintiff's causes of action pursuant to Fed. R. Civ. P. 12(b)(6). Motion to Dismiss (dkt. 38). PC Tools, Ltd. is not party to this motion.

As explained below, the Court GRANTS Symantec's motion in its entirety but permits Plaintiff leave to amend.

II. LEGAL STANDARD

Federal Rule of Civil Procedure 8(a) requires that a complaint contain a "short and plain statement of the claim showing that the pleader is entitled to relief." A complaint must provide the defendant with "fair notice" of the claims against it and the grounds for relief. Bell Atlantic Corp. v. Twombly, 550 U.S. 544, 555 (2007). A court may dismiss a complaint under Rule 12(b)(6) when it does not contain enough facts to state a claim for relief that is plausible on its face. Id. at 570. "A claim has facial plausibility when the plaintiff pleads factual content that allows the court to draw the reasonable inference that the defendant is liable for the misconduct alleged." Ashcroft v. Iqbal, 129 S.Ct. 1937, 1949 (2009). Allegations of material fact are taken as true and construed in the light most favorable to the nonmoving party. Cahill v. Liberty Mut. Ins. Co., 80 F.3d 336, 337-38 (9th Cir. 1996).

Under Federal Rule of Civil Procedure 9(b), the "circumstances constituting fraud" or any other claim that "sounds in fraud" must be stated "with particularity." Fed. R. Civ. P. 9(b); Vess v. Ciba-Geigy Corp. USA, 317 F.3d 1097, 1103-04 (9th Cir. 2003). The purpose of this heightened pleading requirement is to "give defendants notice of the particular misconduct . . . so that they can defend against the charge and not just deny that they have done anything wrong." Neubronner v. Milken, 6 F.3d 666, 673 (9th Cir. 1993). To comply with Rule 9(b), a plaintiff must plead with particularity the time and place of the fraud, the statements made and by whom, an explanation of why or how such statements were false or misleading, and the role of each defendant in the alleged fraud. KEMA, Inc. v. Koperwhats, No. 09-1587, 2010 WL 3464737, at *3 (N.D. Cal. Sept. 1, 2010) (citations omitted).

A complaint should not be dismissed without leave to amend unless it is clear that the claims could not be saved by amendment. Swartz v. KPMG LLP, 476 F.3d 756, 760 (9th Cir. 2007).

III. DISCUSSION

Symantec moves to dismiss Plaintiff's FAC for failure to meet the pleading requirements of each individual cause of action. The Court will examine each in turn.2

A. Fraud

As a preliminary issue, Symantec argues that the entire FAC fails because each of Plaintiff's six claims arises from the same insufficiently pled fraudulent conduct. Symantec's challenge to Plaintiff's fraud allegations rests on three propositions considered here: (1) Plaintiff fails to plead fraud with the specificity required by Rule 9(b), (2) Plaintiff cannot state a claim based on representations of future performance, and (3) the allegations describing fraud are so contradictory as to make them implausible. Mot. at 5-6. As explained below, Symantec's motion is GRANTED, but only for failure to comply with Rule 9(b).3

1. Rule 9(b) Particularity

Because Plaintiff's allegations against Symantec "rely on a unified fraudulent course of conduct," the pleading is "grounded in fraud . . . [and] as a whole must satisfy the particularity requirement of Rule 9(b)." Vess, 317 F.3d at 1106; Kearns v. Ford Motor Co., 567 F.3d 1120, 1125 (9th Cir. 2009).4

Symantec maintains that the FAC does not meet the heightened requirements of Rule 9(b) due to the following deficiencies: (1) failure to identify the specific content and location of the misrepresentations concerning the functionality of software; (2) failure to identify the location or description of the individual "high priority" errors allegedly detected by the free trial scan on Plaintiff's computer; and (3) failure to identify a basis for believing that Plaintiff's computer "health" was not "low" as reported. Mot. at 7.

The two latter defects, which focus on Plaintiff's basis for believing Symantec's statements to be false, are inapposite to the fraud inquiry. The FAC alleges that the results of an investigation by computer forensic experts, and not the actual status of Plaintiff's computer, revealed the falsity of Symantec's representations. FAC ¶¶ 45-46 ("The results of this investigation confirm that Symantec's Scareware always reports that the user's computer's "System Health" is "LOW," that "High Priority" errors exist on the system, and that the user's "Privacy Health" and "Disk Health" are "LOW."); Opp'n at 11 (dkt. 39) ("[T]he actual status of Plaintiff's computer is not at issue . . . [the software] would have reported the very same information regardless of its status."). As Plaintiff's belief derives from the results of the forensic analysis, the allegations in the FAC sufficiently establish a basis for believing Symantec's statements to be false.

However, Symantec is correct in concluding that Plaintiff fails to plead the content of the misrepresentations relating to software utility with particularity.5 The FAC does not provide any allegations indicating what Symantec actually said regarding the functional capabilities of its software. The following allegations are illustrative:

Two cases from within this district inform the Court's analysis of these allegations under Rule 9(b). In Wenger v. Lumisys, Inc., the court held that paraphrased allegations, which "repackaged" various oral statements, were "too vague and impressionistic" to satisfy Rule 9(b), because they did not state, with particularity, what the defendants "actually" said. 2 F.Supp.2d 1231, 1246 (N.D. Cal. 1998). In that case, a plaintiff stock purchaser sued Lumisys and various insiders for allegedly making false and misleading statements about the commercial success of Lumisys products in order to artificially inflate the post-IPO price of Lumisys stock. Id. at 1238. In the complaint, the plaintiff had alleged that during various phone calls and roadshows in anticipation of the IPO, Lumisys executives represented that "Lumisys' business was performing very well and ahead of plan, with strong demand for its core digitizer products, that Imagraph's Imascan Precision product was succeeding and selling well, that Imagraph was successfully developing the ICE Clarity. . . ." Id. at 1246. The court rejected these allegations, and ruled that Rule 9(b) demands direct quotations. Id. at 1246-47 ("Plaintiff does not allege that [defendants] actually said that the Imascan Precision `was succeeding' or `selling well,' or that `Imagraph was successfully developing ICE Clarity,' . . . . What did [defendants] actually say about [their products]? Plaintiff does not inform us.").6

On the other hand, in TransFresh Corp. v. Ganzerla & Assoc., Inc., a plaintiff whose complaint included direct quotations from the website of a defendant competitor, who had allegedly misrepresented the environmental friendliness of products designed to keep produce fresh during transport, had complied with Rule 9(b). No. 11-6348, 2012 WL 994674, at *7 (N.D. Cal. Mar. 23, 2012). The complaint restated text from the defendant's website describing its product as "environmentally friendly" and "gas-free"; using "green methods" and "green technology"; and having the capacity to "reduce your carbon footprint." Brief in Support of Plaintiff TransFresh Corp.'s Opposition to Defendants' Motion to Dismiss Complaint, TransFresh, 2012 WL 664377 (Feb. 10, 2012) (quoting the complaint). The complaint also provided the defendant's tag line in verbatim, as well as direct quotations of alleged misstatements about the plaintiff's competing products. Id. Even though the statements were "described in a somewhat cursory fashion," the plaintiff's complaint survived dismissal under Rule 9(b) because it had "identifie[d] specific statements." TransFresh, 2012 WL 994674, at *7. This exemplifies what Plaintiff could have provided to avoid dismissal under Rule 9(b).

As in Wenger, Plaintiff's allegations are too vague to be actionable in federal court. Without direct quotations from the PC Tools website or other marketing materials, the Court cannot determine exactly how Symantec advertised its products. This is critical to the fraud analysis because Plaintiff's entire suit turns on how Symantec's representations compare to the actual funtionality of its software. This defect, while curable, is fatal to all Plaintiff's claims because the same allegations of fraudulent conduct support each claim.

2. Future Performance

Symantec next argues that Plaintiff's fraud-based claims also fail because they depend on alleged misrepresentations of future performance, not of an existing fact. Mot. at 7.7 Symantec claims that the FAC alleges promises "of what the software would do for Plaintiff in the future if he purchased it and how his computer would perform after using the software. . . ." Id.; Reply at 10 (identifying alleged promises, e.g., "that his computer would run faster, crash less, etc.").

Plaintiff indeed makes a number of allegations concerning the software's utility.8 While couched in language that may, at first blush, sound like a promise for future performance, the alleged representations instead describe the software as it existed at the time they were made. Specifically, Symantec's product marketing identified a number of specific tasks that the software had been programmed to perform. The design of the software code is properly characterized as an existing fact subject to scrutiny in a fraud claim, not a promise to produce certain results in the future. Therefore, the Court resolves this issue in favor of Plaintiff.

3. Contradictory Allegations

The Motion to Dismiss seizes on a handful of specific allegations included in the FAC, which, Symantec argues demonstrate inconsistencies as to whether the free trial version does or does not perform "an evaluation" as promised. Mot. at 8 (comparing FAC ¶ 68 (alleging software "did not perform an actual evaluation of Plaintiff's computer") with ¶ 50 ("the `free scan' was performed")). Consequently, Symantec contends, the FAC fails to meet the plausibility requirement of Rule 8 under Twombly. Twombly, 550 US. at 556.

This argument is unpersuasive because it loses sight of the central argument presented in the FAC. As the Motion acknowledges, Plaintiff alleges that the "free trial" software does not perform a "meaningful evaluation" or perform any of the "other valuable tasks" as Symantec promised. FAC ¶ 44 (emphasis added). According to the FAC, even if the software does perform some function, it cannot perform those specific functions advertised. This does not present a contradiction that defeats plausibility. As with Symantec's "future performance" theory, this argument does not warrant dismissal of Plaintiff's FAC.

Although Symantec's second and third arguments fail, the Court nevertheless GRANTS Symantec's Motion to Dismiss as to all claims without prejudice for failure to plead the alleged "functionality" misrepresentations with particularity. Should Plaintiff choose to amend, he must allege exact language used by Symantec in describing the utility of its software, including the individual tasks it purports to perform.

B. Unfair Competition Law, Cal. Bus. & Prof. Code § 17200

Section 17200, California's Unfair Competition Law ("UCL"), prohibits any "any unlawful, unfair or fraudulent business act or practice." Cal. Bus. & Prof. Code § 17200. Plaintiff alleges that Symantec violated the "fraudulent" and "unfair" prongs of the UCL by (1) misrepresenting the utility of its software, (2) misrepresenting the results of the "free scan" to induce consumer purchases of the software, and (3) selling software that lacks the advertised utility. FAC ¶¶ 66, 70-71.9 Symantec contends that Plaintiff cannot bring a UCL claim because the factual allegations lack any connection to California, as (1) Plaintiff is a non-resident and (2) the alleged wrongful conduct occurred outside of California. Mot. at 6.

The UCL allows claims by non-California plaintiffs when the alleged misconduct or injuries occurred in California. Doe v. Nestle, 748 F.Supp.2d 1057, 1122 (C.D. Cal 2010); In re Intel Laptop Battery Litig., No. 09-2889, 2010 WL 5173930, at *2 (N.D. Cal. Dec. 15, 2010). "[A] California court may properly apply California laws to non-California members of a nationwide class where the defendant is a California corporation and some or all of the challenged conduct emanates from California." Red v. Kraft Foods, Inc., No. 10-1028, 2011 WL 4599833, at *6 (C.D. Cal. Sept 29, 2011) (quoting Wershba v. Apple Comp., Inc., 91 Cal.App.4th 224, 243 (2001)). Application of California state law is impermissible where the alleged misconduct "simply has no connection to California." See Safjr v. BBG Commc'ns, Inc., No. 10-2341, 2012 WL 398991, at *4 (S.D. Cal. Jan. 10, 2012). In short, the location of the alleged conduct giving rise to liability controls application of UCL, not the domicile of the plaintiff or defendant. Id. ("The fact that Plaintiffs are California residents does not change [the court's] conclusion" that the UCL does not apply extraterritorially to the defendants' international conduct).

In Parkinson, cited by both Plaintiff and Symantec, a federal district court permitted a nonresident plaintiff to bring a UCL claim against a car distributor for failure to disclose defects in the clutch of a particular car model, because the plaintiff successfully alleged that the decisions controlling the alleged nondisclosure emanated from the defendant's offices in Orange County, California. Parkinson v. Hyundai Motor Am., 258 F.R.D. 580, 598 (C.D. Cal. 2008). Specifically the Plaintiffs had alleged that the "defendant's relevant operations, including its headquarters, marketing department, warranty department, customer affairs department, and engineering department, [were] located in California." Id.10

Plaintiff attempts to bring similar allegations against Symantec, contending that the challenged conduct "occurred in, was directed and/or emanated from" Symantec's California offices. FAC ¶ 10; Opp'n at 10. However, as Symantec points out, Plaintiff does not describe the geography of Symantec's "relevant operations" with the same degree of specificity as in Parkinson. Reply at 7; Parkinson, 258 F.R.D. at 598. While Plaintiff does allege that Symantec is headquartered in Mountain View, CA, FAC ¶ 10, several courts have found that this allegation is not enough to create a plausible inference that the unlawful conduct emanated from that location. See Tidenberg v. Bidz.com, Inc., No. 08-5553, 2009 WL 605249, at *4-5 (C.D. Cal. Mar. 4, 2009) (holding that plaintiffs residing in Texas lacked standing under the UCL to bring suit against a California-based company because, absent "any specific facts linking Defendants' contacts with California to the claims asserted against them," the court cannot "presume that any false or misleading statements emanated from California").

An earlier case from this Court clarified the plaintiff's burden of linking the alleged misconduct to California in order to take advantage of California state law. In Badella v. Deniro Mktg. LLC, this Court denied certification of a nation-wide class for California state law claims (including the UCL) because, apart defendants' California residency, the plaintiffs did "not present [any] types of actual evidence regarding Defendants' actions in California. . . ." No. 10-3908, 2011 WL 5358400, at *9, *11 (N.D. Cal. Nov. 4, 2011) (emphasis in original). The case involved the owners of an online dating website who allegedly created and controlled fake user profiles to induce free trial customers to upgrade to paid memberships. In describing the deficiency of the plaintiff's Motion to Certify this Court wrote:

Id. at *11.

Even though the FAC does take one step beyond the complaint in Badella by alleging generally that Symantec runs its business in California, it is nevertheless deficient because it fails to allege the state in which Symantec's fraudulent conduct occurred. FAC ¶¶ 7,10. Specifically, because the fraudulent scheme materialized "during the marketing and sale of [Symantec's] computer software products," Plaintiff should allege that Symantec's sales and marketing departments operate out of it California offices. Id. ¶ 72.11

Accordingly, while the Court already dismisses Plaintiff's UCL claim under the fraud analysis, it additionally instructs Plaintiff to amend the FAC to allege specific conduct that occurred in California.

C. Fraudulent Inducement

Symantec moves to dismiss Plaintiff's claim for Fraudulent Inducement on the single ground that it insufficiently pleads the factual allegations supporting a claim for fraud. Mot. at 5-8. As discussed above in Section A(1), Symantec's argument is persuasive because Plaintiff fails to plead the circumstances surrounding fraud with particularity. Accordingly, the Court GRANTS Symantec's Motion to Dismiss Plaintiff's fraudulent inducement claim without prejudice.

D. Breach of Express Warranties, Cal. Com. Code § 2313

In his third cause of action Plaintiff alleges that Symantec violated California Commercial Code Section 2313 for breach of an express warranty that the software could perform accurate diagnostic tests on consumers' computer systems. FAC ¶ 90. Symantec contends that this claim fails for four reasons: (1) California law does not apply to a software license transaction between a Washington resident and an Irish company; (2) Section 2313 does not apply to software licenses generally; (3) Plaintiff has failed to plead the elements of an express warranty; and (4) the express warranty was disclaimed in the EULA agreement. Mot. at 8-11.

1. Application of California Law

In challenging the applicability of California state law to Plaintiff's express warranty claim, Symantec reiterates the same argument it asserted in the context of the UCL. Mot. at 8. Like Plaintiff's UCL claim, Plaintiff's express warranty claim is dismissed because the allegations fail to tie Symantec's relevant operations to California.

2. Application of Cal. Com. Code § 2313 to Software Licenses

Symantec next argues that the California Uniform Commercial Code ("UCC") does not govern Plaintiff's purchase of the Registry Mechanic software because it only covers the sale of goods, which excludes licenses for the use of intellectual property, like Symantec's software.

The California UCC defines "goods" as "all things (including specially manufactured goods) which are movable at the time of identification to the contract for sale. . . ." Cal. Com. Code § 2105. Software transactions often straddle the line between goods and services, so courts look to the "essence of the agreement" to determine how best to characterize the transaction. RRX Indus., Inc. v. Lab-Con, Inc., 772 F.2d 543, 546 (9th Cir. 1985). Furthermore, "because software packages vary depending on the needs of the individual consumer," the Ninth Circuit has ruled that such contracts merit a case-by-case analysis. Id.; Phoenix Solutions, Inc. v. Sony Elecs., Inc., 637 F.Supp.2d 683, 694 (N.D. Cal. June 5, 2009).

Symantec cites Sys. Am., Inc. v. Rockwell Software, Inc., No. 03-2232, 2007 WL 218242, at *4 (N.D. Cal. Jan 26, 2007), to support its contention that the California UCC does not cover the "transfer of intellectual property rights." Mot. at 9. However, Rockwell is distinguishable because it concerns a contract for software development services, not a consumer sales transaction. Id. at 4 ("Under the SDA, Versant must develop new software to supplement existing Rockwell Software software" and "[grant] a license to Rockwell Software."). Significantly, the court in that case explicitly distinguished the software development contract from "the sale of a Windows CD at Best Buy," a "license for mass-produced [software]," much like Plaintiff's purchase Symantec's consumer software in the present case. Id. Although Plaintiff purchased and downloaded Symantec's software from the internet, and did not install the software from a CD, the "essence of the agreement" is the same. FAC ¶ 51; RRX Indus., 772 F.2d at 546.

In RRX Industries, the Ninth Circuit held that the California UCC covered computer software that the defendants had sold and installed in plaintiff's medical laboratories. RRX Indus., 772 F.2d at 545. Even though the software contract also provided for ancillary services, such as training, repair services, and system upgrading, the sale of the software package was paramount, so characterization as a "good" for the purposes of the California UCC was proper. Id. at 546.12

The software transaction in the case at hand resembles the sale in RRX Industries, except that it doesn't include the installation, training, maintenance, and upgrading services that might have jeopardized the applicability of the California UCC in that case. Accordingly, Registry Mechanic shall be regarded as a "good," and the California UCC applies. The Court therefore permits Plaintiff to bring a claim under Section 2313, provided Plaintiff can amend the factual allegations as already suggested above.

3. Express Warranty Elements

As an alternative to its challenges to the applicability of California law, Symantec argues that the FAC inadequately alleges the elements of an express warranty claim. Specifically Symantec contends that Plaintiff fails to provide the exact terms of the alleged warranty, as well as where and when Symantec stated them. Mot. at 10. Furthermore, Symantec argues that the representations alleged in the FAC are "vague, highly subjective," and amount to "mere statements of opinion and puffery." Id.

To prevail on a breach of express warranty claim under California law, "a plaintiff must prove (1) the seller's statements constitute and `affirmation of fact or promise' [which relates to the goods] or a `description of the goods'; (2) the statement was `part of the basis of the bargain'; and (3) the warranty was breached." Weinstat v. Dentsply Int'l, Inc., 180 Cal.App.4th 1213, 1227 (2010) (quoting Cal. Com. Code § 2313(1)(a-b)). "Statements constituting `mere puffery' cannot support liability under a claim for breach of warranty." Sanders v. Apple, Inc., 672 F.Supp.2d 978, 987 (N.D. Cal. 2009). "The distinguishing characteristics of puffery are vague, highly subjective claims as opposed to specific, detailed factual assertions." Id. (quotation omitted).

Defendant's first argument, that Plaintiff failed to express the exact terms of the express warranty, is coextensive with its argument that Plaintiff failed to plead with particularity the misrepresentations at the heart of Symantec's alleged fraudulent conduct. Both concern the way in which Symantec described the functionality of its software. To the extent that Plaintiff amends his FAC pursuant to Rule 9(b), those amendments should address Symantec's concerns regarding specificity of the express warranty as well.

As to the second argument, Symantec is incorrect that the challenged statements are too vague to rise above "mere puffery" or "opinion." According to the FAC, Symantec marketed its software to suggest an ability to perform specific functions related to computer security and system optimization. FAC ¶¶ 38, 40. This is not opinion about the quality of the software's performance or a "vague superlative" that a "consumer could not reasonably believe." sanders, 672 F. Supp. 2d at 987. Rather, the alleged statements offer objective descriptions of software utility, which inform the consumer of the specific functions that Symantec's software has been programmed to perform. Representations of "a particular product's performance specification based on its design" are the substance of an express warranty. Bros. v. Hewlett-Packard Co., No. 06-2254, 2007 WL 485979, at *7 (N.D. Cal. Feb. 12, 2007) (holding that a statement that a computer product was compatible with a particular graphics card constituted an express warranty).

Thus, should Plaintiff take the opportunity to identify what exact statements Symantec made about its software, the Court will be satisfied that the elements of this cause of action have been sufficiently pled.

4. Disclaimer of Warranty

Finally Symantec argues that Plaintiff's express warranty claim must fail because the EULA explicitly disclaimed all warranties pertaining to the effectiveness of the software. Mot. at 10-11. As proof, Symantec submitted a copy of the EULA with its first Motion to Dismiss. (Dkt. 28, Ex. 1). According to Symantec, the EULA states that "PC Tools does not guarantee that the Software will detect, remove or rectify any errors on your computer. . . ." and "PC Tools makes no warranties in relation to the software, including warranties as to the performance or fitness for purpose of the Software." EULA at ¶¶ 4.1, 4.5(a). The Plaintiff did not attach the EULA to the FAC, nor did Symantec request judicial notice to place it on the record.

While federal district courts do not typically look beyond the complaint when adjudicating a 12(b)(6) motion to dismiss, they may take judicial notice sua sponte of documents containing adjudicative facts "not subject to reasonable dispute." Fed. R. Evid. 201(b); United States v. Cantu, 12 F.3d 1506, 1509 n.1 (9th Cir. 1993). Under the incorporation-by-reference doctrine, courts may consider relevant documents not physically attached to the plaintiff's pleading if (1) the contents are "central to the allegations" and (2) no party questions the authenticity of the documents. Darensburg v. Metro. Transp. Comm'n, No. 05-1597, 2006 WL 167657, at *2 (N.D. Cal. Jan. 20, 2006); Knievel v. ESPN, 393 F.3d 1068, 1076 (9th Cir. 1999).

Although the FAC does acknowledge the existence of the EULA, it does not include any factual allegations related to the content of the agreement, so the EULA cannot be "central to the allegations."13 Darensburg, 2006 WL 167657, at *2. Furthermore, Plaintiff challenges the enforceability of the EULA. See Phillips Med. Capital, LLC v. Med. Insights Diagnostic Ctr., Inc., 471 F.Supp.2d 1035, 1042 (N.D. Cal. 2007) (refusing to dismiss a breach of express warranty claim in light of a warranty disclaimer in contract for medical equipment because the contract might be "void because [it was] procured by fraud"); FAC ¶¶ 30-33 (alleging that the "EULA serves as an extension of Defendants' fraud"). Therefore, the Court declines to consider the EULA at this stage.

Finally, as Plaintiff points out, California courts generally regard warranty disclaimers as void when they contradict the express terms of the alleged warranty. Teknekron Customer Info. Solutions, Inc. v. Watkins Motor Lines, Inc., No. 93-3422, 1994 WL 11726, at *5 (N.D. Cal. Jan. 5, 1994) (citing Hauter v. Zogarts, 14 Cal.3d 104, 119 (1975)); Cal. Com. Code § 2316(1). Consistent with California law, the Court will not allow any disclaimers in the EULA to trump the express warranty alleged in the FAC, especially at this stage of litigation.14 Accordingly, the disclaimers stated in the EULA do not provide grounds for dismissal of Plaintiff's claim for breach of express warranty.

E. Breach of Contract

Symantec next disputes Plaintiff's breach of contract claim, which is predicated on the theory that a contract formed when Plaintiff agreed to pay $29.99 in exchange for software that Symantec had promised could "detect and remove legitimate computer errors." FAC ¶ 95. According to Plaintiff, Symantec breached its promises by "failing to honestly and accurately inform [customers] about the condition of their computers, and further by providing software that failed to offer the benefits promised, namely, resolution of problems detected, and improvements in performance, privacy protection, and security." Id. ¶ 98. Symantec argues that the above allegations cannot support a breach of contract claim because (1) Plaintiff fails to allege the specific terms of an express contract and when those terms became part of the contract, and (2) Plaintiff does not sufficiently allege breach. Mot. at 11.15 As a point of clarification, Symantec does not contest Plaintiff's breach of contract claim on the grounds that no contract formed at all when Plaintiff purchased the software.16 Rather, Symantec challenges Plaintiff's allegations as to which terms were incorporated into that sales contract. It theorizes that Plaintiff cannot allege breach without properly alleging the terms that he claims were breached.

A complaint for breach of contract must plead: (1) the existence of a contract, (2) a breach of the contract by defendant, (3) performance or excuse of non-performance on behalf of plaintiff, and (4) damages suffered by plaintiff as a result of defendant's breach. McDonald v. John P. Scripps Newspaper, 210 Cal.App.3d 100, 104 (1989). To sustain this cause of action plaintiffs must either attach a copy of the contract to the complaint or plead the essential terms of the contract. McAfee v. Francis, No. 11-0821, 2011 WL 3293759, at *2 (N.D. Cal. Aug. 1, 2011).

Some federal district courts in California have dismissed breach of contract claims for failure to allege the exact terms that were allegedly breached, so Symantec's first argument challenging the specificity of the pleadings has merit. See, e.g., id. However, this argument is another species of its failure-to-plead-with-particularity theory (discussed above). To the extent that Symantec is unsatisfied with the specificity of the alleged express terms of the contract, as well as when those terms were established, a new complaint amended to comply with Rule 9(b) should suffice.

However, regardless of the whether Plaintiff pleads the existence and terms of a contract as required under California law, Symantec is correct in concluding that the FAC does not allege a plausible breach. Mot. at 13-14. This is because the allegations pointing to breach concern software performance prior to Plaintiff's purchase of the full version of the software. Plaintiff's basis for challenging the functionality of Symantec's software arises from a computer forensic expert's analysis of the Registry Mechanic "free diagnostic scan," not the full version of the software. FAC ¶¶ 45-47. Thus, the factual allegations only support a plausible theory that the free trial version did not function as advertised. Plaintiff alleges that the contract was formed at the point of sale, so any "breach" stemming from defects in the free trial version must have occurred before the contract formed. Unless Plaintiff can offer factual allegations establishing that the full version of the software failed to perform the advertised functions, the breach of contract claim must fail, for a breach cannot occur before contract formation.

F. Breach of the Implied Covenant of Good Faith and Fair Dealing

"To establish a breach of an implied covenant of good faith and fair dealing, a plaintiff must establish the existence of a contractual obligation, along with conduct that frustrates the other party's rights to benefit from the contract." Rosal v. First Fed. Bank of Cal., 671 F.Supp.2d 1111, 1129 (N.D. Cal. 2009).

Plaintiff claims that "Symantec breached the implied covenant of good faith and fair dealing by failing to honestly and accurately inform consumers about the true condition of their computers. . . ." FAC ¶ 108. Symantec moves to dismiss this claim on the grounds that (1) it duplicates the previous breach of contract claim, (2) Plaintiff has failed to demonstrate how he has been denied the benefit of the bargain, and (3) the EULA explicitly permits the conduct comprising the alleged breach.

Symantec's first argument is persuasive. "If the allegations in a breach of implied covenant claim do not go beyond the statement of a mere contract breach and, relying on the same alleged acts, simply seek the same damages or other relief already claimed in a companion contract cause of action, they may be disregarded as superfluous as no additional claim is actually stated." Zepeda v. PayPal, Inc., 777 F.Supp.2d 1215, 1221 (N.D. Cal. 2011) (citing Malcolm v. JPMorgan Chase Bank, N.A., No. 09-4496, 2010 WL 934252, at *6 (N.D. Cal. Mar. 15, 2010)) (dismissing plaintiffs' cause of action for breach of implied covenant because the supporting allegations were the same as those alleged for their breach of contract claim, even though the breach of contract claim was dismissed for failure to state a claim).

In the present case, the allegations supporting breach of the implied covenant are identical to those supporting breach of contract. FAC ¶¶ 98, 108 (alleging that Symantec breached both by "failing to honestly and accurately inform the consumers about the true condition of their computers"). Therefore, the implied covenant claim is superfluous.

Plaintiff, noting an exception recognized in California state and federal courts, contends that this rule does not apply to his case because Symantec "acted in bad faith to frustrate the contract's actual benefits." Opp'n at 18 (citing Guz v. Bechtel Nat., Inc., 24 Cal.4th 317, 353 n.18 (2000)). However, this exception does not apply when the bad faith alleged pertains only to a defendant's inducement of a plaintiff to enter into the contract. Shaterian v. Wells Fargo Bank, N.A., 829 F.Supp.2d 873, 884 (N.D. Cal. 2011) (distinguishing between "actions presumably taken to induce [contract formation]" and those taken "to frustrate the benefits of the contract"). Because the FAC only plausibly alleges lack of functionality in the free trial version of the software, and not the full version, the only bad faith conduct at issue relates to inducement. Thus, the exception does not apply.

Accordingly, the Court GRANTS Symantec's Motion as to this claim without prejudice, so that Plaintiff may have the opportunity to properly allege that he qualifies for the "bad faith" exception permitted under Guz.

G. Unjust Enrichment

As an alternative to his claims for breach of contract and breach of the implied covenant of good faith and fair dealing, Plaintiff seeks relief for unjust enrichment. He alleges that Symantec benefitted from software purchases at the expense of its customers by "falsely informing Plaintiff and the Class that they needed to pay to repair problems that did not exist." FAC ¶ 113. Symantec responds that the facts of this case cannot support a cause of action for unjust enrichment because an express contract existed between Plaintiff and Symantec. Symantec's conclusion is correct.

California recognizes unjust enrichment as an action for quasi-contract. Paracor Fin., Inc. v. Gen Elec. Capital Corp., 96 F.3d 1151, 1167 (9th Cir. 1996). An action based on quasi-contract "does not lie when an enforceable, binding agreement exists defining the rights of the parties." Id.; Gerlinger v. Amazon, Inc., 311 F.Supp.2d 838, 856 (N.D. Cal. 2004) (citations omitted). Here, Plaintiff and Symantec indeed shared a contractual relationship, thus barring Plaintiff's unjust enrichment claim.17

Accordingly, Symantec's Motion to Dismiss Plaintiff's unjust enrichment claim is GRANTED with prejudice.

IV. CONCLUSION

For the foregoing reasons, the Court GRANTS Symantec's Motion to Dismiss Plaintiff's UCL, fraudulent inducement, express warranty, breach of contract, and breach of implied covenant claims without prejudice, and GRANTS Symantec's Motion to Dismiss plaintiff's unjust enrichment claim with prejudice. If Plaintiff successfully serves PC Tools in Ireland, PC Tools may move on its own to dismiss the substantive claims under Rule 12(b)(6).

IT IS SO ORDERED.