You write a draft in an AI-powered editor, decide it’s not working, hit delete, and move on. The text disappears from your screen. But in most cases, it’s still sitting on a server somewhere—sometimes for weeks, sometimes indefinitely.
This isn’t a privacy scare piece. It’s a practical map of what actually happens to your writing when you use AI assistance, and what control you have over it.
What gets cached and why
AI writing assistants—whether standalone tools or features baked into editors—send your text to remote servers for processing. That’s how the model generates suggestions, rewrites, or completions. The question is what happens after.
Most tools cache your input for at least two reasons: model improvement and abuse monitoring. OpenAI’s API retains inputs for 30 days by default unless you’re on a zero-retention enterprise plan. Anthropic’s Claude keeps data for 90 days for trust and safety review, then deletes it unless you opt into training (which is off by default for API users). Google’s Gemini API stores prompts for up to 48 hours for abuse detection.
If you’re using a third-party tool that wraps one of these APIs—most AI writing assistants do—you’re subject to both the tool’s retention policy and the underlying model provider’s policy. A tool might delete your draft from its database immediately, but the API provider still has a copy for 30–90 days.
What “delete” actually means
Deleting a draft in your editor doesn’t usually trigger deletion on the backend. It removes the text from your view and maybe marks a database record as deleted, but the actual data often remains in backups, logs, or cached inference requests.
Notion AI, for example, keeps deleted content in version history for 30 days. Jasper retains your documents on their servers indefinitely unless you manually delete your account. Most tools don’t surface this clearly—you have to dig into privacy policies or support docs.
If you’re writing anything sensitive—client work, unpublished research, early-stage product positioning—treat “delete” as “hide from my dashboard,” not “erase from existence.”
How to minimize exposure
If retention matters for your use case, you have a few levers:
- Use API-direct tools with zero-retention agreements. If you’re calling OpenAI or Anthropic’s API directly (or via a tool that passes through your own API key), you can request zero data retention. OpenAI offers this for API users who fill out a form; Claude offers it by default for paid API tiers. You lose some abuse protection, but your prompts aren’t stored.
- Run local models. Tools like Ollama or LM Studio let you run open-weight models on your own hardware. Nothing leaves your machine. Performance lags behind frontier models, but for drafting or brainstorming, it’s often good enough.
- Check whether the tool stores text or just metadata. Some AI features—like grammar checkers or readability scores—process text without sending full documents. Grammarly, for instance, sends sentences in chunks, not entire drafts, and claims not to store user content for training. That’s a smaller surface area than tools that upload whole documents.
- Clear your account periodically. If you’re using a tool that keeps documents indefinitely, set a monthly reminder to delete old drafts. It’s manual, but it’s the only way to force removal in tools that don’t auto-expire content.
When it actually matters
For most solo operators writing blog posts or newsletters, cached drafts aren’t a real threat. The risk is low, and the convenience of AI assistance usually outweighs it.
But if you’re drafting anything that could create liability—unreleased product specs, client strategy memos, legal documents, or anything under NDA—you need to know where your text lives and for how long. A 90-day retention window means a deleted draft from April is still on a server in July.
The non-obvious move: use AI tools for generic scaffolding (outlines, headline variations, structural edits), then write the sensitive parts in a local text editor. You get the speed boost without the exposure.
One Two Three Send covers the tools and tactics solo operators actually use. If this kind of breakdown is useful, subscribe—we publish daily.
Heads up — some links in this article are affiliate links. If you sign up through them, we may earn a small commission at no extra cost to you. We only recommend tools we use ourselves.