Privacy notice

Alts assistants · Development draft · Updated 5 October 2026

This notice describes the current development pilot of Alts assistants, including Ace. It will be updated before broader client deployment as hosting, service providers and retention arrangements are finalized.

What we receive

When you interact with an installed assistant, we may receive message text, user and organization identifiers, conversation or channel identifiers, timestamps, and message metadata needed to respond. Depending on the platform and installation permissions, this can include direct messages, mentions and related thread messages. Platforms may deliver additional events; receipt of an event does not mean the assistant replies to it.

How we use information

We use this information to answer requests, maintain conversation context, route replies to the correct organization and conversation, prevent duplicate processing, troubleshoot the pilot and manage authorized access. Your organization controls installation and available permissions. Replies in a group, channel or thread are visible to the participants who can access that conversation.

Development review and service providers

Authorized developers may review messages and prepare replies manually during testing. Message content may be used in developer assistance tools, including OpenAI tools, to prepare or troubleshoot responses. The pilot currently has no automatic model API connection. If an organization later enables a model provider, relevant requests and context will be processed by that provider under the applicable configuration and terms. Messaging platforms also process information under their own policies.

Storage and retention

The development application stores captured messages and reply records in its local working environment. Some conversation context is held in memory. There is currently no automatic deletion schedule; stored development records remain until removed. Retention periods, production hosting locations and organization-specific arrangements must be established before broader deployment.

Your choices and requests

Avoid sending passwords, payment details or sensitive personal information during testing. You can stop interacting with the assistant and ask your organization administrator to remove it or change its access. For questions or requests to access, correct or delete pilot information, contact the Alts representative who arranged your pilot, directly or through your organization administrator. Deleting application records does not automatically delete copies held by the messaging platform or other service providers.

Security and changes

Access is intended for authorized pilot participants and developers. This development version is still being tested; do not use it for information requiring production security assurances. We will update this notice as the service changes. A legal operator identity and dedicated privacy contact will be added before broader deployment.