Skip to main content

Privacy · Policy guide

Do AI Chatbots Use Your Conversations for Training? How to Check

There is no single answer for every chatbot. Check the product tier, data controls, feedback behavior, provider chain, retention, and policy date.

By SayAll Editorial Team
Reviewed by SayAll Product TeamPublished Last reviewed

The short answer

It depends on the product and setting

AI chatbots may use conversations for model training or improvement, but the rule varies by provider, consumer or business tier, account control, temporary-chat mode, feedback choice, and model provider. Check the current policy and settings for the exact service; never infer “no training” from “private,” “no sign-up,” or “history off.”

This guide explains how to inspect published controls. It is not a guarantee about any service beyond its current documentation, and policies can change after the review date shown above.

The useful question is not only “Does this company train on chats?” Ask: “Which product am I using, what is the default, can I change it, does feedback create an exception, which provider receives the prompt, and what storage remains for non-training purposes?”

Training is not the same as storage or human review

Common data purposes that should be checked separately
PurposeQuestion to ask
Model training or improvementCan the content change future model behavior, and is participation default, opt-in, or opt-out?
Service deliveryHow long is the prompt processed or retained to generate, stream, retry, or recover a response?
Safety and abuse preventionCan automated systems or people review content, and under what triggers?
Visible historyWhere is the conversation stored so the user can reopen it?
FeedbackDoes submitting a rating attach the conversation to a separate review or improvement process?

A statement such as “we do not train on your content” addresses one purpose. It does not by itself establish zero retention, no logging, no safety review, or no provider processing. Conversely, a short operational retention period does not necessarily mean content is used for training.

Five things to check before you share a sensitive prompt

  1. Product tierConsumer chat, business workspace, enterprise service, developer API, and third-party app may have different defaults.
  2. Account controlLook for settings labeled model improvement, activity, training, history, or data controls. Record the selected state and date.
  3. Temporary modeCheck what it changes—training, visible history, retention, or all three—and note any safety-retention exception.
  4. Feedback exceptionRead the notice attached to ratings, reports, shared links, or support tickets before including a sensitive conversation.
  5. Provider chainA third-party app or router can have its own policy while sending the prompt to a separate model provider with additional controls.

After those five, check deletion, backups, legal or security exceptions, regional differences, and whether human review is described. Save the URL and update date, not only a paraphrase.

Why product, tier, and setting change the answer

As of the review date for this article, OpenAI documents consumer data controls that can exclude new chats from model improvement and describes Temporary Chat separately. Anthropic publishes different explanations for consumer use and commercial products. Google’s Gemini privacy hub describes how its activity controls affect storage and model improvement. These are provider-specific policies, not universal rules.

The details can change and may include exceptions. A consumer account setting should not be assumed to govern an API integration. A business default should not be assumed for a free personal account. A temporary mode may still retain content for a stated safety period. Feedback can also be treated separately.

How to evaluate SayAll's provider chain

SayAll sends prompts through its backend and OpenRouter to a selected model provider for response generation. SayAll does not write chat content to its database as server-side conversation history; the reopenable history remains in the current browser. Those facts do not make inference local and do not remove the need to consider provider processing.

OpenRouter’s privacy policy states that OpenRouter does not train on user inputs or outputs, while also explaining that requests are routed to model providers. Provider behavior can differ. The current SayAll Privacy Policy, OpenRouter policy, and relevant provider controls should therefore be read together.

Whatever service you choose, minimize first. Remove names, credentials, exact locations, private third-party messages, and other details the answer does not need. “Not used for training” is useful, but sharing less remains the most portable privacy control.

Turn a privacy policy into a checklist

Bring the current policy text or settings description. Ask what it says, what it does not say, and which date and product tier apply.

Need a place to start?

Questions about this topic

Sources and references

  1. Data Controls FAQOpenAI
  2. How do you use personal data in model training?Anthropic
  3. Gemini Apps Privacy HubGoogle
  4. Privacy PolicyOpenRouter

How this guide is maintained

The SayAll Product Team reviews product-specific statements against the current application and dates the latest check. Category guidance is educational rather than a promise that every model response will behave in a particular way.

Found an error or a product fact that changed? Email support@sayall.ai.

Related SayAll guides

Privacy foundationsAI Chat Privacy

Understand local history, cloud processing, pseudonymity, and provider roles.

ArchitectureLocal AI vs Cloud AI

Compare on-device inference with remote processing and hybrid designs.

Authoritative policySayAll Privacy Policy

Read SayAll's current product-specific privacy commitments.

From reading to conversation.

Explore the idea in your own words.

Try for free