OpenAI stores more from your ChatGPT conversations than most users realize, but less than the privacy horror stories claim. Here’s the unvarnished breakdown.
What OpenAI saves from every ChatGPT conversation
Every message lands on OpenAI’s servers: your prompts, the AI’s responses, file attachments, custom instructions, and metadata (model version, timestamp, account ID). All indexed to your account.
Storage and training rules by tier:
- Free tier, stored and used for training by default
- Plus, stored and used for training by default
- Teams + Enterprise, stored but not used for training by default. Workspace data isolation active
- Temporary chats, stored for 30 days (abuse monitoring), then deleted. Never used for training
Free and Plus users can disable training via Settings → Data Controls → Improve the model for everyone → toggle off. Your chats still save to history (so you can revisit them), but OpenAI won’t train models on them.
The critical distinction: stored vs. trained
Opting out of training doesn’t erase your conversation history. Past chats remain in your sidebar, living on OpenAI’s infrastructure, which matters if data sovereignty is a concern.
To remove conversations from OpenAI’s servers entirely: export what you need, then purge your history. Navigate to Settings → Data Controls → Manage → Delete all chats.
What ChatExport AI changes (and what it doesn’t)
ChatExport AI doesn’t alter what OpenAI stores server-side. Zero effect on their retention policies.
What it does change: you gain a local copy under your control. ChatExport AI creates portable files (PDF, Markdown, JSON, and 8 other formats) that live on your machine, not in a vendor’s cloud. Delete the original from ChatGPT? Your local archive persists.
ChatExport AI’s privacy footprint is minimal:
- Chat content never leaves your device, zero upload to ChatExport AI servers
- The only network request is optional Pro license validation (sends encrypted device fingerprint, never chat data)
- Complete security architecture documented here
Bottom line: OpenAI retains what they retain regardless. The export tool hands you a copy you own.
Privacy actions that actually move the needle
Ranked by real-world impact:
- Default to Temporary chats for sensitive topics. Auto-delete after 30 days, never enters training data
- Flip the training opt-out switch in Settings if you’re on Free or Plus. Single toggle, immediate effect
- Export then delete any conversation you’d lose sleep over in a breach. Defense in depth
- Never paste credentials into ChatGPT. API keys, passwords, third-party PII, the interface warns you for good reason
- Segregate sensitive work to a dedicated account. Some legal teams maintain separate paid accounts exclusively for privileged material
What barely matters:
- Custom Instructions, transmitted with every prompt. OpenAI sees them. Don’t embed secrets
- Browser incognito mode, hides chats from local browser history only. Server-side: no change
- VPN use, valuable for other threat models; won’t hide chat content from OpenAI
Privacy defaults across the AI platform landscape
- Claude (Anthropic), consumer chats not used for training by default. Enterprise workspace isolation comparable to OpenAI Teams
- Gemini (Google), training opt-out available in Settings. Workspace accounts get Google Workspace data isolation
- Microsoft Copilot, tier-dependent. M365 Copilot enterprise: no customer data training
- Perplexity, Grok, Poe, policies vary. Check each platform’s privacy documentation
The pattern holds: enterprise tiers typically default to no-training. Free consumer tiers usually train on your chats unless you opt out.
The essential takeaway
ChatGPT stores your conversations. You can block training but you can’t block storage. Export conversations that matter, delete the originals if necessary. Use Temporary chats for sensitive material. Never paste secrets.
Further reading
- /security, ChatExport AI’s complete privacy architecture
- /for-lawyers, maintaining attorney-client privilege with AI tools
- How to back up your entire ChatGPT history