NDA (Non-Disclosure Agreement): When Is It Needed and How to Draft It to Make It Work?

Are you preparing for a meeting with an investor and planning to show them your “secret” technology? Or are you hiring a freelancer for a project and sharing your business ideas with them? In such situations, there is a risk that your most valuable information could “accidentally” end up with competitors. To prevent this, there is a legal “shield” — a non-disclosure agreement, or NDA.

What is an NDA in simple terms? It is a legal agreement under which one party undertakes not to disclose confidential information received from the other party. Essentially, it is an official promise to “keep your mouth shut,” backed by the threat of penalties. And it is not just a formality. It is a powerful tool that allows you to freely discuss your ideas and plans, knowing they are protected by law.

Section 1. When you definitely need an NDA

A non-disclosure agreement is not a universal document that needs to be signed with everyone you meet. It is a targeted legal tool used when you are forced to disclose valuable, non-public, commercially significant information to another party. There are three classic business situations where the absence of a signed NDA is not just negligence, but a direct threat to the security of your idea, client base, or even your entire business.

1.1. Before negotiations with investors or partners

Imagine you are preparing for the most important meeting in your startup’s life — pitching to a venture capital fund or a strategic partner. To convince them of your project’s potential, you need to show your cards and reveal the “inner workings”: a detailed business plan, financial projections, unique features of your technology, marketing research results, and perhaps even a product prototype. All this information is your trade secret and your main competitive advantage.

What is the risk? Investors and potential partners see dozens of projects every day. Even if they act in good faith, there is a significant risk that the details of your brilliant idea could “accidentally” leak to another startup they are also considering for funding. Or worse: a potential business partner might be your friend today, but tomorrow, after seeing the full potential of your model, they might decide not to cooperate but to become your direct competitor, using the knowledge they gained from you to launch their own similar product, but with more resources.

How does an NDA protect you? Signing an NDA before starting any substantive negotiations (ideally, even before sending a presentation) is the gold standard in the business world.

• Creates a legal obligation: your interlocutor officially, under the threat of financial sanctions, undertakes not to use your information for their own purposes and not to disclose it to third parties.
• Demonstrates your professionalism: by proposing an NDA, you show that you take your intangible assets seriously, understand the rules of big business, and value your intellectual property. This commands respect.
• Gives you the right to compensation: if a leak does occur, and you can prove it, you will have a document that gives you the right to demand compensation for all damages incurred through the court. Without an NDA, proving anything will be practically impossible.

1.2. When hiring employees and working with freelancers

Your employees and contractors are the people who have the deepest and most complete access to the “holy of holies” of your business. Programmers see the source code, marketers see the client base and advertising analytics, designers see new products before their official announcement, and financiers see your entire commercial strategy. Protecting this information from intentional or unintentional leaks is not just a matter of security; it is a matter of business survival.

• For full-time employees: an employee non-disclosure agreement is an absolute necessity. Most often, it is not a separate document but an integral part of the employment contract or a mandatory annex to it. It should be signed on the first day of work, before the employee gains access to corporate systems. It is important that the agreement clearly states that the non-disclosure obligations continue to apply for a certain period after the employee’s termination (usually 3-5 years). This protects you from a former sales manager, upset about being fired, “taking” your client base to a direct competitor.
• For freelancers and contractors: since freelancers are not part of your core team and often work with several clients simultaneously (sometimes even your direct competitors), signing an NDA with them before starting any work is critical. This ensures that the details of your technical task, your business processes, access to your internal systems, and any other sensitive information will not be used in other projects or disclosed to third parties.

1.3. Before discussing an unpatented idea

You have a brilliant idea for a new device, a unique technology, or a software algorithm, but you are not yet ready to file a patent application. Perhaps you need to refine technical details, find a partner to manufacture a prototype, or simply consult with an expert to assess the prospects.

What is the risk? Public disclosure of the essence of your invention before the patent application date can “kill” its world novelty — the key and strictest criterion for obtaining a patent. If you simply talk about your idea at a conference, publish it on a blog, or even discuss it in detail with an expert without an NDA, and then file an application six months later, the patent office may refuse you on the grounds that the invention has already become part of the prior art. You will destroy your own innovation with your own hands.

How does an NDA protect you? A non-disclosure agreement creates a legal “cocoon” of confidentiality around your discussion. Information shared under a signed NDA is not considered public disclosure because the receiving party undertakes to keep it secret. This allows you to safely discuss technical details with engineers, manufacturers, and consultants without risking the loss of the ability to patent the development in the future. An NDA does not replace a patent, but it is a vital tool for protecting unpatented developments in their early, most vulnerable stages. We discussed more about how to discuss an idea safely in the article: “How to patent an idea (and is it even possible)?“.

Section 2. Key points that make an NDA effective

Simply naming a document “Non-Disclosure Agreement” and signing it is not enough. Its true power and legal weight lie in the details. A properly drafted NDA is a balanced legal tool that clearly, without any vague wording, defines the “rules of the game” for your confidential information. If these rules are written unclearly or poorly, in the event of a real conflict in court, such an agreement may prove completely powerless. Let’s look at the four pillars on which any reliable and working NDA rests.

2.1. Definition of confidential information

This is the heart of your agreement. In this section, you must describe as clearly and exhaustively as possible what exactly is considered confidential information and, therefore, subject to protection. The more specific and detailed this list is, the fewer opportunities the other party will have for maneuvering and excuses like “I didn’t know that this specific thing was a secret.”

How to properly formulate this point:

• Avoid overly general phrases: wording like “all information received during the course of cooperation” is too broad and can be easily challenged in court as unfairly restricting the other party. You need specificity.
• Use a combined approach: the best practice is to combine a list of specific categories of information with a general definition. For example:
  “Confidential information under this Agreement is any technical, commercial, financial, and other information transmitted by the Disclosing Party to the Receiving Party in written, oral, or electronic form, and which has actual or potential commercial value. In particular, but not limited to, confidential information includes:
  • business plan and marketing strategy of project ‘XYZ’;
  • financial models, projections, and investment data;
  • source code, object code, and technical documentation of software;
  • client databases and supplier information;
  • know-how, technological processes, and formulas;
  • any information contained in documents marked ‘Confidential’ or ‘Trade Secret'”.
• Define exceptions: for legal correctness and balance of interests, it is also worth clearly indicating what information is not considered confidential. Usually, this is information that:
  • Was already publicly known at the time of its transfer.
  • Became publicly known after the transfer, but not through the fault of the receiving party.
  • Was lawfully obtained from third parties who had no non-disclosure obligations.
  • Was independently developed by the Receiving Party without using the Disclosing Party’s confidential information.

A clear definition of “what exactly we are protecting” is your main defense against any future misunderstandings and disputes.

2.2. Obligations of the parties

This section details exactly what the party receiving your secret information (hereinafter the “Receiving Party”) must (and must not) do. It is, in essence, an instruction manual for handling your data.

Key obligations that should be clearly spelled out:

• Keep secret: this is the main obligation. The Receiving Party undertakes not to disclose confidential information to any third parties (except for its employees or contractors who objectively need this information to work on the project, and who, in turn, are also bound by confidentiality obligations).
• Use only for a specified purpose: this is a critical point. The Receiving Party may use your information exclusively for the purpose for which it was transmitted. This purpose must be clearly defined in the agreement (e.g., “for the purpose of conducting a technical assessment of the feasibility of investing in project ‘XYZ'”). Any other use (e.g., for developing your own similar product or for improving your internal processes) must be expressly prohibited.
• Take appropriate protection measures: the Receiving Party is obligated to take reasonable and adequate measures to protect your information from unauthorized access, copying, or distribution. The level of protection must be no lower than that which it applies to protect its own confidential information.
• Return or destroy information: the agreement should clearly provide that upon termination of cooperation, expiration of the agreement, or upon your first written request, the Receiving Party is obligated to immediately return to you all physical media containing confidential information (documents, flash drives, prototypes) and completely destroy all electronic copies from its systems, providing you with written confirmation of such destruction.

2.3. Term of the agreement

Any legal obligation must have clear time limits. The term of an NDA determines how long the Receiving Party is obligated to keep your secret. An incorrectly defined term can devalue the entire agreement.

There are two important aspects here that are often confused:

1. Term of the agreement itself: this is the period during which the parties plan to exchange confidential information. For example, “this Agreement enters into force from the moment of signing and is valid for 1 (one) year.”
2. Term of confidentiality obligations: this is the most important term. It determines how long the party is obligated to keep the secret after the expiration of the agreement itself or after receiving the last portion of information. Your idea, technology, or client base does not cease to be valuable immediately after negotiations end. Therefore, this term must be long enough to reliably protect your commercial interests. For most business information, a term of 3 to 5 years is considered adequate. For particularly valuable technological secrets and know-how, it can be longer, or even indefinite, as long as the information retains its commercial value.

2.4. Liability for disclosure

This is the point that turns your NDA from a gentleman’s agreement and a declaration of intent into a real financial instrument. Without clearly defined, tangible, and realistic penalties for breach, your agreement is “toothless” and does not have the proper deterrent effect.

What should be in this section for maximum effectiveness:

• Right to compensation for damages: state directly that in case of breach of the agreement, the Disclosing Party (i.e., you) has the right to demand full compensation for all damages incurred from the violator. This includes both actual damages (direct losses) and lost profits (income you could have received if the leak had not occurred).
• Penalty sanctions: since proving the exact amount of damages from an information leak can be extremely difficult and time-consuming, a very effective tool is to establish a contractual penalty. This is a fixed amount or percentage that the violator is obligated to pay for the very fact of disclosure, regardless of whether you managed to prove the amount of damages. Example of effective wording:
  “In case of breach by the Receiving Party of any of the non-disclosure obligations provided for in this Agreement, it undertakes to pay the Disclosing Party a penalty in the amount of 200,000 (two hundred thousand) hryvnias for each established case of such breach, and also to fully compensate for damages exceeding the amount of the penalty.”

The presence of a specific, significant penalty amount is the best psychological and financial deterrent for a potential violator.

Section 3. Common mistakes when drafting an NDA

Even while understanding the importance of a non-disclosure agreement, many entrepreneurs and companies make typical mistakes when drafting and signing it. These mistakes may seem insignificant, but at a critical moment, when a leak has already occurred, they can completely devalue your agreement and deprive you of any chance for compensation. Let’s look at the three most common “rakes” that businesses step on.

3.1. Using unadapted templates

This is mistake number one. In an attempt to save time and money, many search the internet for “nda template Ukraine“, download the first one they find, enter the names of the parties, and consider the job done. This is an extremely dangerous approach.

Why doesn’t it work?

• Non-compliance with legislation: a template downloaded from a foreign (especially Russian or American) site may not comply with Ukrainian law at all. References to non-existent laws, incorrect terms, invalid conditions — all this makes your agreement legally void in Ukraine.
• Lack of specificity: as we have already found out, the strength of an NDA is in the details. Templates always contain the most general, “universal” wording, especially in the key point about defining confidential information. Such an agreement does not take into account the specifics of your project, your industry, and the specific information you are going to protect.
• One-sidedness: many templates are “one-sided,” meaning they protect the interests of only one party (usually the one that drafted it). If you sign an NDA proposed by a potential investor without reading it, you may unknowingly take on unfavorable obligations.

Consider a template only as a draft, as a starting point for understanding the structure. Your final agreement must be either carefully adapted to your situation or, which is much better, developed from scratch by a lawyer who understands the specifics of your business. The company BrandR specializes in developing individual agreements that take into account all the client’s unique risks.

3.2. Too broad a definition of “confidentiality”

It would seem, what could be wrong with protecting as much information as possible? Some companies try to include a clause in the NDA that declares absolutely all information exchanged as confidential. For example: “Any information transmitted during the course of cooperation is confidential”.

Why is this dangerous?

• Risk of invalidation: a court may declare such a clause invalid as being excessive, unclear, and unfairly restricting the other party. If you cannot clearly define what exactly is your secret, then how can the other party protect it?
• Practical impossibility of execution: such a clause creates an absurd situation where even discussing well-known facts or public information formally becomes a breach of the agreement. This makes the agreement impractical and sets the parties up to ignore it from the very beginning.
• Counterproductive in negotiations: by proposing such a “draconian” clause to a potential partner, you may simply scare them off. It looks like an attempt to abuse your position and causes distrust.

As we discussed in the previous section, clearly list the categories of information that are critically important to you, and do not try to include well-known things there.

3.3. Lack of clear sanctions for breach

This is another fatal mistake. The agreement may perfectly describe what is confidential and what the obligations of the parties are, but if the “Liability” section contains vague wording like “the parties bear responsibility in accordance with current legislation”, your agreement loses 90% of its deterrent power.

Why is this bad?

• Difficulty in proving damages: “Current legislation” does indeed allow you to demand compensation for damages. But in practice, proving the exact amount of financial loss from an information leak in court is incredibly difficult. How much money exactly did you lose because a competitor found out about your marketing strategy for the next quarter? This will require complex economic expertise and does not guarantee a result.
• Lack of a deterrent factor: if a potential violator knows that proving damages will be almost impossible, they are tempted to take the risk.

As we have already noted, be sure to include a clause in the agreement about a specific, fixed penalty for the very fact of breach. The presence of a clear amount (e.g., 100,000 or 500,000 hryvnias) that will have to be paid automatically is the best argument for the other party to take their obligations as seriously as possible.

Conclusions

So, a non-disclosure agreement is not just a piece of paper for peace of mind. It is your legal shield that allows you to safely share ideas, conduct negotiations, and cooperate with others without fear that your most valuable assets — information and know-how — will be stolen.

• An NDA is your legal shield for protecting ideas. A confidentiality agreement is a mandatory tool at any stage of business where you are forced to disclose internal information: from negotiations with investors to hiring your first employee. It turns ethical obligations into financially tangible ones.
• Consult a lawyer to develop a reliable agreement. As we have seen, the effectiveness of an NDA depends on the details. To avoid common mistakes and create a document that will truly work and protect you in court, the best solution is to seek professional help. Legal consultation on NDAs and ordering NDA development from specialists, like the BrandR team, guarantees that your agreement will take into account all the nuances of your business and comply with current legal requirements.