NDAs in software projects: what they cover and what they don’t
Every client project we take on is covered by a non-disclosure agreement. It’s why you won’t see client logos all over our website, and it’s a question we get early in most conversations. Here’s what an NDA does in a software project, what it doesn’t do, and what to read before you sign one.
We’re a software company, not a law firm. Treat this as a practical guide and have your lawyer review any agreement you sign.
What an NDA is for
An NDA (non-disclosure or confidentiality agreement) is a contract where one or both parties agree to keep certain information private. In a software project it lets you share what the developer needs to quote and build accurately: business plans, customer data structures, internal processes, pricing, unreleased product ideas.
Sign it before you share anything sensitive, including in the first detailed scoping call.
What it usually covers
- Definition of confidential information: often broad (“anything shared in connection with the project”), sometimes listed specifically.
- Obligations: don’t disclose it, use it only for the project, protect it reasonably.
- Who can see it: usually employees and contractors who need to know and are bound by similar terms.
- Duration: how long confidentiality lasts, often several years after the project ends, sometimes indefinitely for trade secrets.
- Return or destruction: what happens to your information when the project ends.
- Publicity: whether the developer may name you as a client or show the work. Many NDAs, ours included, mean “no” unless you agree in writing.
What it doesn’t cover
This is where people get caught out:
- Ownership of the code. An NDA keeps things secret. It doesn’t transfer intellectual property. You need an IP assignment clause in your services agreement saying that what’s created for you becomes yours.
- Information that was already public, or that the developer knew before, or developed independently. Standard exclusions.
- Legal requirements to disclose, such as a court order. Most NDAs allow this with notice.
- Ideas in general. An NDA won’t stop someone else building a similar product independently.
Clauses worth reading carefully
- Mutual or one-way? If both sides share sensitive information, mutual is fairer.
- Definition scope. Too narrow and it misses things; too broad and it can be hard to work with.
- Non-solicitation. Some NDAs include clauses about hiring each other’s staff. Make sure you’re comfortable with them.
- Governing law and jurisdiction. With an overseas partner, agree whose law applies and where disputes are heard.
- Remedies. What happens if the agreement is breached.
NDAs and IP assignment: get both
For a custom software project you want, at minimum:
- an NDA before sharing details;
- a services agreement with scope, payments and an IP assignment clause;
- agreement on account ownership: repositories, hosting and app store listings in your company’s name.
Together these protect both the secrecy of your information and your ownership of the result. We cover the full checklist in outsourcing software development to India.
If you’d like to start a conversation under NDA, tell us what you need and we’ll send ours over before you share any details.