How to Read an NDA: What Every Freelancer Needs to Know Before Signing

What an NDA Actually Is (and Isn't)

A non-disclosure agreement is a contract that says "I won't share your secrets." That's it. A client hires you to build their app, redesign their brand, or audit their books - they hand you sensitive information to do the job, and the NDA says you won't leak it to competitors, post it on Twitter, or use it to start a rival business. Perfectly reasonable.

What an NDA is not is a non-compete, a work-for-hire agreement, or a blanket gag order on your entire career. But badly written NDAs blur those lines constantly. A clause that defines "confidential information" as "anything the company has ever told you" can effectively prevent you from working in your own field. That's why reading the actual language matters more than trusting the label at the top of the page.

The 6 Clauses That Actually Matter

Most NDAs run 3-8 pages, but the substance lives in a handful of clauses. Here's where to focus your attention.

1. Definition of Confidential Information

This is the single most important clause. It determines what you're actually promising to keep secret. A well-drafted NDA will be specific: source code, customer lists, financial projections, unreleased product designs. A poorly drafted one will say something like:

"Confidential Information means any and all information, whether written, oral, electronic, or visual, disclosed by the Company to the Receiving Party, including but not limited to business strategies, technical data, customer information, and any other proprietary information."

That "any and all" plus "including but not limited to" combo is doing a lot of heavy lifting. In plain English, this says everything the client ever tells you is confidential - including stuff that's already public knowledge or that you already knew before the project started. That's a problem, and it's fixable (see the exclusions clause below).

2. Term Length

How long does this NDA last? Some NDAs expire after 1-2 years. Others say "in perpetuity," which means forever. For trade secrets like proprietary formulas or algorithms, perpetual terms can make sense. For general business information like org charts and marketing plans, a 2-3 year term is standard.

"The obligations of confidentiality shall survive the termination of this Agreement and shall continue in perpetuity."

Translation: you're bound by this agreement for the rest of your life. Ask yourself whether the information you're receiving genuinely warrants that. If a client is sharing their secret sauce recipe, sure. If they're sharing a project brief for a website redesign, perpetual confidentiality is overkill.

3. Exclusions

Good NDAs include carve-outs - situations where information is not considered confidential. Standard exclusions include:

• Information that's already publicly available (or becomes public through no fault of yours)
• Information you already knew before the engagement
• Information you independently developed without using the client's data
• Information a third party lawfully gave you

If the NDA has no exclusions clause at all, that's a red flag. You need these protections. Without them, a client could theoretically claim you violated the NDA by using knowledge you had before you ever met them.

4. Return of Materials

This clause says what happens to the client's files, documents, and data when the project ends. Typically, you're required to return or destroy all confidential materials and confirm in writing that you've done so.

"Upon termination of this Agreement, the Receiving Party shall promptly return or destroy all Confidential Information, including all copies, notes, summaries, and analyses derived therefrom, and shall certify in writing that such return or destruction has been completed."

The tricky part is "notes, summaries, and analyses derived therefrom." If you took notes during meetings, made internal memos about the project, or created any derivative work - those all need to go too. Make sure you understand what "derived from" means in practice before you sign. If you use a tool like ContractAnalyzerPro to parse the agreement, this is one of the clauses it'll flag for ambiguity, because "derived from" is interpreted differently across jurisdictions.

5. Non-Solicitation

Some NDAs sneak in a non-solicitation clause, which prevents you from poaching the client's employees or customers. On its own, a non-solicitation clause is fairly standard. The problem is when it's written so broadly that it prevents you from working with anyone the client has ever worked with.

"The Receiving Party agrees not to directly or indirectly solicit, hire, or engage any employee, contractor, or client of the Company for a period of twenty-four (24) months following the termination of this Agreement."

Read that carefully: it says you can't hire or engage any of their contractors or clients for two years. If you're a freelance designer and the client's customers include half the businesses in your city, this clause just locked you out of a massive chunk of your market. Push back on this. A reasonable version limits it to employees you directly worked with, not the entire client roster.

6. Remedies

This section describes what happens if you breach the NDA. Most NDAs include a clause about "irreparable harm" and the right to seek injunctive relief (a court order to stop you from sharing more information). That's standard.

What's not standard is a clause that includes pre-determined damages, attorney's fees payable only by you, or the right to audit your devices.

"In the event of a breach, the Receiving Party shall be liable for all damages, including consequential and punitive damages, and shall bear all costs of enforcement, including reasonable attorney's fees."

Translation: if they think you breached the NDA, you're paying for their lawyers too - even if a court ultimately sides with you. One-sided remedy clauses like this are negotiable. A fair version says each party bears their own legal costs unless a court finds an actual breach.

Red Flags That Should Make You Pause

Not every aggressive NDA is a dealbreaker, but certain patterns should make you slow down:

Overly broad definitions with no exclusions. If the NDA says "all information disclosed verbally or in writing" with no exclusions for public information or prior knowledge, the client is either using a bad template or intentionally casting a wide net. Either way, ask for exclusions.

Perpetual terms on non-trade-secret information. A 5-year-old project brief is not a trade secret. If the NDA doesn't distinguish between genuinely sensitive IP and routine business information, request a reasonable time limit.

One-sided everything. If every clause protects only the client - they can share your work, you can't discuss theirs; they can terminate at will, you're bound forever; they recover costs, you don't - the NDA isn't a mutual agreement. It's a liability trap.

Non-competes disguised as NDAs. If the "confidential information" definition is broad enough to cover general industry knowledge, and the term is long enough, the NDA effectively prevents you from working in your field. That's a non-compete, and in many states, it's unenforceable for independent contractors. But enforceability doesn't mean you want to spend money proving it in court.

What's Actually Negotiable

Freelancers often assume NDAs are take-it-or-leave-it. They're not. Here's what clients will typically agree to change if you ask professionally:

• Adding exclusions. Almost every client will agree to standard carve-outs for public information and prior knowledge. If they won't, that tells you something.
• Shortening the term. Proposing 2 years instead of perpetuity is reasonable and rarely meets resistance for non-trade-secret work.
• Making it mutual. If you're also sharing proprietary methods, processes, or tools during the engagement, the NDA should protect you too. A one-way NDA rewritten as mutual costs the client nothing and protects both sides.
• Narrowing the definition. Suggesting that "confidential information" be limited to information marked as confidential (or identified as confidential in writing within 10 days of oral disclosure) is a standard, well-accepted approach.
• Removing non-solicitation or limiting its scope. Most clients care about you not poaching their key employees. They usually don't need a clause that covers every contractor they've ever worked with.

The key is framing your requests as clarifications, not objections. "I want to make sure we're both clear on what's covered" lands better than "I won't sign this."

Before You Sign: The Freelancer's NDA Checklist

Run through this list every time an NDA lands in your inbox. It takes ten minutes and can save you years of headaches.

• Read the definition of confidential information. Is it specific or does it say "everything"? Are there exclusions for public info and prior knowledge?
• Check the term. How long are you bound? Is perpetuity justified for this type of work?
• Look for hidden non-competes and non-solicitations. Does the NDA restrict who you can work with after the project ends?
• Read the remedies clause. Are damages and legal costs one-sided? Is there an audit provision?
• Check if it's mutual. If not, should it be? Are you sharing anything proprietary too?
• Verify the return-of-materials clause. Do you understand what "derived from" means in context? Can you comply in practice?
• Run it through ContractAnalyzerPro. Get a plain-English breakdown that catches what you might miss on a quick read. Especially useful when you're reviewing multiple NDAs across different clients.
• Mark up and send back. If something needs changing, redline it and explain your reasoning. Clients who refuse reasonable changes are showing you how the working relationship will go.

NDAs are a normal part of freelance work. Most of them are fine. But "most" isn't "all," and the ones that aren't fine can follow you for years. Ten minutes of careful reading beats ten months of legal trouble every time.