Hire Software Developers 7
Back to blogs

Software Development NDA Template: Every Clause Explained

November 19, 2026
An outside engineer's laptop with a client's code repository open next to a signed software development NDA

Software Development NDA Template: Every Clause Explained

One gated software development NDA template that ranks for this search has a "contractual penalties" clause and no AI clause at all [E40]. So what about your engineers' coding assistant? Read literally, "don't share with third parties" either turns pasting your code into one into a breach, or says nothing about it. Here is an NDA built for outside engineers working in your repo, and the reason behind every clause.

A software development NDA is a confidentiality agreement between a company and a development vendor that covers the code, repositories, access keys and data the vendor's engineers see while working on the company's software.

Key takeaways

  • Name code, repositories and access keys as confidential, but keep it tight: in Brown v. TGS (California, US law), terms so broad they worked as a non-compete were thrown out [E37].
  • As of 19 November 2026, GitHub Copilot Business/Enterprise, the Anthropic API, the OpenAI API and Cursor (with Privacy Mode on) say they don't train on your data; retention varies by plan, model and feature [E28b, E29, E31, E32].
  • An NDA AI clause works better as a pre-approved tool list than as a blanket ban [E35].
  • Under US law, software isn't one of the nine categories that let commissioned work be "made for hire", so ownership usually needs a signed assignment, not an NDA [E19, E21].

Download the template (Word + PDF, free, no form)

Download: Word (.docx) · PDF. No email gate.

Template, not legal advice. Have a lawyer in your country review it before you sign.

This mutual NDA template is yousource's own adaptation of the Common Paper Mutual NDA v1.0, published under CC BY 4.0 [E1]. That licence allows adaptation "for any purpose, even commercially", with credit [E6]. You can use our version in any way, free, including changing it and using it commercially. The only condition: keep the Common Paper credit line.

Disclosure: yousource sells Dev On Demand, and this is the kind of NDA we think a vendor should sign.

How is a vendor NDA different from an investor NDA?

An investor NDA protects a pitch, and professional investors often refuse to sign one [E36]. A vendor NDA protects code and credentials held by people working inside your systems, and we sign one before our engineers access a client's codebase.

Cooley GO's Mike Lincoln writes: "Many investors may simply view an NDA demand as rude." His advice is to keep the sensitive tech out of early pitches [E36]. That can't work with a development vendor, because the people you hire clone your repositories and hold your access keys. An NDA for software developers needs different clauses: who at the vendor sees what, what happens to the code at the end, and which AI tools it may go into.

What each clause in the software development NDA template says

Headings follow the template's numbering.

The basics: a narrow Purpose

The Purpose reads "to discuss and do software development work, namely" followed by a short description. Clause 3(a) allows use "only for the Purpose", so everything hangs off it. The UK IPO's guidance says to define the purpose narrowly: you can widen it later but can't narrow it [E18].

1. What is confidential

Anything marked confidential "or that a reasonable person would see as confidential", as in Common Paper [E12]. Then it names what a dev engagement shares: "source code, repositories, designs, data, test data, passwords and access keys, security documents, roadmaps, prices, and the fact that the parties are talking."

It doesn't say "all information of any kind", on purpose. In Brown v. TGS Management (California, so US law), confidentiality terms so broad they acted as a non-compete were held void from the start and unenforceable, even with a carve-out for generally known information [E37]. Overreach can cost you the whole clause.

2. What is not confidential

Four exclusions: public through no fault of the Recipient, already known, received from someone free to share it, or "built on its own, without using the Sharer's information." These are the standard four from the Common Paper base [E13].

3. What the Recipient must do

Clause 3(b) is need-to-know: share only with staff, contractors and advisers "who need it for the Purpose and who are bound to keep it secret", and the Recipient answers for them [E12]. Clause 3(c) sets the care standard, "never less than reasonably carefully" [E12], then spells it out for code: work in the Sharer's repositories and accounts, never copy code to personal accounts or devices, and remove access once someone no longer needs it.

Clause 3(d) is our addition: written notice within [72 hours] of finding a leak or misuse, plus help limiting the damage. Change the number; keep one.

4. AI tools

Our engineers primarily use Claude and GitHub Copilot, so an NDA that ignored coding assistants would be fiction from day one. A blanket ban fails too: drafted broadly, it can catch ordinary tools like spell-checkers and email spam filters [E35]. Lighter model clauses, such as terms.law's basic and standard tiers, ban training on the information rather than all use, and allow approved tools that don't learn from the information [E35].

Clause 4 follows that model. Code and other information may go into an AI tool only if (a) the tool and its plan are in the Schedule or approved by email, and (b) it "runs on business, enterprise or API terms under which the provider does not train its models on the information", with no-training settings on. "Free, personal and consumer plans are never allowed." Nobody may train or fine-tune a model on the information. The Sharer can withdraw approval by email, and use then stops within [5] business days.

Why approve the plan, not just the vendor? Terms differ by plan. As of 19 November 2026:

  • GitHub Copilot: on Business and Enterprise, GitHub and each model provider it hosts say your data isn't used to train their models [E28b].
  • Anthropic API: no training "without your express permission"; no retention by default, except some models that require 30 days [E29].
  • OpenAI API: no training since 1 March 2023 unless you opt in; abuse logs kept "for up to 30 days" [E31].
  • Cursor: with Privacy Mode on (the default for Enterprise teams), code is "never used for training", but a few models require provider retention and Cloud Agents store code while running [E32].

No training on these plans, but retention varies by plan, model and feature, so check the current terms for the plan you use. So the Schedule asks for the tool and the plan.

5. When the law requires disclosure

Disclose only what a law, regulator or court requires and, where the law allows, warn the Sharer first, as Common Paper does [E13].

6. No other rights, and no "we remembered it" exception

Sharing grants no ownership or licence beyond the Purpose, as in Common Paper ("grants no license") [E14]. The key line: "'We remembered it' is not an exception: people may not use the Sharer's information just because it stayed in their heads."

That rules out a residuals clause, an option in Common Paper [E14]. Venable's Philip T. von Mehren writes that one "insulates a party receiving confidential information from being liable" and advises resisting it [E16]. With code, what stays in an engineer's head is the whole risk.

8. Giving it back

At the end, or earlier on request, the Recipient returns or deletes the information "(including local copies of repositories)", gives up passwords and access keys, and confirms in writing if asked. Automatic backups, and copies the law requires it to keep, may stay until normally deleted, still confidential. Common Paper has the same carve-out [E14]. Without it, nobody could honestly sign the confirmation.

9. If someone breaks this agreement

"A leak can cause harm that money can't fix," so the Sharer may ask a court for an injunction as well as damages, following the Common Paper "irreparable harm" wording [E14].

11. US only: whistleblower notice

Under US law (18 U.S.C. § 1833), an employer must give whistleblower-immunity notice in agreements covering trade secrets [E15]. "Employee" there includes "any individual performing work as a contractor or consultant" [E15]. Without the notice, the employer can't recover exemplary damages or attorney fees from that individual [E15]. Keep clause 11 if an individual signs or individual engineers are bound under US law.

What we left out on purpose

Non-competes. In California, confidentiality terms that act like a non-compete can be voided entirely [E37], so we keep the two apart. The FTC's federal non-compete rule was struck down in August 2024 [E38], and in September 2025 the FTC dropped its appeals in favour of "case-by-case enforcement" [E38].

Penalty clauses. The gated template from the top has one [E40]. Ours doesn't; clause 9 (injunction plus damages) handles a breach.

Code ownership. An NDA governs what happens to your information, not who owns the code an outside engineer writes. Under US law, software isn't one of the nine "work made for hire" categories for commissioned work [E19], and a copyright transfer must be in a signed writing [E21]. Put ownership in a separate IP assignment.

How to use it

  1. Fill in the basics: names, addresses, notice emails, a narrow Purpose, start date, a 2, 3 or 5-year confidentiality period (trade secrets last as long as they're trade secrets, Common Paper's default [E14]), and governing law.
  2. List approved AI tools in the Schedule: tool, plan, approver, date.
  3. Keep or delete clause 11.
  4. Have a lawyer review it before you sign.

Bringing an outside engineer into your repo? See our developer onboarding guide for access and our development team contract guide for the commercial side.

Frequently asked questions

Is this a mutual or one-way NDA?

Mutual. Each party is the Sharer when it gives and the Recipient when it receives.

Can contractors use ChatGPT or Claude on our code under this NDA?

Only on an approved plan with business, enterprise or API terms and no training on your information (clause 4). Free, personal and consumer plans are never allowed.

How long does confidentiality last?

2, 3 or 5 years after the agreement ends, your choice. Trade secrets stay protected for as long as they remain trade secrets [E14].

Does an NDA give us ownership of the code a contractor writes?

No. An NDA covers how your information is used. Ownership needs a signed IP assignment, which the NDA is not [E19, E21].

Can I edit this NDA template and use it commercially?

Yes, in any way, free. Just keep the Common Paper credit line [E1, E6].

Sources

back to top
Book 15 min with Albert
Smiling man with short dark hair and glasses wearing a black suit, white shirt, and black tie against blue background.
Tell Albert what you're shipping.
He'll read this before joining the call. Phone number comes next, on the calendar step.
↳ info@you-source.com
↳ 4-hour response
Please wait while we retrieve meeting schedules.
Oops! There's a problem with your request. We're working on fixing it. Please try again later.