Unreported / Non-Citable
Background
Computer Sciences Corporation (CSC) developed proprietary life insurance software called VANTAGE-ONE/Wealth Management Accelerator, which performs policy valuations, rate-of-return calculations, and other complex computations. CSC licensed this software to Money Services, Inc. (MSI), a Transamerica subsidiary, under strict confidentiality and nondisclosure agreements. The license permitted MSI to grant third-party access only to authorized service providers bound by similar confidentiality restrictions.
In January 2018, Tata Consultancy Services (TCS) contracted with Transamerica to develop a competing software platform called BaNCS to eventually replace Vantage. TCS’s work required access to Vantage as part of its authorized role as an MSI service provider. In March 2019, CSC employee Ashish Barnwal discovered email communications among TCS and Transamerica employees discussing how Vantage calculates rates of return. CSC alleged these emails evidenced misappropriation—that TCS was disclosing Vantage source code to BaNCS developers to replicate the software’s functionality.
The Court’s Holding
The court denied CSC’s application for a temporary restraining order (TRO), finding CSC failed to establish a substantial likelihood of success on the merits of its trade secret misappropriation claim. Although the court acknowledged that Vantage’s source code and user manual qualified for trade secret protection—CSC took reasonable measures to maintain secrecy through technological controls, access restrictions, confidentiality markings, and nondisclosure agreements—it found CSC had not demonstrated that TCS misappropriated these secrets.
The critical weakness in CSC’s case was the lack of clear evidence of improper acquisition or use. TCS had authorized access to Vantage as an MSI service provider under the existing license agreement. The emails CSC cited as evidence showed discussions about how Vantage performed certain calculations, but CSC provided no evidence that this information was actually shared with BaNCS developers, who TCS stated were located in India and not party to the email chain. CSC’s allegation that employee Yogitha Kiran was a BaNCS developer working to copy Vantage functionality was speculative; TCS affirmatively stated Kiran held no programming role. The email mentioning an “intuitive approach to communicate to the BaNCS team” originated from a Transamerica employee (not a defendant) and could reasonably be interpreted as legitimate discussion of how to ensure consistent calculations during a planned software transition.
The court found itself unable to determine, without clarification of the license agreement’s scope and TCS’s authorized use rights, whether TCS’s conduct violated its confidentiality obligations. CSC provided only conclusory allegations of unfair competition and tortious interference, unsupported by evidence, and thus failed to satisfy the four-element test for preliminary injunctive relief.
Key Takeaways
- Trade secret protection requires both reasonable secrecy measures AND evidence of misappropriation through improper means—authorized access under contract significantly weakens misappropriation claims.
- Ambiguous emails discussing software functionality, without evidence of actual disclosure to competitors or unauthorized copying, are insufficient to establish substantial likelihood of success on a trade secret claim.
- Speculative allegations about an employee’s role or intent cannot substitute for concrete evidence of actual misappropriation in seeking emergency relief.
- At the TRO stage, courts require clear proof, not circumstantial inference; the movant bears the cumulative burden of proving all four preliminary injunction elements.
- License agreements defining authorized use and scope matter critically; plaintiffs must address defendants’ arguments about contractual authorization, not ignore them.
Why It Matters
This decision clarifies the limits of trade secret protection when a licensee’s contractor has authorized access. While trade secret owners can restrict how licensees use proprietary information, they cannot easily obtain emergency relief against licensed service providers engaging in ordinary business communications about the licensed software—especially when the parties dispute whether the conduct falls within authorized scope. The ruling emphasizes that contractual authorization and legitimate business purposes are substantial defenses, not mere technical compliance loopholes.
For companies licensing critical software to third parties, the decision underscores the importance of crystal-clear contractual language restricting specific uses (such as competitive development), coupled with monitoring and documentation of actual misuse. Absent concrete evidence of breach—such as copied source code appearing in competing products or direct evidence that trade secret details reached unauthorized developers—courts will not grant emergency orders based on suspicious emails or speculative inferences about employee roles. The decision also reinforces that service providers with legitimate business reasons to access and discuss licensed software functionality retain significant protection against trade secret claims, provided their use remains within contractual bounds.