What Is a Residuals Clause (and Should You Accept One)?

Here is a clause that can quietly undo most of the protection you thought your NDA gave you, written so it reads like housekeeping:

The Receiving Party may use Residuals for any purpose. "Residuals" means information retained in the unaided memory of persons who have had access to the Confidential Information.

That's a residuals clause. In plain English: whatever your information turns into once it's in someone's head, the other side gets to keep and use — for anything, including competing with you. It's one of the most consequential provisions in the NDA world, and one of the least noticed, because it's usually buried near the boilerplate and phrased to sound generous rather than dangerous.

What it actually does

A normal NDA says: we'll give you confidential information, and you'll only use it for our shared purpose. A residuals clause carves a hole in that promise. It says that once information has passed through a person's memory, as opposed to a document they're still holding, the confidentiality obligation no longer restricts what that person can do with it.

The theory behind it is real, and not entirely unreasonable. When two technology companies evaluate a partnership, engineers see each other's approaches. You cannot give an engineer a lobotomy at the end of the meeting. The receiving company worries that its own people, having glimpsed your architecture, are now permanently "contaminated". That anything they build later could be attacked as a breach. The residuals clause is their protection against that: general knowledge, skill, and experience that a person naturally retains isn't locked up forever.

The problem is the distance between that reasonable purpose and how broadly these clauses are usually written. "Anything retained in unaided memory" is an enormous category. Ideas, strategies, product concepts, business plans, pricing logic, roadmap, the very things a founder most wants to protect are exactly the things a smart person remembers without notes. Protect a formula and a residuals clause may not touch it. Protect a concept and the clause can swallow it whole.

The litigator's view: it's not the clause, it's who has to prove what

Here's what I learned watching these get litigated, and it's the part the drafting guides skip. A residuals clause doesn't just narrow your rights. It flips the practical burden of proof, and burden of proof is where confidentiality cases are won and lost.

Without a residuals clause, if the other side ships something suspiciously close to what you showed them, the fight is about whether they used your confidential information. With a broad residuals clause, they have a ready-made answer: whatever we used, we used from memory, and memory is permitted. Now you're not proving they used your information. You're trying to prove they used a document, or that a specific person deliberately memorized something in order to get around the agreement. That is a much harder case, often an impossible one, because the evidence lives inside someone's head. A well-drafted residuals clause can turn a strong misappropriation claim into a coin flip.

And there's a second, quieter danger: a residuals clause can undercut your trade secret protection. Trade secret law protects information that you take reasonable steps to keep secret. If your own signed agreement says the other side may freely use what its people remember, a court can read that as you agreeing your information wasn't meant to stay locked down, handing the other side a defense you gave them yourself. (This is the same trap that a badly drafted term creates; see How Long Should an NDA Last?.)

So should you accept one?

It depends almost entirely on which side of the information flow you're on, and residuals clauses reward the side doing the receiving.

If you're mostly disclosing. You're the startup showing your technology to a bigger company, the founder pitching a concept, the party with the crown jewels, a broad residuals clause works against you, and you should push to strike it or narrow it hard. You're the one with something to lose to "unaided memory."

If you're mostly receiving. You're evaluating someone else's technology and you have engineers you can't firewall, a narrow, mutual residuals clause can be a legitimate protection against future contamination claims. Large technology companies often treat some version of it as standard, and refusing outright can stall a deal.

The honest answer for most standard commercial NDAs, where the exchange is business information rather than deep technical evaluation, is simpler: you probably don't need a residuals clause at all, and if one appears, ask why. Its presence in an otherwise ordinary NDA is often a sign the document was copied from a big-tech template built for a very different situation.

If you do accept one, narrow it

A residuals clause you can live with usually does several of these:

• Excludes trade secrets explicitly, residuals apply to general know-how, never to your genuine trade secrets.
• Excludes intentional memorization, "unaided memory" means genuinely retained, not deliberately committed to memory to evade the agreement.
• Grants no license to intellectual property, using residual knowledge is not permission to infringe your patents, copyrights, or trademarks. Say so.
• Is mutual, if it protects their engineers' memories, it protects yours too.
• Is limited to people who had authorized access, not the whole company.

Each of those turns "they can use anything anyone remembers" back into something closer to the reasonable purpose the clause was invented for.

See whether the NDA you were sent hides one, and how it's written.

Residuals clauses are easy to miss precisely because they don't look alarming, and the difference between a fair one and a dangerous one is a few carefully chosen words. That's the kind of thing YayNDA is built to catch. Drop in the NDA you were sent, alongside your own or our free balanced template, and the tool compares them clause by clause, including whether there's a residuals provision, whether it carves out trade secrets and IP, and whether it runs both ways. You find out it's there before you sign, not after something ships.