Trust Center
Data Handling Explained
A plain-language breakdown of what data is processed, where it goes, and how it is protected.
What data goes where
- Conversation content is processed to generate responses, analytics, and escalation context.
- Operational telemetry (latency, errors, routing events) is processed for reliability and incident response.
- Configured integrations (CRM/helpdesk) receive only mapped fields required for workflow handoff.
Model training exclusions
By default, customer conversation data is processed for runtime inference and service operations. Accounts can request exclusion from model-improvement workflows at tenant level.
- Model-improvement usage controls are applied at workspace policy level.
- Sensitive entities can be redacted before downstream model calls where policies are enabled.
- Training exclusion status is handled through trust and privacy support channels.
Tenant isolation model
- Logical tenant isolation separates conversation, configuration, and event data across workspaces.
- Role-based access controls and audit logs govern access to administrative and operational actions.
- Integration credentials are scoped by workspace and managed through encrypted secret storage.
Data residency options
Default processing regions are selected based on account configuration and availability requirements. Regional processing and retention policies can be aligned through enterprise agreements.
| Data class | Default handling | Enterprise option |
|---|---|---|
| Conversation transcripts | Standard region policy and retention schedule | Contractual region and retention alignment |
| Operational logs | Security and reliability retention controls | Extended retention or regional restrictions by agreement |
| Integration payloads | Sent to configured destination systems only | Additional field minimization and routing constraints |
Need a formal policy packet?
Contact our trust team for policy details, data-handling clarifications, or account-specific controls.