Commitment
Zero Conversational Retention
Your prompts, completions, and agent traces are not a Recursion dataset.
How it works today
Where conversational data goes today
When you talk to a hosted model, the conversation does not stay on your machine. The prompt, the files you attach, tool results, and often the full trace route through the provider's API, land in their logs, and sit in systems you cannot inspect.
Many providers train on conversations and IP by default, or retain them for “safety,” “quality,” or “abuse review.” Even when a no-train toggle exists, the data still left your device. You are trusting a policy page, not a perimeter.
Support tickets, code, payroll, and strategy docs become someone else's training mixture the moment you paste them into a chat window. That is the product: your context in exchange for tokens.
Data path — today
Chat leaves your device, hits a provider API, and is stored — often for training.
How Recursion does it
How Recursion treats conversational data
We retain no conversational data. Chats, prompts, and agent traces are not stored by Recursion for training, analytics, product improvement — or at all.
On Scout and local Courier, inference runs on a Mac you own. There is no Recursion inbox of your conversations because the packets never come to us. We cannot train on what we never receive.
While other providers treat your IP as a byproduct of serving the model, our policy is strict zero conversational retention — by architecture, not by a support ticket asking to be deleted.
Data path — Recursion
The conversation is inferred on your machine. Recursion never receives a copy to keep.
What we do not retain
- User prompts, completions, and multi-turn chat history from Scout or local Courier workloads.
- Agent traces, tool-call payloads, and attached files from those conversations.
- Conversational data for model training, evaluation datasets, or “product improvement.”
What this is not
- A promise that a model you download never saw public web text in its original training — we are talking about your conversations with us and on our stack.
- A claim about third-party sites you choose to paste into. If you use a hosted provider directly, their retention policy applies.
- A hosted logging product. If you self-host and enable your own logs, those logs are yours on your disk.