A confidentiality clause is usually framed as something that protects the client, they share sensitive business information with you, and the clause prevents you from disclosing it. That’s accurate as far as it goes. But freelancers routinely share their own sensitive information during a project too: their processes, their pricing, their client list, their methodologies. A well-written confidentiality clause protects both sides, and the distinction between one-sided and mutual matters more than most freelancers recognize before they’re on the wrong end of one.
What a Confidentiality Clause Covers
The clause defines what counts as confidential information, who can receive it, and what the receiving party is obligated to do with it. The coverage question is the most important: “confidential information” defined too narrowly creates gaps; defined too broadly creates operational problems.
A practical definition covers information that is: (a) marked as confidential at the time of disclosure, or (b) of a type that a reasonable person would understand to be confidential given the context. This second category matters because most client information shared during a project is never explicitly labeled, pricing strategy, personnel decisions, unreleased product plans. The “reasonable person” standard captures these without requiring the client to stamp everything with a CONFIDENTIAL header.
Exclusions are equally important. Standard exclusions: information already publicly available at the time of disclosure, information you independently developed without reference to the confidential materials, information you received from a third party without restriction, and information you’re required to disclose by law. Without these exclusions, the clause can make you responsible for keeping secret things that were never actually secret.
Making It Mutual
One-sided confidentiality agreements protect the client and give you nothing. You share your processes, your tools, your pricing structures, sometimes your client relationships, and none of that is covered unless the clause explicitly runs in both directions.
A mutual clause applies the same obligations to both parties: the client agrees not to disclose your proprietary methods, your rates, or any other information you’ve shared in confidence during the engagement. In practice, clients rarely misuse this information, but having the protection in writing changes the posture of the relationship. It signals that confidentiality is a shared obligation, not a restriction imposed on you.
Some clients will push back on mutual language, particularly larger organizations with standard vendor contracts. The pushback is usually about their legal team’s preference, not a genuine objection to the principle. You can usually negotiate mutuality by narrowing what you’re asking them to protect, your pricing structure and proprietary processes, specifically, rather than a broad mutual clause.
What the Clause Must Include
Beyond the definition and mutuality, a functional confidentiality clause needs:
Duration. How long does the obligation last? “For the duration of the project” is too short; a client can wait until the contract ends and then disclose freely. “Perpetually” is unenforceable in some jurisdictions and often impractical. A defined period, two to five years, is the standard in professional services contracts. If the information has a natural shelf life (a product launch date, for instance), tie the duration to that.
Permitted use. The client can use your confidential information for the purpose of the project and nothing else. You can use their confidential information for the purpose of delivering the contracted work. Neither party should be using the other’s confidential information for other purposes.
Permitted disclosure. Who can the receiving party share the information with? For the client, that typically means their internal team members who need it to manage the project. For you, it might mean subcontractors or assistants involved in the work. Specify this explicitly and add a condition: anyone who receives the information is bound by the same obligations.
Return or destruction. On project completion or termination, what happens to the confidential information? The standard is: return it to the disclosing party or destroy it on request. This rarely comes up in practice, but the clause should address it.
The NDA Question
A standalone NDA (non-disclosure agreement) covers the same ground as a confidentiality clause embedded in your main contract, it’s just a separate document. Some clients, particularly larger organizations, prefer a standalone NDA signed before any project discussions begin. This protects the information shared during the sales process as well as the project itself. The basics of freelance NDAs covers what a standard standalone NDA should and shouldn’t include.
If a client sends you an NDA before engagement, read it the same way you’d read a confidentiality clause in a project contract: check that it’s mutual, check the duration, check the definition of confidential information, and check whether it restricts you from working with their competitors. That last one, a non-compete embedded in what’s presented as a simple NDA, is worth flagging and negotiating.
A non-compete in an NDA is a significant restriction. It can prevent you from taking on similar work in the same industry for the duration of the agreement. Enforceability varies by jurisdiction (they’re largely unenforceable against independent contractors in many places), but they’re worth removing from the document rather than relying on them being unenforceable if challenged.
Writing It Without Sounding Like a Lawyer
The confidentiality clause doesn’t need to be written in legalese to be enforceable. Plain language is legally valid, and it’s easier for both parties to understand what they’re agreeing to.
A working example:
“Each party may disclose to the other certain confidential or proprietary information in connection with this project (‘Confidential Information’). Each party agrees to: (a) keep the other’s Confidential Information strictly confidential; (b) use it only for purposes of this engagement; and (c) not disclose it to any third party without prior written consent, except to employees or contractors who need it to perform the work and are bound by equivalent obligations. This obligation survives termination of this agreement for three years. Confidential Information does not include information that is publicly available, independently developed, or received from a third party without restriction.”
That’s under 100 words and covers the core obligations. You can expand it with the return/destruction provision and the permitted disclosure list, but the core is there and it’s readable.
The clauses that actually protect you in a freelance contract are the ones both parties understand when they sign them. A confidentiality clause buried in legal boilerplate neither party reads carefully is less protection than a plain-language clause you both actually understood at signing.
When Clients Provide Their Own NDA
If the client sends their standard NDA before the project, you don’t have to sign it as-is. The same negotiating logic applies as any other contract term, read it, identify what you’d change, and ask for those changes. How to review an NDA a client sends you walks through each section worth scrutinizing before you sign.
The most common problem with client-provided NDAs: they’re one-sided (only you are bound), the duration is indefinite or unreasonably long, or they include a non-compete or non-solicitation clause. The non-solicitation is worth particular attention: some NDAs prevent you from working with any person or company you encountered through the client relationship, which can significantly restrict your network and future business.
Ask for mutual language, a defined duration, and removal of any non-compete or non-solicitation provisions that go beyond the specific project relationship. If they won’t budge on non-solicitation, narrow its scope: you won’t directly solicit the specific individuals you worked with, but you’re free to work with other companies in the same sector.
The signature is where your use is. Once you’ve signed, negotiating gets harder. Read carefully before you do.
