The Residuals Clause: How the Other Side Keeps Your Ideas

What does a residuals clause actually say?

The typical formulation provides that nothing in the agreement restricts the receiving party from using residuals, defined as information in intangible form retained in the unaided memory of persons who have had access to confidential information, provided they have not intentionally memorised it for the purpose of retaining and later using it.

Read alone, it sounds like an acknowledgement that people cannot unlearn things. Read against the rest of the agreement, it is an exception permitting use of what the other side remembers, which for a conversation about ideas is a large part of what you disclosed.

Watch for the companion sentences that often follow. One says the receiving party is under no obligation to limit or restrict the assignment of its personnel. Another says it owes no royalty or other payment for any use of residuals. A third says nothing in the clause grants a licence under your patents or copyrights. Together they mean: our engineers can work on anything, using what they remember, and we owe you nothing for it.

Why it matters most to the smaller party

Consider who is sharing what. A startup pitching a product concept to a large potential partner is disclosing an idea, an approach, and the reasoning behind it. There is no document at the centre of that; the value is in what the other side now understands.

A residuals clause permits their engineers to use exactly that. The disclosing party has protected its documents and left its know-how available. That asymmetry is why the clause is worth identifying before a pitch rather than after one.

Take a Hyderabad fintech that spends three meetings walking a large bank through its approach to detecting fraud in UPI transactions: the signals it uses, why it weights them, and what it tried that failed. The slides go back. The insight does not. Eighteen months later the bank launches an in-house tool built on the same logic. Under a broad residuals clause, the bank's answer is simple: our team remembered the general approach, which the NDA expressly allowed.

Why counterparties insist on it

It is worth understanding the other side's position, because it is not always unreasonable. A large company that reviews hundreds of proposals a year cannot realistically quarantine every idea it has heard, and an engineer who saw a pitch in March cannot be prevented from working on an adjacent problem in September.

Without a residuals clause, that company faces a claim every time it ships something resembling something it was once shown. So the clause exists to manage a genuine problem. That does not make it acceptable to you, but it explains why removal is sometimes genuinely not on offer, and why a narrowing proposal often succeeds where a flat deletion request fails.

Is a residuals clause enforceable in India?

Generally, yes. Indian contract law starts from freedom of contract, and a clause that carves certain information out of a confidentiality obligation is a lawful bargain between commercial parties. Nothing in the Indian Contract Act, 1872 makes a residuals clause void, and Section 27 of that Act, which deals with restraints of trade, is not engaged because the clause loosens a restriction rather than imposing one.

Statute gives you little fallback. India has no standalone trade secrets law. The Copyright Act, 1957 protects the expression of a work, such as code or a written document, but not the underlying idea or method. Section 3(k) of the Patents Act, 1970 excludes a computer programme per se and business methods from patentability, so much software know-how is not patentable either. For most early-stage know-how, the NDA is the protection, and the residuals clause is a hole in it.

Proof is the other problem. If you allege misuse, the recipient will say the information was retained in unaided memory and not intentionally memorised. Showing otherwise would require evidence of what was in someone's head and why, which is rarely available. In practice, a broad residuals clause shifts nearly all the risk to the discloser.

How do residuals clauses differ in risk?

Not every residuals clause is equally harmful. The drafting detail decides how much of your disclosure is exposed.

What to propose instead

• Ask for it to be struck. In many agreements it is template language rather than a negotiated position, and a short email asking for deletion sometimes works.
• If it stays, exclude anything reduced to writing or any recorded form, including slides, emails, chat messages and code.
• Exclude specific categories: source code, algorithms, technical architecture, product roadmaps, customer and pricing information, and anything marked as a trade secret.
• Limit it to individuals who did not have substantial or repeated access, rather than to everyone who attended.
• Add that the clause does not permit disclosure of the source of the information or of your identity, and does not grant any licence under your intellectual property.
• Add a time limit, so the carve-out applies only after the confidentiality term ends rather than from day one.

Sample wording for a narrower clause

If deletion is refused, a version along these lines is a reasonable counter: "Residuals means information of a general, non-technical nature retained in the unaided memory of the Receiving Party's personnel who had access to Confidential Information, without reference to any written or recorded material. Residuals shall not include source code, algorithms, technical specifications, product roadmaps, customer information, pricing, or any information identified by the Disclosing Party as a trade secret. Nothing in this clause grants any licence under any intellectual property right of the Disclosing Party or permits disclosure of the Disclosing Party's identity as the source."

The phrase doing the most work is "general, non-technical nature". It concedes the counterparty's genuine problem, that people remember broad themes, while keeping your specific methods out of the carve-out.

Stage what you disclose

Where the clause cannot be removed, calibrate what you disclose. Share enough to have the conversation, not enough to be rebuilt from memory. A practical sequence for a pitch looks like this.

First meeting: the problem, the outcome you deliver, early traction and commercial terms. Second stage, once there is a signed term sheet or letter of intent: architecture at a high level, under a negotiated NDA. Final stage, during diligence or a paid pilot: technical detail, ideally under a separate agreement without a residuals clause, and with access limited to named individuals.

Keep a dated record of what you shared at each meeting, with the attendee list. It will not defeat a residuals clause, but it helps show what came from you if a dispute ever turns on what was disclosed and when.

What if you are the receiving party?

The clause looks different from the other side of the table. If you run an agency, a consultancy or a product company that hears many pitches, a residuals clause protects your team's ability to keep working on problems they were already exploring. Without it, every similar feature you ship later can be met with an allegation that it came from someone's pitch deck.

If you want the clause, ask for it openly and keep it reasonable. A version limited to general, non-technical information, excluding recorded material, is much easier for a smaller counterparty to accept than a broad one. Pair it with good internal habits: log what pitches you received, keep disclosed material in a restricted folder, and record your own independent development work with dates. Those records are often more useful in a dispute than the clause itself.

The honest position

If you are a small company signing a large company's standard NDA with a residuals clause you cannot change, the realistic protection is behavioural rather than contractual. Decide in advance what you will and will not say in that meeting.

That is not a satisfying answer, but it is the accurate one, and it is considerably better than assuming the NDA covers you and discovering later that the clause you skimmed was the one that mattered.

One last check before any meeting: search the NDA for the words residuals, unaided memory, general skills and retained. Some templates hide the concept in the exclusions clause or in a separate clause on freedom to develop, rather than using the word residuals at all. If you find it, decide before the meeting what you will hold back.