Risks › No confidentiality

No confidentiality.
The leak you can't get back.

You shared your pricing, your process, your client list. Nothing in the contract says it stays private. Once it's out, the clause you didn't write won't get it back.

Draft an agreement that prevents it

Free. No registration. No card. No catch.

What it means

In plain English.

Confidentiality clauses define what information must be kept private, by whom, and for how long. Without one, information shared in the course of a business engagement has no contractual protection. "Implied" confidentiality exists in limited circumstances — and is harder to enforce than a written clause.

What it looks like

You share your proprietary pricing model during a proposal. You share client names and project details during onboarding. The engagement ends. The other party uses that information with a competitor. Nothing in the contract prevented it.

The "implied" confidentiality myth

Some courts recognize implied duties of confidentiality in certain professional relationships. Most don't apply broadly to business service agreements. "They knew it was confidential" is not a contract clause.

It goes both ways

Mutual confidentiality protects both sides. The client's business information stays with the provider. The provider's methods and pricing stay with the provider. Both parties benefit from a written clause.

Why it's missed

It feels obvious. It needs to be written down anyway.

Why missed

The engagement feels low-stakes

A short project with a small payment doesn't seem to warrant a confidentiality clause. But business information doesn't become less valuable because the engagement was brief.

Why missed

Assumed professional discretion

Both parties assume the other understands what's confidential. Those assumptions diverge as soon as there's a dispute about what was actually private.

Why missed

NDA feels like a separate document

Many people think confidentiality requires a standalone NDA. In most service agreements, a confidentiality clause built into the contract is sufficient and often better — it's signed automatically at contract execution.

What can go wrong

The downstream consequences.

Pricing shared with competitors

Your rates, your cost structure, your margin — disclosed to a former client who is now negotiating with your competitor using your own numbers.

Client list disclosed

Your client roster is a business asset. Without a confidentiality clause, a former contractor can take it to a new employer or use it to solicit your clients directly.

Proprietary process exposed

Your methodology, your workflow, your software stack — information shared to enable the work can be shared forward without restriction.

No injunctive relief available

Without a confidentiality clause, courts are reluctant to issue injunctions stopping disclosure. You can sue for damages after the fact. You can't prevent the leak.

Red-flag wording

These situations leave confidential information exposed.

The most common version is simply no clause at all. But these are the phrases and gaps that create the same exposure.

Red flag

No confidentiality section

The contract simply doesn't address it. Everything shared in the engagement is legally unprotected as confidential.

Red flag

"Parties will keep information private"

Private by whose definition? For how long? With what exceptions? This phrase is a placeholder for a clause that was never written.

Red flag

No definition of "confidential information"

Even when a confidentiality clause exists, if it doesn't define what qualifies as confidential, disputes arise immediately about what's covered.

Red flag

No survival period

Confidentiality that expires when the contract ends means information shared during the engagement can be used freely the day after it terminates.

Safer pattern

The confidentiality clause that covers the gap.

A confidentiality clause needs four elements: a definition of what's confidential, the obligation to protect it, the exceptions to that obligation (publicly available information, prior knowledge, required disclosure), and a survival period after the contract ends.

BizDraft includes mutual confidentiality language by default in all service agreements, with a two-year post-termination survival period as the standard.

The pattern

Define confidential information. "Confidential Information means any non-public information disclosed by one party to the other in connection with this Agreement, including but not limited to: pricing, business methods, client lists, technical processes, and financial information."
Obligation to protect. "Each party shall hold the other's Confidential Information in strict confidence and shall not disclose it to any third party without prior written consent."
Standard exceptions. "The foregoing obligation does not apply to information that: (a) is or becomes publicly available through no breach of this Agreement; (b) was known to the receiving party before disclosure; (c) is required to be disclosed by law or court order."
Survival period. "The confidentiality obligations in this section survive termination of this Agreement for a period of [two years / three years]."

Most affected