> ## Documentation Index
> Fetch the complete documentation index at: https://docs.behaviq.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Data retention

> Understand conversation and audit log retention.

Enterprise workspaces can set conversation retention from the security policies page. By default, saved conversations do not expire automatically.

## Conversation retention

Admins can leave conversation retention as indefinite, or choose 30, 90, 180, or 365 days.

When a finite window is set, conversations become eligible for scheduled deletion from BehavIQ application storage after the conversation has been inactive for longer than that window. Choose the shortest period that still supports the organisation's operational and review needs.

Conversation retention covers the application records and stored message objects BehavIQ uses to show saved chat history. It does not automatically remove every provider-side record, abuse-monitoring record, security log, support record, backup, billing record, or audit record.

Retention settings do not replace a formal offboarding or erasure process. If a pilot or enterprise agreement requires final export, deletion, or certification after the workspace closes, handle that through the agreed offboarding process.

## Audit logs

Audit log views and exports are limited to the fixed audit window shown in the app. The current enterprise settings show a 365-day audit window.

Audit logs are separate from conversation retention because they support security review and administration.

## Knowledge base files

Knowledge base files remain available until an admin removes them or the workspace is otherwise changed.

Delete old or superseded files when they should no longer influence chat answers. Removing a file detaches or purges the provider file objects used by the knowledge-base feature, depending on the action selected in the product.

## Before deletion

If the organisation needs records before a finite retention window removes them, export them first from the relevant page.

Before ending a pilot, agree who will export required records, who will request deletion, which records must be retained for legal or security reasons, and who signs off that offboarding is complete.