Non-disclosure agreements are routine in freelance work. A client asks you to sign one before discussing a project, and most freelancers do — they seem standard, professional, and necessary. The problem is that many NDAs contain language that's far more restrictive than what's actually needed, and freelancers often sign them without understanding what they're agreeing to.
A poorly drafted NDA can restrict not just how you use information from this particular project, but what you can do with general knowledge and skills you've built over years. It can prevent you from working with competitors, talking about your portfolio, or even using standard industry practices you've developed independently.
Here's what you need to know before you sign an NDA.
What an NDA Actually Does
An NDA is a legal agreement that prevents you from sharing or using confidential information you learn during a project. That's the core function — and it's completely reasonable.
The key distinction is between mutual and one-way NDAs. A mutual NDA protects both you and the client. A one-way NDA typically protects only the client — you agree not to share their information, but they can share yours. One-way is standard for client relationships, but the language matters enormously.
The definition of "confidential information" is where most problems start. It should be narrow and specific: client source code, business strategies, customer lists, financial data, product designs not yet released. Instead, many NDAs define it so broadly that it covers nearly everything you see or hear during the project.
The Overbroad Definition Problem
Watch for definitions of "confidential information" that include catch-all language like "any information relating to the Client's business" or "all information shared during the engagement."
This language is so broad that it could reasonably include general industry knowledge, standard design practices, common coding patterns, and even your own observations about what works. If you walk away from the project and apply a technique you learned while working with the client, you could technically be in breach — even if that technique is common knowledge in your industry.
"I'd like to narrow the definition to: specific business strategies, financial information, customer lists, source code, and product designs that are not publicly known. General methodologies, processes, and industry-standard practices should be excluded."
Duration Red Flags
NDAs need a time limit. The question is how long. Standard durations are 1-3 years after the project ends. Some are longer. Some have no expiration date — they're "perpetual."
A perpetual NDA creates an indefinite legal obligation. If the definition of "confidential information" is broad, you're potentially restricted forever from working in your own industry or using your own knowledge. A 5 or 10-year NDA is similarly problematic.
Even reasonable definitions become problematic when perpetual. Information that was actually confidential in 2026 will be common knowledge by 2036 — but the NDA doesn't recognize that passage of time.
"I'd like to add an expiration date of [2-3] years from the end of this engagement. Information that becomes publicly available through no fault of mine should be excluded from protection."
The Non-Solicitation Clause Hiding in Your NDA
Many NDAs sneak in non-compete or non-solicitation language — sometimes subtle, sometimes buried in a section about "restricted activities." This isn't confidentiality. It's a restriction on who you can work for.
Non-solicitation clauses typically prevent you from working with the client's customers or recruiting their employees. In a freelance NDA, you might see language like "Freelancer agrees not to solicit or work with any client or contact introduced by Client during the engagement."
If the client introduced you to a vendor, partner, or potential customer during your project, you'd be banned from working with them. This is especially problematic because it's often hidden in a confidentiality agreement rather than presented as the business restriction it actually is.
"Non-solicitation language should not be included in this NDA. If Client wants to restrict competition, that should be addressed in a separate non-compete or non-solicitation agreement with clearly defined terms and duration."
Residual Knowledge Clauses: What You Need
A residual knowledge clause protects you. It states that even if you've learned something about the client's business during the engagement, you can still use general skills, knowledge, and experience you've acquired — as long as you're not deliberately copying or replicating the client's specific work.
This clause doesn't exist in many NDAs. If yours doesn't have one, you should add it. It clarifies that you can continue using and improving your own skills and methodologies, even if aspects of them were refined during the project.
"Nothing in this NDA prevents Freelancer from using or relying upon general knowledge, skills, techniques, and experience retained in unaided memory after termination of this engagement, provided that Freelancer does not knowingly use or disclose Client's specific work product, source code, or trade secrets."
What's Actually Reasonable in an NDA
A good NDA should:
- Define confidential information narrowly and specifically (not "anything relating to business")
- Exclude publicly available information and information you receive from third parties
- Have a reasonable duration (1-3 years, not perpetual)
- Exclude competitive restrictions (keep non-compete language separate if it exists)
- Include a residual knowledge clause
- Recognize that information loses confidential status over time or when made public
If you're asked to sign an NDA that has most of these features, that's reasonable. If it's missing several, or includes overbroad language and hidden restrictions, push back. In most cases, clients will negotiate or provide a revised version.
Before You Sign
Read the entire NDA, not just the confidentiality section. Look for non-solicitation clauses, non-compete language, and restrictions on what you can do with your own work and knowledge. If you find language you don't understand, ask the client for clarification in writing.
Don't assume the NDA is standard just because it's presented as one. Many contain custom restrictions that benefit the client at your expense. The best time to address these is before you sign — not after a dispute arises.
Upload your NDA to ClauseGuard
Get a full analysis of your NDA in 30 seconds — including specific risks, plain-English explanations, and ready-to-use counter-language.
Analyze your NDA free →