This article tells you where HueChat keeps your conversations, contacts and files, and who is able to see them.
Encryption at rest for the managed database and object storage is provided by DigitalOcean. Channel credentials, OAuth tokens and two-factor secrets are additionally encrypted by HueChat with AES-256-GCM before they are stored.
Some data is processed by third parties because a feature needs it:
The full list, with the purpose and region of each provider, is on the Trust Center at trust.huechat.ai and in the subprocessors article.
Your team. Only people you add to your account can see it. Administrators can change settings and manage agents; agents work in the Team Inbox. Every account-scoped request is authorised against the signed-in user's account, and cross-account access is refused with a 403. PostgreSQL row-level security policies keyed on the account reinforce that boundary for conversations, messages, contacts, inboxes and billing tables.
Your integrations. API keys and MCP keys you create can read or write only the scopes you grant. The MCP server needs a separately approved key.
HueChat operations. A small operations team can reach production systems to run the service, investigate incidents and answer verified support requests. That access goes through a separate operator console protected by Cloudflare Zero Trust, an IP allowlist and a super-admin session, and administrator actions are logged. Production secrets are kept in 1Password and are never committed to source code.
No. HueChat has to read message content to route it, search it and let AI Agents answer. Instead, every connection is encrypted in transit with TLS and HSTS, access is isolated per account, and access is audited. If you need a stricter model for a specific use, email support@huechat.ai.