Non-Disclosure Agreement (NDA) for British Columbia

What makes an NDA enforceable under BC law

An NDA in British Columbia is, at its foundation, a contract, and BC courts will only enforce it if the basic requirements of contract formation are satisfied. There must be an offer, an unambiguous acceptance, mutual intention to create legal relations, certainty of terms, a lawful purpose, and — critically — consideration flowing to the party giving up the right to disclose. An NDA signed at the start of a business relationship almost always has sufficient consideration: the job, the payment, the pitch meeting, the investor diligence. An NDA imposed mid-relationship without fresh consideration is the single most common reason BC NDAs are unenforceable, and it is also the easiest defect to avoid.

Beyond formation, BC courts look for reasonableness in scope, duration, and geographic reach. “All information of any kind ever disclosed by the Discloser” is the kind of definition that gets a BC chambers judge reaching for the pen. A defensible NDA describes the categories of protected information — technical data, financial information, customer lists, source code, unreleased product roadmaps — and carves out a predictable set of exceptions: information already known to the recipient, information independently developed, information in the public domain through no fault of the recipient, and information required to be disclosed by law or court order.

The template on this page is drafted against these requirements. It gives the discloser a defined category of “Confidential Information” that is narrow enough to survive scrutiny and broad enough to capture what actually matters in a commercial or founder context. It pairs that definition with permitted-use, return-or-destroy, and survival clauses that match how BC courts read post-termination confidentiality obligations.

The BC statutory and common-law backdrop

Most of what matters for an NDA in BC comes from the common law of contract — formation, consideration, certainty, restraint of trade — and from equitable principles governing injunctive relief. But two pieces of statutory context are worth flagging. First, the Business Practices and Consumer Protection Act (BPCPA, SBC 2004, c 2) governs consumer transactions in British Columbia and includes unconscionability provisions that can be invoked where an NDA is imposed on a consumer counterparty in a commercial transaction. NDAs between two businesses or between a business and a prospective employee sit outside BPCPA, but NDAs signed by individual consumers — for example, as a condition of receiving a paid service — may attract BPCPA scrutiny. If you are a BC operator asking individual customers to sign confidentiality terms, this template is probably the wrong shape for that relationship.

Second, BC common law applies the restraint-of-trade doctrine more aggressively to employment and post-employment obligations than to arms-length commercial NDAs. A confidentiality clause that functions as a de facto non-compete — because it sweeps in so much information that the employee cannot practically work in the industry — will be tested as a restraint of trade and often read down or severed. The template keeps confidentiality and non-compete as distinct, separately-tested clauses.

Unilateral versus mutual NDAs — which one founders actually need

A unilateral (one-way) NDA binds one party — the Recipient — to hold the Discloser's information in confidence. It is the right shape when only one party is sharing sensitive information. Typical founder cases: hiring a contractor, onboarding an early employee who will see the codebase, giving a prospective enterprise customer access to an unreleased product. The discloser receives all the protection; the recipient bears all the restriction.

A mutual NDA binds both parties. Each is simultaneously a Discloser and a Recipient. Mutual NDAs are the right shape for partnership discussions, M&A diligence, joint ventures, integration conversations between two SaaS companies, and any situation where both sides expect to reveal information the other will want to protect.

The most common mistake BC founders make is using a mutual NDA when the information flow is one-way, or a unilateral NDA when they will also end up sharing. A mutual NDA imposed on a candidate who has nothing to share can weaken the discloser's position later if a dispute arises, because the document reads as if both parties had equivalent protectable interests. Conversely, a unilateral NDA signed by a founder who then shares their roadmap during due diligence leaves the founder unprotected. This template presents both options and the wizard selects the right structure based on how the parties will actually exchange information.

Common reasons BC NDAs fail in court

Most unenforceable NDAs in BC fail for one of five reasons, and all of them are preventable at drafting time.

Overbroad scope. A confidentiality definition that tries to capture “all information” or that lacks exclusions for independently-developed, already-known, or publicly-available information will be challenged as unreasonable. BC courts often read such clauses down to something defensible, but in a close case the whole clause can be severed and the discloser left with no contractual protection at all.

Unreasonable term. A perpetual confidentiality obligation covering non-trade-secret information is routinely struck out in BC. Commercially sensitive but non-secret information typically warrants a two-to-five year obligation; only true trade secrets can be protected indefinitely, and only because the obligation ends the moment the information becomes public through no fault of the recipient.

No consideration for mid-relationship NDAs. Introducing an NDA to an existing BC employee or existing vendor without fresh consideration — a bonus, a raise, a renewed commercial commitment — is one of the most reliable ways to produce an unenforceable document. The original employment or services agreement is not, on its own, consideration for a new obligation added later.

Confidentiality clauses dressed as non-competes. When a confidentiality obligation is so broad it practically prevents the recipient from working in the industry, BC courts treat it as a restraint of trade and test it against the higher bar that applies to non-competes — a bar that is hard to clear in the employment context. The template keeps confidentiality, non-solicitation, and non-compete as clearly distinct, separately-tested clauses.

Missing governing-law and forum-selection clauses. An NDA with no governing-law clause — or one that points at a foreign jurisdiction when both parties are in BC — creates procedural friction and conflict-of-laws argument that can derail an injunction application at the worst possible moment. The template specifies British Columbia governing law and BC courts as the forum.

When an NDA is not the right tool

NDAs are not a universal solvent. Three situations call for a different document or a different strategy.

You are trying to stop a departing employee from joining a competitor. That is a non-compete. Dressing it up as a confidentiality clause will be transparent to a BC chambers judge and will weaken both clauses. Draft the non-compete separately, keep it narrow in time and geographic scope, and pair it with a distinct confidentiality clause.

You are trying to protect an invention, process, or brand. An NDA protects information during a conversation. Patents, copyrights, trademarks, and industrial designs protect the underlying asset. If you are about to pitch an invention to a prospective licensee, the conversation is protected by an NDA, but the invention itself should be protected by a filed patent application first — because once you have disclosed it, your filing window may be narrowing.

You are trying to silence a whistleblower or suppress a good-faith complaint. A confidentiality clause used to muzzle a whistleblower is likely unenforceable and may expose the discloser to separate liability. NDAs do not override statutory reporting rights, BC human-rights complaints, or public-interest disclosures.

What happens if the other party breaches

If a BC counterparty breaches a properly-drafted NDA, the discloser has three categories of remedy, and the document should make all three available on its face.

Damages. Compensation for provable loss — lost sales, lost contracts, reduced enterprise value, cost of remediation. Damages are the default remedy but require the discloser to quantify the loss, which can be hard for intangible harms like loss of competitive position.

Injunctive relief. A BC court can order the recipient to stop using or disclosing the information, destroy copies, and refrain from involving third parties. Injunctions are equitable and discretionary, but they are available on an interlocutory basis — meaning within days, not months. The template expressly acknowledges that damages alone may be inadequate and that the discloser may seek injunctive relief; this language materially helps on an urgent application.

Disgorgement and accounting. Where the recipient has profited from the breach, BC courts can order the recipient to disgorge those profits. This is particularly relevant where the information was used to win a competitive tender, launch a product, or close a financing. The discloser need not prove an equivalent loss to its own business — the measure is the benefit the breaching party received, not the loss the innocent party suffered, which is a meaningful distinction when the confidential information was used to enter a market the discloser had not yet reached.

Contractual liquidated-damages clauses can supplement these common-law remedies, but BC courts will only enforce a liquidated-damages figure that is a genuine pre-estimate of loss; a number that functions as a penalty will be struck out. The template does not set a liquidated figure by default, because the right number varies enormously with the sensitivity of the information — leave that to a conversation with counsel for high-value engagements.

Moving fast matters. BC courts expect a party seeking an injunction to act promptly once the breach is known — sitting on a claim for months can itself be a reason to refuse equitable relief. If you suspect a breach, preserve evidence, document the timeline, and seek advice quickly.