> ## Documentation Index > Fetch the complete documentation index at: https://docs.upsolve.ai/llms.txt > Use this file to discover all available pages before exploring further. # Upsolve for Slack: data and privacy > What Upsolve for Slack collects, how it is used, how long it is kept, and how to have it deleted. This page describes the data the Upsolve for Slack app handles. It adds to Upsolve's [Privacy Policy](https://upsolve.ai/privacy-policy), which covers your use of Upsolve as a whole. ## What we collect **When an admin installs the app:** * The Slack workspace's ID and name (and Enterprise Grid ID, if any), and the bot's own Slack user ID. * The bot token Slack issues, **encrypted at rest**. It is never shown in Upsolve, returned by any API or written to logs. * The settings the admin chooses: whether the bot answers, the IDs of the channels it answers in, and whether it may answer in shared channels. * Which Upsolve user installed it. **When someone uses the bot:** * **The link between a Slack user and an Upsolve account**: the Slack user ID and the Upsolve account it was linked to. While a link is pending, we also keep the Slack user's display name, shown on the confirmation page. A pending link stops working after 15 minutes; its record is deleted when it is used, when the next link is requested, or when the app is disconnected. * **The questions people send the bot** (direct messages to it, and messages that @mention it) and **the answers**, saved in the asker's own Upsolve chat history, labelled Slack, as any conversation in Upsolve is. * **Slack message identifiers**, not content, needed to keep a thread working: the channel and thread a conversation belongs to, and the ID of the bot's latest footer message so the next answer can replace it. * **Slack event IDs**, to avoid answering a question twice. An ID older than a day is deleted as later events arrive. **When someone connects Slack as a tool for the agent** (optional, see [Upsolve for Slack](https://docs.upsolve.ai/slack/overview.md#optional-slack-as-a-tool-for-the-agent)): * Their Slack user token, **encrypted at rest**. * What the agent reads from Slack while answering (search results, a public conversation) is used to produce that answer and can appear in the conversation saved in their Upsolve chat history. It is not stored anywhere else. **What we receive but do not use or keep:** Slack sends some data with every event (for example the IDs of the people and channels involved, and enterprise information). Apart from what is listed above, Upsolve ignores it and does not store it. The bot reads only messages addressed to it: @mentions in the public or private channels an admin has turned on, and people's direct messages with the bot. It does not read other channel messages or anyone's other direct messages. ## How we use it * To answer questions asked in Slack, as the person who asked, under their own Upsolve permissions and row-level security. * To post the answer, charts and follow-up buttons in the right thread, and to let the conversation continue in Upsolve. * To show the conversation in the person's chat history in Upsolve, and to administrators of the Upsolve workspace in its Chat History, as with every Upsolve conversation. * To diagnose problems and keep the service secure. We do not sell this data, use it for advertising, or export Slack messages in bulk. ## AI processing Answers are produced by large language models. To answer a question, Upsolve sends the question, the conversation so far, the workspace's data model and the results of the queries the agent runs to the AI model provider your organization selects in **Project Settings → AI models**. * **Upsolve does not train AI models on your Slack data**, or on your data in Upsolve. * AI-generated answers can be inaccurate. Check important figures against the data behind the answer, which Upsolve shows in the conversation. ## How long we keep it | Data | Kept until | | - | - | | Installation, bot token, settings, account links, thread identifiers | The app is disconnected in Upsolve or removed from Slack. Both delete them, and disconnecting in Upsolve also revokes the token with Slack. | | Pending account links | Used, replaced by the next link request, or the app is disconnected. A link stops working after 15 minutes. | | Slack event IDs | Deleted once older than a day, as later events arrive. | | Questions and answers in Upsolve chat history | Kept like all Upsolve conversations: while your organization uses Upsolve, unless deleted on request. | | A Slack user token connected for the agent | Slack is disconnected in Upsolve. | Removing the app does not delete conversations already saved in Upsolve chat history. Ask us to, as described below. ## Access, export and deletion You can ask to access, correct, export or delete the personal data Upsolve holds about you, including your Slack conversations with the bot, by emailing **[support@upsolve.ai](mailto:support@upsolve.ai)**. We answer within the time the law that applies to you requires (for example, the GDPR or the CCPA). If your organization's administrator manages your Upsolve account, we may involve them to act on your request. ## Security Requests from Slack are verified with Slack's signing secret; the install flow uses a signed, expiring `state` value; tokens are encrypted at rest and only ever sent over HTTPS. More at the [Security Trust Center](https://trust.upsolve.ai). ## Contact Questions about this page or your data: **[support@upsolve.ai](mailto:support@upsolve.ai)**. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.