Hubbl Slack App Privacy Disclosure

This Slack App Privacy Disclosure explains data handling specific to Hubbl for Slack. It supplements, and does not replace, the separate Hubbl Privacy Policy linked below.

What Hubbl processes for the Slack app

Hubbl processes the question and current org data needed to answer it in memory for that turn. It does not persist Slack message text, answers, channel names, topics or conversation titles.

Hubbl stores operational identifiers, fixed outcome labels, token and tool counters, latency, feedback and timestamps.

Conversation memory

A compact summary may be attached to Hubbl's own Slack reply as message metadata. It remains in Slack under the workspace's retention settings and is not copied into Hubbl's database.

Retention and security

Thread sessions are archived after 365 days without activity. 365 days after archival, Hubbl clears the thread's Hubbl user, installation, channel and thread identifiers, and the Slack message timestamps of its requests. Stored Hubbl credentials are deleted as soon as a login session ends, and the login session's Hubbl user identifier and the Slack message timestamps of its requests are cleared 365 days later.

Request records keep Hubbl user, account and org references, turn identifiers, outcomes, feedback, model, token and tool counts, latency and answer-quality scores to measure and improve answer quality. They do not store Slack message text or answer content.

Hubbl's Slack application logs contain fixed operational event descriptions and are retained without a fixed expiry. They may include a random turn ID for correlation, plus bounded operational diagnostics such as outcomes, durations, counts, model and tool names, reason codes, and redacted error details. Application log messages and structured fields do not include person, workspace, installation, account, org or session identifiers, raw Slack channel or thread coordinates, Slack message text or answer content, or model or tool payloads. The shared logger removes credential patterns and error response or body payloads.

Tokens are encrypted and rotated.

Access and deletion

Run /hubbl-logout to revoke and remove your stored Hubbl credentials and end the current Slack login session. Uninstalling immediately purges workspace user tokens and pending sign-ins and clears stored Slack credentials. 10 days after uninstall, Hubbl clears the workspace's Slack identifiers from its sessions and requests and deletes the installation record with its settings.

For a Slack app access or deletion request, contact Hubbl for Slack support.

Hubbl's company-wide policy

This disclosure covers only the Slack app. Read the separate Hubbl Privacy Policy for Hubbl's company-wide privacy practices.