Apex.AI, Inc. v. Langmead

CourtDistrict Court, N.D. California
DecidedMay 10, 2023
Docket5:23-cv-02230
StatusUnknown

This text of Apex.AI, Inc. v. Langmead (Apex.AI, Inc. v. Langmead) 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
Apex.AI, Inc. v. Langmead, (N.D. Cal. 2023).

Opinion

1 2 3 UNITED STATES DISTRICT COURT 4 NORTHERN DISTRICT OF CALIFORNIA 5 SAN JOSE DIVISION 6 7 APEX.AI, INC., Case No. 23-cv-02230-BLF

8 Plaintiff, ORDER GRANTING IN PART 9 v. PLAINTIFF’S EX PARTE APPLICATION FOR TRO AND 10 NEIL RICHARD LANGMEAD, an ORDER TO SHOW CAUSE WHY individual; VERIFA, INC., a Massachusetts PRELIMINARY INJUNCTION 11 corporation; and CODECLINIC LLC dba SHOULD NOT ISSUE; AND SETTING LATTIX, a Massachusetts limited liability HEARING ON PLAINTIFF’S MOTION 12 company, FOR PRELIMINARY INJUNCTION 13 Defendants. [Re: ECF 6]

15 16 Plaintiff Apex.AI, Inc. (“Apex.AI”) filed the complaint in this action on May 8, 2023, 17 asserting a federal trade secret claim against Defendants Neil Richard Langmead (“Langmead”), 18 Verifa, Inc. (“Verifa”), and CodeClinic LLC dba Lattix (“CodeClinic”) under the Defend Trade 19 Secrets Act (“DTSA”), 18 U.S.C. § 1836. See Compl., ECF 1. Apex.AI also asserts state law 20 claims for breach of contract, fraud, and unfair competition. See id. 21 Simultaneously with filing the complaint, Apex.AI filed an ex parte application seeking a 22 temporary restraining order (“TRO”) against Defendants and an order to show cause why a 23 preliminary injunction should not issue. See Ex Parte Applic., ECF 6. Apex.AI’s ex parte 24 application is GRANTED IN PART as set forth below. 25 Apex.AI SHALL file proof of service of process on Defendants by Saturday, May 13, 26 2023. Defendants are hereby ORDERED TO SHOW CAUSE, in writing and on or before May 27 17, 2023, why a preliminary injunction should not issue. A hearing on the motion for a 1 I. BACKGROUND 2 Apex.AI has submitted the declaration of its Chief Technology Officer and Co-Founder, 3 Dejan Pangercic, which establishes the following facts. See generally Pangercic Decl., ECF 6-4. 4 Apex.AI, which is headquartered in Palo Alto, California, develops award-winning and safety- 5 certified software tools for use in autonomous and software-defined vehicles. See id. ¶ 3. One of 6 Apex.AI’s products is Apex.OS, which is a bundle of two other products, Apex.Grace and 7 Apex.Ida. See id. ¶¶ 8-11. Those products are extremely valuable because “they are safety- 8 certified and are more efficient and developer-friendly than the handful of competing products.” 9 Id. ¶ 13. The products incorporate open-source software, but Apex.AI has developed and added 10 numerous proprietary features and products that it has spent substantial time and resources 11 developing. See id. ¶¶ 8-17. Apex.AI treats its products, the products’ source code, and related 12 technology as trade secrets and takes measures to ensure the confidentiality of those trade secrets. 13 See id. ¶¶ 17-29. 14 In November 2019, Apex.AI entered into a Consulting Agreement with Verifa, a 15 Massachusetts-based corporation. See Pangercic Decl. ¶ 34 & Ex. C. Langmead, a resident of 16 England, is the principal of Verifa and signed the Consulting Agreement as “Owner” of Verifa. 17 See id. Under the consulting agreement, Langmead worked on Apex.AI’s functional safety team, 18 which ensures that Apex.AI’s products meet applicable safety requirements and can be safety- 19 certified. See Pangercic Decl. ¶ 35. Langmead had access to virtually all of Apex.AI’s software, 20 source code, and other intellectual property. See id. ¶ 39. Langmead was specifically tasked with 21 developing an automated process for “generating the certification artifacts that are necessary to 22 prove that Apex.AI software meets the applicable functional safety requirements.” Id. ¶ 36. 23 Apex.AI paid Verifa $780,000 under the Consulting Agreement. See id. ¶ 43. 24 Langmead delivered proof of concept regarding the automated process but he never 25 delivered a final version. See Pangercic Decl. ¶ 41. Apex.AI recently learned that Langmead is 26 marketing the automated process to third parties through CodeClinic, another of his companies. 27 See id. Langmead is the bank account holder for CodeClinic, which is located at the same 1 source code, and associated safety certification artifacts, on CodeClinic’s platform. See id. ¶ 68. 2 Apex.AI has submitted the declaration of its Head of Information Technology, Dmytro Tutynin, 3 who captured lists of files and directories present on Langmead’s Apex.AI-issued laptop. See 4 Tutynin ¶¶ 3-6, ECF 6-10. Those files indicate that Langmead has exploited Apex.AI’s trade 5 secrets and proprietary information for his own benefit. See id.; see also Pangercic Decl. ¶¶ 54- 6 68. 7 Apex.AI has not terminated the Consulting Agreement or taken steps to retrieve its 8 company laptop from Langmead, because Apex.AI does not want to alert him that they have 9 discovered his wrongdoing. See Pangercic Decl. ¶ 70. Instead, Apex.AI. has filed the present 10 lawsuit against Langmead, Verifa, and CodeClinic, and seeks a TRO without notice to them. 11 II. LEGAL STANDARD 12 The Court may issue a TRO without notice to the adverse party only if: “(A) specific facts 13 in an affidavit or a verified complaint clearly show that immediate and irreparable injury, loss, or 14 damage will result to the movant before the adverse party can be heard in opposition; and 15 (B) the movant’s attorney certifies in writing any efforts made to give notice and the reasons why 16 it should not be required.” Fed. R. Civ. P. 65(b)(1). In addition, this district’s Civil Local Rules 17 require that a TRO application be accompanied by “[a] declaration by counsel certifying that 18 notice has been provided to the opposing party, or explaining why such notice could not be 19 provided.” Civ. L.R. 65-1(a)(5). 20 Courts use the same standard for issuing a temporary restraining order as that for issuing a 21 preliminary injunction. See Washington v. Trump, 847 F.3d 1151, 1159 n.3 (9th Cir. 2017) 22 (“[T]he legal standards applicable to TROs and preliminary injunctions are substantially 23 identical.” (internal quotation marks and citation omitted)). An injunction is a matter of equitable 24 discretion and is “an extraordinary remedy that may only be awarded upon a clear showing that 25 the plaintiff is entitled to such relief.” Winter v. Natural Resources Defense Council, Inc., 555 26 U.S. 7, 22 (2008). A plaintiff seeking preliminary injunctive relief must establish “[1] that he is 27 likely to succeed on the merits, [2] that he is likely to suffer irreparable harm in the absence of 1 the public interest.” Id. at 20. “[I]f a plaintiff can only show that there are serious questions going 2 to the merits – a lesser showing than likelihood of success on the merits – then a preliminary 3 injunction may still issue if the balance of hardships tips sharply in the plaintiff’s favor, and the 4 other two Winter factors are satisfied.” Friends of the Wild Swan v. Weber, 767 F.3d 936, 942 5 (9th Cir. 2014) (internal quotation marks and citations omitted). 6 III. DISCUSSION 7 Apex.AI asks the Court to issue an order: (1) enjoining Defendants from using or 8 disclosing Apex.AI’s trade secrets or confidential information; (2) enjoining Defendants from 9 destroying evidence; (3) requiring Defendants to return all Apex.AI trade secrets, confidential 10 information, property, and data; (4) allowing expedited discovery; and (5) allowing Apex.AI to 11 serve Defendant Langmead via email and following up with Federal Express. Apex.AI also 12 requests that the Court require Defendants to show cause why a preliminary injunction should not 13 issue. 14 The Court has no difficulty finding that Apex.AI has satisfied the requirements for 15 issuance of a TRO ex parte.

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

Related

Cite This Page — Counsel Stack

Bluebook (online)
Apex.AI, Inc. v. Langmead, Counsel Stack Legal Research, https://law.counselstack.com/opinion/apexai-inc-v-langmead-cand-2023.