ChatIQ
ContactSolutionsDocsBlogDashboard
Sign inSign up
ContactSolutionsDocsBlogDashboard
Sign inSign up
ChatIQ

Build reliable AI chatbots powered by your team’s knowledge. Secure multi-tenant architecture, instant document ingestion, and guided analytics out of the box.

Product
How it worksFeaturesDemo
Resources
SolutionsBlogDocsContactDashboard
Legal & Preferences
Terms of ServicePrivacy PolicySecurityDPA
© 2026 ChatIQ. All rights reserved.Made with care in distributed workspaces worldwide.

Data Retention & Privacy Controls

How ChatIQ stores chat data, retention levels, and end-user privacy controls.

Data Retention & Privacy Controls

ChatIQ lets bot owners control how much conversation data is saved, and lets end users opt out on a per-session basis.

Retention Levels (Per Bot)

Retention is configured per bot:

  • Level 3 — Full content
    Stores full messages and attachments. Best for QA, exports, and analytics.
  • Level 2 — Intent only
    Stores topic/intent labels and minimal metadata. No message content.
  • Level 1 — Metadata only
    Stores timestamps and identifiers only. No message content.
  • Level 0 — No save
    No conversation storage at all.

Retention Duration (Optional)

For Level 3, you can set a retention duration in days.
New bots default to 90 days. If you clear the value, data is kept indefinitely.

Retention windows are enforced by scheduled cleanup that removes message content after the window expires while keeping minimal conversation metadata for analytics.

End‑User Privacy (Private Mode)

End users can opt out per session using private mode:

  • No content or intent is stored
  • The session does not create a conversation record
  • Analytics can still be recorded as minimal, non‑content events

Session Opt‑In (For Bookings)

If a bot is set to Level 0–2 and a booking requires saved data, the user is prompted to opt in for the current session. This allows the booking to proceed without changing the bot’s default retention level.

What Changes When Retention Is Lowered

  • Conversation history views and exports are limited or empty
  • Message previews and content-based features are disabled
  • Analytics still work using non‑content events

Need help choosing a policy? Contact support.