Gemini Data, Inc. v. Google LLC

CourtDistrict Court, N.D. California
DecidedJanuary 27, 2026
Docket4:24-cv-06412
StatusUnknown

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

Bluebook
Gemini Data, Inc. v. Google LLC, (N.D. Cal. 2026).

Opinion

1 2 3 4 UNITED STATES DISTRICT COURT 5 NORTHERN DISTRICT OF CALIFORNIA 6 7 GEMINI DATA, INC., Case No. 24-cv-06412-JSW

8 Plaintiff, ORDER GRANTING MOTION FOR LEAVE TO FILE AMENDED 9 v. COMPLAINT AND MODFIFYING SCHEDULING ORDER 10 GOOGLE LLC, Re: Dkt. No. 75 Defendant. 11

12 13 This matter comes before the Court upon consideration of the motion to modify the 14 scheduling order and for leave to file an amended complaint, filed by Plaintiff Gemini Data, Inc. 15 (“Gemini Data”). The Court has considered the parties’ papers, relevant legal authority, and the 16 record in this case.1 The Court finds the motion is suitable for disposition without oral argument, 17 VACATES the hearing scheduled for February 6, 2026, and GRANTS Gemini Data’s motion. 18 BACKGROUND 19 On September 11, 2024, Gemini Data filed its original complaint accusing Google of 20 trademark infringement and unfair competition under federal and state law after Google rebranded 21 its artificial intelligence chatbot from BARD to GEMINI. According to Gemini Data, “Google 22 has unabashedly wielded its power to rob Gemini of its cultivated brand. Assuming a small 23 company like Gemini Data would not be in a position to challenge a corporate giant wielding 24 overwhelming power, Google continues to knowingly and willfully infringe on Gemini Data’s 25 rights, seemingly without remorse.” (Compl. ¶ 8.) Google filed an answer to the Complaint. 26 1 Defendant Google LLC (“Google”) objected to Gemini Data’s references to statements it 27 made in a settlement conference statement. Gemini Data voluntarily withdrew its reliance on 1 On January 7, 2025, the Court vacated the case management conference and issued a 2 Scheduling Order. (Dkt. No. 28 (Scheduling Order).) The deadline to file amended pleadings was 3 May 2, 2025. (Id.) Neither Gemini Data nor Google amended their pleadings. On September 5, 4 2025, the Court granted the parties’ stipulation to modify the Scheduling Order. (Dkt. No. 44.) In 5 October 2025, Gemini Data filed a motion to further modify the Scheduling Order because it was 6 in the process of retaining new counsel. The Court granted that motion, in part. (Dkt. No. 49.) 7 Gemini Data’s new counsel entered their appearance in November 2025. Under the current 8 Scheduling Order, fact discovery closed on December 18, 2025, expert disclosures are due on 9 February 6, 2026, and expert discovery closes on February 18, 2026. (Dkt. Nos. 44, 49.) 10 Gemini Data attests that in November 2025, it advised Google that it would not be relying 11 on forecasts regarding commercial success because the case was about reverse confusion. 12 (Declaration of Shannon Frazier (“Frazier Decl.”), ¶ 5.) Gemini Data attests that, or about 13 December 2, 2025, Google notified it that it did not believe Gemini Data alleged reverse confusion 14 in the Complaint. (Id. ¶¶ 6, 18.) Google attests that none of Gemini Data’s initial disclosures or 15 discovery responses mentioned reverse confusion until November 25, 2025. (Declaration of 16 Dylan Scher, ¶¶ 3-4.) 17 Although Gemini Data contends the initial complaint was sufficient to plead reverse 18 confusion, it moves to modify the Scheduling Order’s deadline to file amended pleadings and for 19 leave to file an amended complaint that removes allegations of forward confusion.2 20 ANALYSIS 21 A. Applicable Legal Standards. 22 Federal Rule of Civil Procedure 16(b) governs a party’s attempts to amend its pleading 23 once the district court’s deadline for amending pleadings has passed. Johnson v. Mammoth 24 Recreations, Inc., 975 F.2d 604, 607-08 (9th Cir. 1992). The moving party may amend their 25 pleading if they can establish “good cause” to do so. Id. Once Rule 16(b) is satisfied, leave to 26

27 2 Gemini Data also moves for leave to remove the Doe Defendants. Although Google 1 amend should be “freely given as justice so requires” under Federal Rule of Civil Procedure 15(a). 2 Fed. R. Civ. P. 15(a). Granting leave to amend rests in the sound discretion of the district court. 3 Pisciotta v. Teledyne Industries, Inc., 91 F.3d 1326, 1331 (9th Cir. 1996). “Although the rule 4 should be interpreted with extreme liberality, leave to amend is not to be granted automatically.” 5 Jackson v. Bank of Hawaii, 902 F.2d 1385, 1387 (9th Cir. 1990) (citations omitted). 6 B. Gemini Data Has Shown Good Cause Under Rule 16. 7 “Rule 16(b)’s ‘good cause’ standard primarily considers the diligence of the party seeking 8 the amendment.” Johnson, 975 F.2d at 609. Diligence is generally determined by examining the 9 time between the moving party’s discovery of new facts and the time it asks leave of the court to 10 file an amended pleading. See, e.g., Zivkovic v. S. Cal. Edison Co., 302 F.3d 1080, 1087-88 (9th 11 Cir. 2002); Coleman v. Quaker Oats Co., 232 F.3d 1271, 1294-95 (9th Cir. 2000). If a party fails 12 to show it was diligent, the inquiry should end. See Johnson, 975 F.2d at 609. 13 Google does not dispute that Gemini Data promptly filed this motion after learning that 14 Google did not believe it had alleged reverse confusion. Google argues that Gemini Data has not 15 been diligent because it should have known its theory of liability since the outset of the litigation. 16 “[R]everse confusion is not a separate claim that must be specifically pleaded, but instead is a 17 theory of likely confusion that may be alleged by itself or in addition to forward confusion.” 18 Marketquest Grp. Inc. v. Bic Corp., 862 F.3d 927, 932 (9th Cir. 2017). “[W]hen reverse confusion 19 is compatible with the theory of infringement alleged in the complaint, a plaintiff need not 20 specifically plead it.” Id. 21 “Forward confusion” occurs when a consumer believes “that goods bearing the junior 22 mark,” here Google’s GEMINI products, “come from or were sponsored by, the senior mark 23 holder,” i.e., Gemini Data. Surfvivor Media, Inc. v. Survivor Prods., 406 F.3d 625, 630 (9th Cir. 24 2005). In contrast, “reverse confusion occurs when consumers dealing with the senior mark 25 holder believe that they are doing business with the junior one.” Id.; see also Dermfx, Inc. v. 26 Obagi Med. Prods., Inc., No. SACV 15–01999 JVS (DFMx), 2017 WL 2684548, at *4 (C.D. Cal. 27 Mar. 24, 2017) (“[T]he basic question is whether (1) a plaintiff holding a senior mark claims that 1 confusion—or (2) a plaintiff claims that consumers are confused regarding the origination of a 2 plaintiff’s products—which is reverse confusion.”). 3 Gemini Data originally alleged that Google’s use of the GEMINI mark “is likely to 4 deceive consumers as to the origin, source, sponsorship, or affiliation of [Google’s] AI tools, and 5 is likely to cause consumers to believe, contrary to fact, that [Google’s] AI tools are sold, 6 authorized, endorsed, or sponsored by [Gemini], or that [Google] is in some way affiliated with or 7 sponsored by [Gemini].” (Compl.

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

Related

Cite This Page — Counsel Stack

Bluebook (online)
Gemini Data, Inc. v. Google LLC, Counsel Stack Legal Research, https://law.counselstack.com/opinion/gemini-data-inc-v-google-llc-cand-2026.