Part 1: disable training on your data in the major cloud chatbots. Part 2: which tool for which job and effort level. Verified July 2026.
It is not retroactive. Data already baked into a trained model stays there. Some providers accept deletion requests for stored copies, none retrain models.
It is not zero retention. Providers still store chats for service operation, abuse detection and legal compliance, typically 30 days to 18 months.
It does not cover human review for safety. Flagged conversations can still be read by trust & safety teams at most providers.
The real rule: for genuinely confidential material, an opt-out toggle is not the control. Use an enterprise plan with contractual no-training terms, the API, or a local model.
| Use case | Effort | Best tool | Why |
|---|---|---|---|
| Quick factual question, definition, translation | Low | Any free chatbot; fast models (GPT-5 mini class, Gemini Flash, Claude Haiku) | Speed beats depth. The cheapest model that answers correctly wins; don't burn premium quota here. |
| Current events, fact-checking, sourced research | Low | Perplexity; ChatGPT Search; Gemini with grounding | You need citations and fresh data, not model brilliance. Perplexity's source-first layout makes verification fastest. |
| Drafting emails, posts, summaries | Low | ChatGPT or Claude; Copilot if you live in Outlook/Word | Claude tends to produce more natural long-form prose; Copilot wins when the draft must land inside Microsoft 365. |
| Serious writing: articles, reports, arguments with structure | Medium | Claude (Sonnet/Opus class); GPT-5 class as second opinion | Iterating on tone and logic pays off. Use one model to draft, another to critique - disagreement between models exposes weak spots. |
| Deep research with report output | Medium | Deep Research modes (OpenAI, Gemini, Perplexity); Claude research | Agentic research runs 5-30 minutes and returns a cited report. Worth it when the answer drives a decision; overkill for lookups. |
| Working with long documents, PDFs, contracts | Medium | Claude or Gemini (largest usable context windows); NotebookLM for a fixed corpus | NotebookLM answers only from your uploaded sources - the right constraint for document Q&A. Gemini handles very large files well. |
| Data analysis, spreadsheets, charts | Medium | ChatGPT (code interpreter); Claude analysis / Cowork; Gemini in Sheets | Insist on tools that run actual code on your data. A model estimating numbers in its head is a liability. |
| Quick code snippets, debugging, regex | Low | Any frontier chatbot; inline IDE assistants (GitHub Copilot) | Paste error, get fix. Inline completion is faster than chat for small edits. |
| Real software projects, multi-file coding | High | Agentic coding tools: Claude Code, Cursor, Codex-class agents | Agents that read the repo, run tests and iterate outperform copy-paste chat by a wide margin. Setup cost pays back within a day. |
| Image generation and editing | Low | GPT image tools; Gemini (Nano Banana class); Midjourney for art direction | Chatbot-integrated generators win on convenience and text rendering; Midjourney still leads on aesthetic control. |
| Meetings, email triage, calendar workflows | Medium | Copilot (M365) or Gemini (Workspace) - whichever suite you already use | Integration beats model quality here. The assistant inside your mail client sees context no external chatbot has. |
| Recurring automated workflows | High | Agent platforms (Claude Cowork/agents, custom GPTs), Make/n8n/Zapier with LLM steps | If you do it weekly, stop prompting manually. One-time build, recurring payoff - the highest ROI category on this list. |
| Confidential or client data | High | Enterprise plans with no-training contracts; API; local models (Ollama, LM Studio) | Consumer opt-out toggles are not a compliance control. Contractual terms or local execution are. |
Effort should follow stakes, not curiosity. A decision worth 10'000 CHF deserves a deep-research run and a second model as devil's advocate. A lunch recommendation does not.
Verifiability beats eloquence. When being wrong is costly, prefer the tool that shows sources or runs code over the one that writes most convincingly.
Ecosystem beats benchmarks. For daily work, the model inside your existing tools (Workspace, M365, your IDE) usually delivers more value than a marginally smarter model in a separate tab.
Two models, one hard question. For anything important, ask two different frontier models and compare. Divergence tells you where the uncertainty is.