Clear data practices and deliberate access
Understand how to organize access to customer conversations and what to review when connecting a channel, integration or AI agent to your workspace.
Workspace access
Use an individual account for each teammate and review roles, teams and inbox membership. Grant the access needed for the job and remove access when it is no longer required.
- Review members and administrative permissions regularly.
- Use private notes for internal collaboration.
- Protect API tokens and integration credentials; keep them out of browser code and messages.
Data used by the service
Data can include account and contact details, messages, attachments and operational logs, depending on your connected channels and configuration. It supports the conversations, integrations and capabilities you choose.
Web and service connections use HTTPS. Hosting, retention, backup and operational access details are reviewed within the service scope and customer agreement.
AI and connected systems
Define the knowledge, data and actions an agent actually needs. Necessary data may pass to a channel, model or integration provider when used; review connected providers and settings before enabling a workflow.
- Keep unnecessary sensitive data out of knowledge sources.
- Test situations that require human handoff.
- Review run logs and remove permissions the workflow does not need.
Data requests and incidents
For access, correction or deletion requests, contact us with the workspace and request type. Do not send passwords or access tokens. Identity, data scope and account responsibilities are reviewed before processing.
If you notice unexpected access, review workspace members and connections, then contact support with the issue and timing without disclosing secrets.
Questions before an enterprise agreement
Request written details of hosting location, retention, backup and recovery, processing providers, and exit and export procedures. These details depend on the agreed service scope.