NDA Template for Freelancers: What a Fair One Looks Like (With Examples)
What a Fair NDA Looks Like for Freelancers (Clause by Clause)
If you freelance, you don't write NDAs — you receive them. The client sends a PDF drafted by their lawyer (or copied from a template their last lawyer left behind), and you're expected to sign it before the real work starts. That asymmetry is the whole problem: the person who wrote the agreement was optimizing for one side, and it wasn't yours.
Most advice online tells you to "have a lawyer review it," which is correct and also unhelpful when the project pays $2,000 and a review costs $400. The more practical skill is knowing what a fair NDA actually contains, so you can tell at a glance whether the one in front of you is standard boilerplate or something worth pushing back on. This post walks through the clauses a balanced freelance NDA should have — with side-by-side examples of fair versus overreaching language — and ends with a short illustrative template so you have a reference point. For the mechanics of reading one start to finish, see How to Review an NDA; for the specific provisions that should stop you cold, see NDA Red Flags.
A quick, necessary caveat before we start: this is educational information, not legal advice, and the sample language below is illustrative rather than a document to sign. Laws vary by jurisdiction, and no article can account for your specific situation. Use this to understand the shape of a fair agreement, then adapt accordingly.
The Purpose of an NDA — And What It Shouldn't Do
An NDA does one job: it protects confidential information from being disclosed or misused. That's it. A client is sharing something sensitive — source code, customer lists, unreleased product plans, financial figures — and they want a contractual guarantee that you won't leak it or use it against them. That's a completely legitimate interest, and a fair NDA serves it cleanly.
The trouble starts when an NDA is used to do things it was never meant to do. A confidentiality agreement is not the right instrument for locking you out of an entire industry, transferring ownership of everything you create, or exposing you to unlimited financial liability. When you see those provisions bolted onto what's labeled a "Non-Disclosure Agreement," you're looking at scope creep — the client's template is trying to win concessions that belong in a separate, negotiated services or employment contract, if anywhere.
So the test for every clause is simple: does this protect confidential information, or does it do something else under the cover of confidentiality? A fair NDA stays in its lane. The clauses below are what staying in that lane looks like.
Clause 1 — Definition of Confidential Information
Everything in the agreement depends on this clause, because it defines what you're actually on the hook to protect. A fair definition is specific enough that you can tell what counts and what doesn't. An unfair one is so broad that literally everything the client ever says to you becomes "confidential," which makes the obligation impossible to honor and dangerous to sign.
Fair:
"Confidential Information means non-public information that the Disclosing Party designates as confidential in writing, or that a reasonable person would understand to be confidential given the nature of the information and the circumstances of disclosure, including business plans, customer data, source code, and financial information."
Overreaching:
"Confidential Information means any and all information disclosed by the Disclosing Party to the Receiving Party, whether written, oral, or in any other form, and whether or not marked as confidential."
The difference is the word "any." Under the second version, the client mentioning over coffee that they're thinking about hiring is technically confidential information you could be liable for repeating. A fair definition ties confidentiality to a reasonable-person standard or a written-designation requirement, so both sides actually know what's protected.
Clause 2 — Standard Exclusions (Must-Have)
This is the clause freelancers most often overlook, and its absence is one of the clearest signs of a badly drafted NDA. Exclusions are the carve-outs that keep the agreement sane by naming categories of information that are not your responsibility to protect — because protecting them would be either impossible or absurd. A fair NDA always includes them. Four are standard and non-negotiable:
- Public domain. Information that's already public, or becomes public through no fault of yours, isn't confidential. You can't be liable for repeating what's already on the client's website.
- Independently developed. Anything you create or know without using the client's confidential information stays yours. This protects your general skills and prior work.
- Received from a third party. Information you legitimately get from someone else who was free to share it isn't covered.
- Required by law. If a court or regulator compels disclosure, complying isn't a breach (usually with a requirement to notify the client first so they can object).
Fair:
"Confidential Information does not include information that: (a) is or becomes publicly available through no breach by the Receiving Party; (b) was known to the Receiving Party before disclosure; (c) is independently developed without use of the Confidential Information; (d) is rightfully received from a third party; or (e) is required to be disclosed by law, provided the Receiving Party gives prompt notice where legally permitted."
If these exclusions are missing entirely, the agreement is technically claiming ownership over information it has no right to — including things you already knew before you met the client. That's not a subtle drafting error; it's a reason to ask for the standard carve-outs to be added before you sign.
Clause 3 — Duration
Confidentiality obligations should last a defined, reasonable period. For most freelance work, one to two years after the engagement ends is standard. Some genuinely sensitive categories — trade secrets in the legal sense, certain source code — can justify longer terms, but routine business information does not need to be protected forever.
Fair:
"The obligations under this Agreement shall remain in effect for two (2) years following the termination of the engagement."
Overreaching:
"The obligations under this Agreement shall remain in effect in perpetuity."
An indefinite or perpetual term for ordinary confidential information is a red flag. It means that a decade after a small project, you're still theoretically bound — and still theoretically liable — for information that stopped being sensitive years ago. Trade secrets are a legitimate exception (the law protects them as long as they stay secret), so a fair compromise is a defined term for general confidential information and an indefinite term only for material that qualifies as a trade secret. We break this down further in the guide to indefinite NDA clauses.
Clause 4 — Non-Compete (When It Belongs and When It Doesn't)
Here's the first clause that usually doesn't belong in an NDA at all. A non-compete restricts who you can work for — it stops you from taking on the client's competitors, sometimes for years, sometimes across an entire industry. That's a serious restriction on your ability to earn a living, and it has nothing to do with keeping information confidential.
A fair NDA has no non-compete clause, because a non-disclosure agreement isn't the place for one. If a client legitimately needs a non-compete (rare for freelance engagements), it belongs in a separate, negotiated, and properly compensated agreement — and in many jurisdictions, broad non-competes against independent contractors are unenforceable or heavily restricted anyway.
What is sometimes reasonable is a narrow non-solicitation clause: an agreement not to poach the client's employees or actively solicit their customers for a defined period. That's far more limited than a non-compete and doesn't stop you from working in your field.
Overreaching:
"During the term of this Agreement and for two (2) years thereafter, the Receiving Party shall not provide services to any business that competes with the Disclosing Party in any market."
If you see language like that in a document titled "NDA," treat it as scope creep. It's the single most common way a confidentiality agreement quietly becomes a restraint on your career. The non-compete clause guide covers how to push back on it specifically.
Clause 5 — IP Assignment (Always with Carve-Outs)
Intellectual property assignment — the clause that says work you create belongs to the client — is normal and expected in a services relationship. If a client pays you to build something, it's reasonable that they own the deliverable. The problem is when the assignment is written so broadly that it sweeps in things it shouldn't: your pre-existing tools, your reusable code libraries, your general know-how, or work you did for other clients.
A fair IP clause assigns the specific deliverables created for this client under this engagement and explicitly carves out your background IP — the material you brought to the table and use across all your work.
Fair:
"The Contractor assigns to the Client all intellectual property rights in the deliverables created specifically for the Client under this engagement. This assignment does not include the Contractor's pre-existing materials, tools, or general knowledge and skills, which the Contractor retains and may license to the Client as needed to use the deliverables."
Overreaching:
"All work product, inventions, and materials created by the Contractor during the term, whether or not related to the engagement, shall be the sole property of the Client."
"Whether or not related to the engagement" is the tell. That phrasing can claim ownership over a side project you build on your own time. A fair clause is limited to what you made for this client, with your background IP protected. See the IP clause deep-dive for the exact carve-out language to request.
Clause 6 — Indemnification (Mutual + Capped at Fees Paid)
Indemnification is the clause that determines what happens to your finances if something goes wrong. It's a promise to cover the other party's losses, including legal fees, if you breach the agreement. The danger in a freelance NDA is an indemnification clause that runs one direction (only you owe the client) and has no cap (your exposure is unlimited, regardless of how small the project was).
A fair indemnification clause is mutual — both sides indemnify each other for their own breaches — and capped, typically at the total fees paid under the engagement.
Fair:
"Each party's total liability arising out of this Agreement shall not exceed the total fees paid under the engagement. Neither party shall be liable for indirect or consequential damages. This limitation shall not apply to breaches involving willful misconduct or fraud."
Overreaching:
"The Contractor shall indemnify and hold harmless the Client from any and all losses, damages, and expenses, including attorneys' fees, arising from any breach of this Agreement."
The second version has no ceiling. A $1,500 project can carry six-figure exposure. A cap tied to fees paid keeps your worst case proportional to the size of the deal — which is the whole point. The full mechanics are in the indemnification clause guide.
Clause 7 — Dispute Resolution (Mutual Jurisdiction)
If a dispute ever arises, this clause decides where and how it gets resolved. The unfair pattern is a jurisdiction clause that forces you to litigate in the client's home state or country — which, if they're across the world from you, effectively means you can never afford to defend yourself.
A fair NDA either picks a neutral, mutually convenient jurisdiction or provides for a low-cost resolution method like mediation or arbitration before litigation. The key word is mutual: the same rules apply to both sides.
Fair:
"Any dispute shall first be submitted to good-faith mediation. If unresolved, disputes shall be resolved in a mutually agreed jurisdiction, with each party bearing its own costs."
Overreaching:
"Any dispute shall be resolved exclusively in the courts of [Client's distant jurisdiction], and the Receiving Party consents to personal jurisdiction there."
If the client is in a different country and the clause forces their courts on you, that's a structural disadvantage baked into the agreement. The jurisdiction clause guide explains how to propose a neutral alternative.
Clause 8 — Return and Destruction (Reasonable Version with Carve-Outs)
When the engagement ends, it's reasonable for the client to ask you to return or destroy their confidential information. A fair clause makes this practical: it gives you a defined window, accepts destruction as an alternative to return, and carves out copies you're legally required to keep or that live in routine backups you can't surgically delete.
Fair:
"Upon termination, the Receiving Party shall return or destroy the Confidential Information within thirty (30) days, except for copies retained in routine backups or as required by law, which remain subject to the confidentiality obligations of this Agreement."
Overreaching:
"Upon termination, the Receiving Party shall immediately return and permanently delete all Confidential Information and all copies from all systems, and certify such deletion under penalty of perjury."
"Immediately," "all copies from all systems," and a perjury certification set a standard no one with automated backups can honestly meet. A fair version is reasonable about the realities of how data actually gets stored, and keeps retained copies protected rather than pretending they don't exist.
Full Example: Fair NDA Opening
Here's roughly what the opening of a balanced freelance NDA reads like, combining the principles above. This is illustrative only — not legal advice, and not a document to sign as-is. It's a reference for the tone and shape of fair language, so you can compare it against what lands in your inbox.
Mutual Non-Disclosure Agreement
This Agreement is entered into between [Client] and [Contractor] to protect confidential information shared in connection with [project]. Both parties may disclose confidential information, and both agree to the obligations below.
"Confidential Information" means non-public information a party designates as confidential or that a reasonable person would understand to be confidential given the circumstances. It does not include information that is public, was already known, is independently developed, is received from a third party, or is required to be disclosed by law (with prompt notice where permitted).
Each party agrees to use the other's Confidential Information solely for the purpose of the engagement, to protect it with reasonable care, and not to disclose it to third parties without consent. These obligations continue for two (2) years after the engagement ends, except for trade secrets, which remain protected as long as they qualify as such under applicable law.
Each party's liability under this Agreement is limited to the total fees paid under the engagement, and neither party is liable for indirect or consequential damages, except in cases of willful misconduct or fraud.
Notice what's not there: no non-compete, no all-encompassing IP grab, no perpetual term, no unlimited liability. That absence is what makes it fair.
Received an NDA That Doesn't Look Like This?
If the NDA on your desk is longer, denser, and full of the "overreaching" language above rather than the "fair" version, you don't have to reverse-engineer every clause by hand. NDA Guard reads the agreement, flags exactly where it deviates from the fair standard laid out here, scores the risk, and drafts the counter-language to send back — in plain English. It's built specifically for freelancers who get NDAs from clients and need to know, in a few minutes, what's standard and what's not. See how it works for freelancers specifically.
FAQ
Do I need a lawyer to review a standard freelance NDA?
Not always. For a routine engagement where the NDA matches the fair pattern above — specific confidentiality definition, standard exclusions, defined term, no non-compete, capped mutual liability — you can reasonably sign it yourself. Where a lawyer earns their fee is when the agreement contains the overreaching provisions (perpetual terms, unlimited indemnification, broad IP grabs, non-competes) and the engagement is large enough that the risk justifies the cost. Knowing what fair looks like helps you spend legal budget only where it matters.
Can I edit an NDA a client sends me, or do I have to sign it as-is?
You can almost always propose edits. An NDA is a negotiable contract, not a take-it-or-leave-it form, and asking for standard, reasonable changes is normal professional practice — not a sign you're difficult to work with. Most clients, especially smaller ones without in-house counsel, accept fair edits without friction once you frame them as bringing the agreement in line with market standard. How to negotiate an NDA as a freelancer covers the exact wording to use.
Is a mutual NDA better than a one-way NDA for freelancers?
Usually, yes. A mutual NDA protects both parties' confidential information and applies the same obligations to both sides — which reflects the reality that freelancers often share their own methods, tools, and prior work during an engagement. A one-way NDA puts all the obligation on you. That said, a one-way NDA isn't automatically bad if you're genuinely the only party sharing anything sensitive; the structure should match the actual flow of information. See mutual vs unilateral NDAs.
What's the single most important clause to check?
The exclusions clause (Clause 2). Its absence is the clearest signal of a carelessly drafted or deliberately overreaching NDA, because standard exclusions are non-negotiable in any fair agreement — they protect information you have every right to (public knowledge, your own prior work). If the exclusions are missing, read the rest of the document with extra scrutiny, because the drafter either didn't know better or didn't care to be fair.
How long should a freelance NDA be?
There's no magic length, but fair NDAs tend to be shorter rather than longer — often two to four pages. Extreme length usually signals that the document is doing more than protecting confidential information: it's added non-competes, sweeping IP assignments, and liability provisions that belong elsewhere. A ten-page "NDA" isn't automatically abusive, but it's a prompt to read carefully for the scope creep described throughout this post.
Compare What You Received Against the Fair Standard
A fair freelance NDA is not complicated: it defines confidential information specifically, includes standard exclusions, sets a reasonable term, skips the non-compete, limits IP assignment to actual deliverables, caps liability at fees paid, keeps jurisdiction mutual, and stays reasonable about returning data. Everything beyond that is worth questioning.
If you want to check the one in front of you against that standard without parsing the legalese yourself, NDA Guard does exactly that — clause by clause, in the same terms this post uses. Start with How to Review an NDA for the manual approach, or run yours through the tool and see what's different in a couple of minutes.