1. Introduction
This decision addresses two closely connected questions in software trade-secret litigation: what constitutes actionable “use” of confidential technology, and how courts should evaluate documents incorporated into a complaint when the parties disagree about their meaning. The Second Circuit held that allegations of exploiting protected software information to develop, improve, and market competing products can plausibly establish misappropriation without allegations of exact copying. It also held that a court cannot dismiss such a complaint by choosing the defendant’s interpretation of internal communications over a plausible interpretation supporting the plaintiff.
The parties and their commercial relationship
SS&C Technologies Holdings, Inc., and its subsidiary Advent Software, Inc., collectively “SS&C,” own Geneva, portfolio accounting software used by financial institutions. SS&C alleged trade-secret protection over specified aspects of Geneva, including its executable software, integration layer, application programming interfaces, and data model.
Arcesium LLC obtained access to Geneva under a 2015 Hosted Reseller Agreement. That agreement permitted Arcesium to sublicense Geneva and provide related services to customers. It restricted Arcesium’s use of confidential information to authorized contractual purposes and prohibited using Geneva to develop competing products.
According to the complaint, Arcesium nevertheless used Geneva’s confidential technology to develop Trinity, a competing portfolio accounting platform. SS&C also alleged that Arcesium developed Nautilus, an interface enabling continued connectivity with Geneva after Arcesium’s contractual access had ended.
How the dispute reached the court
After the reseller agreement expired in January 2020, the parties disputed Arcesium’s limited rights to continue serving existing Geneva customers. Arcesium brought an antitrust and contract action against SS&C. Documents disclosed during that litigation supplied the basis for SS&C’s subsequent trade-secret allegations.
In the present action, the district court concluded that SS&C adequately alleged the existence of trade secrets but inadequately alleged their misappropriation. It dismissed the complaint on December 20, 2024. SS&C appealed, arguing that its allegations plausibly established misuse and that the district court had improperly resolved factual disputes.
3. Analysis: Legal Reasoning
A. The statutory framework
The Defend Trade Secrets Act of 2016 (“DTSA”), 18 U.S.C. § 1836 et seq., creates a federal civil remedy for trade-secret misappropriation. The opinion organized its analysis around two questions: whether SS&C plausibly alleged that it possessed trade secrets, and whether Arcesium plausibly misappropriated them.
Section 1839(3) broadly accommodates technical and commercial information, including programs, code, methods, processes, and compilations. But information does not become a trade secret merely because it falls within one of those categories. Its owner must take reasonable measures to preserve secrecy, and the information must derive independent economic value from being neither generally known nor readily ascertainable through proper means.
The statute also distinguishes wrongful exploitation from legitimate competition. Its definition of improper means includes breaches of duties to maintain secrecy, while expressly excluding reverse engineering, independent derivation, and other lawful acquisition methods. The decision therefore does not establish ownership over ordinary software functionality or prohibit independently developed competing products.
B. Identifying software secrets without publicly disclosing every detail
The court rejected Arcesium’s contention that the complaint identified only excessively broad categories. SS&C did more than invoke labels such as “software” or “data model”: it described how Geneva stored investment and transaction information, how its database operated, and how its integration layer allowed users to input information, extract data, execute queries, and connect other systems.
Those descriptions supplied boundaries sufficient to notify Arcesium of the information at issue. The governing approach is contextual, not a rigid requirement that every technical detail appear in the complaint.
This distinction is important. A plaintiff must identify its asserted secrets with sufficient specificity, but the court declined to impose a generalized heightened pleading rule. Notice and plausibility—not exhaustive public disclosure—controlled the assessment.
C. Confidential licensing can preserve trade-secret protection
Arcesium argued that Geneva’s availability to licensed users undermined its secrecy. The court rejected the premise that disclosure to third parties necessarily defeats protection. Commercial software often must be shared with customers to generate revenue; treating every licensed disclosure as public disclosure would substantially undermine trade-secret protection for such products.
The complaint alleged restricted access, valid credentials, and confidentiality and nondisclosure obligations imposed before disclosure. Those measures plausibly satisfied the statutory requirement in the circumstances alleged.
The holding is not that a confidentiality clause invariably establishes reasonable protection. Rather, the adequacy of safeguards depends on the information, the manner of access, and the surrounding circumstances. At this stage, SS&C’s allegations were sufficient.
D. Economic value required factual support, not statutory repetition
The court recognized that SS&C’s assertion that its information “derives independent economic value” largely repeated statutory language. Standing alone, that statement would not establish plausibility.
The complaint, however, also alleged decades of development, investment of hundreds of millions of dollars, distinctive analytical capabilities, and confidential methodologies underlying Geneva’s functionality. Taken together, those allegations supported an inference that confidential technical knowledge supplied a competitive advantage.
The reasoning does not equate development expense with trade-secret status. Investment mattered because it was connected to confidential methods and commercially valuable capabilities, rather than offered as an independent substitute for secrecy-derived value.
E. “Use” includes exploiting knowledge to improve or accelerate development
The opinion’s principal substantive clarification concerns the meaning of “use.” Because the DTSA does not define that term, the court considered its ordinary meaning and the broader trade-secret authorities. It endorsed an understanding encompassing exploitation likely to injure the owner or enrich the defendant, including reliance on confidential information to assist or accelerate research and development.
Consequently, a defendant need not reproduce the plaintiff’s product exactly. Protected information may be used as a development shortcut, a source of solutions to technical problems, or a means of creating commercially equivalent capabilities.
SS&C alleged that Arcesium:
- Replicated Geneva’s loader formats, data models, and integration layer in developing Trinity;
- Consulted Geneva’s methods to resolve shortcomings in Arcesium’s own platform;
- Used Geneva’s database schema, data model, and integration layer to develop Nautilus; and
- Marketed Trinity to Geneva customers by promising equivalent functionality.
The complaint further alleged that those activities violated confidentiality and contractual use restrictions. Although Arcesium originally received access through a legitimate licensing relationship, that access did not authorize every subsequent exploitation of the information. The court treated the alleged contractual and confidentiality breaches as sufficient, at the pleading stage, to support the asserted wrongful use.
Importantly, the court did not hold that every contractual breach constitutes trade-secret misappropriation. The alleged conduct concerned exploitation of identified confidential technical information outside the purposes for which access had been granted.
F. The allegations formed a cumulative factual account
The court assessed the complaint as a whole. Direct allegations of use were reinforced by circumstances suggesting that Arcesium had obtained a development advantage: Trinity’s allegedly accelerated completion, the shorter-than-projected customer transition, promises of Geneva-equivalent features, and internal discussions about avoiding references to Geneva in technical requirements.
No individual circumstance was declared independently sufficient. Rapid development or similar functionality could have innocent explanations. Their significance lay in their combination with allegations identifying particular secrets, access to those secrets, and unauthorized exploitation.
The court thus applied plausibility rather than requiring SS&C to prove its factual theory before discovery and adjudication. Equally, it did not dispense with the requirement for concrete supporting facts.
G. Incorporated documents do not authorize fact-finding on dismissal
The decisive procedural error concerned Arcesium’s internal documents. Because SS&C incorporated those materials into its complaint, the district court could consider them without treating the motion as an evidentiary trial. But consideration did not mean accepting every assertion within them as true.
A plaintiff may cite an internal email because it contains evidence of access, knowledge, or conduct while disputing the author’s characterization of events. Incorporating that email does not adopt its exculpatory statements.
The Second Circuit also distinguished actual contradiction from competing interpretation. The district court invoked the principle that an incorporated document may control over inconsistent allegations. Here, however, the documents did not themselves contradict SS&C’s allegations; Arcesium offered a different explanation of their meaning.
Selecting that explanation as superior required weighing evidence and resolving factual inferences. That is not the function of a Rule 12(b)(6) motion. The appellate court did not establish SS&C’s interpretation as correct—it held only that the district court could not resolve the dispute against an otherwise plausible complaint at this stage.
H. State-law claims and matters left open
The court applied the same analysis to New York common-law trade-secret misappropriation because its essential requirements—existence of a trade secret and improper use—were materially equivalent for this appeal. Other state-law claims were not before the court.
The court also declined to decide whether additional trade-secret disclosures submitted outside the complaint could properly be considered on dismissal. The complaint itself sufficed. Neither ultimate trade-secret status, actual misappropriation, damages, nor entitlement to injunctive relief was resolved.
5. Potential Impact
Software disputes will not turn solely on copying
The decision strengthens claims alleging that confidential technical knowledge served as a development shortcut. Future plaintiffs may rely on evidence that a competitor used protected methods to avoid experimentation, resolve problems, or accelerate implementation, even where the final code differs. They must still connect those advantages to identifiable trade secrets and wrongful exploitation.
Confidentiality-based licensing remains commercially viable
The opinion rejects a rule that would make customer disclosure inherently incompatible with secrecy. Software providers can plausibly preserve protection while licensing their products under meaningful access and confidentiality restrictions. Conversely, the decision highlights the importance of documenting those restrictions and the purposes for which access is granted.
Mixed reseller-competitor relationships receive closer scrutiny
A business partner may lawfully possess information yet lack permission to deploy it in a competing venture. Companies operating both as licensees and independent developers should distinguish permitted support activities from development work. The opinion creates no mandatory compliance procedure, but its reasoning underscores the practical value of clear contractual boundaries and evidence of independent development.
Document-heavy complaints gain procedural protection, not immunity from dismissal
Plaintiffs frequently must rely on communications written by their opponents. The decision prevents that reliance from automatically converting an opponent’s explanations into binding admissions by the plaintiff. Nevertheless, conclusory allegations remain insufficient, and a genuine documentary contradiction may present a different issue from the interpretive disagreement found here.
Later evidentiary testing remains decisive
On remand, SS&C must establish actual protectable secrets and actual misappropriation. Arcesium remains free to demonstrate independent derivation, lawful acquisition, inadequate secrecy, or an absence of unauthorized use. The court expressly left open the possibility that the action might fail at a later stage.