Do freelancers really need to sign NDAs?

For engagements touching client data, strategy, pre-release products or customer lists — yes, it is reasonable and refusing it costs the work. What you should not do is sign unread. The few minutes spent on the survival period, the purpose clause and whether the NDA is one-way or mutual are what decide whether the agreement is routine or restrictive.

Can I put client work in my portfolio under an NDA?

Not by default. The purpose limitation in most NDAs restricts use of the client's information to performing the work, and a portfolio post is another use. The fix is a written showcase clause agreed before signing, an approved case study, or an anonymised description that reveals nothing confidential. Asking for the carve-out at signature stage is normal; asking after delivery is awkward.

What should I push back on in a client's NDA?

Survival periods beyond five years, definitions that sweep in "all information" without exclusions, mutual obligations when the exchange is one-way, and liquidated damages clauses sized far beyond any conceivable harm. Also check who signs: your business entity should be the party, not you personally, whenever you operate through one.

Is an NDA the same as an IP assignment?

No, and mixing them up is expensive. An NDA governs information exchanged; an IP assignment or work-for-hire clause transfers ownership of what you create. Many freelance engagements need both, as separate clauses. An NDA alone leaves ownership of your deliverables ambiguous — which is a dispute waiting for the invoice.

What happens if I accidentally leak something?

Most NDAs require prompt written notice once you become aware, and that notice requirement is usually enforceable independently of the leak itself. Notice the same day, contain the leak, document what happened. Clients sue over concealment far more often than over honest accidents that were reported immediately.

Should I send my own NDA or sign the client's?

Send your own when you are the one disclosing — your methods, your rate card, your other clients' identities. Signing yours is faster for the client than redlining theirs, which is why experienced freelancers keep a clean one-page NDA ready. When the client discloses to you, their paper is normal; just read it first.

Freelance NDA Generator

Freelancers meet NDAs from the receiving side: a client hands you their data, their unreleased products, their customer lists, and asks you to keep it quiet. The agreement is usually theirs, written for their protection — which is fine, as long as you notice what it asks of you. The clauses that touch freelance life most directly are the purpose limitation (you may use their information only to do the work, which is what blocks portfolio use), the survival period (the duty outlives the project), and the exclusions (you should not be liable for information that was already public).

Generate a one-way NDA below if you are the one who should be protected before sharing your own methods — or use it to understand the shape of what a client hands you. The sections after it cover the clauses freelancers most often regret not reading.

Disclosing party

Legal name as it should appear in the contract.

Receiving party

Purpose of the exchange

A narrow purpose protects you. 'Any business purpose' protects nobody.

Agreement term (years)

How long the agreement itself runs.

Obligations survive (years)

How long confidentiality outlives the agreement.

Governing state

Optional clausesReturn or destruction of materials on requestNon-solicitation of the other side's employeesResiduals clause (recipient keeps unaided-memory knowledge)

Fill in: Disclosing party name, Receiving party name — the document shows [PLACEHOLDERS] until you do.

Updates live as you edit the form.

NON-DISCLOSURE AGREEMENT (ONE-WAY)

This Non-Disclosure Agreement (the "Agreement") is made effective as of [DATE] (the "Effective Date") between:

  • [DISCLOSING PARTY] ("Party A"), and
  • [RECEIVING PARTY] ("Party B").

Party A is the "Discloser" and Party B is the "Recipient".



The Discloser wishes to explore a business relationship with the Recipient concerning performing contracted services for the client (the "Purpose"). In connection with the Purpose, the Discloser may disclose Confidential Information to the Recipient, and the Recipient agrees to protect it on the terms of this Agreement.



1. Definition of Confidential Information
"Confidential Information" means any non-public information the Discloser discloses to the Recipient, whether before or after the Effective Date, in any form — written, oral, electronic or visual — and whether or not marked "Confidential", that a reasonable person would understand to be confidential given its nature and the circumstances of disclosure. It includes business plans, financial data, pricing, customer and supplier lists, product roadmaps, source code, designs, research, know-how, and the existence and terms of this Agreement.

2. Standard exclusions
Confidential Information does not include information the Recipient can demonstrate: (a) is or becomes public through no breach of this Agreement; (b) the Recipient already lawfully knew before it was disclosed; (c) the Recipient lawfully receives from a third party who owes no duty of confidentiality; or (d) the Recipient develops independently without using or referring to the Confidential Information. A blending of Confidential Information with independently developed material does not make the blend non-confidential.

3. Obligations of the Receiving Party
The Recipient will: (a) keep the Confidential Information in strict confidence and protect it with at least the same care it applies to its own confidential information, and no less than reasonable care; (b) use it only to advance the Purpose and for no other benefit; (c) limit access to employees, affiliates and professional advisers who genuinely need it for the Purpose and who are bound by written obligations at least as protective as this Agreement; (d) remain responsible for any breach by a person or entity it permits to access the information; and (e) notify the Discloser promptly in writing upon becoming aware of any unauthorized use or disclosure.

4. Compelled disclosure
If law, regulation or a court order compels disclosure of Confidential Information, the Receiving Party may disclose the portion legally required, provided that where lawful it gives the Discloser prompt written notice and reasonable cooperation so the Discloser can seek a protective order or confidential treatment before disclosure.

5. No licence; no obligation to proceed
Nothing in this Agreement transfers any intellectual-property right or grants any licence, by implication or otherwise. Confidential Information is provided "as is"; the Discloser makes no warranty of its accuracy or completeness. Disclosing or receiving Confidential Information does not obligate either party to enter into any further agreement or to refrain from developing products independently.

6. Return or destruction of materials
On the Discloser's written request, the Receiving Party will promptly return or destroy all materials embodying Confidential Information and, on request, confirm that it has done so in writing. Records retained by automatic backup systems, and records whose retention is required by law, are exempt until deleted in the ordinary course.

7. Term and survival
This Agreement begins on the Effective Date and continues for 2 years, unless both parties end it earlier in writing. The confidentiality obligations survive for 3 years after the Agreement ends or the relevant information is disclosed, whichever is later. Ending the Agreement does not end the duty of confidence.

8. Remedies
Breach of this Agreement may cause irreparable harm for which damages alone are an inadequate remedy. The parties agree that injunctive relief, in addition to all other remedies available at law or in equity, is an appropriate means of protecting Confidential Information.

9. Governing law
This Agreement is governed by the laws of the State of [STATE], without regard to its conflict-of-laws rules.

10. General
This Agreement is the entire agreement between the parties on its subject matter and supersedes earlier discussions on that subject. Amendments must be in writing and signed by both parties. Failure to enforce any term is not a waiver of it. If a court strikes any term, the remainder continues in force. Neither party may assign this Agreement without the other party's written consent.



Signed for the parties:

[DISCLOSING PARTY]                           [RECEIVING PARTY]

Signature: ______________________     Signature: ______________________
Name: ______________________     Name: ______________________
Title: ______________________     Title: ______________________
Date: ______________________     Date: ______________________

A solid starting draft, not legal advice. Have a lawyer review any agreement that protects something you would genuinely hate to lose — and remember that a trade secret only stays protected if you also treat it like one.

Starting values are set for a typical freelancers scenario — change any field to match yours. Need the plain version? NDA Generator.

What a client NDA actually asks of you

Most of it is reasonable once you have read it once. These are the working obligations you are accepting:

Care standard — protect the client's information at least as well as your own confidential material, which for a freelancer means separating devices or accounts where practical and never reusing one client's material on another's project.
Purpose limitation — you may use what you learn only to perform the contracted work. This is the clause that stands between your finished project and your portfolio page.
Need-to-know access — if you subcontract, you generally may not loop in a sub without the client's permission, because the agreement binds you and whoever you allow access becomes your responsibility.
Return or destruction — on request you must delete the client's files and sometimes certify that you did. Backups usually get a grace period, not an exemption to ignore.
Breach notice — if a laptop is stolen or an email goes to the wrong client, prompt written notice is normally required. It is also what protects you: late notice turns an accident into a breach.

The portfolio problem, and how freelancers solve it

The purpose limitation means a strict NDA forbids showing the work, naming the client, or describing the problem you solved — which collides with how freelancers actually win the next client. The standard fixes, in order of how often they are accepted:

A showcase carve-out: written wording permitting you to display the delivered work, or an anonymised description of it, after the product ships or the engagement ends. Ask for it before signing — adding it later is a favour, adding it now is a term.
An agreed case study: some clients prefer to write the description themselves and approve the screenshot, which takes the conflict off your shoulders.
Anonymisation by default: "a fintech client" with metrics and no name rarely triggers the NDA's purpose clause, provided nothing in the detail is itself confidential.
The honest fallback: without permission, you wait. Confidentiality obligations end on their schedule, not when the case study would be convenient.

Where freelancer NDAs go wrong

Signing a mutual NDA when you only receive. A mutual agreement makes your own client list, pricing and methods the other side's confidential information — ask for one-way, or read exactly what you just handed over.
Perpetual or absurdly long survival. Three to five years is normal; "forever" is a red flag worth negotiating down.
"All information is confidential" with no exclusions. Without the standard exclusions you could technically breach it by repeating something the client had already published.
Confusing the NDA with the IP assignment. Ownership of the work you produce lives in the contract's IP clause, not the NDA. Signing an NDA neither assigns your copyright nor makes the work work-for-hire — check that clause separately.
One agreement for the wrong entity. If you operate through an LLC or company, the agreement should name it, not you personally — otherwise your personal assets sit behind the obligation.

Frequently asked questions

Do freelancers really need to sign NDAs?: For engagements touching client data, strategy, pre-release products or customer lists — yes, it is reasonable and refusing it costs the work. What you should not do is sign unread. The few minutes spent on the survival period, the purpose clause and whether the NDA is one-way or mutual are what decide whether the agreement is routine or restrictive.
Can I put client work in my portfolio under an NDA?: Not by default. The purpose limitation in most NDAs restricts use of the client's information to performing the work, and a portfolio post is another use. The fix is a written showcase clause agreed before signing, an approved case study, or an anonymised description that reveals nothing confidential. Asking for the carve-out at signature stage is normal; asking after delivery is awkward.
What should I push back on in a client's NDA?: Survival periods beyond five years, definitions that sweep in "all information" without exclusions, mutual obligations when the exchange is one-way, and liquidated damages clauses sized far beyond any conceivable harm. Also check who signs: your business entity should be the party, not you personally, whenever you operate through one.
Is an NDA the same as an IP assignment?: No, and mixing them up is expensive. An NDA governs information exchanged; an IP assignment or work-for-hire clause transfers ownership of what you create. Many freelance engagements need both, as separate clauses. An NDA alone leaves ownership of your deliverables ambiguous — which is a dispute waiting for the invoice.
What happens if I accidentally leak something?: Most NDAs require prompt written notice once you become aware, and that notice requirement is usually enforceable independently of the leak itself. Notice the same day, contain the leak, document what happened. Clients sue over concealment far more often than over honest accidents that were reported immediately.
Should I send my own NDA or sign the client's?: Send your own when you are the one disclosing — your methods, your rate card, your other clients' identities. Signing yours is faster for the client than redlining theirs, which is why experienced freelancers keep a clean one-page NDA ready. When the client discloses to you, their paper is normal; just read it first.