Confidentiality clauses protect legitimate business secrets — but they're routinely used to silence freelancers, hide bad behavior, and prevent you from even mentioning you worked with a client. Here's how to tell the difference between reasonable and overreaching.
Paste or upload it and get a full risk analysis in 30 seconds — including whether your NDA terms are reasonable or overreaching.
Check your contract free →No credit card required. Your files are never stored.
A confidentiality clause (also called a non-disclosure agreement or NDA provision) restricts you from sharing information you learn during a project. It defines what counts as "confidential information," how long you must keep it secret, and what happens if you breach it.
Confidentiality clauses are standard in freelance contracts, employment agreements, consulting engagements, and partnership deals. They exist to protect trade secrets, client lists, and proprietary processes — but many are drafted so broadly that they cover everything, forever, with no exceptions.
No expiration (perpetual confidentiality)
If the clause says confidentiality lasts "in perpetuity" or "indefinitely," that means you can never discuss what you learned — even decades later. Most courts and industry standards consider 2–3 years reasonable for non-trade-secret information. Perpetual obligations should be reserved only for actual trade secrets, if at all.
Covers publicly available information
A well-drafted NDA excludes information that becomes publicly known through no fault of yours. If the clause lacks this carve-out, you could technically breach it by discussing something the company posted on their own website.
Prevents you from saying you worked with the client
Some confidentiality clauses prohibit you from disclosing "the existence of this agreement" or naming the client in your portfolio. This is a portfolio restriction that can severely hurt freelancers who rely on past work to win new clients.
One-sided obligations (only you are bound)
If the confidentiality clause only applies to you and not the client, that's a red flag. You may share sensitive information too — your pricing, processes, or proprietary methods. Confidentiality should be mutual unless there's a clear reason it isn't.
No carve-out for legally required disclosures
You should always be able to disclose confidential information when required by law, court order, or regulatory investigation. If the clause has no exception for legal obligations, you could be put in an impossible position — breach the NDA or break the law.
Actual clause from a real contract
"Contractor agrees to hold in strict confidence, in perpetuity, all information relating to Company's business, operations, clients, finances, and any other matters disclosed during the term of this Agreement, including the existence of this Agreement itself. Contractor shall not use or disclose such information for any purpose whatsoever without Company's prior written consent."
This clause is problematic because it combines four overreaching elements: perpetual duration (no end date), covers "any other matters" (absurdly broad scope), prohibits mentioning the client relationship (portfolio restriction), and is entirely one-sided. ClauseGuard would flag all four.
Suggested counter-language
"I'd like to limit the confidentiality period to 2 years after the end of the engagement, with exceptions for information that becomes publicly available, was already known to me, or is required to be disclosed by law. I'd also like to retain the right to list the client name and a general project description in my portfolio, and request that confidentiality obligations be mutual."
Key negotiation points:
Not all confidentiality clauses are bad. A well-drafted NDA protects genuinely sensitive information — customer lists, unreleased product plans, proprietary algorithms, financial data — for a reasonable period, with standard exceptions.
The problem is when companies use boilerplate NDAs that sweep in everything, last forever, and give you no rights. A confidentiality clause should protect secrets, not silence people.
If you're asked to sign a standalone NDA before even seeing a contract or proposal, that's common and usually fine — but still read it carefully. The same red flags apply whether the clause is in a standalone NDA or embedded in a larger agreement.
Upload your contract and ClauseGuard will identify every confidentiality issue, score the overall risk, and give you copy-pasteable negotiation language.
Analyze your contract →Free to start. Analysis takes 30 seconds.