Does ChatGPT, Claude or Gemini Use Your Data for Training?
ChatGPT, Claude, and Gemini all train on consumer data by default — here's what each actually does, and how to opt out.

It's a fair question, and the honest answer isn't a simple yes or no — it depends heavily on which account tier you're using, not just which company built the product. All three of the major AI assistants have converged on a broadly similar structure in 2026: consumer accounts may use your conversations to help train future models, generally through a setting you can control, while business, enterprise, and API-level access typically exclude your data from training by default, under separate commercial terms. The vendor matters less than most people assume. The tier you're actually on matters more.
The general pattern across all three
Before getting into vendor-specific detail, it's worth understanding why this consumer-versus-business split exists in the first place, because it's consistent enough across the industry to be the real headline here rather than a footnote. Consumer products are generally priced to be accessible, and the companies building them have historically treated real user conversations as one of the more valuable sources of feedback for improving a model's usefulness over time. Business, enterprise, and API tiers are priced differently, come with contractual data protection commitments, and are built around a different premise entirely — that a company using AI for real work needs a guarantee its data won't end up shaping a future model, not just a toggle it has to remember to check.
That structural split means the most useful question to ask about any AI tool generally isn't "does this company train on data" — it's "does the specific account tier and product I'm using train on data, and did I set it the way I want." The answers below reflect the general policies each of the three has published, though it's worth checking each provider's current settings directly, since exactly this kind of policy has changed more than once across all three platforms over the past year.
ChatGPT
OpenAI's consumer tiers — the free plan and ChatGPT Plus — have generally used conversations to help improve their models, with an opt-out available in settings rather than requiring an opt-in choice. A Temporary Chat mode exists specifically for conversations you don't want factored into that process; conversations run in that mode aren't used for training, though they're still retained briefly for safety and abuse-monitoring purposes before deletion. Business-tier and above — Team, Enterprise, and API access — generally exclude customer data from training by default, under separate commercial terms with stronger contractual protections than the standard consumer agreement provides.
Claude
Anthropic's approach shifted meaningfully as of late 2025. Consumer accounts — Claude Free, Pro, and Max, including Claude Code used from those accounts — now include a setting, generally labeled something like "help improve Claude," that determines whether your conversations can be used for model training; when that setting is enabled, data retention extends considerably longer than it does when it's off. Anthropic has been explicit that this change applies only to consumer plans, not to Enterprise, Team, API access, or usage through Amazon Bedrock or Google Cloud Vertex AI, all of which operate under separate commercial terms that exclude customer data from training. An Incognito chat mode, similar in spirit to ChatGPT's Temporary Chat, is also excluded from training, with a short retention window kept for safety purposes.
Gemini
Google's pattern follows the same general shape. Standard consumer use of Gemini, tied to a personal Google account with activity tracking enabled, has historically fed into model improvement, with an opt-out available through the account's activity settings. A temporary or incognito-style chat mode again exists specifically to exclude a given conversation from that process. Google's enterprise offering, delivered through Google Workspace rather than a personal consumer account, comes with contractual data protection guarantees that the standard consumer tier does not include — the same consumer-versus-business split showing up under Google's branding as it does with the other two.
Why "did I opt out" isn't the whole story
Even with training turned off, it's worth understanding that opting out of training and having your data fully forgotten aren't the same thing. All three providers generally retain conversation logs for some period regardless of the training setting, often justified by abuse monitoring, safety review, and legal compliance requirements — a window that can run anywhere from a few days on the short end to considerably longer, particularly for content flagged during safety review. Turning off the training toggle stops your conversations from being used to shape a future model. It doesn't necessarily mean the conversation is deleted immediately, and it's a different setting entirely from questions about legal discoverability, government data requests, or whether the content might be reviewed by a human as part of ordinary safety processes.
This distinction matters more for anyone using AI professionally than the training question alone. A prompt containing a client's confidential information, sent through a personal consumer account, is generally sitting on a provider's servers for some period regardless of whether the training toggle happens to be off — a meaningfully different risk profile than the same prompt sent through an account with a genuine zero-data-retention or enterprise-grade data processing agreement in place. For anyone handling sensitive business information through AI regularly, the training toggle is worth getting right, but it's really only the first of several settings worth understanding, not the whole picture.
What this actually means in practice
The practical takeaway across all three platforms is consistent enough to state plainly: for personal, low-stakes use, checking your privacy settings and turning off training if you'd prefer your conversations not be used that way is a reasonable, sufficient step. For genuinely sensitive or client-facing professional work, the consumer tier of any of these three tools — regardless of which training toggle you've set — generally isn't the level of data protection that kind of work actually warrants. That's a business-tier or API-level decision, not a settings-menu decision, and it's worth treating the two as genuinely different questions rather than assuming a training opt-out alone covers everything a professional use case actually needs.
Where Kahlo fits into this
This is precisely the layer Kahlo's architecture is built around for anyone using more than one of these models for real work. Rather than three separate consumer accounts, each with its own training toggle to check and its own retention policy to track, Kahlo talks to providers over their APIs — the same access tier that generally excludes data from training across all three companies by default, rather than the consumer tier where that protection depends on remembering to flip a setting correctly. Each provider only receives the prompt and context actually needed to answer a given request, and your account identity stays with Kahlo rather than being passed along to Anthropic, OpenAI, or Google individually.
For businesses that want to go further, Pro and Max plans let you bring your own provider keys and pay providers directly under whatever data processing agreement you've separately negotiated with them, while memory, projects, and every other feature continue working the same way. The practical effect is that the training question this article walks through — checking a separate toggle on three separate consumer accounts and hoping nothing resets after the next policy update — isn't something you have to manage individually across three different platforms in the first place.