Privacy Policy
Last updated: April 26, 2026
1. Introduction
Resolve ("we," "our," or "us") is a Slack-integrated knowledge management service operated by Adam Siegel. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use Resolve through our Slack application and web interface at app.resolveos.co.
By installing or using Resolve, you agree to the collection and use of information in accordance with this policy. If you do not agree with these terms, please do not install or use the service.
2. Information We Collect
2.1 Slack Workspace Data
When you install Resolve in your Slack workspace, we access and process:
- Messages and threads — content of messages posted in channels where Resolve is active, specifically to detect questions and track thread resolutions.
- Thread replies — reply content within watched threads to determine if a thread has been resolved.
- User identifiers — Slack user IDs and display names, used to attribute resolved threads and personalise the inbox experience.
- Channel identifiers — channel IDs and names, used to scope activity to the correct channels.
- Workspace identifiers — Slack team ID and workspace name, used to associate data with your organisation.
Resolve operates as a bot user and only reads messages in channels it has been added to. We do not read direct messages (DMs) between other users. We do read DMs sent directly to the Resolve bot, because that's how the bot's DM Q&A feature works — the bot needs to see your question in order to search for an answer. Replies in those DMs are stored only for the duration needed to generate the response and are not added to your knowledge base.
2.2 Account and Authentication Data
When you sign up for a Resolve account via our web interface, we collect:
- Email address
- Display name
- Hashed password (we never store plaintext passwords)
- Session tokens for authentication
2.3 Usage and Log Data
We automatically collect certain technical information, including:
- IP addresses and browser/device type (for security and fraud prevention)
- Pages visited within the web application and timestamps
- API request logs (retained for up to 30 days)
- Error logs for debugging purposes
3. How We Use Your Information
We use the information we collect to:
- Detect and watch questions — identify messages in Slack that appear to be questions and begin monitoring those threads.
- Detect resolutions — use AI to determine when a thread has been resolved and generate a summary of the resolution.
- Build your knowledge base — store resolved threads, their summaries, and semantic vector embeddings to enable future search and retrieval.
- Surface related answers — when a new question is posted, search your knowledge base for past resolved threads and suggest them in Slack.
- Answer DMs — when a user sends a direct message to the Resolve bot, search your knowledge base and reply with relevant past resolutions (or a link to the web inbox if no matches are found).
- Welcome new users — send a one-time welcome message the first time a user opens the Messages tab in the Resolve App Home.
- Bootstrap your knowledge base on install — page through the last 90 days of public-channel history (capped to the top 50 most-active channels and 1,000 question threads), run AI to identify resolved threads, and save them to your knowledge base so the bot can answer historical questions on day one. Same data is used to generate your free Knowledge Audit (top repeated questions, top decisions, hours/week wasted on duplicate Q&A) at app.resolveos.co/audit.
- Operate the web inbox — display your saved resolved threads and enable search at app.resolveos.co.
- Send Slack notifications — post resolution summary cards and related-thread suggestions as bot messages in Slack.
- Maintain security — detect and prevent abuse, fraud, or unauthorised access.
- Improve the service — aggregate, anonymised usage patterns to understand how the product is used and where to improve it.
We do not sell your data to third parties. We do not use your Slack message content for advertising purposes.
4. AI Processing
Resolve uses artificial intelligence to analyse Slack thread content. Specifically:
- Resolution detection — thread content is sent to OpenAI's API to determine whether a thread has reached a resolution. Only the thread messages are sent; no other workspace data is included.
- Summarisation — resolved thread content is sent to OpenAI's API to generate a concise summary of the question and its resolution.
- Semantic embeddings — thread content is converted into numerical vector embeddings via OpenAI's API and stored in our database to enable semantic (meaning-based) search across your knowledge base.
Data sent to OpenAI is governed by OpenAI's Privacy Policy. We use OpenAI's API under terms that prohibit OpenAI from training on API-submitted content by default.
5. Data Storage and Security
5.1 Where Your Data Is Stored
All data is stored in a PostgreSQL database hosted on Railway, a cloud infrastructure provider in the United States. Vector embeddings are stored in the same database using the pgvector extension.
5.2 Security Measures
We implement industry-standard security practices, including:
- TLS encryption for all data in transit
- Slack request signature verification on all inbound webhook events
- Encrypted session tokens via better-auth
- Environment-variable-based secret management (no secrets in source code)
- Least-privilege OAuth scopes — we request only the Slack permissions required for Resolve to function
No system is perfectly secure. In the event of a data breach that affects your personal information, we will notify affected users as required by applicable law.
5.3 Data Retention
- Resolved threads and embeddings — retained indefinitely while your workspace is connected, as they form the core of your knowledge base.
- Watched threads (unresolved) — retained for up to 90 days from the last activity; deleted if no resolution is detected.
- API and request logs — retained for 30 days.
- Account data — retained until you delete your account.
When a workspace disconnects Resolve (revokes OAuth access), we stop processing new data immediately. Existing stored data is deleted within 30 days of disconnection upon request.
6. Slack OAuth Scopes
Resolve requests the following Slack OAuth permission scopes and uses them as described:
| Scope | Purpose |
|---|---|
| channels:history | Read messages in public channels to detect questions and resolutions |
| channels:read | List channels to display workspace context |
| channels:join | Join channels where Resolve is invited |
| groups:history | Read messages in private channels where Resolve has been added |
| groups:read | List private channels Resolve belongs to |
| chat:write | Post resolution summary cards and related-thread suggestions |
| users:read | Retrieve user display names for attribution |
| users:read.email | Retrieve user email addresses for account linking |
| im:history | Read direct messages sent to the Resolve bot so it can answer questions in DMs |
| im:write | Send the welcome message when a user first opens the Messages tab in App Home, and post DM replies |
7. Third-Party Services
Resolve relies on the following third-party services:
- Slack — the platform we integrate with. Slack Privacy Policy
- OpenAI — AI provider for resolution detection, summarisation, and embeddings. OpenAI Privacy Policy
- Railway — cloud hosting and database infrastructure. Railway Privacy Policy
We do not share your data with any other third parties except as required by law.
8. Your Rights and Choices
8.1 Access and Portability
You may request a copy of the personal data we hold about you by contacting us at support@resolveos.co. We will respond within 30 days.
8.2 Deletion
You may request deletion of your account and associated data at any time by contacting us. Workspace admins may disconnect Resolve from their Slack workspace at any time via the Slack App Management settings, which stops all further data collection. Data stored prior to disconnection will be deleted within 30 days upon written request.
8.3 Correction
If you believe any information we hold about you is inaccurate, please contact us and we will correct it promptly.
8.4 Objection and Restriction
You may object to or request restriction of our processing of your personal data. Where processing is based on legitimate interests, we will cease processing unless we have compelling grounds to continue.
8.5 Opting Out of AI Processing
If you do not wish your Slack messages to be processed by AI, you may remove Resolve from your workspace or remove it from specific channels. Contact us if you need assistance.
9. Children's Privacy
Resolve is not directed at children under the age of 16. We do not knowingly collect personal information from children under 16. If you believe we have inadvertently collected information from a child under 16, please contact us and we will delete it promptly.
10. International Data Transfers
Our infrastructure is located in the United States. If you are accessing Resolve from outside the United States, your information may be transferred to and processed in the United States, where data protection laws may differ from those in your jurisdiction. By using Resolve, you consent to this transfer.
For users in the European Economic Area (EEA) or United Kingdom, we rely on your consent and our legitimate interests as the legal basis for processing your personal data.
11. California Privacy Rights (CCPA)
If you are a California resident, you have the right to know what personal information we collect, to request deletion of your personal information, and to opt out of any sale of personal information. We do not sell personal information. To exercise your rights, contact us at support@resolveos.co.
12. Changes to This Policy
We may update this Privacy Policy from time to time. We will notify you of material changes by posting the new policy on this page with an updated "Last updated" date. For significant changes, we will also notify workspace administrators via email or Slack.
Your continued use of Resolve after any changes constitutes your acceptance of the updated Privacy Policy.
13. Contact Us
If you have any questions, concerns, or requests regarding this Privacy Policy or our data practices, please contact us: