Key Points in This Guide
- 1What information is typically covered by freelance confidentiality clauses
- 2The difference between NDA and general contract confidentiality provisions
- 3Duration: how long do confidentiality obligations last?
- 4Portfolio rights: can you show work covered by a confidentiality clause?
- 5Testimonials and case studies: what you can ask for
- 6How to negotiate a portfolio rights carve-out
Confidentiality clauses are standard in most freelance and contractor agreements — and most freelancers sign them without fully understanding what they cover. A broad confidentiality clause can prevent you from mentioning the client on your website, showing the work in your portfolio, or even listing the engagement on your resume. Understanding what you are agreeing to before you sign protects your ability to market your services afterward.
What Confidentiality Clauses Actually Cover (And What They Don't)
Most freelancers sign confidentiality clauses without reading them carefully — and then discover months later that the clause prevents them from adding the work to their portfolio, mentioning the client on LinkedIn, or even listing the engagement on their resume. Understanding exactly what is covered protects your ability to market your services after the project ends.
| Typically Covered | Often Covered But Negotiable | Typically NOT Covered |
|---|---|---|
| Client trade secrets | Fact of the engagement itself | Your own skills and methods |
| Proprietary product info | Client name in portfolio | General industry knowledge |
| Unreleased product roadmaps | Work samples (blurred/anon) | Generic testimonials |
| Customer/user data | Revenue / financial details | Publicly available information |
| Internal processes | Team names and structures | Your own tools and frameworks |
| Pricing information | Project timelines | Work you created before the project |
One-Sided vs Mutual NDAs: What to Ask For
Most client-provided confidentiality clauses are one-sided: you agree to keep their information confidential, but they have no reciprocal obligation. This is often appropriate for standard client engagements, but becomes problematic when you share your own proprietary methods, pricing, or processes with the client.
If you are sharing your proprietary workflow, pricing model, or business methodology as part of the engagement, propose a mutual NDA. A mutual NDA protects both parties and is standard for agency-client relationships and senior consulting engagements. Most professional clients will accept it — and those who refuse are signaling that they intend to share your confidential information with others.
💬 Script: Requesting a portfolio rights carve-out
"The confidentiality clause as written would prevent me from showing this work in my portfolio, which affects my ability to market my services to other clients. I'd like to add a portfolio rights provision that allows me to display anonymized samples of the work for promotional purposes — without naming your company or disclosing any confidential business information. Here's the language I'd propose: 'Notwithstanding the foregoing, Contractor may display completed work product in Contractor's portfolio and marketing materials, provided that no Confidential Information of Client (including Client's name and branding) is disclosed.' Does that work for your team?"
Duration: When "Forever" Is Too Long
Confidentiality clauses with no end date — perpetual obligations — are common but often overreaching. Trade secrets warrant indefinite protection; general project information does not. Most professional legal standards treat business information as sensitive for two to three years, after which competitive relevance typically fades.
For general business information, propose a two-to-three year limitation. For trade secrets specifically, indefinite protection is reasonable. The distinction matters: "Client's Confidential Information shall mean... trade secrets (indefinitely) and all other confidential information (for two years following project completion)."
Also check whether there is a carve-out for information that becomes publicly available. If the client later publishes the work publicly (launches the product, publishes the article, releases the brand), your confidentiality obligation on that specific work should terminate. A well-drafted clause will say: "Confidentiality obligations do not apply to information that becomes publicly available through no fault of Contractor."
Have a contract to review?
Upload your contract now and get an AI risk analysis in under 90 seconds.