Skip to content

Retention and deletion

Understand record retention, request deletion, and manage copies held by other services.

Last reviewed
On this page

Current conversation retention

Conversation records and related information currently have no automatic expiry or configurable retention period.

Request access, correction, or deletion

An employee from your organization should contact Runs Agents directly to request access, correction, or deletion of stored chatbot data. Include your workspace address and enough information to identify the relevant records.

Knowledge sources and team accounts

Deleting a knowledge source removes its indexed website content. Removing a team account removes its portal access and personal notification subscriptions. Conversation records are managed separately through a deletion request.

Copies sent outside the workspace

Notification recipients and form destinations can hold their own copies. Deleting information from Runs Agents does not recall an email or delete the receiving website's records. The organization should include relevant receiving systems when handling a request.

Residency and AI retention

Where a workspace stores records is separate from how long it keeps them. A region choice does not impose an expiry. Likewise, an AI provider's zero-data-retention route does not delete the workspace transcript or eliminate technical metadata under provider policies.

See Data residency and Data collection, use, and access.