KNOW YOUR WORKSPACE
Data and privacy.
This page explains the information used by the Halo application and its optional integrations. Your workspace administrator manages your team’s account and communication practices.
Information in your workspace
Halo stores account names and email addresses, workspace membership, permissions, connected Twilio account details, phone numbers, contacts, SMS content and delivery status, call history and workspace activity. It uses this information to provide your team’s calls, messages and account management.
Workspace access
Customer workspaces are separate. Administrators manage the people and number access in their own workspace. Operators use their assigned numbers. Platform administration exposes workspace status and basic counts; it does not provide a view into other customers’ message content or Twilio credentials.
Communication providers
Twilio processes calls and SMS using the account connected by your workspace. If Brevo is configured, it sends account email such as verification and password recovery. If Amazon Bedrock is configured and an AI feature is used, prompts and relevant message or speech context are sent to that provider to generate a response. Provider services have their own terms and data practices.
AI and automation choices
Manually generated AI drafts are reviewed before sending. SMS and voice automations are separate choices controlled by your workspace administrator and start disabled. Avoid including information you do not want an AI provider to process. Generated content can be inaccurate and should be reviewed when a person uses it.
Application storage and security
Twilio credentials are encrypted on the Halo server. The browser uses a secure session cookie on the live HTTPS site; private API responses and conversations are not cached by the service worker. The installation keeps database backups on its persistent server storage. The installation owner manages retention, backups and requests concerning stored records.
Getting help with your data
Contact your workspace administrator for account access, communication practices and requests involving your information. Your administrator can contact the installation owner for server-level data and backup handling. Do not send passwords or provider keys through public messages.