Should you sign a client's NDA, or ask for one yourself? A plain-English guide to freelance NDAs: when they matter, what to check, and red flags.
What an NDA Actually Is
A non-disclosure agreement is a contract in which one or both parties agree to keep certain information confidential. In freelance work, that usually means a client shares something sensitive (an unreleased product, internal data, a business strategy) and wants a legal commitment that you won't share it with anyone else. NDAs come in two main forms:
- One-way (unilateral): only you, the freelancer, are bound to keep the client's information confidential. This is the most common type in freelance work.
- Two-way (mutual): both sides agree to protect each other's confidential information. This is more common when you're sharing your own proprietary methods, tools, or early ideas too.
When You Actually Need an NDA
Not every project needs one. Many freelance jobs, like designing a logo or writing a blog post, involve nothing truly confidential, and requiring an NDA for them just adds friction. An NDA usually makes sense when: An NDA is usually unnecessary when: A useful gut check: if the information leaked tomorrow, would it genuinely harm the client or you? If yes, an NDA is reasonable. If not, a confidentiality clause inside your regular contract is often enough.
- The client is sharing unreleased products, features, or launch plans
- You'll have access to internal data, customer information, or financials
- You're working with proprietary processes, source material, or trade secrets
- The client is a larger company whose legal or procurement process requires one by default
- You're pitching your own original idea to a client and want your concept protected
- The work is based entirely on public information
- The project is a standard deliverable with no sensitive context (a generic social graphic, a typical article)
- The "confidential" material is really just ordinary business details most clients would share freely
NDA vs. a Confidentiality Clause in Your Contract
You don't always need a standalone NDA. Many freelance contracts already include a short confidentiality clause that covers the same ground in a paragraph or two. For lower-risk projects, that can be simpler and faster than a separate document. A standalone NDA tends to make sense when the information is especially sensitive, when the client's legal team requires it, or when confidentiality needs to be established *before* the contract is even signed, for example to discuss project details during scoping.
What to Check Before You Sign a Client's NDA
Never sign an NDA without reading it, even a "standard" one. These are the points worth checking:
1. How Broadly "Confidential Information" Is Defined Look out for definitions so broad they cover everything, including information you already knew or that is publicly available. A reasonable NDA excludes information that was already public, that you already had, or that you developed independently.
2. How Long It Lasts Some NDAs expire after a set number of years; others last forever. An indefinite term isn't automatically unreasonable for true trade secrets, but for ordinary project information, a fixed term is more typical and fairer to you.
3. What It Restricts Beyond Disclosure Watch for clauses that quietly restrict more than sharing secrets, such as preventing you from working with any competitor, or claiming ownership of your work. A pure NDA should only cover confidentiality, not limit your ability to earn a living.
4. Whether You Can Show the Work in Your Portfolio Many freelancers forget this. An NDA that bars you from ever mentioning the project can mean you can't include it in your portfolio. If portfolio use matters to you, ask for permission to show the work after launch, or to include an anonymized case study.
5. Penalties and Liability Check what happens if the NDA is breached. Extremely steep penalties or open-ended liability are a reason to slow down and get the document reviewed.
6. Which Law and Location Govern It The agreement should state which jurisdiction's laws apply. If that's far from where you live, enforcing or defending yourself under it can become complicated and costly.
Red Flags in a Freelance NDA
If you spot any of these, it's completely reasonable to ask for changes. Most legitimate clients expect some negotiation, and their reaction to a polite request is itself useful information.
- It's not mutual even though you're sharing your own original ideas or materials
- It has no end date and no exclusions for public information
- It contains non-compete or exclusivity terms disguised inside "confidentiality"
- It transfers ownership of your pre-existing work or tools
- The client pressures you to sign immediately without time to read it
- It's attached to unpaid work, like a test project or "trial" that stays unpaid indefinitely
Should You Ask Your Clients to Sign an NDA?
Occasionally, yes. If you're sharing proprietary templates, a unique process, or an early-stage idea you'd like to protect, a mutual NDA is a reasonable ask. For routine client work, though, requiring an NDA from every client can feel excessive and slow down starting projects. Keep it for situations where there's genuinely something worth protecting.
A Simple Process for Handling NDAs
1. Decide if it's actually needed based on the sensitivity of the information 2. Read the whole document, not just the headline terms 3. Check the key points: definition, duration, restrictions, portfolio rights, penalties, governing law 4. Ask for changes politely if something is unreasonable 5. Store the signed copy with the client's record so you can find it later 6. Keep a note of what's confidential for that client so you don't accidentally share it in a portfolio or a case study That last step is where many freelancers slip, not out of bad faith, but because they simply forget which projects were under NDA by the time they're updating their portfolio months later. Building NDA checks into a repeatable client intake workflow keeps signed agreements easy to find and helps you avoid common freelance portfolio mistakes when publishing case studies later.
Frequently Asked Questions
Do freelancers need to sign NDAs? Not for every project. NDAs make sense when you'll handle genuinely sensitive information, like unreleased products, internal data, or trade secrets. For routine work, a confidentiality clause in your contract is often enough.
Can I refuse to sign a client's NDA? Yes. You can decline, or ask for specific changes. Many clients will negotiate reasonable terms, though some projects may require signing as a condition of the work.
Can I include NDA-protected work in my portfolio? Only if the NDA or the client allows it. Many freelancers ask for permission to show the work after launch, or to publish an anonymized version, before agreeing to the terms.
What happens if I break an NDA? Consequences depend on the agreement and your jurisdiction, but can include damages and legal action. This is one reason to read the terms carefully, and to have a lawyer review anything high-stakes.
Final Thoughts
An NDA isn't something to fear, but it isn't something to sign blindly either. Most freelance projects don't need one, and when they do, a few minutes spent checking how confidential information is defined, how long the agreement lasts, and whether you can still show your work will protect you from the most common problems. When the stakes are high or the terms feel off, a lawyer's review costs far less than a dispute. To keep signed agreements, confidentiality notes, and client records organized in one workspace, try Flanceflow for free or explore client management for freelancers.