Before sharing a proposal, design, customer information or financial data with a potential partner, put clear rules around what may be disclosed and how the recipient may use it. A confidentiality agreement (NDA) can help document those rules. It does not replace choosing the right counterparty or controlling access to files.
Describe the information with enough precision
Identify the categories that matter to the project, such as technical designs, specifications, pricing, financial information, customer or supplier details, business plans, and files or samples. A clause that labels everything confidential may appear broad, but it can make day-to-day compliance and later proof more difficult. For information disclosed orally, state whether and how it must be confirmed in writing, and within what period.
Limit use and access
State why the information is being shared: for example, to evaluate a proposed transaction or to perform a defined project. The agreement should say who may access it, whether professional advisers or contractors may receive it, and what safeguards and confidentiality duties apply to them. Keep access limited to people who need the information for that purpose.
Consider practical exceptions for information that is public through no breach, already lawfully known to the recipient, independently developed, or received lawfully from another source. Include a process for legally compelled disclosure, such as giving notice where permitted and disclosing only what is required.
Set the period and the return or deletion process
Specify how long confidentiality and restricted-use duties apply, taking account of the information and project. Explain what happens when discussions end or a party asks: return documents, securely delete copies, and address routine backups or records that must be retained. Keep a record of the files shared, their versions, dates, recipients and purpose. Share information in stages, beginning with aggregated or less sensitive material where possible.
Keep confidentiality separate from ownership
An NDA does not, by itself, transfer or grant ownership or a licence in designs, software, inventions, trademarks or other intellectual property. Address ownership, permitted development and any licence in separate, clear terms. Non-compete or non-solicitation restrictions also need their own scope, duration and enforceability review; they should not be inserted automatically into a generic confidentiality form.
Build a usable disclosure process
For an investment discussion, a company might initially share summary figures without customer names, then provide more detail after the parties have agreed on the evaluation purpose and access controls. Reassess permissions if the participants, project scope or negotiation stage changes. A disclosure log can help identify who received which material if a concern arises.
Remedies, including any agreed compensation or penalty, should be drafted and reviewed for the relevant parties, transaction and applicable law. A stated amount does not eliminate the need to establish what happened or resolve a dispute under the agreed process.
Frequently asked questions
Does signing an NDA prevent a leak? No document can physically prevent disclosure. Clear duties work best alongside restricted access, secure sharing and a record of disclosures.
Can I use a template? A template can be a starting point, but adapt it to the parties, purpose, information, languages, access arrangements and project. Check that any translated versions express the same obligations.
What should I do before sending files? Confirm the recipient and purpose, classify the material, remove unnecessary sensitive details, agree on access and permitted use, and record what was sent.
This article provides general information, not legal advice. The appropriate terms depend on the transaction and applicable law. Consider obtaining advice before signing or disclosing sensitive information.