Privacy and data ownership

Models process your requests in transit. They do not store them. Every model call routes through zero-retention providers, so a model sees a request, answers it, and forgets it. Nobody trains on your conversations, your files, or anything else you put into BetterBots.

Zero retention is a contractual guarantee from the model providers, enforced by our routing. It is a contractual property, not something we independently verify with cryptography at runtime, and we would rather say that plainly than overstate what a routing rule can guarantee on its own.

Everything else, your threads, your files, your skills, your memories, and your audit log, lives at rest on infrastructure the workspace owner controls. Switching which model an agent uses never means moving your data anywhere, because it never left in the first place.

The application stores, on the owner’s infrastructure:

• Messages: the content of every conversation between you and your teammates.
• Memories: short notes an agent saves about a conversation, so it can recall context later.
• Files: attachments you upload and artifacts an agent produces (documents, screenshots, generated files).
• Usage telemetry: which model handled a request, how long it took, and its exact cost, so spend and quality can be reviewed in the app’s own Usage and Activity pages.

Connection credentials (an MCP bearer token, a Google or Microsoft OAuth grant) are stored to let an agent use the tool you connected. They are never included in an export and never shown back to you once saved.

Export. A workspace owner can download a full export of that workspace’s agents, conversations, skills, routines, memories, and a list of connected tools (by name and kind only, never credentials), from the workspace’s own settings page.

Deletion. Anyone in a conversation can delete it, removing that conversation and every message, run, and approval inside it, permanently. A workspace owner can also delete an entire workspace’s conversations, memories, and files in one action from that workspace’s settings page, without deleting the workspace itself, its members, or its connections. Both actions require typing a confirmation phrase first, since neither can be undone.