Bureau Veritas Technical Assessments LLC et al. v. Blake Brosa et al.

• Court: District Court, D. Arizona
• Decided: December 1, 2025
• Docket: 2:25-cv-02339
• Status: Unknown

Opinion

1 WO 2 3 4 5 6 IN THE UNITED STATES DISTRICT COURT 7 FOR THE DISTRICT OF ARIZONA

9 Bureau Veritas Technical Assessments LLC, No. CV-25-02339-PHX-JJT et al., 10 ORDER Plaintiffs, 11 v. 12 Blake Brosa, et al., 13 Defendants. 14 15 At issue are three Motions to Dismiss and supporting memoranda filed separately 16 by Defendant Apex Imaging Services Incorporated (Docs. 21, 22), Defendant Blake Brosa 17 (Docs. 24, 25), and Defendant Todd Tankersley (Docs. 27, 28). The Court finds this matter 18 appropriate for resolution without oral argument. See LRCiv 7.2(f). For the reasons set 19 forth below, the Court will grant Defendant Apex’s Motion to Dismiss, deny Defendant 20 Tankersley’s Motion to Dismiss, and grant in part and deny in part Defendant Brosa’s 21 Motion to Dismiss. 22 I. BACKGROUND 23 Plaintiffs Bureau Veritas Technical Assessments, LLC (“BVTA”) and Bureau 24 Veritas North America, Inc. (“BVNA”) provide project management services, building 25 assessment, and code compliance for multi-site customers. (Doc. 1, Compl., ¶¶ 24–26.) To 26 generate business with new or existing customers, Plaintiffs submit responses to Requests 27 for Proposals (“RFPs”) in a confidential, competitive bidding process. (Id. ¶ 27.) According 28 1 to Plaintiffs, Defendant Apex is “a new entrant in the project management services 2 industry” and provides services for “multi-site rollouts.” (Id. ¶ 33.) 3 Defendant Brosa began working for Plaintiffs in July 2015 as their Senior Vice 4 President of Sales. (Id. ¶ 37.) He managed Plaintiffs’ national and multinational customer 5 accounts, sold services, and generated business. (Id.) In October 2021, Defendant Brosa 6 was promoted to the Executive Vice President of Sales and, in addition to managing 7 customer accounts, led sales and marketing strategy and guided sales team meetings. (Id. 8 ¶¶ 37–39.) In this role, Defendant Brosa had direct access to Plaintiffs’ product 9 information, customer list, pricing, RFP submissions, product development, strategy and 10 marketing initiatives, and contact with some of Plaintiffs’ “Whale” customers. (Id. ¶ 40.) 11 As a part of his employment, Defendant Brosa entered a Confidentiality, Non-Competition, 12 Non-Solicitation, and Assignment of Rights Agreement (“Brosa Agreement”). (Id. ¶¶ 41– 13 48; Doc. 1-2.) The Brosa Agreement contained four covenants at issue in this matter: (1) 14 confidentiality; (2) non-competition; (3) non-solicitation; and (4) non-recruitment (“Brosa 15 Covenants”). 16 In 2011, Defendant Tankersley was hired by Quality Project Management, LLC 17 (“QPM”) as a Project Manager. (Compl. ¶ 49.) QPM was a child company of Plaintiff 18 BVNA and an affiliate company of Plaintiff BVTA. (Id. ¶ 50.) As a part of his employment 19 with QPM, Defendant Tankersley entered a confidentiality agreement (“Tankersley 20 Agreement”). (Id. ¶¶ 50, 60–65; Doc. 1-1.) According to Plaintiffs, BVTA acquired QPM 21 and received a transfer or assignment of the Tankersley Agreement. (Compl. ¶ 50.) Due to 22 the acquisition, Defendant Tankersley “became a BVTA employee.” (Id.) In 2019, 23 Defendant Tankersley was promoted to Plaintiffs’ Senior Product Developer and 24 developed client-specific project tracking software through an application called 25 “ProTrack.” (Id. ¶¶ 52–55.) 26 In November 2024, Defendant Brosa extracted several files from his work computer 27 to a flash drive and sent customer communications and documents to his personal email 28 account. (Id. ¶¶ 68–82.) In December 2024, Defendant Brosa terminated his employment 1 with Plaintiffs and began working for Defendant Apex as its Director of Business 2 Development for Multi-Site Retail. (Id. ¶¶ 66–67.) Even after his employment ended, 3 Defendant Brosa retained possession of his former work computer and extracted additional 4 information. (Id. ¶¶ 83–84.) On December 23, 2024, Plaintiffs sent Defendants Apex and 5 Brosa a letter that recited portions of the Brosa Covenants. (Id. ¶ 85; Doc. 1-3.) 6 In April 2025, Defendant Tankersley terminated his employment with Plaintiffs and 7 began working for Defendant Apex as its Director of Systems the following month. 8 (Compl. ¶¶ 87–90.) In June 2025, Defendant Brosa sent an airline ticket from his personal 9 email account to Plaintiffs’ sales executive to fly from the Ontario airport back to the 10 executive’s home city of Phoenix, Arizona. (Id. ¶ 92.) The Ontario airport is twenty 11 minutes from Defendant Apex’s headquarters. (Id.) Sometime after this flight, the 12 executive terminated her employment with Plaintiffs. (Id.) 13 On July 3, 2025, Plaintiffs sued Defendants Apex, Brosa and Tankersley, asserting 14 nine claims: (1) misappropriation of trade secrets under the federal Defend Trade Secrets 15 Act of 2016 (“DTSA”), 18 U.S.C. § 1836, against all Defendants; (2) misappropriation of 16 trade secrets under the Arizona Uniform Trade Secrets Act (“AUTSA”), A.R.S. §§ 44-401– 17 07, against all Defendants; (3) breach of the confidentiality covenant in the Brosa 18 Agreement against Defendant Brosa; (4) breach of the non-solicitation and non-recruitment 19 covenants in the Brosa Agreement against Defendant Brosa; (5) breach of the non- 20 competition covenant in the Brosa Agreement against Defendant Brosa; (6) breach of the 21 confidentiality covenant in the Tankersley Agreement against Defendant Tankersley; 22 (7) breach of the duty of loyalty against Defendant Brosa; (8) tortious interference with a 23 contract or expectancy against Defendant Apex; and (9) unfair competition against all 24 Defendants. (Id. ¶¶ 98–216.) Defendants each filed their respective Motions to Dismiss and 25 supporting memoranda (Docs. 21, 22, 24, 25, 27, 28),1 to which Plaintiffs responded 26 (Docs. 36–38) and Defendants replied (Doc. 48–50). 27 . . . 28 1 No Defendant moves to dismiss the seventh claim, so the Court will not address it. 1 II. LEGAL STANDARD 2 Rule 12(b)(6) is designed to “test[] the legal sufficiency of a claim.” Navarro v. 3 Block, 250 F.3d 729, 732 (9th Cir. 2001). A dismissal under Rule 12(b)(6) for failure to 4 state a claim can be based on either: (1) the lack of a cognizable legal theory; or (2) the 5 absence of sufficient factual allegations to support a cognizable legal theory. Balistreri v. 6 Pacifica Police Dep’t, 901 F.2d 696, 699 (9th Cir. 1990). When analyzing a complaint for 7 failure to state a claim, the well-pled factual allegations are taken as true and construed in 8 the light most favorable to the nonmoving party. Cousins v. Lockyer, 568 F.3d 1063, 1067 9 (9th Cir. 2009). A plaintiff must allege “enough facts to state a claim to relief that is 10 plausible on its face.” Bell Atl. Corp. v. Twombly, 550 U.S. 544, 570 (2007). “A claim has 11 facial plausibility when the plaintiff pleads factual content that allows the court to draw the 12 reasonable inference that the defendant is liable for the misconduct alleged.” Ashcroft v. 13 Iqbal, 556 U.S. 662, 678 (2009) (citing Twombly, 550 U.S. at 556). “The plausibility 14 standard is not akin to a ‘probability requirement,’ but it asks for more than a sheer 15 possibility that a defendant has acted unlawfully.” Id. 16 “While a complaint attacked by a Rule 12(b)(6) motion does not need detailed 17 factual allegations, a plaintiff’s obligation to provide the grounds of his entitlement to relief 18 requires more than labels and conclusions, and a formulaic recitation of the elements of a 19 cause of action will not do.” Twombly, 550 U.S. at 555 (cleaned up and citations omitted). 20 Legal conclusions couched as factual allegations are not entitled to the assumption of truth 21 and therefore are insufficient to defeat a motion to dismiss for failure to state a claim. Iqbal, 22 556 U.S. at 679–80. However, “a well-pleaded complaint may proceed even if it strikes a 23 savvy judge that actual proof of those facts is improbable, and that ‘recovery is very remote 24 and unlikely.’” Twombly, 550 U.S. at 556 (quoting Scheuer v. Rhodes, 416 U.S. 232, 236 25 (1974)). 26 . . . 27 . . . 28 . . . 1 III. ANALYSIS 2 A. Counts One and Two: Misappropriation of Trade Secrets 3 Plaintiffs bring claims for trade secret misappropriation under both the federal 4 DTSA (Count One) and its state law counterpart AUTSA (Count Two). (Compl. ¶¶ 98– 5 132.) Defendants Apex and Tankersley, but not Defendant Brosa, move to dismiss these 6 claims. (Doc. 22 at 3–7; Doc 28 at 3–9.) 7 District courts have analyzed claims arising under the DTSA and AUTSA together 8 because the elements are identical. See Early Warning Servs. LLC v. Johnson, No. CV-24- 9 01587-PHX-SMB, 2025 U.S. Dist. LEXIS 89594, *4 (D. Ariz. May 12, 2025); ReBath 10 LLC v. HD Sols. LLC, No. CV-19-04873-PHX-JJT, 2020 U.S. Dist. LEXIS 223194, *2–3 11 (D. Ariz. Sep. 18, 2020). This approach is especially appropriate because Plaintiffs’ 12 allegations underlying both claims are the same. (Compare Compl. ¶¶ 98–115 with ¶¶ 116– 13 32.) For a trade secret misappropriation claim to survive a motion to dismiss, a plaintiff 14 must sufficiently plead: “(1) that the plaintiff possessed a trade secret[;] (2) that the 15 defendant misappropriated the trade secret; and (3) that the misappropriation caused or 16 threatened damage to the plaintiff.” InteliClear, LLC v. ETC Glob. Holdings, Inc., 978 F.3d 17 653, 657–58 (9th Cir. 2020) (citing 18 U.S.C. § 1839(5)). 18 1. Trade Secrets 19 First, “plaintiffs must identify the trade secrets . . .” Id. at 658 (citation and internal 20 quotation marks omitted). Trade secrets are defined broadly and include three components: 21 “(1) information, (2) that is valuable because it is unknown to others, and (3) that the owner 22 has attempted to keep secret.” Id. at 657; see also 8 U.S.C. § 1839(3); A.R.S. § 44-401(4). 23 Even though trade secrets are defined broadly, “[t]he plaintiff should describe the subject 24 matter of the trade secret with sufficient particularity to separate it from matters of general 25 knowledge in the trade or of special knowledge of those persons . . . skilled in the trade.” 26 Inteliclear, 978 F.3d at 658 (citation and internal quotation marks omitted). “Plaintiffs may 27 not simply rely upon catchall phrases[,] identify categories of trade secrets they intend to 28 pursue at trial . . . [or] cite and incorporate by reference hundreds of documents that 1 purportedly reference or reflect the trade secret information.” Id. Identifying a trade secret 2 with particularity is important because it allows a defendant to adequately prepare a rebuttal 3 and for the trier of fact to navigate the “sophisticated and highly complex system[s]” that 4 trade secrets typically create. Id. 5 Defendants Apex and Tankersley argue that Plaintiffs fail to sufficiently identify 6 trade secrets in their Complaint. (Doc. 22 at 3–6; Doc. 28 at 7.) The Complaint broadly 7 describes Plaintiffs’ trade secrets to include “confidential and proprietary processes and 8 methods, customer-specific applications, customer pipelines, business plans and strategies, 9 pricing information, customer lists, customer-service factors, financial records, marketing 10 strategies, and plans for maintaining, developing, and growing BVTA’s project 11 management business, and compilations of such data and information.” (Compl. ¶¶ 100, 12 118.) According to Defendant Apex, this description of the purported trade secret amounts 13 to Plaintiffs’ entire business, contains “business puffery,” and is not particular. (Doc. 22 at 14 3–4.) 15 Such a broad description, without more, would likely fail to plead the first element 16 of a trade secret misappropriation claim. But the Complaint describes at least one purported 17 trade secret with particularity. Plaintiffs allege that they developed “proprietary and highly 18 confidential client-specific applications on ProTrack,” which required considerable time, 19 money and resources. (Compl. ¶¶ 52, 58.) According to Plaintiffs, the trade secret is the 20 customer-specific applications of ProTrack, not ProTrack itself. (Id. ¶¶ 53–56.) These 21 applications and the knowledge of how to create them is allegedly unique to Plaintiffs and 22 distinguishes them from other businesses in the industry because “it can be applied across 23 hundreds or thousands of locations across the United States.” (Id. ¶ 56.) This feature of 24 Plaintiffs’ business “is often a determinative factor for customers in deciding which 25 proposal to an RFP is successful.” (Id.) These customer-specific applications and the 26 knowledge and skill of how to create them “would be of tremendous value to a competitor,” 27 including “a new entrant into the market like Apex.” (Id. ¶ 59.) Taking these facts as true, 28 1 Plaintiffs sufficiently plead that the client-specific applications of ProTrack constitute 2 information that is valuable because it is not known to others. 3 Defendant Tankersley attacks Plaintiffs’ allegations for failing to distinguish the 4 knowledge and skill of creating the software from general skills and knowledge gained in 5 the industry. (Doc. 28 at 6–7.) However, the Complaint alleges that the knowledge and 6 skill to create customer-specific applications were derived from expensive and resource- 7 intensive development efforts. (Compl. ¶¶ 56, 58–59.) Taking these facts as true, this 8 knowledge and skill transcends that which would be “general” in the industry. See, e.g., 9 Joshua David Mellberg LLC v. Will, 96 F. Supp. 3d 953, 978 (D. Ariz. 2015) (holding that 10 information derived from years of data development and analysis was not general 11 knowledge). 12 In addition to being information that is valuable for not being known by others, it 13 must also be subject to Plaintiffs’ efforts to keep it a secret. Here, Plaintiffs allege that their 14 purported trade secrets are subject to various protections under Plaintiffs’ confidentiality 15 agreements executed by employees, Code of Ethics, and password protection for computer 16 systems. (Compl. ¶¶ 36, 61–63.) These efforts are sufficient to identify Plaintiffs’ 17 reasonable measures to maintain the secrecy of the software. See Inteliclear, 978 F.3d at 18 658 (instituting confidentiality policies that protect purported trade secrets constitute 19 reasonable efforts); Fire Sec. Elecs. & Commc’ns Inc. v. Nye, No. CV-23-02730-PHX- 20 DLR, 2024 U.S. Dist. LEXIS 25575, at *9 (D. Ariz. Feb. 13, 2024) (instituting computer 21 passwords constitute reasonable efforts). At this early stage of the proceedings, Plaintiffs 22 sufficiently identify at least one trade secret under the broad definition of the DTSA and 23 AUTSA. 24 2. Misappropriation 25 Second, a plaintiff must sufficiently plead that a defendant misappropriated the trade 26 secret. The term “misappropriation” is defined as: 27 28 1 (A) acquisition of a trade secret of another by a person who knows or has reason to know that the trade secret was acquired 2 by improper means; or 3 (B) disclosure or use of a trade secret of another without 4 express or implied consent by a person who— 5 (i) used improper means to acquire knowledge of the 6 trade secret; 7 (ii) at the time of disclosure or use, knew or had reason 8 to know that the knowledge of the trade secret was— 9 (I) derived from or through a person who had 10 used improper means to acquire the trade secret; 11 (II) acquired under circumstances giving rise to 12 a duty to maintain the secrecy of the trade secret 13 or limit the use of the trade secret; or

14 (III) derived from or through a person who owed a duty to the person seeking relief to maintain the 15 secrecy of the trade secret or limit the use of the 16 trade secret; or

17 (iii) before a material change of the position of the 18 person, knew or had reason to know that—

19 (I) the trade secret was a trade secret; and 20 (II) knowledge of the trade secret had been 21 acquired by accident or mistake. 22 23 18 U.S.C § 1839(5); see also A.R.S. § 44-401(2). Improper means includes “theft, bribery, 24 misrepresentation, breach or inducement of a breach of a duty to maintain secrecy, or 25 espionage.” 18 U.S.C § 1839(6); A.R.S § 44-401(2). 26 While improper means include several kinds of conduct, “[m]ere possession of trade 27 secrets by a departing employee is not sufficient to establish misappropriation or show 28 injury.” Cutera, Inc. v. Lutronic Aesthetics, Inc., 444 F. Supp. 3d 1198, 1207 (E.D. Cal. 1 2020). Rather, the purported misappropriation must extend beyond mere possession. Id. at 2 1207–08 (allegations that the defendant deployed a sales method claimed to be a trade 3 secret were sufficient to plead misappropriation); Early Warning Servs. LLC, 2025 LEXIS 4 89594, at *12–13 (allegations that the defendant published previously unknown 5 information without the plaintiff’s consent were sufficient to plead misappropriation); see 6 e.g., Fire Sec. Elecs. & Commc’ns Inc., 2024 U.S. Dist. LEXIS 25575, at *10–11 (evidence 7 of a former employee coordinating with a current employee to copy files supported 8 misappropriation). 9 Defendants Apex and Tankersley dispute that Plaintiffs sufficiently allege facts 10 giving rise to misappropriation. (Doc. 22 at 6–7; Doc. 28 at 3–8.) Defendant Tankersley 11 specifically argues that Plaintiffs’ allegations that he will “inevitably” use or disclose a 12 trade secret are insufficient under the “inevitable disclosure doctrine.”2 (Doc. 28 at 5–8.) 13 However, Plaintiffs do not merely allege inevitable use or disclosure. Rather, 14 Plaintiffs assert that Defendant Tankersley is currently using or disclosing his knowledge 15 of how to create Plaintiffs’ proprietary computer software to “develop copies of 16 [Plaintiffs’] customer-specific applications for Apex” without Plaintiffs’ permission. 17 (Compl. ¶ 91.) According to Plaintiffs, Defendant Apex did not have a similar computer 18 software prior to Defendant Tankersley’s employment. (Id. ¶ 57.) Plaintiffs also allege that 19 Defendant Tankersley signed a confidentiality agreement that expressly prohibited the use 20 or disclosure of computer software outside the scope of his employment with Plaintiffs, 21 which supports an inference that Defendant Tankersley owed a duty of secrecy to Plaintiffs. 22 (Id. ¶¶ 61–63.) These facts, taken as true and construed in a light most favorable to 23 Plaintiffs, sufficiently allege that Defendant Tankersley misappropriated Plaintiffs’ trade 24

25 2 This doctrine has not been clearly recognized as a cognizable legal theory under AUTSA in Arizona or under the DTSA in the Ninth Circuit. (Doc. 49 at 2–4.) See Liss v. Exel 26 Transp. Servs., No. CIV-04-2001-PHX-SMM, 2007 U.S. Dist. LEXIS 20555, at *27 (D. Ariz. Mar. 20, 2007) (“It is unclear whether Arizona recognizes the theory of inevitable 27 disclosure as the Court did not locate a single case in Arizona applying this theory.”); Kinship Partners, Inc. v. Embark Veterinary, Inc., No. 3:21-cv-01631-HZ, 2022 U.S. Dist. 28 LEXIS 2804, at *19 (D. Or. Jan. 3, 2022) (“DTSA specifically forecloses courts from granting relief based on the inevitable disclosure doctrine . . .”). 1 secret by developing the same software for Defendant Apex while owing a duty to 2 Plaintiffs to maintain the secrecy of the trade secret. See 18 U.S.C. § 1839(5)(B). 3 As for Plaintiffs’ claim against Defendant Apex, Plaintiffs’ allegations of 4 misappropriation are far less detailed. Plaintiffs advance that Defendant Apex hired 5 Defendants Brosa and Tankersley “to induce them to unlawfully disclose BVTA’s 6 confidential and trade secret information.” (Compl. ¶ 2.) But nowhere in the Complaint do 7 Plaintiffs allege facts supporting that Defendant Apex knew or had reason to know that 8 Defendants Brosa and Tankersley acquired Plaintiffs’ trade secrets by improper means, or 9 that Defendant Apex used improper means to acquire trade secrets itself. See, e.g., Solar 10 Optimum Inc. v. Elevation Solar LLC, No. CV-23-00135-PHX-SMB, 2024 U.S. Dist. 11 LEXIS 80983, *14–15 (D. Ariz. May 3, 2024) (allegations that executives of the defendant 12 company directed the plaintiff’s former employee to use a current employee’s credentials 13 and access trade secret information was sufficient to plead misappropriation); Early 14 Warning Servs. LLC, 2025 U.S. Dist. LEXIS 89594 at *11–12 (allegations that a defendant 15 company registered the plaintiff’s intellectual property knowing it was procured 16 improperly by the plaintiff’s employee was sufficient to plead misappropriation). 17 The only factual assertions advanced by Plaintiffs appear to be that Defendant Apex 18 received the benefit from Defendants Brosa and Tankersley’s misappropriation. For 19 instance, Plaintiffs allege that Defendant “Apex did not have the ability to quickly develop 20 customer-specific applications to scale to meet the demands of BVTA’s national and 21 multinational multi-site customers” prior to hiring Defendant Tankersley. (Compl. ¶ 57.) 22 When Defendant Tankersley allegedly joined Defendant Apex as its Director of Systems, 23 he became “responsible for developing Apex’s software development, including the 24 development of customer-specific project management applications on the same ProTrack 25 platform utilized by BVTA.” (Id. ¶ 90.) These allegations are insufficient on their own 26 under DTSA and AUTSA, which requires that Defendant Apex knew or had reason to 27 know that the software was misappropriated. See Joshua David Mellberg LLC, 96 F. Supp. 28 3d at 982–83 (allegations that a competitor business merely benefitted from its employees 1 using trade secrets in the course of employment is insufficient to allege misappropriation 2 as to the competitor business); Bombardier Inc. v. Mitsubishi Aircraft Corp., 383 F. Supp. 3 3d 1169, 1182 (D. Wash. 2019) (“[M]erely recruiting another company’s employees does 4 not meet the knowledge requirement for trade secret misappropriation.”) Without 5 sufficiently pleading misappropriation, Counts One and Two fail as alleged against 6 Defendant Apex. 7 3. Threatened or Caused Damage 8 Finally, a plaintiff must sufficiently plead that the misappropriation caused, or 9 threatened to cause, the plaintiff harm. “Damages are an essential element of . . . [a] 10 misappropriation of trade secret . . . claim[], and a claim fails as a matter of law without a 11 cognizable theory of proximately caused damages.” W.L. Gore & Assocs. v. GI Dynamics, 12 Inc., 872 F. Supp. 2d 883, 888 (D. Ariz. 2012) (modifications in original) (citation and 13 internal quotation marks omitted). “The very purpose of trade secret law is to protect 14 valuable confidential information from discovery.” Ctr. for Auto Safety v. Goodyear Tire 15 & Rubber Co., 247 Ariz. 567, 573 (Ariz. App. 2019) (citation and internal quotation marks 16 omitted). 17 Defendant Tankersley argues that Plaintiffs fail to state facts to form a basis for 18 damages. (Doc. 28 at 8.) The Court disagrees. According to Plaintiffs, Defendant 19 Tankersley’s misappropriation of the proprietary client-specific software harms Plaintiffs’ 20 competitive offering of that software, which “is often a determinative factor for customers” 21 in selecting a company to provide services. (Compl. ¶¶ 57, 91, 93–94; Doc. 38 at 12.) 22 Factual allegations identifying an injury to competitive standing, along with allegations 23 that the software was developed at a substantial cost (Compl. ¶ 58), is sufficient at this 24 stage. 25 In sum, Plaintiffs sufficiently plead the elements of trade secret misappropriation 26 under the DTSA and AUTSA as to Defendant Tankersley, but not as to Defendant Apex. 27 Accordingly, the Court will dismiss Counts One and Two against Defendant Apex. It is 28 possible that Plaintiffs can cure this pleading defect by amendment with additional, well- 1 pled facts. Lopez v. Smith, 203 F.3d 1122, 1130 (9th Cir. 2000). The Court will therefore 2 grant Plaintiffs leave to amend Counts One and Two as to Defendant Apex. 3 B. Counts Three through Six: Breach of Contract 4 Plaintiffs bring three breach of contract claims against Defendants Brosa for 5 violating the Brosa Covenants (Compl. ¶¶ 133–77), and one breach of contract claim 6 against Defendant Tankersley for violating the confidentiality covenant in the Tankersley 7 Agreement (Id. ¶¶ 178–94). In asserting a breach of contract claim, a plaintiff must allege 8 sufficient facts that identify (1) a contract, (2) breach, and (3) damages. Thunderbird 9 Metallurgical, Inc. v. Ariz. Testing Lab., 423 P.2d 124, 126 (Ariz. 1967). 10 1. Assignment of the Tankersley Agreement 11 Defendant Tankersley argues that Plaintiffs’ breach of contract claim fails because 12 they do not properly allege that a contract exists between Plaintiffs and Defendant 13 Tankersley. (Doc. 28 at 10–11.) Rather, that contract is held between QPM and Defendant 14 Tankersley. (Id.) However, Plaintiffs expressly allege that the Tankersley Agreement was 15 transferred or assigned to Plaintiff BVTA after an “acquisition” of QPM. (Compl. ¶¶ 49– 16 50.) Arizona law recognizes transfers or assignments of restrictive covenants to a 17 successive employer, which is the kind of transfer or assignment alleged by Plaintiffs. See 18 Supplies for Indus. v. Christensen, 659 P.2d 660, 661–62 (Ariz. App. 1983) (holding that 19 restrictive covenants in an employment agreement can be equitably assigned to a 20 successive employer); see also Sogeti USA LLC v. Scariano, 606 F. Supp. 2d 1080, 1082 21 (D. Ariz. 2009) (collecting and discussing Arizona case law regarding the assignment of 22 employment agreements) (citations omitted). 23 Defendant Tankersley argues that the Tankersley Agreement could not be 24 transferred or assigned because it lacks an assignment clause and Defendant Tankersley 25 did not consent to the transfer or assignment. (Doc. 28 at 10.) Defendant Tankersley 26 provides no legal authority for this proposition. In fact, district courts have observed the 27 opposite proposition—that “Arizona law is most consistent with the jurisdictions that allow 28 successor companies to enforce restrictive covenants, even when the contract is silent 1 regarding assignability and the employee has not consented.” Sogeti USA LLC, 606 F. 2 Supp. 2d at 1085. At this early stage, Plaintiffs’ allegations are sufficient to identify at least 3 one Plaintiff as a party to the Tankersley Agreement by transfer or assignment. 4 2. Enforceability of the Brosa Covenants 5 Defendant Brosa asserts that Plaintiffs’ breach of contract claims fail because the 6 Brosa Covenants are unenforceable. (Doc. 25 at 3–7.) The enforceability of a covenant 7 depends on the reasonableness of the restraint, which “is a fact-intensive inquiry that 8 depends on the totality of the circumstances.” Valley Med. Specialists v. Farber, 194 Ariz. 9 363, 369 (Ariz. 1999). While fact-intensive, enforceability of a restrictive covenant is 10 ultimately a question of law. Id. at 366–67. “The legitimate purpose of post-employment 11 restraints is to prevent competitive use, for a time, of information or relationships which 12 pertain peculiarly to the employer and which the employee acquired in the course of the 13 employment.” Id. at 367. A restrictive covenant is unreasonable, and therefore 14 unenforceable: “(1) if the restraint is greater than necessary to protect the employer’s 15 legitimate interest; or (2) if that interest is outweighed by the hardship to the employee and 16 the likely injury to the public.” Id. at 369. 17 a. Confidentiality Covenant 18 A confidentiality covenant is overly broad if it seeks to protect information that is 19 available to the public. Orca Communs. Unlimited, Ltd. Liab. Co. v. Noder, 233 Ariz. 411, 20 417 (Ariz. App. 2013) (“Orca I”), de-published in part on other grounds, 236 Ariz. 180 21 (Ariz. 2014) (“Orca II”). If a confidentiality covenant is overbroad, it is considered a non- 22 compete covenant and must have reasonable temporal and geographical restrictions to be 23 enforceable. Amex Distrib. Co., Inc. v. Mascari, 150 Ariz. 510, 517 (Ariz. App. 1986). 24 Arizona’s public policy promotes use of and access to information in the public 25 domain. See Enter. Leasing Co. v. Ehmke, 197 Ariz. 144, 149 (Ariz. App. 1999). For 26 example, in Orca I, the Arizona Court of Appeals held that an employer’s confidentiality 27 agreement was overly broad because it dubbed publicly available information as 28 “confidential” based on two qualifications: (1) whether a member of the public would have 1 difficulty in locating the information; and (2) whether the information was learned through 2 employment. 233 Ariz. at 417. The court reasoned that an employer has “no protectable 3 interest in public information” even if “a member of the public may have to expend 4 substantial time to gather it and comprehend its significance” or the employee learned of 5 the information by virtue of her employment. Id. 6 Here, Defendant Brosa argues that the confidentiality covenant is unenforceable 7 because it includes non-confidential information and lacks temporal and geographic 8 restrictions. (Doc. 25 at 4–5.) Plaintiffs argue that the confidentiality covenant is properly 9 tempered because it restricts only the use of information arising out of Plaintiffs’ business 10 and excludes information made available to the public or information Defendant Brosa 11 knew prior to his employment with Plaintiffs. (Doc. 36 at 10–11.) 12 Plaintiffs overstate the mitigative effect of those exclusions contained in the 13 confidentiality covenant. The covenant states:

14 All documents or information, in whatever form or medium, 15 regarding the business or affairs of the Company and its affiliates . . . shall all be deemed ‘Confidential Information,’ 16 except to the extent the same shall have been lawfully and 17 without breach of obligation made available to the general public without restriction . . . 18

19 (Doc. 1-2 ¶ 1(a) (emphasis modified).) In other words, Defendant Brosa would be 20 prohibited from using public information if it was made public by someone else in 21 Plaintiffs’ employ in a manner that violated that person’s obligations to Plaintiffs. The 22 effect of the confidentiality covenants here and in Orca I are the same: they prohibit an 23 employee from using information that is freely in the public domain. See 233 Ariz. at 417. 24 “Information easily or readily available to the public remains public knowledge and not 25 protectable as confidential information” no matter the manner in which it becomes public. 26 Id. For these reasons, Plaintiffs’ confidentiality covenant is overbroad. Due to the 27 overbreadth of the confidentiality covenant, it will be construed as a non-competition 28 agreement and must be limited in time and geography. Plaintiffs do not identify, and the 1 Court cannot find, any temporal or geographic limitation in the confidentiality covenant. It 2 is therefore unreasonable and unenforceable. 3 Plaintiffs request that the Court sever the unenforceable portions under the 4 severance clause contained in the Brosa Agreement. (Doc. 36 at 16 n.4; Doc. 1-2 ¶ 5.) 5 “Arizona courts will ‘blue pencil’ restrictive covenants, eliminating grammatically 6 severable, unreasonable provisions.” Valley Med. Specialists, 194 Ariz. at 372. But 7 “[w]here the severability of the agreement is not evident from the contract itself, the court 8 cannot create a new agreement for the parties to uphold the contract.” Olliver/Pilcher Ins. 9 v. Daniels, 148 Ariz. 530, 533 (Ariz. 1986) (“Olliver”). And the blue pencil doctrine cannot 10 be used to create temporal or geographical terms that do not exist. Because the 11 confidentiality covenant is unenforceable on its face and incurable, the Court will dismiss 12 Count Three with prejudice. 13 b. Non-Compete Covenant 14 “A covenant not to compete precludes former employees from working in the same 15 business as the employers for certain time periods in specified areas.” Hilb, Rogal & 16 Hamilton Co. v. McKinney, 190 Ariz. 213, 216 (Ariz. App. 1997) These covenants “are 17 disfavored and thus are strictly construed against employers.” Id. To be enforceable, a non- 18 compete covenant should “not exceed that reasonably necessary to protect the employer’s 19 business, is not unreasonably restrictive of the rights of the employee, does not contravene 20 public policy, and is reasonable as to time and space.” Bed Mart, Inc. v. Kelley, 202 Ariz. 21 370, 372 (Ct. App. 2002) (citation omitted). “An employer has a legitimate interest in 22 preventing competitive use, for a time, of information or relationships which pertain 23 particularly to the employer and which the employee acquired in the course of the 24 employment . . . [and] in having a reasonable amount of time to overcome the former 25 employee’s loss . . .” Id. (citation and internal quotation marks omitted). 26 Plaintiffs assert that Defendant Brosa violated the non-compete covenant by 27 working for Defendant Apex, a competitor of Plaintiffs, in a similar role. (Compl. ¶¶ 170– 28 71.) Defendant Brosa argues the non-compete covenant is unenforceable because it 1 prohibits him “from taking employment with any ‘competitor’ anywhere in the world.” 2 (Doc. 25 at 5.) Plaintiffs argue that the “geographic scope is limited to only activities that 3 jeopardize BVTA’s confidential information and goodwill.” (Doc. 36 at 16.) 4 Upon review of the covenant and Plaintiffs’ well-pled allegations, however, the 5 covenant restricts more than activities that jeopardize Plaintiffs’ business interests in the 6 area that those activities occurred. As Plaintiffs themselves allege, Defendant Brosa 7 broadly managed sales and marketing strategies on a vast national and multi-national scale. 8 (Compl. ¶¶ 37, 39.) In applying the plain language of the covenant to Defendant Brosa’s 9 expansive role, it is evident that the covenant effectively prevents Defendant Brosa from 10 pursuing any role that involves sales, marketing or client management nationally and 11 internationally for a business that offers any one of Plaintiffs’ many project management 12 services. These restrictions are not merely based on whether Defendant Brosa’s role would 13 use confidential information or existing customer relationships, Bed Mart, Inc., 202 Ariz. 14 at 372; rather, they amount to a per se restriction on competition. As currently pled, this 15 covenant is overbroad in terms of the restricted activity and unreasonable as to the 16 geographic scope, rendering it unenforceable. 17 Plaintiffs request that the Court sever the unenforceable parts under the severance 18 clause contained in the Brosa Agreement. (Doc. 36 at 16 n.4; Doc. 1-2 ¶ 5.) Here, striking 19 the geographic scope as written will leave no geographic scope at all, which does not cure 20 the defect that renders the non-compete covenant unreasonable. Accordingly, the Court 21 will dismiss Count Five. It is possible that the defect can be cured by amendment with 22 additional, well-pled facts, so the Court will grant Plaintiffs leave to amend this claim. 23 Lopez, 203 F.3d at 1130. 24 c. Non-Solicitation Covenant 25 A non-solicitation covenant “is designed to prevent former employees from using 26 information learned during their employment to divert or to ‘steal’ customers from the 27 former employer.” Olliver, 148 Ariz. at 531. This type of covenant is “ordinarily not 28 deemed unreasonable or oppressive.” Id. Still, a non-solicitation covenant must be “no 1 broader than necessary to protect the employer’s legitimate business interest.” Bed Mart, 2 Inc., 202 Ariz. at 372. An employer has no legitimate business interest in protecting persons 3 or entities with whom it has no business ties, such as potential or former customers. Hilb, 4 190 Ariz. at 216; Orca I, 233 Ariz. at 418. 5 Defendant Brosa argues the non-solicitation covenant3 is unenforceable because it 6 is based on an unreasonable one year-long time restriction and improperly prohibits 7 solicitation of prospective clients with whom Plaintiffs have no legitimate interest to 8 protect. (Doc. 25 at 6–7.) Plaintiffs contend that the covenant is reasonable because a one- 9 year time limitation is routinely enforced in Arizona, and it limits solicitation only to those 10 clients with whom Defendant Brosa had a relationship within eighteen months prior to his 11 termination. (Doc. 36 at 13–14.) 12 Even assuming the reasonableness of a one-year time restriction, the non- 13 solicitation covenant is still unreasonable because it ultimately prohibits solicitation of 14 prospective and former clients with whom Plaintiffs have no legitimate interest to protect. 15 The non-solicitation covenant defines a class of individuals and entities falling within the 16 covenant’s protection as follows:

17 Employee agrees that during Employee’s employment with the 18 Company and for a period of twelve (12) months immediately following the date of Employee’s termination from 19 employment for any reason (the “Non-Solicit Restricted 20 Period”), other than in connection with Employee’s duties for the Company: . . . Employee shall not directly or indirectly 21 solicit business from or interfere with, or attempt to solicit 22 business from or interfere with, any actual or prospective customer, service provider, vendor, or supplier of the 23 Company or any affiliate of the Company with whom the 24 Company or any affiliate did business or who the Company or any affiliate solicited within the eighteen (18) months 25 prior to Employee’s termination from employment with 26 3 The Court assumes the following enforceability argument made by Defendant Brosa 27 pertains only to the non-solicitation covenant of the Brosa Agreement (Doc. 1-2 ¶ 2(b)) and not to the non-recruitment covenant (Doc. 1-2 ¶ 2(c)). The Court reaches this 28 assumption because Defendant Brosa cites paragraph 2(b) in his Motion to Dismiss and Reply thereto, but not once does he cite paragraph 2(c). (Doc. 25 at 6–7; Doc. 50 at 4–5.) 1 the Company, and (1) who or which Employee contacted, called on, serviced, or did business with, on behalf of the 2 Company or any affiliate of the Company, during 3 Employee’s employment with the Company, or (2) about whom Employee received Confidential Information. 4

5 (Doc. 1-2 ¶ 2(b)(i) (emphasis added).) The plain language of this covenant identifies two 6 qualifications of the protected customer class. First, the customer must have an actual or 7 prospective relationship with Plaintiffs during the eighteen months prior to Defendant 8 Brosa’s termination date. Second, the customer must have had contact with Defendant 9 Brosa during his employment. 10 As Plaintiffs point out, Arizona courts have found that a non-solicitation covenant 11 limited “to only those clients that the employee had relationships with during the period of 12 employment is not unreasonable or oppressive.” Colwell Consulting LLC v. Papageorge, 13 No. 2:24-cv-01824-JCG, 2024 U.S. Dist. LEXIS 144503, at *16 (D. Ariz. Aug. 14, 2024) 14 (citing Olliver, 148 Ariz. at 531–32). However, Arizona Courts have also found that an 15 employer has no legitimate interest in protecting former or potential business relationships. 16 Hilb, 190 Ariz. at 216; Orca I, 233 Ariz. at 418. Here, the non-solicitation covenant 17 expressly includes prospective customers that were merely “solicited” by Plaintiffs. It also 18 includes customers who “did” business with Plaintiffs within the eighteen months prior to 19 Defendant Brosa’s termination. The use of past tense expands the class of customers to 20 include former customers. The inclusion of prospective and former customers is clearly 21 disfavored under Arizona law and is unreasonable. 22 Plaintiffs urge the Court to strike these unreasonable portions under the blue pencil 23 doctrine. (Doc. 36 at 16 n.4; Doc. 1-2 ¶ 5.) If the Court were to sever the offending portions 24 stating “or prospective” and “with whom the Company or any affiliate did business or who 25 the Company or any affiliate solicited within the eighteen (18) months prior to Employee’s 26 termination from employment with the Company,” the language that remains would 27 prohibit Defendant Brosa from soliciting “any actual customer, service provider, vendor, 28 or supplier of the Company or any affiliate of the Company” within the one-year period 1 after his termination. This alteration expands the covenant’s scope beyond what the parties 2 originally contemplated. What once prohibited solicitation of only those customers that 3 existed in the eighteen months prior to Defendant Brosa’s termination would now include 4 customers that formed business ties with Plaintiffs after Defendant Brosa’s termination 5 date. Such a significant change amounts to judicial reformation that this Court cannot 6 effect. See Varsity Gold, Inc. v. Porzio, 202 Ariz. 355, 358 (Ariz. App. 2002). 7 Because the non-solicitation covenant is unenforceable on its face and incurable, 8 the Court will dismiss Count Four pertaining only to the non-solicitation covenant4 with 9 prejudice. 10 3. Breach 11 The remaining covenants at issue are the non-recruitment covenant in the Brosa 12 Agreement (Count Four), and the confidentiality covenant in the Tankersley Agreement 13 (Count Six). In Count Four, Plaintiffs claim that Defendant Brosa violated the non- 14 recruitment covenant that prohibited Defendant Brosa from actual or attempted 15 solicitation, recruitment, or encouragement of Plaintiffs’ employee to terminate 16 employment with Plaintiffs during the one-year period after Defendant Brosa’s 17 termination. (Doc. 1-2 ¶ 2(c); Compl. ¶ 154–55, 157.) Defendant Brosa argues that there 18 are insufficient factual allegations identifying a breach of this covenant. (Doc. 25 at 8–9.) 19 But Plaintiffs recount that Defendant Brosa sent an airline ticket to Plaintiffs’ sales 20 executive from an airport located less than twenty minutes from Defendant Apex’s 21 headquarters. (Compl. ¶ 92.) This contact occurred in June 2025 (id.), which falls within 22 the one-year restriction period from the date of Defendant Brosa’s termination. Later, the 23 executive terminated her employment with Plaintiffs. (Id.) A reasonable inference can be 24 made that Defendant Brosa’s actions were, at minimum, an attempt to encourage Plaintiffs’ 25 employee leave her employment. When taken as true, these allegations establish breach of 26 the non-recruitment covenant under Count Four. 27 . . .

28 4 The non-recruitment covenant in the Brosa Agreement (Doc. 1-2 ¶ 2(c)) was not challenged by Defendant Brosa as unenforceable. 1 In Count Six, Plaintiffs claim that Defendant Tankersley violated the confidentiality 2 covenant that prohibited Defendant Tankersley from using or disclosing “Confidential 3 Information” to others outside the Company. (Doc. 1-1 ¶ 4; Compl. ¶ 183.) Confidential 4 Information included “business systems and computer programs.” (Doc. 1-1 ¶ 3; Compl. 5 ¶ 62.) Defendant Tankersley contends that there are insufficient factual allegations 6 identifying a breach of this covenant. (Doc. 28 at 11.) But Plaintiffs allege Defendant 7 Tankersley breached those contractual terms by “using and/or disclosing [Plaintiffs’] 8 computer codes, processes, techniques . . . to develop copies of [Plaintiffs’] customer- 9 specific applications for Apex.” (Compl. ¶ 188.) These facts, while merely allegations at 10 this stage, are sufficient to identify a breach of the Tankersley Agreement under Count Six. 11 4. Damages 12 In each breach of contract claim, Plaintiffs allege in a copy-and-paste fashion that 13 they suffered “irreparable injury, in addition to monetary damages” because of the breach. 14 (Compl. ¶¶ 161, 192.) Defendants Brosa and Tankersley argue that these allegations are 15 illusory, not grounded in facts, and not connected to the alleged breach. (Doc. 25 at 11; 16 Doc. 28 at 11–12.) In response, Plaintiffs argue that they have sufficiently pled, “among 17 other things, irreparable harm,” which Plaintiffs contend is a cognizable type of damage in 18 a breach of contract claim. (Doc. 36 at 16–17; Doc. 38 at 15.) 19 “Arizona has long held that damages for breach of contract are those damages which 20 arise naturally from the breach itself or which may reasonably be supposed to have been 21 within the contemplation of the parties at the time they entered the contract.” All Am. Sch. 22 Supply Co. v. Slavens, 125 Ariz. 231, 233 (Ariz. 1980). An irreparable harm is one that 23 cannot be adequately remedied by monetary damages and can take many forms. See, e.g., 24 Toma v. Fontes, 258 Ariz. 109, 127 (Ariz. App. 2024); Best W. Int’l Inc. v. Doe, 2006 U.S. 25 Dist. LEXIS 77942, at *17–18 (D. Ariz. Oct. 24, 2006) (holding that destruction of 26 corporate goodwill may be irreparable); Phx. Orthopaedic Surgeons v. Peairs, 164 Ariz. 27 54, 59 (Ariz. App. 1989) (“Once a protectable interest is established, irreparable injury is 28 presumed to follow if the interest is not protected.”). 1 Here, Plaintiffs expressly allege that each covenant protects “legitimate competitive 2 advantages, relationships with customers and employees, trade secrets and confidential 3 information, and other valid business interests” and breach creates “irreparable injury.” 4 (Compl. ¶¶ 155, 161, 186, 192; see also Doc. 1-2 ¶ 2(e)(1).) Both the Brosa and Tankersley 5 Agreements contemplate that damages for breach may encompass equitable remedies to 6 protect Plaintiffs’ business interests. (See Doc. 1-1 at 3; Doc. 1-2 at 6; Compl. ¶¶ 96–97.) 7 These facts and the plain language of the Agreements are sufficient to plead damages at 8 this stage because they identify a harm arising from breach that is both legally cognizable 9 and contemplated by the parties in the Agreements. Counts Four (as related to the non- 10 recruitment covenant) and Six satisfy the pleading standard and will not be dismissed. 11 C. Count Eight: Tortious Interference with Contract or Expectancy 12 Plaintiffs bring a state law tortious interference claim against Defendant Apex. 13 (Compl. ¶¶ 201–07.) The claim asserts two forms of interference: (1) interference with 14 Plaintiffs’ business expectancies and contracts with current or prospective customers; and 15 (2) interference with Plaintiffs’ contracts with its employees. (Id.) Defendant Apex argues 16 that this claim should be dismissed because Plaintiffs’ allegations amount to nothing more 17 than a recitation of the elements of the claim and lack specificity. (Doc. 22 at 8–9.) 18 To plead a claim for tortious interference with contractual relations, the plaintiff 19 must allege the following: “(1) existence of a valid contractual relationship, (2) knowledge 20 of the relationship on the part of the interferer, (3) intentional interference inducing or 21 causing a breach, (4) resultant damage to the party whose relationship has been disrupted, 22 and (5) that the defendant acted improperly.” Safeway Ins. Co., Inc. v. Guerrero, 210 Ariz. 23 5, 9 (Ariz. 2005). Improper conduct is the crux of this claim, and “a competitor does not 24 act improperly if his purpose at least in part is to advance his own economic interests.” Bar 25 J Bar Cattle Co. v. Pace, 158 Ariz. 481, 483 (Ariz. App. 1988). 26 Plaintiffs’ allegations ultimately fail to satisfy the third element that requires 27 Defendant Apex to intentionally interfere with Plaintiffs’ contractual relationships. First, 28 Plaintiffs allege that Defendant Apex knew of and intentionally interfered with Plaintiffs’ 1 customer relationships “by misusing BVTA’s software programs, techniques, processes 2 and other confidential and proprietary information . . . to cause customers to select Apex’s 3 proposals over those submitted by BVTA.” (Compl. ¶ 205.) This allegation is conclusory 4 and lacks reasoning and factual support. For example, Plaintiffs do not allege a higher 5 incidence—or even a single incident—of losing bids or customers cancelling existing 6 contracts in the time that Defendant Apex supposedly interfered with those relationships. 7 Second, Plaintiffs allege that Defendant Apex knew of and intentionally interfered 8 with Plaintiffs’ employee relationships “by inducing them to commit material breaches of 9 contract.” (Id. ¶ 204). Plaintiffs advance the following factual basis to support this 10 allegation: (1) Defendant Brosa breached the non-recruitment covenant by sending “airline 11 ticket information from his personal Gmail account to the work email account of a BVTA 12 sales executive” (id. ¶ 92); (2) Defendant Brosa breached the confidentiality covenant by 13 extracting numerous files and contacts that belonged to Plaintiffs (id. ¶¶ 66–84); and (3) 14 Defendant Tankersley breached the confidentiality covenant by using or disclosing his 15 knowledge and skills obtained through his employment to make copies of the ProTrack 16 software (id. ¶ 91). These facts, even if they are true, do not establish an inference that 17 Defendant Apex induced Defendants Brosa and Tankersley to breach their contractual 18 obligations to Plaintiffs. For instance, the Court already found no allegations suggesting 19 that Defendant Apex knew of, let alone induced, Defendants Brosa and Tankersley’s use 20 or disclosure of Plaintiffs’ confidential or trade secret information. As for Defendant 21 Brosa’s alleged breach of the non-recruitment covenant,5 the fact that Defendant Brosa 22 used his personal email account indicates that Defendant Apex was not involved in, much 23 less induced, that specific communication. Finally, the fact that Defendants Brosa and 24 Tankersley terminated their employment with Plaintiffs and now work for Defendant Apex 25 is insufficient to allege or infer inducement. See, e.g., Solar Optimum Inc., 2024 U.S. Dist. 26 LEXIS 80983, at *3, 24 (allegations that an executive of the defendant company sent a 27 5 The Court does not consider Plaintiffs’ responsive remarks that the sales executive now 28 works for Defendant Apex because that allegation does not appear on the face of the Complaint. (Doc. 37 at 8.) 1 non-disclosure agreement to the plaintiff’s employee “to distribute to the other employees 2 they were attempting to hire” were sufficient to plead a tortious interference claim). 3 Because Plaintiffs fail to allege the requisite elements of a tortious interference 4 claim with respect to its customer and employee relationships, the Court will dismiss Count 5 Eight. This pleading defect may be cured by amendment, and this Court will grant Plaintiffs 6 leave to do so. Lopez, 203 F.3d at 1130. 7 D. Count Nine: Unfair Competition 8 Plaintiffs bring a common law tort claim for unfair competition against all 9 Defendants. (Compl. ¶¶ 208–16.) Unfair competition claims are based on principles of 10 equity and encompasses several tort theories, including trademark infringement, false 11 advertising, and misappropriation. Fairway Constructors, Inc. v. Ahern, 193 Ariz. 122, 124 12 (Ariz. App. 1998). Here, Plaintiffs assert their claim under a theory of misappropriation.6 13 (Compl. ¶¶ 208–16.) 14 Defendant Brosa argues that this claim is preempted by the AUTSA. (Doc. 25 at 15 12.) The AUTSA preempts tort claims that provide a civil remedy for misappropriation of 16 a trade secret, but not for misappropriation of confidential information. A.R.S. § 44-407; 17 Orca II, 236 Ariz. at 181 (“AUTSA does not displace common-law claims based on alleged 18 misappropriation of confidential information that is not a trade secret.”); Joshua David 19 Mellberg LLC, 96 F. Supp. 3d at 963 (permitting the plaintiff to amend a claim of unfair 20 competition based on misappropriation of confidential information). In determining 21 whether Plaintiffs’ tort claim survives the AUTSA’s preemptive force, the Court must 22 identify if any portion of the claim is based on the alleged misappropriation of information 23 distinguishable from trade secrets. 24 . . . 25 6 The Arizona Supreme Court has declined to recognize a common law claim for unfair 26 competition based on misappropriation. Orca II, 236 Ariz. at 184. In the absence of a state pronouncement otherwise, district courts sitting in Arizona have permitted this claim to 27 proceed. See, e.g., Joshua David Mellberg LLC, 96 F. Supp. 3d at 963; Athene Annuity & Life Co. v. Athene Grp. Ltd., No. CV-24-01120-PHX-JZB, 2025 U.S. Dist. LEXIS 165062, 28 at *15 n.7 (D. Ariz. Jul. 18, 2025); Solar Optimum Inc., 2024 U.S. Dist. LEXIS 80983, at *29 1 Plaintiffs argue that their unfair competition claim is based on the misappropriation 2 of “confidential information,” not trade secrets. Such confidential information includes 3 “customer specific project management software applications.” (Doc. 36 at 17.) But that 4 category of information was successfully pled as a trade secret, as discussed infra. Nowhere 5 in their Complaint or responsive briefing do Plaintiffs distinguish what other information 6 is “confidential” but not a “trade secret.” In fact, Plaintiffs appear to allege that all their 7 confidential information are trade secrets, making it implausible that Defendant Brosa 8 could misappropriate one without the other. (Compl. ¶ 100.) As currently pled, the unfair 9 competition claim against Defendant Brosa is preempted under AUTSA. 10 Neither Defendants Apex nor Tankersley argue preemption. Rather, they argue that 11 Plaintiffs fail to allege specific conduct supporting misappropriation of Plaintiffs’ 12 confidential information. (Doc. 22 at 11; Doc. 28 at 12.) In considering these arguments, 13 the Court will apply the same legal definition of “misappropriation” as set forth in Counts 14 One and Two under the DTSA and AUTSA.7 As to Defendant Tankersley, the Court 15 already found that Plaintiffs alleged sufficient facts that he misappropriated Plaintiffs’ 16 customer-specific computer software and harmed Plaintiffs. (See Compl. ¶¶ 57, 91, 93– 17 94.) These factual assertions form the basis for Plaintiffs’ unfair competition claim (Id. 18 ¶ 209) and are similarly sufficient to allege misappropriation. However, Plaintiffs 19 allegations fall short when it comes to Defendant Apex. Plaintiffs allege no specific 20 conduct or facts suggesting that Defendant Apex itself is currently misappropriating, or has 21 misappropriated, any of Plaintiffs’ confidential information. For these reasons, the Court 22 will dismiss Count Nine as to Defendant Apex. Because the pleading defects can be cured 23 with additional, well-pled facts, the Court will grant Plaintiffs leave to amend Count Nine 24 against Defendants Brosa and Apex only. Lopez, 203 F.3d at 1130. 25 . . .

26 7 Defendants Apex and Tankersley do not suggest, and this Court is not aware of, a unique legal definition or standard for misappropriation in the common-law unfair competition 27 context. See, e.g., Joshua David Mellberg LLC, 96 F. Supp. 3d at 961, 962–63 (declining to identify a standard for misappropriation in an unfair competition claim); Athene Annuity 28 & Life Co., 2025 U.S. Dist. LEXIS 165062, at *15 n.7 (noting that the Arizona Supreme Court declined to recognize unfair competition claims based on misappropriation). 1 IV. CONCLUSION 2 The Court will dismiss—and grant Plaintiffs leave to amend—Counts One, Two 3 and Eight against Defendant Apex, Count Five against Defendant Brosa, and Count Nine 4 against Defendants Brosa and Apex. Count Three and the portion of Count Four pertaining 5 to the non-solicitation covenant will be dismissed with prejudice and without leave to 6 amend. The claims remaining at this stage include Counts One and Two against Defendants 7 Tankersley and Brosa, Count Four against Defendant Brosa as it pertains to the non- 8 recruitment covenant, Count Six against Defendant Tankersley, Count Seven against 9 Defendant Brosa, and Count Nine against Defendant Tankersley. 10 No later than fourteen days from the date of this Order, Plaintiffs may file an amended 11 complaint and a separate Notice of Filing Amended Complaint with an attached redlined 12 copy showing the changes between the Complaint and the amendment. No new claims may 13 be added to an amendment absent leave of court pursuant to Federal Rule of Civil Procedure 14 15 and Local Rule 15.1. If Plaintiffs do not file an amended complaint in the time 15 prescribed, the Clerk of Court is directed to dismiss Defendant Apex as a party to this 16 matter without further order of the Court. 17 Plaintiffs’ Motion for Preliminary Injunction (Doc. 17) remains pending. The Court 18 will set a hearing on Plaintiffs’ Motion for Preliminary Injunction, and the parties shall 19 abide by the instructions set forth in greater detail below. 20 IT IS THEREFORE ORDERED granting Defendant Apex Imaging Services 21 Incorporated’s Motion to Dismiss (Docs. 21, 22). Counts One, Two, Eight, and Nine 22 against Defendant Apex will be dismissed. 23 IT IS FURTHER ORDERED denying Defendant Todd Tankersley’s Motion to 24 Dismiss (Docs. 27, 28). 25 IT IS FURTHER ORDERED granting in part and denying in part Defendant 26 Blake Brosa’s Motion to Dismiss (Docs. 24, 25). Count Three, Five, Nine, and the portion 27 of Count Four pertaining to the non-solicitation covenant against Defendant Brosa will be 28 dismissed. 1 IT IS FURTHER ORDERED that, no later than fourteen days from the date of this 2 Order, Plaintiffs may file an amended complaint and a separate Notice of Filing Amended 3 Complaint with an attached redlined copy showing the changes between the Complaint and 4 the amendment. Plaintiffs may only amend Counts One, Two, and Eight as to Defendant 5 Apex, Count Five as to Defendant Brosa, and Count Nine as to Defendants Apex and Brosa. 6 No new claims may be added to an amendment absent leave of court pursuant to Federal 7 Rule of Civil Procedure 15 and Local Rule 15.1. 8 IT IS FURTHER ORDERED directing the Clerk of Court to dismiss Defendant 9 Apex as a party to this matter if Plaintiffs do not file an amended complaint within fourteen 10 days from the date of this Order. 11 IT IS FURTHER ORDERED setting a hearing on Plaintiffs’ Motion for 12 Preliminary Injunction (Doc. 17) on January 27, 2026, at 2:00 PM (Arizona time), before 13 District Judge John J. Tuchi in Courtroom 505, Sandra Day O’Connor Federal Courthouse, 14 401 West Washington Street, Phoenix, Arizona 85003. Each side will have two hours— 15 that is, two hours for Plaintiffs collectively and two hours for Defendants collectively—for 16 their presentation to the Court, including all evidence and legal argument. 17 IT IS FURTHER ORDERED that the parties shall jointly prepare and file a pre- 18 hearing statement by January 20, 2026, setting forth the following information with regard 19 to their presentation on Plaintiffs’ Motion for Preliminary Injunction (Doc. 17): 20 A. WITNESSES 21 Because the parties rely on witness statements in their briefing, no party shall 22 conduct direct examination of witnesses at the hearing, but rather the Court will rely on 23 declarations and affidavits the parties have filed in support of their briefing as of September 24 12, 2025, for direct testimony. However, the opposing party may conduct cross- 25 examination of any witness. Accordingly, in the joint pre-hearing statement, the parties 26 shall separately list the names of their witnesses upon which they rely, the witnesses’ 27 respective addresses, and whether a fact or expert witness. 28 . . . 1 The parties shall adhere to the following provision and include it in this section of 2|| the joint pre-hearing statement: “Each party understands that it is responsible for ensuring 3|| that the witnesses on whose testimony the party will rely are subpoenaed. Each party 4|| further understands that any witness whose testimony is offered to the Court shall be listed || on that party’s list of witnesses, and that party cannot rely on any witness having been listed or subpoenaed by another party.” 7 The party conducting cross-examination of the opposing party’s witnesses at the 8 hearing shall determine which witnesses it calls to cross-examine. Accordingly, in the joint ? pre-hearing statement, each party shall separately list the opposing party’s witnesses it 10 plans to cross-examine and the order in which it will cross-examine them. The time taken to cross-examine a witness counts against the side conducting the cross-examination. 12 B. EXHIBITS 1S The Court will rely on the exhibits submitted with the parties’ briefs as of 4 September 12, 2025. No additional exhibits will be admitted. The parties shall list any objections it has to the opposing party’s exhibits in the pre-hearing statement. The parties shall adhere to the following provision and include it in this section of the joint pre-hearing 13 statement: “Each party hereby acknowledges that, by signing this joint pre-hearing 19 statement, any objections not specifically raised herein are waived.” 20 C. PROPOSED BOND AMOUNT 4 The parties shall each provide a proposed bond amount under Federal Rule of Civil 9 Procedure 65(c) in the event the Court grants Plaintiffs’ Motion for Preliminary Injunction. 3 Each party’s proposed bond amount should be listed in the pre-hearing statement. 14 Dated this Ist day of December, 2025. CN

26 Ui State isirict Judge 27 28

-27-