Non-Disclosure Agreement Prospective Licensee Template

In plain language: Identifies the disclosing party (licensor or IP owner) and the receiving party (prospective licensee) by full legal name, and states that the purpose of disclosure is to evaluate a potential licensing arrangement.

Common mistake: Using a trade name instead of the registered legal entity name for either party — if enforcement becomes necessary, a mismatch between the agreement and corporate registry records can complicate standing to sue.

In plain language: Sets out precisely what information is protected — typically all non-public technical, business, and financial information related to the IP, whether disclosed orally, in writing, or by inspection, and how it must be marked or designated.

Common mistake: Limiting the definition to written, marked materials only. Oral disclosures and demonstrations — often the most sensitive exchanges in licensing negotiations — are left unprotected unless the definition expressly includes them.

In plain language: Restricts the receiving party's use of confidential information strictly to evaluating whether to enter into a licensing agreement with the disclosing party, and prohibits any other use.

Common mistake: Drafting the permitted purpose too broadly — e.g., 'evaluating a business relationship' — which allows the receiving party to argue the information was used for a permissible purpose even if no license was ever pursued.

In plain language: States the receiving party's duties: maintain the confidentiality of disclosed information using at least the same care as for its own confidential information (and no less than reasonable care), limit access to employees with a need to know, and bind those employees to equivalent obligations.

Common mistake: Omitting the requirement to bind employees and advisors with access to written obligations — if a receiving party's employee independently discloses the information, the licensor has no direct recourse against that individual.

In plain language: Lists the standard circumstances under which the receiving party's obligations do not apply — information already in the public domain, already known before disclosure, independently developed, or received lawfully from a third party.

Common mistake: Agreeing to a broad residuals carve-out that exempts anything retained in employees' unaided memory. This clause can render trade-secret protection meaningless for software, formulas, and technical know-how.

In plain language: Expressly states that signing the NDA does not transfer any rights, title, or license in the confidential information or underlying IP to the receiving party — the disclosing party retains full ownership.

Common mistake: Omitting this clause entirely and relying on the permitted-purpose restriction alone. Without an express no-license statement, a court applying implied-license doctrine could find that access to information implies a narrow right to use it.

In plain language: Sets the duration of the agreement — typically one to three years from the date of signing — and specifies that obligations relating to trade secrets survive expiration indefinitely, while other confidentiality obligations survive for a defined period.

Common mistake: Setting a uniform two-year survival period for all confidential information, including trade secrets. Statutory trade-secret protection can last decades — capping it contractually gives away protection the law would otherwise provide.

In plain language: Requires the receiving party to promptly return or certify the destruction of all confidential materials — documents, copies, digital files, and derivative works — upon request or when the Purpose concludes.

Common mistake: Failing to include digital files and derivatives (notes, analyses, and models based on disclosed information) in the return/destruction obligation — physical documents are returned but the receiving party retains detailed spreadsheets built on the licensor's proprietary data.

In plain language: Addresses what happens if a court or regulator orders the receiving party to disclose the confidential information — requires prompt notice to the disclosing party so it can seek a protective order before disclosure occurs.

Common mistake: No compelled-disclosure clause at all, leaving the receiving party free to comply with a subpoena or regulatory request without warning the disclosing party — who loses the opportunity to obtain a protective order.

In plain language: States that breach will cause irreparable harm entitling the disclosing party to seek injunctive relief without proving monetary damages, and specifies the governing law and venue for disputes.

Common mistake: Choosing a governing law that has no connection to where either party operates. Courts in California, for example, may not enforce a choice-of-law clause that attempts to apply a different state's trade-secret law to avoid California's stricter non-compete and IP protections.

A non disclosure agreement for a prospective licensee is a legally binding contract that protects confidential information — trade secrets, proprietary technology, formulas, or product designs — shared by an IP owner with a party evaluating a potential license. It restricts the prospective licensee to using the disclosed information only for the purpose of assessing the licensing opportunity, and prohibits further disclosure or independent use. It does not itself grant any license to the underlying IP.

A standard mutual NDA creates reciprocal confidentiality obligations — both parties disclose and both parties protect. A prospective licensee NDA is typically one-directional: the licensor discloses IP and proprietary details; the prospective licensee receives and protects them. Because the information flow is asymmetric, the obligations and remedies are weighted toward the licensor's protection. Use a mutual NDA only if the prospective licensee will also share its own confidential technology or business data during the evaluation.

The NDA must be executed before any confidential information is shared — before sending a data room link, before a technical demonstration, and before sharing product specifications or financial projections. Retroactive NDAs are difficult to enforce and may leave pre-signature disclosures unprotected. Treat the countersigned NDA as the unlock event for any substantive discussion.

No. A well-drafted prospective licensee NDA expressly states that no license, express or implied, is granted by the agreement. The receiving party may review the confidential information solely to evaluate whether to enter into a license. Actual rights to use the IP are granted only by a separate, fully negotiated license agreement executed after the evaluation concludes.

Most prospective licensee NDAs run one to three years — long enough to cover the evaluation and negotiation period. However, obligations relating to trade secrets should survive the agreement's expiration indefinitely, because trade- secret protection under statutes like the US Defend Trade Secrets Act does not expire as long as secrecy is maintained. Cap general confidentiality at three to five years post-expiration; leave trade-secret obligations open-ended.

Yes, and the NDA should specifically require it. The return-or-destruction clause should cover all tangible and digital materials, including copies, notes, analyses, and models derived from the disclosed information. Request a written certification of destruction rather than relying on verbal confirmation. Retaining the certification creates an enforceable record if the prospective licensee later uses the information.

The primary remedy for NDA breach involving IP disclosure is injunctive relief — a court order preventing further use or disclosure — because monetary damages are often impossible to quantify once confidential information is out. The NDA should include a clause acknowledging that breach causes irreparable harm and that the disclosing party is entitled to seek emergency injunctive relief without posting bond. Monetary damages, attorney's fees, and disgorgement of profits may also be available depending on jurisdiction and the specific breach.

Cross-border NDA enforcement is possible but jurisdiction-dependent. Courts in most common-law countries (US, UK, Canada, Australia) will enforce foreign NDAs if the governing-law clause has a reasonable connection to the parties and the dispute. EU courts apply local data-protection and trade-secret laws regardless of contractual choice of law in some cases. For high-value cross-border licensing negotiations, include an international arbitration clause (ICC or WIPO) rather than relying solely on domestic courts.

Notarization is not required for a prospective licensee NDA to be legally binding in the US, Canada, the UK, or the EU. Signature by an authorized representative of each entity is sufficient. Electronic signatures are enforceable under the ESIGN Act (US), PIPEDA (Canada), eIDAS (EU), and the Electronic Communications Act (UK) for NDAs of this type.