Customer data not used for training clause checklist
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.
Who it is for
Legal, privacy, security, sales, and founder teams reviewing a customer-facing AI model training statement.
Template
Clause review checklist with 5 starter rows.
Download formats
Markdown for docs, CSV for spreadsheet review.
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.
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.
Clause review checklist
Use these rows as a starting point, then replace the example language with your vendor, source, customer data, and owner details.
- Question
- Which product does the clause cover?
- Current answer
- API, enterprise workspace, consumer account, cloud-hosted model, or internal tool.
- Review action
- Name the product path inside the clause or evidence note.
- Evidence
- Vendor profile and product-specific source.
- Question
- What data is covered?
- Current answer
- Prompts, outputs, files, fine-tuning data, feedback, embeddings, and logs.
- Review action
- Remove data categories that are not in scope or add a qualifier.
- Evidence
- Data-flow inventory.
- Question
- What settings or contracts change the answer?
- Current answer
- Opt-in, opt-out, enterprise setting, zero retention, order form, or negotiated addendum.
- Review action
- Attach configuration or contract evidence.
- Evidence
- Admin screenshot or agreement note.
- Question
- Does feedback or fine-tuning apply?
- Current answer
- Record whether users send feedback or upload training examples.
- Review action
- Review separately from ordinary prompt processing.
- Evidence
- Product owner note and vendor source.
- Question
- How should the clause be worded?
- Current answer
- Use a narrow statement with product scope and review date.
- Review action
- Send wording changes to legal or privacy review.
- Evidence
- Approved clause text.
| 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. |
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.
AI Vendor Packet organizes review packet evidence and review workflow support. This template is not legal advice.
Related vendor pages
Use these vendor pages to fill in vendor-specific rows before sharing the template with customers or auditors.
Related templates
These templates pair well when the review leads to a customer-facing update, evidence packet, or internal decision.
Turn this template into a review packet.
Select your vendors, customer commitments, and data categories. AI Vendor Packet turns official-source checks into a review packet your team can keep as evidence.