# Customer data not used for training clause checklist

Last reviewed: 2026-05-21

AI Vendor Packet organizes review evidence and workflow support. This template is not legal advice.

## Who this is for

Legal, privacy, security, sales, and founder teams reviewing a customer-facing AI model training statement.

## What this template is for

Use this checklist before saying customer data is not used for model training. The answer must match the vendor, product, plan, settings, and any feedback or fine-tuning flow.

## When to use it

- Before signing an AI addendum or answering an enterprise AI questionnaire.
- Before publishing a Trust Center AI data-use statement.
- After changing AI vendors, plans, or model provider routes.

## Clause review checklist

| Question | Current answer | Review action | Evidence |
| --- | --- | --- | --- |
| Which product does the clause cover? | API, enterprise workspace, consumer account, cloud-hosted model, or internal tool. | Name the product path inside the clause or evidence note. | Vendor profile and product-specific source. |
| What data is covered? | Prompts, outputs, files, fine-tuning data, feedback, embeddings, and logs. | Remove data categories that are not in scope or add a qualifier. | Data-flow inventory. |
| What settings or contracts change the answer? | Opt-in, opt-out, enterprise setting, zero retention, order form, or negotiated addendum. | Attach configuration or contract evidence. | Admin screenshot or agreement note. |
| Does feedback or fine-tuning apply? | Record whether users send feedback or upload training examples. | Review separately from ordinary prompt processing. | Product owner note and vendor source. |
| How should the clause be worded? | Use a narrow statement with product scope and review date. | Send wording changes to legal or privacy review. | Approved clause text. |

## How to fill it out

- Treat model training as product-specific.
- Mention scope and exclusions in the evidence note.
- Keep proof of admin settings or agreement terms with the source link.

## Common mistakes

- Writing a universal clause that covers unmanaged employee accounts.
- Ignoring feedback, fine-tuning, or product analytics paths.
- Using a vendor blog post instead of the current official policy source.

## Example clause evidence

For production support summarization, customer ticket excerpts are sent through Azure OpenAI under the Microsoft cloud agreement. Direct OpenAI API and employee ChatGPT accounts are excluded from this clause.

## Generate this automatically

Use the AI Vendor Packet scanner to generate this template from selected vendors, customer data categories, and customer-facing commitments.