# NDA and AI Contractors: What to Put in the Contract Before Work Starts

> How to protect company data when working with an AI contractor: what to mandate in the contract, NDA, and code and automation rights.

- Author: Yaroslav Maxymovych (Founder & CEO, AI Advisory Board)
- Published: 2026-11-14
- Updated: 2026-11-16
- Source: https://aiadvisoryboard.me/blog/nda-ai-contractor-contract-clauses

You hire a contractor to build AI automation or integration, and a month later you discover the work was done on their account, your company data is still in their chat with the model, and the code belongs to them—not you. For a company owner, this isn’t just a technical mistake. It’s a loss of control over your business processes.

## TL;DR
- Your contract with an AI contractor must clearly state who owns the created code and automations.
- The NDA should cover not just data, but prompts, working logic, and business scenarios.
- Before work begins, fix which data can be shared with external models and which is forbidden.

## Why a Standard NDA Isn’t Enough for AI Projects

A standard NDA protects trade secrets, but it doesn’t address the specifics of working with artificial intelligence. A contractor can upload your commercial proposals or client list to a public model, and you won’t see it until that data shows up in responses to other users. Since the model “remembers” entered information, the leak risk is higher than with a regular file sent by email.

So the contract must state not only that data shouldn’t be disclosed, but also that it must not be uploaded to external AI services without written consent.

## What to Mandate in a Contract with an AI Contractor

### 1. Rights to Code and Created Automations

By default, the author of the software code is the person who wrote it. If the contract doesn’t say otherwise, the contractor remains the owner of the code, and you only get the right to use the result. This means you can’t hand the automation over to other developers or change it without the first executor’s permission.

The contract must explicitly state:

- code and all created automations transfer to your ownership after payment;
- you have the right to edit, move, and use them on your own tools;
- the contractor doesn’t keep copies of code and data after the project ends.

### 2. Limits on Using Company Data

Clearly list the data the contractor may process and the forbidden data. For example, payroll data, client passport details, or trade secrets should not end up in external models without separate agreement.

Add a provision that the contractor uses data only to execute the specific project—not to train their own models or create other products.

### 3. Where the Created Automations “Live”

Specify which accounts and tools the contractor must use to do the work. If the automation is created under their account in a service, you risk losing access to it after the contract is terminated. The contract should state that work is done on company accounts or with the ability to fully transfer administrator rights.

### 4. Liability for Data Leaks

Specify exactly which damages the contractor is liable for and to what extent. This could be compensation for losses, penalty sanctions, or liability capped at the contract amount. Without this clause, you could be left alone with the losses if company data ends up in the open.

## Checklist Before Signing the Contract

1. Is it clearly stated that code and automations belong to the company after payment?
2. Is the contractor forbidden from uploading company data to external AI models without consent?
3. Is it specified whose accounts the work is performed on?
4. Is there a clause on liability for data leaks and the compensation amount?
5. Is it stated what happens to data and code after the project ends?

> **Definition:** NDA — a non-disclosure agreement that obligates parties not to transfer confidential data to third parties.

> **Definition:** AI contractor — an external executor or agency that creates automations, integrations, or tools based on artificial intelligence under a contract.

## How to Verify the Contractor Is Complying

After work begins, require regular reports on what data was uploaded to which services. Ask them to show which accounts the automations were created on, and verify you have full administrator access. If the contractor refuses to provide access or says the code “stays with them,” that’s a signal to review the terms or find another executor.

> **How this works on our side:** Our corporate program ensures that code and created automations are company property, they run on the client’s tools, and there is no vendor lock-in. The program includes two groups of up to 20 employees each at one fixed price per company, with a result of at least 3 working automations on priority tasks with a money-back guarantee. The first step is a free 30-minute consultation-diagnostic where one real company task is analyzed. https://course.aiadvisoryboard.me/corporate?utm_source=blog&utm_medium=article_body&utm_campaign=corporate

## FAQ

### Do I need a separate NDA if there’s already a contract for work execution?

Yes, if the contract doesn’t contain sufficiently detailed confidentiality clauses. It’s better to have one document that clearly states which data is forbidden to transfer outside, and how the contractor should use it.

### Who owns the code if the contractor uses a ready-made template or their own code?

It depends on the contract. Usually, code created specifically for you becomes yours, while ready-made templates remain the contractor’s property. Spell this out separately to avoid disputes later.

### Can I forbid the contractor from using public AI models?

You can forbid uploading confidential company data to them. A total ban on using models is unrealistic, but restricting the entry of sensitive information is mandatory.

### What to do if the contractor has already uploaded our data to an external model?

Contact them in writing with a demand to delete the data and confirm it. Then review the contract for the data leak liability clause and consult a lawyer if the data contains personal or trade secrets.

## Conclusion

A contract with an AI contractor must protect not only your data but also your right to own the work result. Spell out code rights, limit data uploads to external models, and fix liability for their leak. Tomorrow, take one step: review your current contractor contracts and check whether they contain clauses on automation rights and data confidentiality. If not, schedule a free consultation-diagnostic to analyze one real task of your company.

---

When citing, link to https://aiadvisoryboard.me/blog/nda-ai-contractor-contract-clauses. More articles: https://aiadvisoryboard.me/blog
