Garcia v. Build.com, Inc.

CourtDistrict Court, S.D. California
DecidedMarch 29, 2024
Docket3:22-cv-01985
StatusUnknown

This text of Garcia v. Build.com, Inc. (Garcia v. Build.com, Inc.) is published on Counsel Stack Legal Research, covering District Court, S.D. California primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Garcia v. Build.com, Inc., (S.D. Cal. 2024).

Opinion

1 2 3 4 5 6 7 8 UNITED STATES DISTRICT COURT 9 SOUTHERN DISTRICT OF CALIFORNIA 10 11 Case No.: 22-cv-1985-DMS-KSC SILVIA GARCIA, individually and on

12 behalf of all others similarly situated, ORDER GRANTING DEFENDANT’S 13 Plaintiff, MOTION TO DISMISS v. 14 BUILD.COM, INC., and DOES 1–10, 15 inclusive, 16 Defendants. 17 18 Pending before the Court is Defendant’s motion to dismiss. Based on her 19 interactions with the chat feature on Build.com’s website, Plaintiff Silvia Garcia 20 (“Plaintiff” or “Garcia”) alleges on behalf of herself and all others similarly situated that 21 Defendant Build.com, Inc. (“Defendant”) violated Cal. Penal Code § 631(a), Clause Four. 22 For the reasons explained below, the Court grants Defendant’s motion to dismiss. 23 I. BACKGROUND 24 A. Factual Allegations 25 Defendant Build.com is “an online home improvement retailer” that operates an e- 26 commerce website, www.build.com (“Website”). (Def.’s Mot. to Dismiss (“Def.’s Mem.”) 27 at 7, ECF No. 26.) The website includes a chat feature which allows customers to ask 28 questions about Build.com’s products and services. (Id.) At some point between July– 1 November 2022, she visited the Build.com website on her smartphone. (See First Am. 2 Compl. (“FAC”) ¶ 2, ECF No. 20; Compl. ¶ 18, ECF No. 1, Ex. A.) When she visited the 3 website, she initiated a chat conversation with Defendant in which she disclosed personally 4 identifiable information. (FAC ¶¶ 2, 10.) Plaintiff alleges she “was not advised that the 5 chat was monitored, intercepted, or recorded” and did not “consent thereto.” (Id. ¶ 2.) 6 Plaintiff alleges that Defendant “has allowed a third party, Salesforce, to embed its 7 chat technology code into the chat feature” on the Build.com website. (Id. ¶ 9.) Plaintiff 8 explains that Salesforce’s “Live Agent” product “acquires . . . chat communications by first 9 having its software . . . route them to Salesforce’s own computer servers that it owns, 10 controls, and maintains.” (Id. ¶ 10.) Accordingly, Salesforce has the capability to “secretly 11 intercept in real time, eavesdrop upon, and store transcripts of consumers’ chat 12 communications.” (Id.) Plaintiff further alleges that Defendant “has synched its chat 13 feature with Facebook.” (Id. ¶ 16.) “The integration allows various software sub-systems 14 to share data to operate as a unified system” and “is all part of Meta’s secret ‘plan to profit 15 from private chats.’” (Id., quoting Kurt Wagner, Meta Closes $1 Billion Kustomer Deal 16 After Regulatory Review, Bloomberg (Feb. 15, 2022, 1:30 PM), 17 https://www.bloomberg.com/news/articles/2022-02-15/meta-closes-1-billion-kustomer- 18 deal-after-regulatory-review.) Plaintiff explains: 19 First, Meta identifies “user interests” by monitoring a collection of “offsite” user activity such as website visits and interactions (including private chat 20 communications between Defendant and visitors) by “integrating” its 21 software with Salesforce Live Agent. Second, Meta generates revenue by selling advertising space through its subsidiaries’ ability to identify those 22 offsite user interests. Third and finally, after the chat transcripts intercepted 23 by Salesforce are provided to Meta through “integration,” Meta brands like Facebook and WhatsApp bombard the unsuspecting Website visitors with 24 targeted advertising based upon the user’s Website visits and interactions. 25 26 (FAC ¶ 17.) According to Plaintiff, “[a]s such, Salesforce does more than merely provide 27 a storage function for Website users’ chat communications with Defendant,” but also uses 28 the chat transcript data it collects “for data analytics and marketing/advertising to 1 consumers.” (Id. ¶ 19.) “Salesforce’s exploitation, monetization, use of, and interaction 2 with the data it gathers through the chat feature on Defendant’s Website in real time,” 3 therefore, “makes it a third-party interceptor and eavesdropper known to and enabled by 4 Defendant.” (Id. ¶ 20.) Salesforce is not a party to this suit. 5 Plaintiff further alleges that Defendant did not inform Class members that Defendant 6 “secretly allow[ed], aid[ed], and abet[ed]” Salesforce to intercept and eavesdrop on their 7 conversations, or that Salesforce “provided data from such transcripts to Meta and similar 8 entities through ‘integration’ of their softwares.” (Id. ¶ 22.) “Given the nature of 9 Defendant’s business, visitors often share personal and/or confidential data, in addition to 10 personally identifying information, with Defendant via the Website chat feature.” (Id. ¶ 11 21.) Defendant did not obtain Plaintiff’s or the Class members’ consent for such intrusions, 12 and Plaintiff and Class members did not know at the time they engaged in chat 13 communications on the Website. (Id. ¶ 23.) 14 B. Procedural History 15 Plaintiff filed the original complaint in this action on November 17, 2022, which 16 Defendant removed to this federal court on December 14, 2022, and raised two claims 17 based on violations of two provisions of the California Invasion of Privacy Act (CIPA), 18 Cal. Penal Code §§ 631(a), 632.7. (See generally Compl.; Notice of Removal, ECF No. 19 1.) Specifically, in Count One, Plaintiff alleged that Defendant violated all four clauses of 20 CIPA § 631(a), Cal. Penal Code § 631(a), and in Count Two, Plaintiff alleged that 21 Defendant violated CIPA § 632.7, Cal. Penal Code § 632.7. (See generally Compl.) On 22 July 13, 2023, this Court dismissed the original complaint in its entirety. (Order dated July 23 13, 2023 (“Order”), at 12.) The Court found that Plaintiffs failed to allege an aiding- 24 abetting claim under CIPA § 631(a), Clause Four, because Plaintiffs had not “plausibly 25 allege[d] the existence of a third-party eavesdropper,” or alternatively, because Plaintiffs 26 had not alleged that the third-party eavesdropper had “intercepted and used the data” for 27 its own purposes and that Defendant aided and abetted such conduct. (Id. at 9–10.) The 28 Court dismissed the Clause Four claim with leave to amend because it concluded that 1 amendment would not be futile. The Court dismissed all other claims and theories with 2 prejudice. (Id. at 10, 12.) 3 Plaintiff filed the operative FAC on July 17, 2023. Defendant filed its motion to 4 dismiss on August 30, 2023. (Def.’s Mot., ECF No. 26.) Plaintiff filed a response in 5 opposition on September 29, 2023.1 (Pl.’s Opp’n, ECF No. 28.) On October 6, 2023, 6 Defendant replied in support of its motion to dismiss, (Def.’s Reply, ECF No. 29), and the 7 Court took this matter under submission without oral argument, see S.D. Cal. Civ. L.R. 8 7.1(d)(1). Plaintiff filed two notices of supplemental authority on October 17, 2023, (ECF 9 No. 31), and November 6, 2023, (ECF No. 32). On November 7, 2023, Defendant 10 responded to the notices. (ECF No. 33.) 11 II. LEGAL STANDARD 12 Under Federal Rule of Civil Procedure 12(b)(6), a party may file a motion to dismiss 13 on the grounds that a complaint “fail[s] to state a claim upon which relief can be granted.” 14 Fed. R. Civ. P. 12(b)(6). A motion to dismiss under Rule 12(b)(6) “tests the legal 15 sufficiency of a claim.” Navarro v. Block, 250 F.3d 729, 732 (9th Cir. 2001). To survive 16 a motion to dismiss, “a complaint must contain sufficient factual matter, accepted as true, 17 to ‘state a claim to relief that is plausible on its face.’” Ashcroft v. Iqbal, 556 U.S. 662, 18 678 (2009) (quoting Bell Atl. Corp. v. Twombly, 550 U.S. 544, 570 (2007)).

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

Related

Foman v. Davis
371 U.S. 178 (Supreme Court, 1962)
Bell Atlantic Corp. v. Twombly
550 U.S. 544 (Supreme Court, 2007)
Watters v. Wachovia Bank, N. A.
550 U.S. 1 (Supreme Court, 2007)
Ashcroft v. Iqbal
556 U.S. 662 (Supreme Court, 2009)
Ribas v. Clark
696 P.2d 637 (California Supreme Court, 1985)
Manzarek v. St. Paul Fire & Marine Insurance
519 F.3d 1025 (Ninth Circuit, 2008)
Tavernetti v. Superior Court
583 P.2d 737 (California Supreme Court, 1978)
Intri-Plex Technologies, Inc. v. Crest Group, Inc.
499 F.3d 1048 (Ninth Circuit, 2007)
In Re Gilead Sciences Securities Litigation
536 F.3d 1049 (Ninth Circuit, 2008)
Rogers v. Ulrich
52 Cal. App. 3d 894 (California Court of Appeal, 1975)
Perrin Davis v. Facebook, Inc.
956 F.3d 589 (Ninth Circuit, 2020)
Navarro v. Block
250 F.3d 729 (Ninth Circuit, 2001)
Sprewell v. Golden State Warriors
266 F.3d 979 (Ninth Circuit, 2001)
Starr v. Baca
652 F.3d 1202 (Ninth Circuit, 2011)

Cite This Page — Counsel Stack

Bluebook (online)
Garcia v. Build.com, Inc., Counsel Stack Legal Research, https://law.counselstack.com/opinion/garcia-v-buildcom-inc-casd-2024.