From the journal

Employee use of AI and trade secrets: protecting confidential information after an upload

Company information can retain trade-secret protection after an employee uploads it to an AI service. The strongest case combines a defined secret, lawful authority to use it, restricted recipients and purposes, and protective measures that operated in practice. An unauthorised upload can breach an employment duty or customer agreement while the information remains confidential.

32 min read

Company information can retain trade-secret protection after an employee uploads it to an AI service. The strongest case combines a defined secret, lawful authority to use it, restricted recipients and purposes, and protective measures that operated in practice. An unauthorised upload can breach an employment duty or customer agreement while the information remains confidential. Broad reuse rights, inadequate controls or actual public dissemination can weaken or defeat secrecy-based protection. Each conclusion requires evidence about the particular information and account. US: 18 USC §1839(3), (5); EU: Directive 2016/943, Arts 2–4.

Consider employees analysing source code, pricing and a customer's confidential material through personal and enterprise accounts. The accounts have different retention settings, sharing permissions and contractual terms. Management needs three answers: whether the information still qualifies for protection, whether a duty has already been breached, and what conduct by each recipient can be restrained or compensated. Those answers determine the response.

An AI confidentiality breach therefore starts with an evidence exercise. Identify the upload, preserve the applicable terms and configuration, restrict continuing exposure through authorised controls, and establish the customer's permissions. A provider's promise about training answers only part of the inquiry. Its confidentiality duties, permitted uses, reviewers, connectors and downstream recipients also matter.

This analysis compares the United States and Canada; the EU framework, Germany and the United Kingdom; Singapore and Japan; the United Arab Emirates (UAE) and Saudi Arabia; South Africa and Kenya; Brazil and Mexico; and Australia and New Zealand. The UAE discussion distinguishes onshore law, the Dubai International Financial Centre (DIFC) and Abu Dhabi Global Market (ADGM). The analysis states the law and contract terms as at 19 November 2026. Country rules below identify the differences that change the decision.

Establish what left the business

Create a restricted schedule of the exact information in each upload. A repository name or a label such as “customer data” is too broad to explain the claimed secret. Identify the code, pricing logic, negotiated terms, selected customer information or valuable combination that requires protection. Record the version and which parts were already public. In InteliClear v ETC, the US Ninth Circuit required sufficient identification while recognising that a confidential combination may qualify. 978 F.3d 653 (9th Cir. 2020), pp 659–661.

For company information, retain the ownership, assignment, licence or lawful-control documents. For customer information, add the customer non-disclosure agreement (NDA), statement of work and permitted-recipient provisions. A company may hold the material only for a defined project. Its authority to analyse the material must extend to the chosen provider and the permitted uses. Internal management approval cannot vary the customer's contract without the required contractual authority.

Keep three legal classifications distinct. Statutory trade-secret protection has jurisdiction-specific elements. A confidentiality agreement or confidence duty may cover a wider category. Personal-data rules concern their own protected interests and can apply alongside either category. A data-processing agreement or a “confidential” label alone does not establish every trade-secret element. The EU directive's definition, Quebec's contractual duties and Australia's company-information rule illustrate those different routes. Directive, Art 2; Quebec Civil Code, Arts 1458, 2088; Corporations Act 2001, s183.

Next, reconstruct the actual transmission. Record the account holder and provider contracting entity, upload date, accepted terms, workspace membership and administrative access. Preserve the relevant setting history. Establish whether the employee used a chat interface, API, project, retrieval store, connector or external action. Identify any shared link and its audience. Ask what human review, subprocessors, support access and retention applied to that feature.

Separate permission from observed conduct. A clause permitting model improvement raises a consent and protective-measures issue. A finding that the provider actually trained on the content needs evidence of that use. A finding that a model disclosed the secret needs evidence of the output and its provenance. A similar answer can have an independent source. The applicable misappropriation or confidence claim must connect the defendant's conduct to the identified protected information. US, §1839(5)–(6); Japan UCPA, Art 2(1)(iv)–(ix).

Disclosure conditions and likely protection outcomes

The following list applies the national rules discussed below. Where secrecy can survive, the evidence can support continuing protection; the claimant must still establish the applicable elements. A weakened position identifies a proof problem requiring investigation. Where secrecy fails, that loss concerns the particular information and legal ground affected, while accrued breach claims require a separate assessment.

  • The holder authorised a restricted service; relevant recipients are bound to confidence and limited use. Protection and breach analysis: Secrecy can survive. Assess value, confidential character and protective measures under the applicable law. Decisive element and evidence: Holder's permission, accepted terms, recipient restrictions, actual configuration and access. Action for the responsible actor: The company preserves the permission chain and confirms that the service stayed within it.
  • An employee used an unapproved account, but recipients remain effectively restricted. Protection and breach analysis: An employment or customer-contract breach can arise while secrecy survives. Decisive element and evidence: The employee's authority, the exact duty, transmission and recipient obligations. Action for the responsible actor: The company contains exposure, assesses the breach and establishes each recipient's separate responsibility.
  • The account permits broader provider reuse. Protection and breach analysis: Consent and reasonable-measures arguments may be materially weakened. Actual use and public availability remain facts to establish. Decisive element and evidence: Historic licence, opt-in or opt-out, purpose, rights to grant that permission, and actual processing. Action for the responsible actor: The contracting party seeks factual confirmation and enforceable limits; the customer controls any permission it must grant.
  • A public share link or onward release makes the relevant information generally accessible. Protection and breach analysis: The secrecy element may fail for the exposed material. Claims for the earlier wrong and remaining undisclosed information need separate analysis. Decisive element and evidence: Scope and timing of access, downloads, indexing, material actually revealed and causation. Action for the responsible actor: The authorised administrator disables exposure and preserves evidence; the claimant assesses targeted relief and loss.
  • The provider retains restricted copies for security, legal retention or evidence. Protection and breach analysis: Continued retention requires assessment of access, purpose and duties. It does not itself establish general availability. Decisive element and evidence: Retention exception, duration or event, recipients, segregation and non-use controls. Action for the responsible actor: The contracting party seeks a precise retention explanation and restriction of residual copies.
  • A generated answer resembles the business's material. Protection and breach analysis: A claim requires proof of protected content and actionable acquisition, use or disclosure. Decisive element and evidence: Original secret, exact output, prompt, date, account, model identifier and alternative sources. Action for the responsible actor: The company preserves the output and investigates lawfully without uploading more secrets to test the theory.

For source code, remove credentials and unrelated customer material before any future approved analysis. Redaction must also remove the claimed secret where permission remains absent. A pricing table may reveal a protected margin or discount strategy even after personal identifiers disappear. For customer material, an approved enterprise tool is usable only within the customer's permitted purpose and recipient conditions.

Read the account's actual AI confidentiality agreement

“Enterprise” and “personal” describe a starting point for document collection. Determine the agreement that actually governed the upload, including the order form, service-specific terms and incorporated policies. An employee's paid personal subscription can have different terms from the employer's workspace. The current public webpage also may differ from the version accepted at the relevant time.

OpenAI's published business agreement provides one concrete contractual comparison. The version effective 1 January 2026 limits use of customer content in section 4.2 and provides confidentiality obligations in section 7. It also places responsibility for input rights on the customer. The agreement permits defined operational recipients and contains retention, liability and dispute provisions. Its terms therefore require reading together. OpenAI Services Agreement, §§4.2–4.3, 7, 11, 14–16. The incorporated Service Terms contain separate permissions for shared GPTs and transfers to connected applications; check the version and features actually used. Service Terms, §§5, 7.

The published individual terms effective 1 January 2026 for users outside the European Economic Area, Switzerland and UK permit content use for stated service purposes, including improvement, with an opt-out mechanism described separately. Identify the applicable regional terms and feature. Ownership language does not answer the scope of the provider's use permission. OpenAI individual terms, “Content”.

For each affected account, obtain the signed or accepted terms, settings and exceptions in force at upload. Determine what an opt-out changed and when it took effect. Ask separately about human access, feedback, connectors, retention and other features. Preserve the setting history and distinguish it from later changes.

Contract clause issues after an upload is found

  • Ownership and authority. Documents and question: Assignments, licences, customer NDA and employee delegation: who may authorise this disclosure and purpose? Consequence and response: Obtain missing permission from the holder where available. Preserve claims arising before any later permission.
  • Permitted purpose and recipients. Documents and question: Customer contract, provider terms, subprocessor commitments and connector terms: does the agreed project include this processing chain? Consequence and response: Confine use to the authorised purpose. A provider permission granted beyond the company's authority can expose the company to the customer.
  • Provider use rights. Documents and question: Accepted terms and setting history: what service, training, evaluation, safety and feedback uses are permitted? Consequence and response: Identify each permitted act and any conflicting customer restriction; obtain a specific amendment or choose an authorised workflow.
  • Confidentiality and exceptions. Documents and question: NDA and incorporated terms: who is bound, and when do public-domain, prior-knowledge, independent-development or required-disclosure exceptions apply? Consequence and response: Test the evidence for the exception and whether the recipient caused the disclosure. Preserve mandatory reporting rights.
  • Incident notice and assistance. Documents and question: Customer and provider incident clauses: which event triggers notice, to whom, and within what actual period? Consequence and response: Assign responsibility and meet the applicable trigger. Record continuing factual uncertainty without waiting for a final loss calculation.
  • Warranties and indemnities. Documents and question: Input-rights warranty, covered claims, exclusions, defence control and notice provisions. Consequence and response: Check whether customer confidentiality claims are covered. An output intellectual-property indemnity may have a different subject and excluded inputs.
  • Caps and excluded loss. Documents and question: General cap, confidentiality carve-outs, deliberate-conduct terms and mandatory local limits. Consequence and response: Calculate exposure under each applicable clause. An exception to an excluded-loss clause does not necessarily remove the aggregate cap.
  • Return, deletion and survival. Documents and question: Retention schedule, termination terms, legal holds and downstream obligations. Consequence and response: Require specific treatment of active copies, logs, backups and permitted retained records. Preserve evidence and surviving non-use duties.
  • Law, forum and interim relief. Documents and question: Each party's accepted law, court or arbitration clause and relevant mandatory law. Consequence and response: Identify the respondent, forum and enforceable relief. A customer may lack contractual rights against the provider.

The cap distinction has a practical example in the cited OpenAI business agreement. Its confidentiality/security exception to the exclusion of certain losses appears in section 14.1. The aggregate cap in section 14.2 has its own exceptions. Treating ordinary confidentiality liability as wholly uncapped would skip that second inquiry. Check the actual order form and mandatory law before calculating recoverable loss.

Licentium's AI supplier contracts service addresses negotiation of the customer and upstream-provider documents. Here, those documents serve a narrower task: establishing the permissions, duties and remedies that existed when the upload occurred.

AI trade secrets: protection and remedies across jurisdictions

North America: retain the contract claim and identify the claimant

Under the US Defend Trade Secrets Act (DTSA), the owner must identify information with independent economic value from secrecy and reasonable measures to keep it secret. The federal civil route also requires the statutory connection to interstate or foreign commerce. A qualifying licensee can fall within the statutory owner definition. An employee's access to information does not itself authorise every disclosure or provider use. Downstream liability depends on the applicable acquisition, knowledge, duty and consent requirements. 18 USC §§1836(b)(1), 1839(3)–(6); civil action.

Restricted sharing can be consistent with reasonable measures. In InteliClear, confidentiality terms and protective practices supported reversal of premature summary judgment. The appellate court did not finally establish that every alleged feature was a trade secret. Applied to AI uploads, the decision supports examining actual restrictions and proof, with the provider's permitted uses assessed separately. Official opinion, pp 8–16, 21.

California adds two useful distinctions. Its trade-secret statute expressly preserves contractual remedies even where they are not based on trade-secret misappropriation. Its injunction provision can continue a restraint for a reasonable period to eliminate a commercial advantage caused by misappropriation after secrecy has ceased. A company should therefore preserve the NDA and causation evidence even if publicity damages the secrecy claim. A confidentiality obligation must also respect California's limits on employment restraints. Civil Code §§3426.2, 3426.7; Business and Professions Code §16600. Monetary relief includes actual loss and non-duplicative unjust enrichment; a royalty is available if neither is provable. Enhanced recovery has additional statutory conditions, and the discovery-based limitation is three years. Civil Code §§3426.3–3426.6.

In Canada's common-law provinces, the confidence relationship and unauthorised use provide a civil route. Cadbury Schweppes v FBI Foods shows why the remedy must reflect the misuse and resulting advantage. The Supreme Court rejected a permanent restraint on the facts and addressed compensation for the lost competitive head start. A claimant should identify what the upload enabled, how long any advantage lasted, and what relief can address it. 1999 1 SCR 142, paras 19–26, 52–54, 67–78.

Quebec requires its own civil-code analysis. Article 2088 imposes loyalty and confidentiality duties on employees, continuing for a reasonable time after employment; the duty continues indefinitely where the information concerns another person's reputation or private life. Articles 1457–1458 govern the relevant civil or contractual responsibility. Article 1612 includes the owner's investment in acquiring, developing and exploiting the secret in the loss assessment and permits lost gain to be compensated through royalties. A proposed claim should identify the duty and available remedy under those provisions. Civil Code, Arts 1457–1458, 1612, 2088.

The practical Canadian result is to preserve confidentiality evidence even if a US-style statutory definition is an imperfect fit. For customer information, establish to whom the confidence or contract duty is owed. Do not assume that a company which owes damages to its customer has an equivalent claim against the provider.

Europe: reasonable measures and employee limits must work together

The EU Trade Secrets Directive requires secrecy, commercial value because of secrecy, and reasonable steps by the lawful controller. Its unlawful-use and disclosure rules expressly address breaches of confidentiality and use restrictions. It also protects specified public-interest, expression and worker-representative interests. The private claim is pursued through applicable national law. Directive 2016/943, Arts 2, 4–5.

Germany's implementing law adds a legitimate-interest element and requires measures appropriate to the circumstances. The Federal Labour Court's decision of 17 October 2024 illustrates the proof burden. General assertions of information technology security did not establish the required measures. The court also rejected an unlimited standard-form post-employment confidentiality clause covering every internal matter. A targeted, justified secrecy obligation requires a different assessment. GeschGehG §2; BAG 8 AZR 172/23, paras 23–28, 30–42.

That matters after a shadow AI upload. A policy prohibiting unauthorised tools is useful evidence only when connected to the information, access controls, employee instructions and actual implementation. Replacing missing evidence with a sweeping NDA can leave both the statutory and contractual routes vulnerable. Preserve what existed before the event and record subsequent improvements separately.

The UK's 2018 Regulations retain a statutory definition and accommodate wider breach-of-confidence protection. For the England and Wales confidence route, recipient awareness remains important. In Vestergaard Frandsen v Bestnet, the Supreme Court declined to impose liability on the relevant former employee who lacked the necessary knowledge. In Lifestyle Equities v Ahmed, the Supreme Court later confirmed that trade-secret knowledge holding while disapproving a separate obiter comparison concerning patent liability. 2024 UKSC 17, paras 89–90, 130–132. The case supports an actor-specific inquiry: the provider's responsibility needs its own duty, notice and conduct analysis. Regulations 2–3; 2013 UKSC 31, paras 21–31, 39.

An injunction application must use the procedural route in force. The UK's court-definition amendment took effect on 1 October 2026. England and Wales court allocation must be considered with the Civil Procedure Rules in force, including technical trade-secret claims. A company's historic template may point to an outdated provision. SI 2026/723, Art 1(2), Sch 2 para 20; CPR Part 63.

Asia: distinguish wrongful taking from disclosure and misuse

Singapore's confidence law requires particular care over the claim being made. I-Admin v Hong Ying Ting recognised an approach addressing unauthorised acquisition. The Court of Appeal's later discussion in Lim Suk Ling Priscilla v Amber Compounding Pharmacy distinguishes that approach from the conventional claim for unauthorised use or disclosure. An AI upload should be analysed by the information category, the employee's initial authority and the subsequent act. A general presumption of liability for every upload would erase those distinctions. 2020 SGCA 32, paras 61–66; 2024 SGCA 16, paras 31–34, 45–50.

The Singapore inquiry can protect a confidential compilation and address misuse without a public release. For the company, a useful remedy still requires an identified wrong and evidence supporting the requested relief. In I-Admin, the court treated equitable remedies as discretionary and considered whether forward-looking orders were needed on the facts. A prompt, output or upload log should therefore be tied to the actual claim and continuing threat. 2024 judgment, paras 35–40; 2020 judgment, paras 67–77.

Japan's Unfair Competition Prevention Act uses a different statutory structure. A trade secret must be managed as secret, useful for business and not publicly known. The Act's definition of disclosure can include showing information to specified persons while maintaining secrecy. Consequently, an upload can constitute disclosure while secrecy survives. Liability then requires the elements of the relevant prohibited-conduct provision. UCPA, Art 2(6), Art 2(1)(iv).

For an employee legitimately shown the secret, Article 2(1)(vii) requires the prescribed purpose of wrongful gain or harm to the holder. Careless use of an unapproved tool can raise contractual responsibility without proving that statutory purpose. A claim against a downstream recipient has its own knowledge or gross-negligence conditions under the applicable limb. Preserve evidence of instructions, authority, purpose, notice and actual use. UCPA, Art 2(1)(vii)–(ix), Arts 3–4.

The Japanese result is especially useful when assessing a hurried employee's productivity use. Establish what happened before deciding which claim fits. A statutory claim that requires wrongful purpose cannot be completed by showing only that the account lacked approval. Contractual permission and the continued management of the material as secret remain separate issues.

UAE onshore law expressly addresses undisclosed information. Federal Law 11/2021 requires secrecy, secrecy-derived commercial value and effective measures. Article 63 also addresses internal circulation and protective effort. Article 64 identifies dishonest practices, including specified breaches of confidentiality, with separate requirements for downstream conduct. The holder should preserve both external-provider restrictions and internal access records. Arts 61–65, Arabic text. The implementing regulation also specifies confidentiality terms for employment, outsourcing that permits access, and assignment/licence contracts. Check the applicable agreement against those requirements, including continuing employee and outsourcing restrictions. Cabinet Resolution 6/2022, Art 71(2)(e)–(g).

The UAE's 2025 Civil Transactions Law has applied since 1 June 2026. Article 123 addresses unpermitted use or disclosure of confidential information obtained during negotiations or in connection with a contract, with responsibility under the general rules. This supplies an additional reason to examine the customer and provider agreements even where statutory trade-secret qualification is contested. Federal Decree-Law 25/2025, Art 123.

Choose relief carefully. Article 68 of the industrial-property law concerns precautionary seizure; Article 69 is penal. Neither provision supplies a general promise that a court will order an overseas AI provider to erase every copy or remove model effects. The claimant needs an applicable civil and procedural route, standing, a forum connection and technically specific relief. Federal Law 11/2021, Arts 66–69.

DIFC has its own published trade-secret provisions and a separate confidence provision in Article 37 of its Law of Obligations. The distinction matters when information remains confidential but use exceeds the authorised purpose. In Gate Mena v Tabarak, the Court of Appeal considered the intended purpose and misuse in applying Article 37. Identify the applicable DIFC instrument and the particular recipient's knowledge and conduct before choosing the claim. IP Law 4/2019, Arts 52–55, 67; Law of Obligations, Art 37; 2023 DIFC CA 002, judgment 13 June 2024, paras 137–142.

ADGM receives English common law and equity through its own framework, subject to applicable local legislation. UK statutes require their own reception basis. The confidence inquiry can therefore draw on English authority while jurisdiction, procedure and protected disclosures require ADGM-specific analysis. A choice of ADGM law alone does not establish jurisdiction over every overseas recipient. Application of English Law Regulations 2015, sections 1–2; ADGM English Law Guidance, §§2.1–3.1.

Saudi Arabia's operative regulations address unconsented acquisition, use or disclosure contrary to honest commercial practices. Article 1 lists secrecy, value and reasonable protective measures; Article 3 addresses contractual confidence and downstream knowledge. Preserve evidence of all those characteristics. The Arabic definition's “any of the cases” wording requires particular attention if a claim depends on only one listed characteristic. As at 19 November 2026, the Trade Secrets Law under consultation in October–November 2026 remained a proposal, which cannot supply operative rights or remedies. SAIP regulations, Arts 1–3, 8; official consultation.

These UAE systems and Saudi law should be treated separately in the incident file. Ordinary analysis of code, pricing and customer information supplies no virtual-asset activity trigger for Dubai's Virtual Assets Regulatory Authority. A regulated business may have additional duties when its actual activities bring those rules into scope. Dubai Law 4/2022, Arts 2–3, 15–16.

Africa: prove the confidential relationship and the threatened harm

South Africa's Supreme Court of Appeal in Pexmart v H Mocke Construction identified useful trade or industrial information, restricted-circle secrecy and objective economic value. The court also recognised that confidential circumstances and authorised rights can support protection without a written NDA. The reasonable-measures language of a foreign statute should not replace that common-law inquiry. 2018 ZASCA 175, paras 62–65, 72–78.

For an AI upload, South African access restrictions and provider commitments help establish the confidential circle, duty and authorised purpose. A missing NDA is an evidence problem to investigate; the surrounding relationship may still impose confidence. Conversely, a written promise cannot make already public information secret. The company should identify the valuable know-how or compilation and the particular use it can lawfully prevent.

Kenya contributes a direct customer-information concern. In Nduati v Ernst & Young, the Employment and Labour Relations Court addressed employees' disclosure of confidential customer contracts and the resulting exposure of their employer to customer obligations. In Mediheal v Umesh, the same court required specific protected information and evidence supporting the threatened misuse; general employee experience and a fear of competition were insufficient for the requested interim restraint. Both were interlocutory rulings, which limits what they establish about final liability. 2022 KEELRC 3926, paras 5–10; 2022 KEELRC 3811, paras 19–28.

The Kenyan application is practical. Separate the customer's contract from the employer's ownership claim. Preserve the employee's permission and the information actually disclosed. An urgent application should identify a continuing disclosure or use risk and the precise material to protect. A general ban on the employee's future work would require a different justification.

Latin America: separate civil protection from penal and administrative routes

Brazil's Industrial Property Law addresses unauthorised disclosure, exploitation or use of confidential knowledge, information or data obtained through employment or contract, including after termination. Article 195 XI excludes public information and information evident to a person skilled in the field. Article 195 XII addresses illicit or fraudulent acquisition. The criminal mental-element requirements require their own analysis; an accidental upload cannot simply be treated as a completed offence. Lei 9.279/1996, Art 195 XI–XII; Penal Code, Art 18.

Civil remedies remain important. Articles 207–210 address civil action and compensation, and Article 209 permits an urgent cessation measure under its conditions, potentially before the defendant is heard. Article 206 protects confidential information in proceedings. Where the dispute arises from employment, Brazil's constitutional labour-court allocation must be considered. The response file should support the relevant civil or employment claim while preserving the confidential material. Industrial Property Law, Arts 206–210; Constitution, Art 114 I, VI.

Mexico expressly requires sufficient means or systems to maintain confidentiality and restrict access to an industrial secret. Its statute addresses authorised users and employees or professional recipients warned of confidentiality. This makes actual notices, permissions and access controls particularly important. The company's provider permission must fit the legal controller's authorisation, including any customer restriction. LFPPI, Arts 163–169.

An amendment effective 4 April 2026 also states that the listed administrative infringements are sanctionable when committed using artificial intelligence. The underlying infringement conditions still have to be established. It therefore matters whether the conduct meets the relevant industrial-secret misuse provision; the use of an AI tool alone does not complete the test. Decree published 3 April 2026, Art 386 second paragraph, XIV–XV and first transitional provision.

Mexico's industrial-property authority, IMPI, has targeted digital provisional-measure powers. Applications require the statutory proof, identification and security assessment, and the measure must satisfy the applicable proportionality conditions. The company should identify the account, material, infringement and ongoing harm before requesting a block, removal or cessation measure. A request to erase an entire provider system would need a basis far beyond proof of one unauthorised upload. LFPPI, Arts 344–353.

Oceania: a failed confidence claim may leave another route

Australia's New Aim v Leung, decided in April 2026, illustrates the importance of identifying the particular information. The Full Federal Court considered a selected group of supplier information and assessed its confidentiality despite imperfect controls and personal-phone storage. Such facts require evaluation in context. They do not establish a universal permission for personal AI accounts. 2026 FCAFC 49, paras 108–131.

The same judgment distinguishes a claim under section 183 of the Corporations Act. That provision addresses improper use of information obtained through a company role to gain an advantage or cause company detriment, and can reach information outside equitable confidentiality protection. Its conditions still require proof. The court established Leung's liability but remitted remedies and questions concerning the other companies; it did not find every recipient liable. Judgment, paras 148–170; Corporations Act, s183.

This gives an Australian company a reason to investigate the employee's purpose and benefit even where secrecy is contested. It must still identify the proper claimant, respondent, statutory connection and available remedy. A request for permanent non-use also needs care if information has entered the public domain. Maggbury v Hafele demonstrates the restraint issue where the owner published the information and sought an enduring contractual prohibition. 2001 HCA 70, paras 45, 49–59.

In New Zealand, Crown Finance v Crown Asia Pacific Group supports confidence obligations arising from a limited commercial purpose even without an express NDA. A compilation can retain confidential character although some components are public. Receipt, purpose and knowledge must be assessed for the actual defendant. Applied to an AI service, the provider's permitted processing and the customer's original purpose are central. 2024 NZCA 614, paras 77–95, 102–105.

New Zealand's section 230 offence requires specified taking, obtaining or copying of a document, model or other depiction containing or embodying a trade secret, or taking or obtaining a copy. It also requires knowledge of the secret, dishonesty, absence of a claim of right, and intent to obtain a pecuniary advantage or cause another person loss. Its requirement concerning all reasonable efforts belongs to section 230 of the Crimes Act. Civil confidence claims should be assessed under their own authorities. The incident file should therefore identify which route is proposed and the evidence each route requires. Crimes Act 1961, s230.

Protect reporting rights and ordinary employee skills

An investigation should distinguish routine unapproved analysis from a report of wrongdoing. The relevant protection depends on the subject, purpose, recipient and statutory conditions. A general confidentiality clause cannot override mandatory protection. At the same time, the employee's description of an upload as a report does not settle those conditions.

  • United States. Protection that changes the response: DTSA immunity covers specified confidential disclosures to a government official or attorney for reporting or investigating suspected illegality, and specified sealed filings; contract-notice rules affect certain employer recoveries. Practical consequence: Check purpose, channel and notice before threatening trade-secret liability. The immunity does not authorise otherwise unlawful access. 18 USC §1833(b).
  • Canada. Protection that changes the response: Criminal Code section 425.1 prohibits specified employer threats or retaliation aimed at preventing or punishing employee reports of believed offences to law-enforcement officials. Practical consequence: Check the subject, recipient and employer's purpose before discipline. Provincial employment protections also require their own triggers. Criminal Code, s425.1.
  • Quebec. Protection that changes the response: Civil Code Article 1472 recognises an overriding general-interest defence to trade-secret disclosure, including specified health or safety concerns. Practical consequence: Assess the asserted public interest alongside the confidentiality duty. Art 1472.
  • EU/Germany and Great Britain. Protection that changes the response: The EU framework and German statute preserve specified public-interest and worker-representative disclosures. GB agreements cannot exclude qualifying protected disclosures. Practical consequence: Test the relevant exception and reporting route. Keep Northern Ireland employment law separate from the GB framework. Directive Art 5; GeschGehG §5; ERA 1996, §§43A–43J.
  • South Africa and Kenya. Protection that changes the response: South Africa's Protected Disclosures Act protects qualifying routes and limits contractual exclusion. Kenya's Access to Information Act section 16 protects specified public-interest disclosures. Practical consequence: Establish eligibility, information, recipient and applicable conditions before discipline or demands for silence. South Africa, §§2–9, 2017 amendments; Kenya, §16.
  • Australia and New Zealand. Protection that changes the response: Australian corporate whistleblower protection has defined eligibility, subject and recipient conditions. New Zealand also addresses confidential advice about whether or how to make a protected disclosure. Practical consequence: Verify the particular route. AI-assisted preparation requires an assessment of confidentiality, purpose and recipient; neither protection nor exclusion follows from the tool's label. Corporations Act, Part 9.4AAA; NZ Act, §§9–11, 23–24.

The other jurisdictions require the same eligibility check against their own law. For example, Japan's Whistleblower Protection Act distinguishes protected recipients and conditions, while Saudi Arabia's protection law concerns its defined serious-crime and protected-person framework. A customer NDA or provider request should preserve any applicable mandatory route. Japan, Arts 2–5, 7; Saudi law, Arts 1, 5, 7, 17–18.

Keep a secrecy undertaking focused on protected information and prohibited uses. Employee mobility has separate limits: the DTSA restricts employment injunctions based merely on what a person knows; Ontario's statute prohibits covered non-competes subject to specified exceptions; Germany's cited judgment rejects the unlimited standard-form clause before it. These rules matter when management asks for a post-incident undertaking. 18 USC §1836(b)(3)(A); Ontario ESA, §§67.1–67.2; BAG 8 AZR 172/23, paras 30–42.

Post-upload response checklist

The following sequence is an operational application of the legal elements above. Ongoing exposure, evidence preservation and notice assessment often require parallel action. Contractual or statutory deadlines must be calculated from the actual applicable instrument and event.

  • Identify and preserve. Responsible actor and required record: Incident lead, information owner and authorised technical staff: restricted content schedule, prompt/output, upload time, account and logs. Condition and intended result: Capture relevant evidence promptly, including the original configuration. Limit access to people needed for the response.
  • Contain continuing exposure. Responsible actor and required record: Authorised account administrator: shared links, workspace invitations, connector grants and access history. Condition and intended result: Disable exposed routes and further unapproved uploads within lawful authority. Record each change.
  • Establish the permission chain. Responsible actor and required record: Legal and contract owners: customer NDA, employee instructions, licence, order form and historic provider terms. Condition and intended result: Determine who could approve each recipient and purpose. Separate the company's own material from customer-controlled material.
  • Obtain provider facts. Responsible actor and required record: The actual contracting party through the authorised provider channel: content identifiers, dates and a bounded factual request. Condition and intended result: Ask about actual access, training or other use, onward recipients, retention and available restrictions. A request alone creates no compulsory response power.
  • Seek enforceable containment. Responsible actor and required record: Contract owner and counsel: non-use, limited access, downstream restrictions, deletion and permitted-retention proposal. Condition and intended result: Invoke a contractual right or seek an agreed undertaking. Coordinate active-copy deletion with restricted evidence preservation and legal holds.
  • Assess notices. Responsible actor and required record: Customer relationship owner and counsel: exact notice clause, trigger facts and mandatory obligations. Condition and intended result: Give required notices through the prescribed route. Distinguish confirmed facts, open questions and further updates.
  • Evaluate urgent relief. Responsible actor and required record: The holder with standing and litigation counsel: respondent, forum, secret schedule, continuing threat, harm and proposed order. Condition and intended result: Use the applicable interim-relief test, security requirements and confidentiality procedure. Identify service and enforcement prospects against the particular actor.
  • Repair and document. Responsible actor and required record: Management, security, procurement and appropriate employee representatives: revised approvals, settings, training and control evidence. Condition and intended result: Implement an authorised workflow for future use. Keep historical evidence separate from the record of improvements.

Preservation can be legally significant once litigation is reasonably anticipated or underway. US Federal Rule of Civil Procedure 37(e), for example, addresses loss of electronically stored information that should have been preserved in that setting. Quebec's Civil Procedure Code also expressly addresses preservation of relevant evidence. Avoid indiscriminate erasure while seeking containment. Licentium's AI chat history, discovery, privilege and preservation analysis explains the separate retrieval and disclosure questions. FRCP 37(e); Quebec CPC, Art 20.

A useful provider request distinguishes the uploaded file, chat history, retrieval store, outputs, operational logs, backups and downstream recipients. Ask what can be removed, what must remain and under what restrictions. If training occurred, ask what the provider can establish about that processing and any proposed remediation. A deletion confirmation concerning stored content does not establish removal of model effects. The legal remedies examined here provide no general guarantee of technical unlearning.

For cross-border enforcement, record the employee's work location, place of upload, relevant processing and recipient locations, provider entity, customer connections, contractual law and forum, and reachable assets. These facts can point to different claims and courts. US section 1837 and Japan's Articles 19-2 and 19-3 contain particular extraterritorial rules. Each still requires its own statutory conditions; ordinary jurisdiction, service and enforcement questions remain. 18 USC §1837; Japan UCPA.

An urgent order should describe conduct the respondent can perform or stop. Restricting an identified share link, preventing a specified use, segregating retained material or delivering up defined files requires different evidence from a claim for all profits associated with a model. Preserve causation and value records for damages. A contractual right to request equitable relief still leaves the court's legal requirements to be satisfied.

Build a reasonable-measures evidence pack

The evidence pack should connect each secret to its protection and permitted use. It supports the express measures tests in the US, EU/Germany, Japan, UAE and Mexico, and the confidentiality, notice and purpose inquiries in the other systems discussed above. The same evidence can have different legal functions.

  • Information and rights schedule. What it helps establish: Specific secret, owner, lawful controller and standing. What a usable record contains: Content/version identifiers, provenance, assignments, licences and customer restrictions, with public elements identified.
  • Value and usefulness records. What it helps establish: Secrecy-derived advantage where required; business usefulness and loss. What a usable record contains: Development effort, pricing leverage, competitor advantage or other supported value; separate proof of causal loss.
  • Classification and access history. What it helps establish: Secret management, restricted circulation and notice. What a usable record contains: Dated classifications, access grants/removals, sharing and export controls, and actual recipient lists.
  • Approved-account and use records. What it helps establish: Permitted purposes and recipients; actual protective measures. What a usable record contains: Account identifiers, accepted terms, no-training or other use limits, exceptions, settings and change history.
  • Customer permissions. What it helps establish: Authority to use another party's confidential material. What a usable record contains: Permitted purpose, approved providers/subprocessors, required consents, conditions and relevant amendments.
  • Training and enforcement records. What it helps establish: Employee knowledge and practical implementation. What a usable record contains: Instructions delivered, acknowledgments, approval decisions, documented exceptions and follow-up.
  • Monitoring and retention basis. What it helps establish: Lawful evidence collection and reliable records. What a usable record contains: Applicable authority, required employee information or participation, scope, retention and preservation exceptions.
  • Incident and provider-response log. What it helps establish: Timing, recipient notice, continuing threat, causation and remedy. What a usable record contains: Evidence captures, containment actions, requests, actual confirmations and unresolved factual questions.

Monitoring needs a lawful local basis. Germany's works-council rules address certain technical employee-monitoring arrangements. Ontario's electronic-monitoring provision requires a written policy for covered employers and expressly concerns transparency; it does not supply unrestricted inspection powers. Restrict access to the evidence pack itself. BetrVG §87(1) no 6; Ontario ESA, §41.1.1.

Management should retain evidence that the controls actually operated. A policy, standard subscription or security certificate alone leaves questions about this information, this account and this disclosure. Licentium's AI Governance Compliance Stack provides the wider implementation context. The post-upload file should show the exact protective measures and the facts each measure helps prove.

Where source code or a model release is involved, keep the licensing inquiry alongside secrecy. Identify which components were lawfully public, which rights cover the release, and which customer or proprietary material remained restricted. Licentium's open-source AI licence analysis explains the separate permission chain for a model supplier. Public availability of one component does not itself establish permission to disclose the customer's remaining material.

Review the contracts after an upload

For a scoped contract review, assemble the customer NDA, employment or contractor terms, provider agreement and order form, relevant settings history, and a restricted description of the uploads. Identify the countries, contracting entities and continuing disclosure pathways. Those records allow the business to assess surviving protection, existing liability, immediate containment and the permissions required for future AI use.

Planning a launch somewhere new?

Prefer email? Write to hello@licentium.io. By sending, you accept our privacy policy.