NDAs for Freelancers: When You Need One and What to Watch Out For

Sarah Mitchell

NDAs -- Non-Disclosure Agreements -- are one of the most frequently misunderstood documents in a freelance practice. Some freelancers sign them reflexively without reading them. Others refuse them on principle, losing work as a result. Most have a vague sense that they should probably read them more carefully but lack a framework for what to actually look for.

This guide gives you that framework. I'm not a licensed attorney, and this isn't legal advice -- it's a practical explanation of what NDAs do, which clauses are standard and reasonable, which ones should give you pause, and when you might want to push back before signing. For any specific NDA with unusual language or significant financial stakes, a 30-minute review with a contract attorney is worth the cost.

What an NDA Actually Does

An NDA creates a legal obligation for one or both parties to keep specified information confidential and not share it with third parties without permission. In a freelance context, the typical scenario is a client sharing information you need to do your work -- product plans, financial data, customer information, proprietary processes -- and wanting assurance that you won't share it with their competitors or disclose it publicly.

The mutual benefit that's often overlooked: an NDA also protects you. By defining exactly what counts as confidential, the NDA tells you what you can't share -- and by implication, what you can. A well-drafted NDA with a specific definition of confidential information means you know exactly where the line is. Without an NDA, the scope of your confidentiality obligations is unclear, which is actually worse.

What an NDA doesn't do: prevent you from using your general skills and knowledge developed during the engagement. Working on a project teaches you things -- about the client's industry, about technical approaches, about business challenges. That learning is yours. An NDA prevents you from disclosing the client's specific confidential information, not from applying general expertise you developed.

The enforceability question: NDAs between companies and freelancers (independent contractors) are generally less well-enforced than those between employers and employees. Courts apply stricter scrutiny to contracts that restrict an individual's ability to earn a living from their skills. This doesn't mean you can ignore NDA obligations, but it does mean the risk profile is different from what most clients assume when they hand you a standard employment-style NDA.

Free tools for this topic

The Standard NDA: What Every Clause Means

Definition of confidential information: the most important clause. It defines exactly what you're agreeing to keep confidential. A well-drafted definition is specific: 'technical specifications, product roadmaps, customer lists, financial projections, and other business information marked as confidential.' A problematic definition is excessively broad: 'any information disclosed by either party during the course of this relationship.' The broad version can restrict you from discussing general methods, approaches, or even your existence as a client's vendor. Push back on overly broad definitions and ask for specific categories.

Exclusions from confidentiality: standard NDAs include exclusions for information you already knew before the engagement, information that becomes publicly available through other means, information you received from other sources without confidentiality obligations, and information you independently developed. These exclusions are necessary to prevent the NDA from restricting knowledge you legitimately possess. If an NDA lacks these exclusions, it's a red flag.

Term (duration): how long the confidentiality obligation lasts. One to three years is standard for most commercial NDAs. 'Indefinitely' or 'forever' is unusual and worth questioning, particularly for information that will become stale or irrelevant quickly. Five years or more is unusual for freelance relationships.

Return or destruction of materials: most NDAs require you to return or destroy confidential materials at the end of the engagement. This is reasonable and worth complying with actively -- having client materials on your systems after an engagement ends creates unnecessary risk.

Remedy clause: what happens if you breach the NDA. Standard language describes the right to seek injunctive relief (a court order stopping you from disclosing) and damages. Look for disproportionate penalty clauses -- an NDA that specifies fixed damages of $500,000 for any breach is unusual and worth negotiating.

The Non-Compete Hidden in the NDA

The single most important thing to check in any NDA: does it contain a non-compete clause? A non-compete restricts you from working for competitors or in the same industry for a defined period after the engagement. This is a fundamentally different obligation from confidentiality, and it has much more significant financial implications for a freelancer.

Non-compete clauses in NDAs are more common than most freelancers realise. They're often buried in a section titled 'Additional Covenants' or 'Restrictions' after the confidentiality provisions. If you've been reading an NDA assuming it's only about confidentiality and not checking for non-compete language, you may have signed restrictions on your ability to work with entire categories of clients.

What to look for: any language restricting you from working with 'competitors' of the client, from working in specific industries or markets, or from soliciting the client's customers or employees for a defined period. Any of these is a non-compete provision.

How to respond to a non-compete in an NDA: decline to sign as presented and explain why. 'I'm happy to agree to confidentiality obligations, but I can't agree to a non-compete restriction -- my practice depends on working across multiple clients in adjacent industries. Can we remove that section?' Most reasonable clients will agree to remove the non-compete from the NDA and keep the confidentiality provisions. Clients who insist on a non-compete should be pushing you to consult an attorney before signing.

Mutual vs One-Way NDAs

A one-way NDA (sometimes called a unilateral NDA) creates obligations for only one party -- typically the freelancer. You agree to keep the client's information confidential; the client agrees to nothing.

A mutual NDA (bilateral NDA) creates obligations for both parties. Both you and the client agree to keep each other's confidential information private. This is the appropriate structure for most freelance engagements because you're sharing information too -- your methods, tools, processes, and potentially proprietary approaches that you've developed.

The negotiation position: when presented with a one-way NDA, it's entirely appropriate to request a mutual NDA. 'I'm happy to agree to these confidentiality obligations, but I'd prefer a mutual structure since I'll also be sharing information about my methods and processes. Can we make this bilateral?' Most clients will agree -- the request signals professionalism rather than obstruction.

The practical difference: in a mutual NDA, the client agrees not to share your methods, tools, and proprietary processes with third parties. This is particularly valuable if you've developed templates, frameworks, or approaches that you use across multiple clients and would prefer not to have disclosed to competitors or co-opted without attribution.

When to Ask for an NDA (Not Just Sign One)

NDAs are a two-way protection tool that freelancers can also initiate. There are specific situations where you should be the one proposing the NDA.

When you're sharing genuinely proprietary work methods: if the engagement requires you to share a framework, system, or approach that represents real intellectual capital -- not generic skill, but something you've developed and invested in -- a mutual NDA protects you from the client sharing it without restriction.

When the client is a competitor or adjacent to your other clients: if you're working with a client who could benefit from knowing your other clients' information, the mutual NDA provides explicit protection for that information.

When the project involves information about your own client relationships: if a project requires you to discuss how you work with other clients (for workflow or process reasons), a mutual NDA protects those client relationships from being discussed beyond the engagement.

How to propose an NDA as the freelancer: 'Before we get into the specifics of the project, I'd like to sign a mutual NDA -- I'll be sharing some proprietary methods and process information, and I want to make sure we're both protected. I have a standard template I use for this -- would that work, or do you prefer to use yours?'

Having your own NDA template signals professionalism and ensures the document starts from language that's balanced rather than client-favoring. The contracts library includes a standard mutual NDA template.

Red Flags: When to Push Back or Walk Away

Most NDA issues are negotiable. These are the situations worth taking seriously.

Excessively broad confidentiality definition that includes 'all information shared' with no carve-outs: push back with a request for specific categories and standard exclusions.

Non-compete provisions embedded in the confidentiality agreement: negotiate removal of the non-compete. If the client insists, the engagement may not be worth the restriction on your practice.

Permanent confidentiality obligations with no term: push back with a request for a 2-3 year term. Permanent obligations on information that will become stale are unusual and inappropriate for most freelance engagements.

Liquidated damages clauses with disproportionate penalty amounts: negotiate to cap damages at the project value or to remove fixed-penalty clauses in favour of actual damages language.

Any language restricting your ability to work in your industry after the engagement without a direct non-compete label: this is a non-compete by another name and should be treated as one.

The situations where you walk away rather than negotiate: when the client refuses all negotiation on clauses that significantly restrict your practice (broad non-competes, permanent restrictions, unlimited liability), the engagement may not be worth the obligation. An NDA that prevents you from working with most of your target clients for two years after a three-month engagement is not a fair exchange for the project value.