8 NDA Red Flags Every Freelancer Should Know (With Examples)
Research from independent contractor surveys consistently finds that 1 in 3 freelancers has signed an NDA with a clause that limited their future work — often without realizing it until after the damage was done. A non-compete that covers their entire industry. An IP assignment that captured tools they'd built years earlier. A survival clause that created confidentiality obligations with no end date.
NDAs are routine. The red flags inside them are not obvious. And because freelancers typically sign without legal counsel — you're excited about the project, the client seems legitimate, and pushing back on legal documents feels like bad form — these clauses go unchallenged.
This post breaks down the eight most dangerous NDA provisions, with real examples of risky language, an explanation of why each one matters, what market standard actually looks like, and counter-language you can use to push back professionally.
If you want the full process for reviewing an NDA from start to finish, read How to Review an NDA Before You Sign first. This post focuses specifically on the clauses most likely to hurt you.
Red Flag #1 — Non-Compete With No Time Limit (or Over 2 Years)
"Contractor agrees not to engage in any competitive business activity for a period of five (5) years following the termination of this Agreement."
Why it's dangerous: A five-year non-compete is not a protective measure — it's a career restriction. For a freelancer, this clause could prevent you from taking on clients in your primary industry for half a decade. Courts in some jurisdictions will reduce unreasonable durations, but you shouldn't rely on litigation to make a bad clause workable. And in jurisdictions that don't scrutinize non-competes closely, you'd be bound to the full term.
What market standard looks like: Non-competes in freelance NDAs should be limited to 12 months from the end of the engagement. Up to 18 months is sometimes acceptable for senior advisory roles with genuine access to strategic information. Anything beyond 24 months is almost never commercially justified for a contractor relationship, and should be flagged regardless of the project.
Counter-language: "Contractor agrees not to engage in any directly competitive business activity for a period of twelve (12) months following the termination of this Agreement."
Red Flag #2 — Non-Compete With No Geographic or Industry Limit
"During the term of this Agreement and for eighteen (18) months thereafter, Contractor shall not provide services to any company that competes with Client in any market globally."
Why it's dangerous: "Any company that competes in any market globally" is not a non-compete — it's a blanket prohibition on working in your field. A clause like this could theoretically prevent a designer from working with any software company, or a copywriter from serving any SaaS business, because the client happens to have a product in that category. Without geographic or industry scope, the restriction is defined entirely by what the client decides to claim as competition.
What market standard looks like: Non-competes should be scoped to direct competitors — ideally named in a schedule — within the geographic markets where the client actually operates. "All companies in the global SaaS industry" is not a reasonable competitor definition for a client with regional operations. The tighter the definition, the more enforceable and the fairer the clause.
Counter-language: "Contractor shall not provide services to any company listed in Exhibit A (Direct Competitors) during the twelve (12) month period following termination, within the geographic markets where Client operates as of the termination date."
Red Flag #3 — IP Assignment With No Pre-Existing IP Carve-Out
"All work product, inventions, tools, libraries, and materials created or used by Contractor in connection with this Agreement shall be the sole and exclusive property of Client."
Why it's dangerous: "Created or used" is the phrase that turns a reasonable IP assignment into a trap. If the clause captures materials you use — not just what you create for this specific engagement — then any pre-existing tools, frameworks, templates, or libraries you bring to the project become the client's property. A developer who incorporates a logging utility they built two years ago could find that utility is now legally owned by this client. That's not hypothetical — it's a recurring pattern in contractor disputes.
What market standard looks like: IP assignment should be scoped to work product created specifically for this engagement. There should be an explicit carve-out — often called a "pre-existing IP carve-out" or "background IP carve-out" — that excludes tools, methodologies, and materials you developed prior to or independently of this project. Ideally these are listed in a schedule you both sign.
Counter-language: "Client shall own all work product created specifically and solely for Client under this Agreement. Notwithstanding the foregoing, Contractor retains all rights to pre-existing tools, libraries, templates, and methodologies ('Background IP'), including any incorporated into deliverables. Contractor grants Client a perpetual, non-exclusive license to use Background IP as incorporated into the deliverables."
Red Flag #4 — Confidentiality Covering Publicly Available Information
"All information disclosed by Client to Contractor, whether oral, written, electronic, or otherwise, shall be considered Confidential Information regardless of whether it has been publicly disclosed."
Why it's dangerous: A confidentiality clause with no carve-out for public information means you could theoretically be held liable for discussing something the client announced in a press release. More practically, it makes the obligations impossible to comply with — you can't un-know publicly available information, and you can't avoid referencing it in future work. Clauses like this also tend to be interpreted expansively in disputes: the client defines the scope, and without carve-outs, their definition has no natural limit.
What market standard looks like: Confidentiality should cover genuinely sensitive information: customer data, financial projections, technical specifications, business strategy. Standard carve-outs include: (1) information already in the public domain through no fault of the recipient; (2) information the recipient already knew before disclosure; (3) information independently developed without use of the disclosed materials; (4) information received from a third party without restriction.
Counter-language: "'Confidential Information' shall not include information that: (a) is or becomes publicly available other than through Contractor's breach; (b) was in Contractor's possession prior to disclosure; (c) is independently developed by Contractor without use of the disclosed materials; or (d) is rightfully received from a third party without restriction."
Not sure if your NDA has these red flags? NDA Guard scans for all 8 automatically — risk scored, plain English, with counter-language ready to paste. Try your first review free →
Red Flag #5 — Unlimited Indemnification With No Cap
"Contractor shall defend, indemnify, and hold harmless Client and its officers, directors, employees, and agents from and against any and all claims, damages, losses, and expenses, including attorneys' fees, arising out of or relating to Contractor's breach of this Agreement."
Why it's dangerous: An uncapped indemnification clause means your financial exposure has no ceiling. If the client faces a lawsuit — even a frivolous one — and they decide your alleged breach contributed to it, you could be on the hook for their full legal defense costs plus any damages awarded. "Arising out of or relating to" is the other danger here: it's broader than "arising directly from," which means the client can draw a connection to your conduct even when it's indirect or contested.
What market standard looks like: Indemnification in freelance NDAs should be capped at the total fees paid under the contract. It should also be limited to claims arising directly and solely from your proven breach — not claims that are tangentially related. Most standard agreements also require that the indemnifying party receive prompt written notice of any claim and have the right to participate in its defense.
Counter-language: "Contractor's indemnification obligations under this Agreement shall not exceed the total fees paid to Contractor in the twelve (12) months preceding the claim. Contractor shall have no indemnification obligation for claims arising from Client's own acts, omissions, or negligence."
Red Flag #6 — Liquidated Damages Clause
"In the event of any unauthorized disclosure of Confidential Information, Contractor agrees to pay Client liquidated damages in the amount of $25,000 per breach, which the parties acknowledge represents a reasonable estimate of harm."
Why it's dangerous: Liquidated damages clauses set a fixed financial penalty per breach — regardless of whether any actual harm occurred. Under this clause, accidentally mentioning a project name to the wrong person costs $25,000, even if nothing was disclosed, no one was harmed, and the client suffered no measurable loss. The phrase "reasonable estimate of harm" is the client pre-justifying a penalty in the contract itself, making it harder to challenge later.
What market standard looks like: Liquidated damages clauses are unusual in standard freelance NDAs. They appear occasionally in highly sensitive engagements — pharmaceutical research, financial services — but even there, the per-breach amounts are typically proportionate to documented risk. If you see a liquidated damages clause in a routine freelance NDA, it's worth flagging every time. Most clients will remove it if you ask professionally.
Counter-language: Remove the liquidated damages clause entirely, or: "The parties agree that damages for any breach shall be limited to actual, documented losses suffered by Client directly attributable to such breach, subject to the liability cap set forth in Section [X]."
Red Flag #7 — Jurisdiction in a Foreign State or Country
"This Agreement shall be governed by and construed in accordance with the laws of the State of Delaware, and the parties submit to the exclusive jurisdiction of the courts of Delaware for any disputes arising hereunder."
Why it's dangerous: If you're based in London, Sydney, Berlin, or anywhere other than Delaware, this clause means any dispute requires you to either hire Delaware-licensed counsel, appear in Delaware courts, or default on the dispute because the cost of participation is prohibitive. That's not a neutral choice — it's an enforcement advantage for the client, who likely has local presence or counsel in that jurisdiction. For smaller disputes, it effectively prevents you from seeking any remedy at all.
What market standard looks like: Jurisdiction and governing law should default to your location, or the client's location if both parties are in the same country. For international engagements, binding arbitration through a recognized body (AAA, JAMS, or ICC) in a mutually agreed neutral location is common and fair. Online arbitration options have expanded significantly and can be specified for contracts below a certain value threshold.
Counter-language: "This Agreement shall be governed by the laws of [Contractor's jurisdiction]. Any disputes shall be resolved by binding arbitration administered by [AAA/JAMS/ICC] in [City], or via online arbitration for claims under $[X]. The prevailing party shall be entitled to recover reasonable attorneys' fees."
Red Flag #8 — Survival Clause With No Sunset Date
"The obligations of confidentiality set forth in this Agreement shall survive the termination or expiration of this Agreement and shall remain in full force and effect indefinitely."
Why it's dangerous: A survival clause with no sunset date means your confidentiality obligations never expire. Information you received in a six-month engagement in 2025 could legally restrict what you say or do in 2040. This is particularly problematic in fast-moving industries: information that is genuinely sensitive today may be public knowledge, obsolete, or freely discussed in three years. Indefinite survival clauses also create compliance nightmares — you're expected to maintain records and caution around information that may no longer exist or matter.
What market standard looks like: Confidentiality obligations should survive termination for a defined period: typically 2–5 years for general business information, and up to 7 years for trade secrets in genuinely sensitive industries. After that period, the obligations should expire — or at minimum, convert to a lower standard of care (reasonable precautions rather than the full contractual standard). Information that becomes publicly available should exit the confidential category regardless of the survival clause.
Counter-language: "The confidentiality obligations in this Agreement shall survive termination for a period of three (3) years. Obligations with respect to trade secrets shall survive for five (5) years or until such information enters the public domain, whichever occurs first."
FAQ
Do NDA red flags mean I should refuse to sign?
No. A red flag means negotiate, not walk away. Most of the clauses above appear in standard NDAs because the client's legal team drafted them to be as protective as possible — not because the client specifically intends to enforce them aggressively. When you push back professionally with specific counter-language, most clients will engage. The ones who refuse to modify genuinely one-sided terms are telling you something useful about how the relationship will go.
Which NDA red flag is the most dangerous for freelancers?
IP assignment without a pre-existing IP carve-out causes the most lasting financial harm, because it's immediately enforceable and hard to undo. A non-compete might be challenged or might expire — but once you've handed over ownership of your pre-existing tools, reclaiming them typically requires litigation. If you only have bandwidth to scrutinize one clause closely, make it the IP assignment section.
How do I bring up NDA red flags without damaging the client relationship?
Frame it as making the agreement workable, not as an accusation. Something like: "I've reviewed the NDA and have a couple of questions on clauses 3 and 6. Happy to send tracked changes or discuss on a quick call — shouldn't take long." Most legitimate clients understand that professional contractors read what they sign. The ones who don't are worth knowing about before the engagement starts.
Can I use counter-language from this post in an actual negotiation?
The counter-language examples above are starting points for negotiation, not legally reviewed templates. They're designed to show you what reasonable alternative language looks like so you can approach the conversation from a position of knowledge. For high-value engagements or complex terms, have a qualified attorney review the final language before you sign. For routine freelance NDAs, these examples will get you most of the way there.
Are NDA red flags different for different types of freelancers?
The core red flags are consistent — IP assignment, non-compete scope, indemnification caps, and jurisdiction matter for designers, developers, consultants, and writers alike. The weight of each varies by profession. Developers and product designers face more IP assignment risk because of pre-existing tools and frameworks. Writers and consultants face more non-compete risk because their "competitive activity" is often defined broadly. The NDA review for freelancers page covers how these risks break down by profession if you want a more targeted breakdown.
A Red Flag Is a Starting Point, Not a Deal-Breaker
None of the eight clauses above automatically means you should refuse the engagement. Non-competes are legitimate. Indemnification makes sense. IP assignment is standard. The problem isn't the clause type — it's the scope, the duration, and the absence of the limits that make these obligations reasonable.
Reading an NDA with this list in hand takes fifteen minutes. It tells you whether you're signing something fair or something that's going to limit your career and finances in ways you didn't agree to. And when you find a red flag, you now have specific counter-language to propose — which is the difference between a professional negotiation and an awkward objection.
For a faster path, NDA Guard reviews your full NDA automatically — flags all eight risk categories, explains every flagged clause in plain English, and gives you counter-language ready to paste. You can also read more about how to structure the full review process if you want a step-by-step walkthrough. For pricing information, see what NDA Guard costs.
The document in your inbox is probably fine. But you won't know until you look.