The Phoenix Company, Inc. v. Castro-Badillo

District Court, D. Puerto Rico·Decided November 25, 2024·No. 3:23-cv-01371·Unknown

Opinion

IN THE UNITED STATES DISTRICT COURT FOR THE DISTRICT OF PUERTO RICO

THE PHOENIX COMPANY, INC., Plaintiff

v. CIVIL NO. 23-1371 (RAM) JAVIER CASTRO-BADILLO; ROCK SOLID TECHNOLOGIES, INC.,

Defendants.

OPINION AND ORDER RAÚL M. ARIAS-MARXUACH, United States District Judge I. FACTUAL AND PROCEDURAL BACKGROUND On July 17, 2023, Plaintiff The Phoenix Company, Inc. (“Plaintiff” or “Phoenix”) filed a lawsuit against Rock Solid Technologies, Inc. (“Rock Solid”) and Javier Castro-Badillo (“Castro-Badillo”) (collectively “Defendants”). (Docket No. 1). On December 7, 2023, Plaintiff filed an Amended Complaint alleging Defendants violated the Defend Trade Secrets Act, 18 U.S.C. § 1836., as well as the Computer Fraud and Abuse Act, 18 U.S.C. § 1830 (“the CFAA”), as well as Puerto Rico law. (Docket No. 19 ¶¶ 1.1, 7.2, 8.5, 9.3). Phoenix claims Defendants misappropriated a trade secret and accessed its computers and software, Monet GFS, without authorization. Id. On August 9, 2024, the Court issued an Opinion and Order granting co-defendant Rock Solid’s Motion to Dismiss Amended Complaint (the “Motion to Dismiss”) and thereby dismissing all federal law claims against Rock Solid.1 (Docket No. 44). Specifically, the Court concluded that Plaintiff failed to: (1) adequately allege facts showing there was a trade secret; and (2) adequately allege a computer fraud claim under 18 U.S.C. § 1030.

Id. The Court subsequently issued an order to show cause instructing Plaintiff “show cause as to (1) why the claims against Javier Castro-Badillo should not be dismissed in light of the Court's Opinion and Order at Docket No. 44; and (2) why the Court should not decline to exercise supplemental jurisdiction over the Puerto Rico law claims against all Defendants.” (Docket Nos. 53 and 54).2 Phoenix filed a one paragraph response to the order to show cause merely stating that it “incorporates the reasons stated in opposition to the motion to dismiss [ECF #37] and in support of the motion to amend [ECF#52] as reasons why this Court should not dismiss this action against Defendant Javier Castro Badillo.”

(Docket No. 53). II. LEGAL STANDARD Fed. R. Civ. P. 12(b)(6) provides for the dismissal of a complaint that “fails to state a claim upon which relief can be

1 The Court incorporates by reference that Opinion and Order in its entirety for the purposes of the present Motion.

2 Plaintiff failed to comply with the order to show cause at Docket No. 53 and the Court sua sponte granted Plaintiff an extension at Docket No. 54. granted.” Under Rule 12(b)(6), a plaintiff must plead enough facts to state a claim that is “plausible” on its face, and the “[f]actual allegations must be enough to raise a right to relief above the speculative level . . . on the assumption that all the allegations in the complaint are true (even if doubtful in fact).”

Bell Atlantic Corp. v. Twombly, 550 U.S. 544, 555 (2007) (citations omitted). “[A] plaintiff’s obligation to provide the ‘grounds’ of his ‘entitle[ment] to relief’ requires more than labels and conclusions, and a formulaic recitation of the elements of a cause of action will not do.” Id. Further, a complaint will not stand if it offers only “naked assertion[s] devoid of further factual enhancements.” Ashcroft v. Iqbal, 556 U.S. 662, 678 (2009) (internal quotation marks and citation omitted). To determine whether a complaint has stated a plausible, non-speculative claim for relief, courts must treat non-conclusory factual allegations as true. See Nieto-Vicenty v. Valledor, 984 F. Supp. 2d 17, 20 (D.P.R. 2013) (citations omitted). In certain circumstances, “sua

sponte dismissals of complaints under Rule 12(b)(6) ... are appropriate,” under the condition that “the parties have been afforded notice and an opportunity to amend the complaint or otherwise respond.” Chute v. Walker, 281 F.3d 314, 319 (1st Cir. 2002) (quoting Futura Dev. of P.R., Inc. v. Estado Libre Asociado de P.R., 144 F.3d 7, 13–14 (1st Cir.1998)). III. DISCUSSION A. Plaintiff failed to adequately allege the existence of a trade secret.

As discussed at length in the Opinion and Order at Docket No. 44, Phoenix has failed to plead sufficient factual allegations to establish that it was plausibly in possession of a trade secret capable of being misappropriated by Castro-Badillo. “It is hornbook law that ‘the parties and the court cannot accurately decide the question of whether a trade secret exists without first understanding what precisely is asserted as a secret.’” Sutra, Inc. v. Iceland Exp., ehf, 2008 WL 2705580, at *3 (D. Mass. 2008) (quoting Charles Tait Graves and Brian D. Range, Identification of Trade Secret Claims in Litigation: Solutions for a Ubiquitous Dispute, 5 Nw. J. Tech. & Intell. Prop. 68, 69 (2006)); see also Mallet and Co. Inc. v. Lacayo, 16 F.4th 364, 380-81 (3d Cir. 2021) (explaining that “each . . . element[] is predicated on an adequate identification of what the plaintiff contends to be its trade secret”). The First Circuit has interpreted sufficient specificity to mean the plaintiff has “separate[d] the purported trade secrets from the other information . . . that was known to the trade.” Allstate Ins. Co. v. Fougere, 79 F.4th 172, 197 (1st Cir. 2023) (quoting TLS Mgmt. & Mktg. Servs., LLC, 966 F.3d 46, 49 (1st Cir.

2020)) (internal quotations and alterations omitted) (emphasis added). Phoenix’s factual allegations do not distinguish between matters of general knowledge in the trade and the particularities that make its software, Monet GFS, a trade secret. Phoenix alleges “[o]ne of the most innovative and distinct aspects of Monet GFS is the data storage design, which stores the information in a very

efficient manner.” (Docket No. 19 ¶ 3.3). Plaintiff claims the data storage design and the access codes constitute the trade secret that was misappropriated. Id. This fails to adequately describe any characteristics of the software that are distinguishable from that which is within the general or special knowledge of persons skilled in the trade. See Allstate, 79 F.4th at 197; TLS Mgmt., 966 F.3d at 49. Rather than alleging that its efficient data storage design is unique to its software and is not common among companies that provide similar services, Phoenix only asserts that the access codes for each municipality are different and “the software is updated and changes.” 3 (Docket No. 37 at 4). However, although the

access codes themselves are secret, they are not a “trade secret.” Courts in other circuits have held that passwords enabling access to confidential information are not themselves trade secrets unless they are “the product of any special formula or algorithm that it developed[.]” State Analysis, Inc. v. Am. Fin. Services

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

The Phoenix Company, Inc. v. Castro-Badillo, (prd 2024).

The Phoenix Company, Inc. v. Castro-Badillo (The Phoenix Company, Inc. v. Castro-Badillo) — published by Counsel Stack Legal Research, free access to 12M+ legal documents.

Related

Carnegie-Mellon University v. Cohill
484 U.S. 343 (Supreme Court, 1988)
Bell Atlantic Corp. v. Twombly
550 U.S. 544 (Supreme Court, 2007)
Ashcroft v. Iqbal
556 U.S. 662 (Supreme Court, 2009)
Chute v. City of Cambridge
281 F.3d 314 (First Circuit, 2002)
Redondo Construction Corp. v. Izquierdo
662 F.3d 42 (First Circuit, 2011)
LVRC HOLDINGS LCC v. Brekka
581 F.3d 1127 (Ninth Circuit, 2009)
State Analysis, Inc. v. American Financial Services Assoc.
621 F. Supp. 2d 309 (E.D. Virginia, 2009)
Wilber v. Curtis
872 F.3d 15 (First Circuit, 2017)
Sexual Minorities Uganda v. Lively
899 F.3d 24 (First Circuit, 2018)
Zell v. Ricci
957 F.3d 1 (First Circuit, 2020)
TLS Mgmt. and Mktg. Ser. LLC v. Rodriguez-Toledo
966 F.3d 46 (First Circuit, 2020)
Nieto-Vicenty v. Valledor
984 F. Supp. 2d 17 (D. Puerto Rico, 2013)
Allstate Insurance Company v. Fougere
79 F.4th 172 (First Circuit, 2023)