Trusq

factual analysis · traceable to primary sources

Explainer

AI, trade secrets and confidentiality

Adopted 2026-06-22 ยท ≈ 2 min read ยท Dirk Baaijen

Feeding confidential information into an external AI model can undermine trade-secret status and breach confidentiality or GDPR obligations. Protection depends on secrecy measures; uncontrolled sharing erodes them. Manage it with policy, contract and access rules.

Short answer: Feeding confidential business information into an external (cloud) AI model is legally risky. A trade secret is protected only as long as it is secret and you take reasonable steps to keep it so. Uncontrolled sharing with an external provider โ€” which may reuse or store the input โ€” can undermine that protection and may breach confidentiality or GDPR obligations.

Why input can undermine a trade secret

The protection of trade secrets (Directive (EU) 2016/943) depends on three conditions: the information is secret, has commercial value because it is secret, and is subject to reasonable steps to keep it secret. If that last pillar disappears โ€” for example by placing information without safeguards into an external model that retains the input or uses it for training โ€” the secret can lose its protected status. This is not only about actual leakage, but about the failure to take reasonable steps.

Contractual and confidentiality risks

Confidential information you receive from clients or partners is often covered by a non-disclosure agreement (NDA). Those NDAs typically restrict to whom and how you may disclose the information. An AI provider is a third party; entering information there can breach an NDA, even unintentionally. The same applies to source code, pricing models and unpublished strategy.

The GDPR layer for personal data

If the input contains personal data, the GDPR comes into play. You need a legal basis, a processor agreement with the provider, and clarity on where the data is processed and whether it leaves the EEA. Reuse of input for model training is a separate processing operation that is rarely covered by your original basis.

The difference between offerings

Not every offering is equal. Consumer versions of chat models may reuse input for training by default; business and enterprise variants often contractually guarantee that input is not used for training and not retained. Read those terms carefully: default settings differ from paid tiers, and a free trial environment is rarely covered by the same guarantees. Making this risk manageable begins with choosing an offering with the right contractual safeguards โ€” see also RAG and enterprise AI governance.

Shadow AI as the biggest leak

The real risk often lies not in a deliberate choice but in shadow use: employees who open a free chat model without consultation and paste in a quote, contract or customer file. A single act can then undo an NDA, the GDPR and the secrecy measure all at once. Policy without a usable, approved alternative does not solve this โ€” employees revert to whatever works. So offer a safe route alongside the prohibition.

What to do

  • Classify information before input: public, internal, confidential or secret. Secret and NDA-bound information does not belong in an unmanaged model.
  • Choose an enterprise offering with a contractual guarantee that input is not used for training and not retained.
  • Conclude a processor agreement and check the processing location where personal data is involved.
  • Set an input policy in your AI use policy for employees, with clear "do not enter" categories.
  • Restrict and log access, so your reasonable steps are demonstrable.

Sources

  1. https://eur-lex.europa.eu/eli/dir/2016/943/oj
    Directive (EU) 2016/943 (protection of trade secrets); protection requires reasonable steps to keep information secret.
  2. https://eur-lex.europa.eu/eli/reg/2016/679/oj
    Regulation (EU) 2016/679 (GDPR); legal basis, processor agreements and transfers where personal data enters AI models.

Share on LinkedIn

Read next

A

AI sentiment analysis of employees: the thin line to the emotion ban

AI inferring employee mood from email, chat, surveys or speech brushes against the emotion-recognition ban (Art. 5 AI Act) and the GDPR. Aggregated and anonymous is sometimes possible; individual monitoring almost never.

U

RAG and enterprise AI: governing proprietary generative AI

RAG connects a generative model to your own sources so answers come from company documents. That lowers fabrication but shifts the risk to access, confidentiality and provenance. Governance turns on source scoping, authorisation, logging and human oversight.

W

An AI use policy for employees: generative AI at work

Employees already use generative AI โ€” often without rules. A use policy bounds the risks: leakage of confidential or personal data, unreliable output, IP questions and transparency. The AI literacy duty (Art. 4) also makes such a policy part of compliance.

Dirk Baaijen

About this knowledge base

Compiled and maintained by YRproject โ€” programme and project direction at the intersection of digital transformation, AI and regulation. Every factual claim is traceable to its primary source. YRproject is led by Dirk Baaijen About & method โ†’

A project or programme? Work with YRproject โ†’

The monthly briefing

AI regulation in five minutes: what changed, what is coming and what it means. No spam, unsubscribe anytime.

Your address is used for this only and stored on our own servers.