Convolve v. Compaq: Trade Secrets

Q: Does signing an NDA automatically protect everything I disclose?

No. Convolve holds the opposite. If the agreement specifies how information becomes "Confidential Information" (for example, by marking or by a follow-up writing), then information disclosed without following those steps may fall outside the protected category entirely.

The Federal Circuit held that a disclosing party who ignored its NDA's written-designation protocol lost trade-secret protection at the moment of disclosure.

Convolve, Inc. v. Compaq Computer Corp., No. 2012-1074 (Fed. Cir. July 1, 2013), is a nonprecedential opinion that has nonetheless become required reading for anyone who drafts or relies on a non-disclosure agreement. On appeal from the Southern District of New York (No. 00-CV-5141, Daniels, J.), the Federal Circuit affirmed summary judgment against Convolve on its trade-secret misappropriation claims, holding that when a party promises in an NDA to confirm confidentiality in a particular way, and then does not, the information it disclosed is not confidential, and trade-secret protection evaporates at the instant of disclosure.

The lesson is uncomfortable for technology owners who treat an executed NDA as a self-executing shield. Here the agreement did precisely the opposite of what its drafters presumably intended: it became the instrument by which the secret was lost.

At a glance

Case: Convolve, Inc. v. Compaq Computer Corp., No. 2012-1074 (Fed. Cir.)
Decision: Opinion affirming summary judgment in relevant part, July 1, 2013 (nonprecedential)
Court below: S.D.N.Y., No. 00-CV-5141 (Daniels, J.)
Subject matter: Vibration-reduction and disk-drive seek technology (“Quick and Quiet”); licensing negotiations with Compaq and component supplier Seagate
Governing standards: Trade-secret misappropriation; the parties’ NDA defined what qualified as protected “Confidential Information”
Holding: Where the NDAs required that orally or visually disclosed information be confirmed confidential in a follow-up writing (the Convolve-Seagate NDA set a twenty-day window), Convolve’s failure to follow that protocol meant the disclosures were not confidential under the agreements, and, under California law, no separate duty of confidentiality could be implied to fill the gap

The disclosures and the protocol the parties chose

In August 1998 Convolve and Compaq signed an NDA in advance of licensing talks over Convolve’s input-shaping technology for reducing vibration and acoustic noise in hard-disk drives. Compaq did not make its own disk drives; it bought them from suppliers including Seagate, so Convolve signed a similar NDA with Seagate that October. Each agreement did what careful NDAs do: it set out exactly how a disclosure became protected. Information marked confidential at the time of disclosure was covered. Information disclosed orally or visually (the inevitable mode of a technical presentation) had to be treated or designated as confidential when disclosed and then confirmed in a later written memorandum identifying the specific information claimed as confidential. Paragraph 7 of the Convolve-Seagate NDA put a clock on that step: the confirming writing had to be delivered within twenty days of the disclosure.

Convolve, Compaq, and Seagate met on October 15 and 16, 1998, and afterward the parties acknowledged in writing that the oral disclosures at that meeting were covered. Convolve presented again on February 10 and April 7, 1999. It sent Seagate copies of the February slides and a letter discussing the April demonstration, but it never stated in writing that anything disclosed at or in connection with those later meetings was confidential. That omission is the entire case.

Convolve argued, in substance, that the parties plainly understood the meetings to be confidential, that the relationship was a confidential one, and that the law should protect a secret shared in that setting regardless of paperwork. The Federal Circuit disagreed, not because Convolve’s secrets lacked value, but because the parties had already answered the confidentiality question in their own contract, and the answer they wrote left these disclosures outside the protected category.

Why the contract displaced the common-law backstop

The intuitive move for a trade-secret plaintiff is to argue that, even if the NDA’s designation machinery was not followed, the recipient still owed a duty of confidence arising from the circumstances of the disclosure. Courts in many settings will imply such a duty. The Federal Circuit, applying California law to the claims against Seagate, held that they will not do so when the parties have an express agreement that defines the scope of their confidential relationship and specifies the conditions under which information becomes confidential.

The reasoning is one of contractual displacement. An NDA that says “here is how information becomes confidential between us” is not merely a floor; it can be read as the complete statement of the parties’ mutual obligations on that subject. To imply a broader duty would rewrite the bargain, relieving the disclosing party of the very steps it agreed to take in exchange for the recipient’s agreement to receive the information at all. The designation requirements protect the recipient, too: a company taking in a stream of presentations is entitled to know, by a clear contractual signal, which morsels carry liability and which do not. Allowing an after-the-fact claim that “everything in the room was secret” would defeat that allocation of risk.

The practical consequence is severe. The court treated the protection as lost at the moment of disclosure, not merely unenforceable against Compaq going forward. Once information that should have been designated is disclosed without designation, the disclosure itself is the act that strips secrecy, because nothing in the agreement obligated the recipient to treat undesignated material as secret.

The asymmetry between contract and tort

A useful way to read Convolve is as a study in the gap between a breach-of-contract theory and a misappropriation theory. The two claims sound similar but turn on different facts. A contract claim asks whether the recipient did something the agreement forbade. A misappropriation claim asks, as a threshold matter, whether the plaintiff held a trade secret protected by reasonable measures. Here the “measure” the plaintiff selected was the NDA’s designation protocol. Having chosen that mechanism and then bypassed it, Convolve could not establish the predicate of secrecy that misappropriation requires.

This is why the decision resonates beyond its nonprecedential status and beyond the Federal Circuit’s usual patent docket. It applies a principle of general trade-secret and contract law: when you define your own secrecy measures by contract, you will be held to them. The agreement is not just evidence of reasonable measures; it can be the measure, and falling short of it is fatal in a way that a more informal secrecy posture might not have been.

Open questions

How complete is the displacement? The court read AT&T Communications of California v. Pacific Bell as allowing, at most, an implied confidential relationship as to subject matter the contract does not cover, and it stressed that Convolve did not dispute that its Seagate NDA covered the substance of what it disclosed. How a narrowly drawn NDA (one addressing only certain categories of information) would fare as to everything else is left open.
What counts as substantial compliance? The court confronted a clean failure to send any confirmatory writing. Harder cases involve late, partial, or imperfect designations. How much deviation from the protocol a court will tolerate before secrecy is lost is unresolved.
Does the choice of law change the answer? Choice of law mattered here: California law governed the Seagate claims, New York law the Compaq claims. Convolve argued that the California Uniform Trade Secrets Act, which does not require a writing, saved its tort claim. The court rejected that and said CUTSA itself compelled the result: because misappropriation under Cal. Civ. Code § 3426.1(b) turns on whether the information was acquired under circumstances giving rise to a duty of secrecy, and those circumstances were dictated by the NDA, no duty ever arose. Whether a state whose courts have squarely addressed the interaction between NDAs and implied duties (the panel found no California case that had) would reason the same way is a separate question.

Implications

Treat designation as a recurring task, not a one-time signature. An executed NDA does nothing if its post-disclosure steps are ignored. Build a checklist tied to every meeting and demo.
Calendar the confirmation window. Oral and visual disclosures are the norm in technical negotiations; the writing that confirms their confidentiality is the step most often skipped and the one this case punishes.
Do not assume a common-law safety net. Where a contract defines the confidential relationship, courts may decline to imply a broader duty to rescue a party from its own non-compliance.
Audit legacy NDAs before disclosing. If an agreement imposes burdensome marking or confirmation duties you cannot realistically meet, renegotiate the protocol before the presentation, not after.
Align secrecy measures across counterparties. Convolve dealt with multiple recipients; inconsistent compliance across agreements multiplies the risk that the same secret is protected against one party and forfeited against another.

Frequently asked questions

Does signing an NDA automatically protect everything I disclose? No. Convolve holds the opposite. If the agreement specifies how information becomes “Confidential Information” (for example, by marking or by a follow-up writing), then information disclosed without following those steps may fall outside the protected category entirely.

Why couldn’t Convolve rely on an implied duty of confidence? Because the parties had an express agreement defining the scope of their confidential relationship. The court declined to imply a broader duty that would have relieved Convolve of the designation obligations it had agreed to perform.

Is this decision binding precedent? It is a nonprecedential Federal Circuit opinion, so it is not binding. But it is widely cited because it cleanly illustrates a principle of general application: contractual secrecy measures will be enforced as written, and failing to meet them can forfeit trade-secret protection.