NDAs and Confidential Information
NDAs and Confidential Information: Is Your Business Really Protected?
By Stephanie Pritchett, and Ben Wootton, Partners at Pritchetts Law
Do we need an NDA to protect our confidential information, and what should I check before I sign one? This article explores some key themes for businesses to consider, whether they are sending or receiving confidential information.
Key points to know:
-
English law can protect confidential information through contract (such as an NDA) and the equitable law of confidence.
-
Marking information "confidential" is not enough on its own - it must have the necessary quality of confidence and be shared in circumstances that make confidentiality clear.
-
NDAs work best alongside practical controls over what is shared, with whom and for what purpose.
-
Generic NDAs often fail to deal with AI tools, cloud platforms, contractors and how information is actually used in practice.
-
Recent court decisions, such as the Court of Appeal's ruling on what "public domain" means in an NDA, and new legal limits on what NDAs can prevent mean many NDA templates may need updating.
Confidential information is often one of the most valuable assets a business holds - and, in our experience, one of the most easily overshared. It may sit in commercial proposals, pricing models, customer lists, technical know-how, source code, product roadmaps, unreleased product videos, pre-release software, AI prompts, proprietary datasets that could be used to train or fine-tune AI models, security and privacy information, due diligence materials or strategic plans. Yet it is frequently shared quickly, informally and under pressure: with suppliers, investors, consultants, technology providers, customers, advisers and potential collaborators.
A non-disclosure agreement (
NDA
), also known as a confidentiality agreement, can be an important part of the protection. But it is not a complete solution on its own. English law can protect confidential information through both contract and the equitable law of confidence, but that protection depends heavily on the nature of the information, the circumstances in which it is shared, the purpose for which it is used, and the steps taken to keep it secret. In this article, we explain how that protection works in practice, where NDAs commonly fall short, and what UK businesses can do to close the gaps. Often an NDA is the first step in a new commercial relationship. As discussions progress, the same confidentiality issues will need to be carried into the contracts that follow, such as supply, SaaS, licensing, collaboration or investment agreements, so it pays to get the foundations right.
Pritchetts Law can help you with your NDA and your wider requirements.
What counts as confidential information?
Confidential information can take many forms. It can include technical information, processes, formulae, business plans, customer lists, financial information, pricing structures, software, algorithms, designs, product improvements and strategic commercial information. Trade secrets are a particular category of confidential information: information which is secret, has commercial value because it is secret, and has been subject to reasonable steps to keep it secret (as defined in the
Trade Secrets (Enforcement, etc.) Regulations 2018
).
However, simply labelling something “confidential” does not automatically make it confidential. The information must have the necessary quality of confidence. In broad terms, it must not be public property or public knowledge. Information may still be confidential where some elements are publicly available, if the particular compilation, selection, analysis or commercial context is not generally accessible and involved sufficient thought, or effort.
When does English law protect confidential information?
A useful way to think about the English law position is to ask three questions, which reflect the classic test in Coco v A N Clark (Engineers) Ltd [1969] RPC 41.
First, does the information have the necessary quality of confidence?
Secondly, was it shared in circumstances importing an obligation of confidence, whether because of a contract or because a reasonable recipient would understand the information was being shared confidentially?
Thirdly, has there been unauthorised use or disclosure?
This is why confidentiality is not just a legal drafting point. It is also an operational discipline. A well-drafted NDA helps, but businesses also need to control what is shared, with whom, when, for what purpose and on what practical safeguards.
Do you still need an NDA?
A written NDA or confidentiality clause in your contract, agreed before you share information, is usually the clearest way to show that information is being disclosed in confidence. It can define the relevant information, restrict permitted use, limit onward disclosure, regulate access by representatives, set return or destruction obligations, deal with compelled disclosure, and provide a contractual route to enforcement.
An NDA should be tailored to the transaction and the information at stake. By way of example, a generic NDA may not deal adequately with AI tools, cloud platforms, external advisers, group companies, contractors, model training, data rooms, software development, regulatory submissions or post-negotiation use of information. It may also be too narrow to protect against the real risks, or so broad that it becomes difficult to comply with in practice.
Common NDA pitfalls in commercial and technology relationships
Many confidentiality problems arise not because there is no NDA, but because the practical flow of information has not been analysed. For example, sensitive materials may be uploaded into a shared workspace, used in a demonstration, copied into an AI tool, sent to subcontractors, shared with a wider project team, retained after talks end, or used internally to develop a competing product or service.
Businesses should also be careful about disclosure before an NDA is signed. If early-stage discussions require sharing sensitive information, the disclosing party should make the confidential nature of the information clear, limit the volume of information shared, appropriately mark materials as confidential, use secure channels and record the purpose for which the information is being provided. Signing an NDA after the event, even one drafted to cover earlier disclosures, is rarely a satisfactory substitute for managing disclosures properly at the time.
AI and NDAs: a growing confidentiality risk
The use of AI tools creates particular confidentiality risks. Information may be entered into a system without a clear understanding of where it is stored, who can access it, whether it may be used to improve or train the system, whether it is retained, and whether outputs could reveal or reflect confidential inputs. Those risks are particularly important where teams use AI informally to summarise documents, review code, draft responses, analyse datasets or prepare commercial materials.
Businesses should consider whether their NDAs, supplier contracts, AI policies and internal guidance expressly address use of confidential information with AI systems. This may include restrictions on inputting confidential information into public or unapproved tools, requirements to use approved enterprise environments, obligations on suppliers not to use customer confidential information for model training, and controls around logging, retention, access and deletion.
When can confidential information be disclosed despite an NDA?
Confidentiality is powerful, but not absolute. Information may lose protection, and no longer be confidential, if it becomes public or ceases to have commercial sensitivity. Confidentiality obligations may also be displaced or qualified by statutory requirements, court processes, regulatory obligations, whistleblowing protections, public interest considerations, or properly framed disclosures to professional advisers or authorities.
Disclosure in litigation, freedom of information requests (where information is shared with public bodies), regulatory submissions and international sharing arrangements can all require careful handling. Businesses should not assume that a confidentiality clause will always prevent disclosure, particularly where another legal obligation or public interest issue is engaged.
Recent developments: time to review your NDA templates?
Several recent and ongoing developments are a good prompt to check whether your standard NDA still does the job:
-
What “public domain” means in an NDA.
In
Illiquidx Limited v Altana Wealth & Ors
[2026] EWCA Civ 874, the Court of Appeal held that “public domain” in a professionally drafted NDA will ordinarily be taken to carry its established legal meaning, unless the wording indicates otherwise. Information was not in the public domain simply because some of its components were publicly available or it had been selectively circulated; the question was whether it was generally accessible. This is helpful for disclosers, but it underlines the importance of drafting public domain and other exclusions carefully: if the parties intend a different meaning, the NDA should say so expressly. It strikes us, separately that with the advent of AI tools that are highly adept at surfacing information from the internet, organisations would be wise to take a very broad view and assume that information is more easily accessible than it may appear, could be in the public domain, and so may be harder to protect as confidential information. Practical steps should be taken to limit and secure confidential information, rather than relying on the NDA alone.
-
A confidentiality clause is not a cyber security clause.
In
Logix Aero Ireland Ltd v Siam Aero Repair Co Ltd
[2026] EWCA Civ 510, the Court of Appeal upheld the striking out of a claim, finding that an assumed breach of a confidentiality clause in a letter of understanding was not the effective cause of loss where information was unwittingly disclosed to fraudsters who intercepted emails and substituted bank details. The Court held that the confidentiality clause did not impose a special duty to protect against fraudsters manipulating information. If information security matters, it should be addressed expressly.
-
Disclosures by victims of crime.
Section 17 of the Victims and Prisoners Act 2024
makes contractual provisions (including confidentiality provisions) entered into on or after 1 October 2025 void to the extent they would prevent a victim of criminal conduct (or a person who reasonably believes they are one) from making certain permitted disclosures about that conduct to specified people for defined purposes. This applies in England and Wales to agreements of all kinds, including commercial NDAs and confidentiality clauses, so templates used for new agreements may need updating. Section 17 is due to be replaced by
section 6 of the Victims and Courts Act 2026
(not in force at the time of writing), which will broaden the protection for victims by allowing victims to make allegations or disclosures about the criminal conduct (and the other party's response to it) to anyone and for any purpose, subject to any “excepted agreements” set out in regulations, so templates will need to be kept under review.
-
Solicitors and the SRA warning notice.
The
Solicitors Regulation Authority’s warning notice on NDAs, updated in August 2024
, applies to everyone the SRA regulates (including in-house lawyers) who negotiate, draft, advise on, enforce or are party to any NDA, including business-to-business agreements. The SRA considers it improper to use an NDA to prevent, impede or deter reporting to regulators or law enforcement, co-operation with criminal investigations or protected disclosures, and NDAs must not give the impression that such disclosures are prohibited. More generally, well-drafted NDAs should include appropriate carve-outs for these kinds of disclosure, as well as for disclosures required by law or made to professional advisers.
-
Watch this space: NDAs in the workplace.
The Department for Business and Trade consulted (from 15 April to 8 July 2026) on regulations under the Employment Rights Act 2025. The Act will void provisions preventing workers from speaking out about workplace harassment and discrimination, with regulations setting out limited “excepted agreements”. The SRA published its consultation response on 23 July 2026. The government’s response to
the consultation
is still awaited. While this is primarily an employment law issue, it forms part of a wider trend of increasing scrutiny of NDAs.
Our top 10 tips for protecting confidential information
-
Identify what information is genuinely sensitive and why it needs protection as confidential information.
-
Put an appropriate NDA or confidentiality clause in place before disclosure where possible, with suitable carve-outs for permitted disclosures such as reporting to regulators or law enforcement.
-
Limit disclosure to what is necessary for the relevant purpose.
-
Make the confidential nature and permitted purpose clear at the point of disclosure.
-
Control onward disclosure to employees, advisers, group companies, subcontractors and technology providers.
-
Use secure channels, access controls, appropriate file storage, data rooms and sensible retention arrangements.
-
Address use of confidential information by AI tools expressly in contracts, policies and supplier controls.
-
Keep records of what was disclosed, when, to whom and for what purpose.
-
Require return, deletion or continued protection of confidential information when discussions or projects end.
-
Review confidentiality provisions against the actual operational workflow, not just the legal template.
Key takeaway
Confidentiality protection works best when legal drafting and practical controls are aligned. NDAs remain important, but they should sit within a broader approach to information governance, contract management, supplier oversight and AI/data risk.
For businesses sharing valuable information in commercial, technology, AI or regulated environments, the real question is not simply “do we have an NDA?” but “does our confidentiality framework actually match how information is being used?”
For business on the receiving confidential information, and being asked to sign an NDA, make sure you understand the scope of the information it protects, how long it is protected for, what you can use that information for, what security or other practical measures should be put in place, and what do you do with the data at the end of the arrangement, or when you no longer need it. Consider if the NDA is one-way or mutual – does it for example, if you are a supplier does it protect your pricing information as well as the customer data being shared? If your customer, does it only protect the supplier’s secret sauce, but not your valuable datasets that they are testing?
Frequently asked questions
Is information confidential just because it is marked "confidential"?
No. Labelling helps show that information is shared in confidence, but the information itself must have the necessary quality of confidence. Information that is generally accessible will not usually be protected.
Can an NDA cover information shared before it was signed?
An NDA can be drafted to cover earlier disclosures, but it is better to agree confidentiality terms before sharing anything sensitive. Where that is not possible, make the confidential nature and purpose of the information clear at the time.
Can an NDA stop someone reporting to a regulator or the police?
Generally not.
Whistleblowing
protections and the Victims and Prisoners Act 2024 limit what NDAs can prevent, and solicitors must not use NDAs to stop or deter reporting to regulators or law enforcement.
Should an NDA deal with AI tools?
Often, yes. If confidential information could be entered into AI systems, the NDA or related contracts should say whether that is allowed and on what terms, including whether the information may be used for model training.
How long does an NDA last?
It depends on the drafting. Many NDAs set a fixed period, while trade secrets may need protection for as long as they remain secret.
How we can help
We advise businesses of all sizes, from SMEs to multinationals and regulated organisations,
on NDAs, confidentiality agreements
and the wider
technology and commercial contracts
that sit around them. We can help you:
-
Draft bespoke mutual or one-way NDAs for specific deals, collaborations, investment discussions or R&D projects.
-
Review and negotiate NDAs you have been asked to sign.
-
Refresh your NDA templates for recent legal developments,
AI use
and regulatory carve-outs.
-
Align confidentiality terms in supplier, SaaS, cloud, outsourcing and AI contracts.
-
Put in place practical policies and controls, including AI use guidance, so that your contracts and day-to-day practices align with how information is actually shared.
If you are about to share sensitive information, have been sent an NDA to sign, or think your templates may be out of date, please get in touch with Stephanie Pritchett or Ben Wootton for a no-obligation chat. We provide clear, practical advice in plain English, tailored to your business and proportionate to what is at stake, with fees agreed in advance where the work can be appropriately scoped.
This article is for general information only, reflects the law and guidance at the date of publication and does not constitute legal advice. Specific advice should be sought on your particular circumstances.
|
Who
|
Why you can rely on us
|
|
Pritchetts Law LLP
|
A specialist, partner-led English law firm advising on data protection, AI, technology and commercial contracts. Ranked in The Legal 500 UK. Authorised and regulated by the Solicitors Regulation Authority (SRA no. 647155). Exclusive IR Global advisor for Data Privacy & Security in England. LOCS:23 Qualified Consultancy.
|
|
Stephanie Pritchett
, Partner
|
Over 20 years advising on IT, commercial contracts and data protection. Data Protection Trainer for PDP Companies. Formerly head of data protection at Burges Salmon LLP; worked at Foot Anstey LLP and in-house at Virgin Mobile, Royal Botanic Gardens Kew, GBR Challenge and Seattle Challenge for the America's Cup. Founded Pritchetts Law in 2009. Ranked in Chambers UK and a Legal 500 UK recommended lawyer.
|
|
Ben Wootton
, Partner
|
Over 20 years advising on IT, commercial contracts and data protection. Trained at Pinsent Masons; worked at Burges Salmon and Addleshaw Goddard; in-house at Heathrow Airport and Air New Zealand. Partner at Pritchetts Law since 2018. Legal 500 UK recommended lawyer.
|
|
Contact
|
Contact Us: Data Protection, AI & Technology Solicitors | Pritchetts Law LLP
|