How to Write an NDA That Actually Protects You
Non-disclosure agreements show up constantly in freelance work. A startup sends one before sharing their pitch deck. An agency requires one before you meet the end client. A founder asks you to sign something "standard" before a discovery call. Most freelancers sign without reading — or skip NDAs entirely when they should not.
Both mistakes can hurt you. An overly broad NDA can limit your ability to take future work. No NDA at all can leave you exposed if a client claims you misused confidential information. The fix is knowing how to write — or negotiate — an NDA that actually protects you.
What an NDA Is (and Is Not)
An NDA, or non-disclosure agreement, is a contract where one or both parties agree not to share certain information with outsiders. It does not mean you cannot talk about the fact that you worked with a client — unless a separate publicity clause restricts that. It does not automatically give the client ownership of your work. It covers information, not deliverables.
Think of it as a set of rules for secrets: what counts as secret, how long you must keep it secret, and what happens if someone slips.
When Freelancers Should Use an NDA
You need an NDA when you will access information that could harm the client if leaked — source code, unreleased product plans, customer lists, pricing data, marketing strategies, or internal financials. You might also want a mutual NDA when you are sharing your own proprietary methods, tools, or client lists during sales conversations.
You probably do not need an NDA for generic project briefs with publicly available information. Overusing NDAs slows deals down and signals distrust. Use them when the sensitivity of the information justifies it.
One-Way vs. Mutual NDAs
A one-way NDA protects only the disclosing party — usually the client. A mutual NDA protects both sides. If you are sharing your frameworks, processes, or subcontractor network, insist on mutual terms. If only the client shares sensitive data, one-way may be fine — but read it carefully anyway.
Essential Clauses That Protect You
Definition of Confidential Information
This is the heart of the agreement. Watch for definitions so broad they cover "everything learned during the relationship." Push for specific categories: technical data, business plans, customer information, and marked documents. Information that is not labeled confidential should not automatically qualify unless it is obviously sensitive.
Exclusions — What Is Not Confidential
Standard exclusions protect you: - Information already public through no fault of yours - Information you already knew before the engagement - Information independently developed without using their secrets - Information received lawfully from a third party
Without these carve-outs, you could accidentally violate an NDA by using general industry knowledge.
Duration and Survival
How long do obligations last? Two to five years after the relationship ends is typical for business information. Trade secrets may legitimately require longer protection. Be wary of "perpetual" obligations on general knowledge you pick up on the job — that can unreasonably restrict your career.
Permitted Disclosures
You may need to show work to accountants, lawyers, or subcontractors. The NDA should allow disclosure to advisors under confidentiality and to comply with legal requirements. If you use subcontractors, clarify that they must sign equivalent obligations.
Remedies and Return of Materials
Many NDAs state that breach may cause irreparable harm and allow the injured party to seek injunctive relief — a court order to stop disclosure. At project end, you should return or destroy confidential materials and confirm in writing that you did.
Red Flags in Client NDAs
Watch for non-compete language smuggled into an NDA. Non-competes restrict whom you can work for; they belong in a separate clause with clear limits, not hidden in a confidentiality definition. Watch for assignment clauses that bind you to terms you never agreed to if the company is acquired. Watch for one-sided indemnification where you pay unlimited damages for any leak, even if the client's own lax security caused it.
If a clause feels wrong, ask to revise it. Reasonable clients expect negotiation. Unreasonable ones reveal themselves early — which is useful information.
How to Talk About NDAs Without Killing the Deal
Frame NDAs as mutual protection, not suspicion. "I want to make sure your roadmap stays private and that my existing client relationships are respected too — can we use a mutual NDA with standard exclusions?" Most professional clients appreciate clarity.
Sign before accessing sensitive materials, not after you have already seen the codebase. Order matters for enforcement and for your peace of mind.
Writing Your Own NDA Template
Freelancers who bring their own NDA to the table look professional. Keep it short — two to four pages — and aligned with your jurisdiction. Include fields for parties, effective date, purpose of disclosure, and term.
When projects combine creative work with sensitive access, pair an NDA with a service contract. The NDA covers secrets; the service contract covers deliverables, payment, and IP.
ContractCraft generates jurisdiction-aware NDAs alongside freelance service agreements, so you can send both documents before a kickoff without drafting from scratch. That speed matters when a client wants to move fast — you can move fast and still be protected.
The Bottom Line
An NDA that actually protects you is specific, time-limited, and mutual when you are sharing your own confidential information. It excludes public and independently developed knowledge, defines what happens at project end, and avoids sneaky non-compete traps.
Read every NDA before you sign. Redline unreasonable terms. Use your own template when you are the one introducing confidential information. And never confuse "standard" with "fair" — standard just means common, not necessarily good for you.
When your NDA matches the real risk of the project, you can collaborate openly without wondering whether you just signed away your next client.