Skip to content
Support AIStart free

Privacy

What data we collect, store, and share.

Support AI is designed to help teams automate support workflows while keeping customer support data scoped to the right workspace. This page explains the main data categories in plain language.

Data we collect

  • Account data such as name, email address, role, organization membership, and verification state.
  • Workspace configuration such as widget settings, knowledge base documents, URLs, API keys, integration settings, and webhook endpoints.
  • Support interaction data such as chat sessions, messages, visitor email addresses when provided, escalation requests, CSAT scores, and audit events.
  • Operational data such as auth email delivery logs and billing-related subscription state.

How we use it

  • To authenticate users, verify email ownership, and enforce organization-scoped access controls.
  • To answer support questions, retrieve knowledge, route escalations, and power dashboard analytics.
  • To send transactional email such as verification, password reset, invite, billing, and notification messages.
  • To support billing, quota enforcement, troubleshooting, and auditability inside the product.

What we share

  • Support prompts and related context may be processed by configured AI/model providers when features require generation or retrieval workflows.
  • Authentication and application data are stored in core infrastructure services used to run the product.
  • Billing, email, and integration providers receive the minimum operational data needed for those workflows.
  • We do not describe selling customer data. Public claims should be read together with the Subprocessors page for provider-level detail.

What you can control today

  • Teams can export data from the dashboard and can bulk-delete stored conversation data from the Data & Privacy section.
  • Workspace owners and admins can configure a retention setting in the dashboard today.
  • Automatic scheduled deletion tied to the retention setting is not described as live on this site because the current product does not clearly enforce that policy automatically.