Non Disclosure Agreements for UK Pitch Decks

Sharing a pitch deck can feel risky when your product roadmap, customer traction, pricing model and fundraising plans are all on the page. Many founders respond by sending a non disclosure agreement to everyone, while others avoid NDAs entirely and rely on trust. Both approaches can backfire.

The common mistakes are asking professional investors to sign a one-sided NDA too early, giving contractors access to trade secrets without any written confidentiality terms, or assuming a business idea is protected just because it feels original. The right approach depends on who is receiving the deck, what information is inside it, and what you want them to do next.

A well-used confidentiality agreement can protect sensitive commercial information without slowing down a funding round, partnership discussion or product build. The key is to separate what belongs in a teaser deck from what should only be shared after written confidentiality commitments are in place.

When an NDA Helps and When It Hurts

A non disclosure agreement is most useful when you are sharing specific confidential information, not merely describing a broad business opportunity.

In the UK, an NDA is a contract that restricts how the recipient can use and disclose information. It can sit alongside other protections, such as copyright in the deck itself, trade mark protection for your brand through the UK IPO, confidentiality duties in employment contracts, and data protection duties under the UK GDPR and the Data Protection Act 2018.

An NDA is not a magic shield for every business idea. A general concept, such as a marketplace for local services or an AI tool for a sector, is hard to protect on its own. What may deserve protection is the confidential detail behind it, such as your algorithmic approach, supplier pricing, customer acquisition data, unreleased product designs, technical architecture, pilot results, financial model, commercial strategy or investor list.

An NDA can help where:

• You are giving a contractor access to product specifications, source code, customer data or internal processes.
• A potential strategic partner needs to review your margins, customer pipeline, technical integration plan or supplier terms.
• An acquirer or competitor is conducting due diligence before making an offer.
• You are sharing a detailed financial model, proprietary research or confidential customer insights.
• You are giving access to a data room, demo environment or internal documents rather than a high-level pitch deck.

An NDA can hurt where:

• You ask a venture capital investor to sign it before they have even seen your teaser deck.
• The NDA is too broad and appears to restrict the recipient from working with any business in your sector.
• The document looks copied from another jurisdiction and does not fit English law or UK business practice.
• You rely on the NDA instead of controlling what you disclose.
• You send different versions to different recipients and lose track of who is bound by what.

Professional investors often see hundreds of pitches in overlapping sectors. Many will refuse to sign an NDA at the first meeting because it may create conflicts with other startups they have already met or may meet later. That does not mean your information is unprotected in every sense, but it does mean you need a staged disclosure strategy.

For example, a founder might first send a deck that explains the market, team, traction, problem and funding ask without revealing the source code, full customer list, detailed unit economics or commercial contracts. If an investor then progresses to deeper diligence, the founder can share more sensitive materials under controlled access, and in some cases under confidentiality terms in a founders term sheet, side letter or data room rules.

A Founder Checklist Before Sharing a Pitch Deck

Your safest approach is to decide what information is genuinely confidential before deciding whether to ask for an NDA.

Start by marking up your deck from the point of view of a competitor, investor, supplier and contractor. If a page would give one of them a practical commercial advantage, it may need to be withheld, simplified or shared only after confidentiality terms are agreed.

Use this checklist before sending the deck:

1. Identify the recipient. A VC, angel investor, corporate partner, agency, freelance developer and potential buyer each present different risks.
2. Define the purpose. Are they considering an investment, quoting for work, exploring a partnership, assessing an acquisition or simply giving feedback?
3. Separate public and confidential information. Public market size, team bios and product screenshots are different from non-public revenue, code, pricing, data sets and customer names.
4. Create disclosure levels. Use a teaser deck for first contact, a fuller pitch deck for serious discussions, and a data room for deeper diligence.
5. Check ownership of the deck content. Make sure you have the right to use images, diagrams, contractor-created content, customer logos and testimonials.
6. Remove unnecessary personal data. If you include customer information, employee details or case studies, consider UK GDPR principles, data sharing terms and lawful use.
7. Record who receives what. Keep a simple log of recipients, dates, versions and any confidentiality terms signed.
8. Use document controls where sensible. Watermarks, view-only sharing, expiry dates and access logs can support contractual protections.

A startup confidentiality agreement works best when it matches the deal stage. A first conversation may only need a lighter mutual NDA, or no NDA if the deck is carefully sanitised. A technical build, strategic partnership or acquisition discussion may justify stronger terms because the recipient needs to see information that could damage the business if misused.

Think about what you would need to prove if there were a dispute. It is much easier to show misuse of confidential information if you can identify the specific documents shared, the date of disclosure, the people who accessed them, and the purpose for which they were shared. A vague claim that someone copied your idea is harder to enforce than a clear claim that they used your unreleased supplier pricing or technical process in breach of a signed agreement.

Also consider whether you are sharing information that belongs partly to someone else. If a co-founder, university, employer, agency or contractor has contributed to the underlying IP, you may need to resolve ownership before pitching. The Companies Act 2006 is also relevant where a company is raising funds, issuing shares or giving investors information that supports company decisions. Your company records, cap table and shareholder approvals should be consistent with what the pitch deck says.

Investors, Partners, Contractors and Acquirers

The answer to whether you should ask for an NDA changes depending on the person across the table.

A single NDA policy for every conversation can make fundraising harder and leave real risks uncovered elsewhere. Founders often treat all external recipients as the same, but each category has different incentives, bargaining power and access needs.

Investors

Most institutional investors will not sign an NDA before reviewing an initial pitch deck. That is normal in UK fundraising and does not automatically mean they are acting unfairly.

Investors see many companies in similar markets. If they signed confidentiality terms for every early pitch, they could be accused of breaching one founder's NDA simply by funding another company in the same broad category. Many angel investors take a similar approach, particularly where the first deck is high level.

The practical answer is to prepare an investor-friendly deck that is persuasive without revealing crown jewels. You can still label the deck confidential, control distribution and avoid unnecessary detail. For later-stage discussions, confidentiality may be addressed in a term sheet, data room access rules or separate NDA, especially if you disclose detailed financials, customer contracts, source code summaries or information about pending commercial deals.

A common founder mistake is sending a 40-page deck with every metric, customer name and product plan attached, then trying to impose an NDA after the fact. If you want confidentiality, raise it before disclosure. If the investor refuses, decide whether the opportunity justifies a narrower disclosure.

Strategic Partners

A strategic partner is more likely than a financial investor to need an NDA because they may operate in your market or have the ability to use your information commercially.

For example, a healthtech startup might pitch a pilot to a private clinic group, or a SaaS company might discuss integration with a larger platform. The partner may need to see technical requirements, pricing assumptions, implementation plans and customer feedback. Those materials could be valuable even if no deal proceeds.

In these discussions, a mutual NDA is often sensible because both sides may share confidential information. The agreement should permit use of the information for evaluating and negotiating the proposed collaboration, but not for competing projects, reverse engineering, approaching your customers or sharing it widely inside the recipient's organisation.

Be realistic about internal circulation. A corporate partner may need to share your deck with legal, finance, product, procurement and senior management. Your NDA should allow appropriate internal disclosure to people who need to know, while making the recipient responsible for keeping those people bound by confidentiality obligations.

Contractors and Agencies

Contractors should usually sign confidentiality terms before receiving detailed product, customer, technical or operational information.

This applies to developers, designers, marketing agencies, consultants, manufacturers, data analysts and virtual assistants. Contractors often need deep access to deliver the work. They may see your codebase, product roadmap, ad strategy, supplier contacts, customer database or unreleased creative materials.

For contractors, confidentiality should usually sit inside a wider services agreement, not just a standalone NDA. That agreement should cover scope, fees, timing, IP ownership, licence terms, data protection, subcontracting, warranties, termination and return of materials. If the contractor processes personal data for you, you may also need UK GDPR compliant processor clauses.

Do not assume that paying a contractor automatically transfers IP to your company. Copyright in designs, code, copy and other creative work may remain with the creator unless assigned in writing. An NDA stops disclosure, but it does not necessarily give you ownership of the deliverables.

Acquirers and Competitors

A potential buyer, especially one that competes with you, should not receive sensitive due diligence materials without clear confidentiality, business sale and use restrictions.

Acquisition discussions can require disclosure of detailed financial information, staff details, customer contracts, supplier agreements, code, IP, complaints, regulatory issues and pipeline. If the buyer walks away, they may still have learnt a great deal about your business.

An acquisition NDA should be more tailored than a light pitch deck NDA. It may include restrictions on contacting customers, suppliers and employees, limits on copying documents, named recipient groups, data room controls, return or destruction obligations, and rules for announcements. If personal data is included in diligence materials, UK data protection principles should also be considered, particularly around minimisation, access controls and lawful processing.

Where a potential acquirer is also a competitor, staged disclosure is critical. Share summary information first, then release more sensitive documents only when commercial intent is clearer and the NDA is signed.

What Your Pitch Deck NDA Should Cover

A good NDA for pitch materials should clearly say what is confidential, what the recipient can do with it, and what happens when discussions end.

The document does not need to be aggressive to be effective. In fact, a balanced NDA is often easier to get signed. The best drafting usually focuses on practical behaviour: who can see the information, why they can use it, how long the duty lasts, and what must be returned or deleted.

Key clauses to consider include:

• Parties. Name the correct legal entities or individuals. If your company has been incorporated at Companies House, the company should usually be the contracting party rather than the founder personally.
• Definition of confidential information. Cover written, oral, visual and electronic information, including pitch decks, demos, financials, customer details, product plans, code, know-how and data room materials.
• Purpose. Limit use to a specific purpose, such as evaluating an investment, partnership, services proposal or acquisition.
• Permitted disclosures. Allow disclosure to employees, officers, advisers or group companies who need to know and are under confidentiality duties.
• Exclusions. Standard exclusions usually cover information already public, already known, independently developed or lawfully received from another source.
• Security obligations. Require reasonable steps to protect the information and prevent unauthorised access, copying or onward disclosure.
• Return or destruction. Set out what happens to copies, notes and data room downloads if discussions end.
• Duration. Choose a period that fits the information. Some trade secrets may need protection for as long as they remain confidential.
• IP ownership. State that sharing information does not transfer ownership of IP, copyright, trade marks, know-how or other rights.
• No obligation to proceed. Make clear that discussions do not force either party to invest, partner, buy or appoint the other.
• Governing law and jurisdiction. For UK startups, English law and the courts of England and Wales are commonly used where appropriate.

Some clauses need careful handling. Non-compete agreement style wording can make an NDA look unreasonable if it stops the recipient from working in an entire sector. A clause that prevents use of your confidential information is usually more targeted than a broad ban on competition. Non-solicitation wording may be appropriate in acquisition or partnership discussions, but it should be proportionate and clearly connected to the deal.

Mutual NDAs are useful where both sides disclose confidential information. One-way NDAs are suitable where only you disclose sensitive material. Founders sometimes send a one-way NDA to a corporate partner that also plans to share information. That can slow negotiations because the other side will need to amend it. If both businesses are opening up, start with a mutual structure.

Confidentiality also overlaps with data protection. If your pitch deck includes personal data, such as named customers, patient information, staff data or identifiable user analytics, an NDA is not enough on its own. The UK GDPR and the Data Protection Act 2018 require you to consider lawful basis, minimisation, transparency, security and any processor or controller relationship. A safer approach is to anonymise or aggregate data unless the recipient genuinely needs identifiable information.

For founders pitching a new product, trade mark and copyright points matter too. Copyright may protect the deck's original text, diagrams and visuals, but it will not protect the business concept itself. A registered trade mark can protect your brand name or logo if it meets the requirements and is accepted by the UK IPO. Patents may be relevant for some technical inventions, but public disclosure before filing can create serious problems, so specialist advice is usually needed before pitching patentable material.

The format of the NDA also affects signing. A concise, plain English document is more likely to be accepted than a dense document full of unnecessary clauses. Include the right protections, but avoid turning a first commercial conversation into a negotiation about remote risks.

FAQs

Should I Ask Every Investor To Sign an NDA Before Sending My Pitch Deck?

Usually, no. Many professional investors will refuse an NDA before seeing an initial deck. Use a high-level deck first, then consider confidentiality terms before sharing detailed financials, customer contracts, technical documents or data room materials.

Can an NDA Protect My Business Idea?

An NDA can protect confidential information about your idea, but it cannot protect a broad concept on its own. Focus on protecting non-public details such as product design, technical know-how, market research, pricing, customer insights and commercial strategy.

Is a Confidentiality Agreement Needed for Contractors?

Usually, yes. Contractors often need access to sensitive information to do their job. Confidentiality should normally sit inside a wider services agreement that also covers IP ownership, deliverables, fees, data protection and termination.

What If Someone Refuses To Sign My NDA?

Decide whether you can share a less sensitive version of the deck. If the recipient needs access to confidential information and will not accept reasonable restrictions, it may be safer to pause the discussion or release information in stages.

Should My NDA Be Mutual or One-Way?

Use a one-way NDA where only your business is disclosing confidential information. Use a mutual NDA where both sides will share sensitive information, such as in a strategic partnership, joint venture discussion or technical integration.

Key Takeaways

• A non disclosure agreement is most useful when you share specific confidential information, not just a broad startup idea.
• Investors often resist early NDAs, so founders should use a staged disclosure process and keep sensitive details out of first-contact decks.
• Strategic partners, contractors and acquirers usually create higher confidentiality risks because they may receive deeper operational, technical or commercial information.
• A pitch deck NDA should define the confidential information, limit its use, control internal sharing, preserve IP ownership and set rules for return or deletion.
• Confidentiality terms should sit alongside practical controls, such as data room access, version tracking, document permissions and careful use of personal data.
• Contractor arrangements should cover more than secrecy, including IP assignment or licensing, services scope, data protection and ownership of deliverables.

If you are preparing to share your pitch deck with investors, partners, contractors or a potential buyer, Sprintlaw's legal team can help with your confidentiality agreement, services contract, data room terms and IP ownership documents. Contact us on 08081347754 or at team@sprintlaw.co.uk for a free, no-obligations chat.