Privacy policy
Last updated November 14, 2026
Community Manager is a Discord, Telegram and Slack bot and dashboard run by Aditya Umale, an individual based in India (“we”). This page says what it stores, who it shares it with, and how to delete it. Questions: aditya.umale17@gmail.com.
What we store
- When you sign in: with Google, your Google account ID, name, email and picture; with Discord, your Discord user ID, name, avatar and email, and the list of servers you're in (to show the ones you manage); with Telegram, your Telegram user ID and name; with Slack, your Slack user ID, name, email and workspace. Also a session cookie that keeps you signed in. We use no advertising cookies, and a visitor who isn't signed in gets no analytics cookie or identifier.
- Your team list: who can open each workspace in the dashboard, their role (admin or member), who invited them, and invite links not used yet (we keep only a scrambled copy of each link, and the email address it was sent to, if an admin emailed it). Everyone on a workspace's team sees the others' names, emails and sign-in methods. If you link a Discord, Slack or Telegram account, the bot treats your messages in that workspace's communities as the team's.
- From your Discord server: its name and channel names, and messages posted in the channels you pick for the bot to read, plus messages that @mention the bot anywhere in the server. For each message: the text, the author's Discord ID and name, the time, and a link to it. If you import history, the same for up to the last 30 days (at most 5,000 messages). The bot reads no other channels.
- From your Telegram group: its name, forum topic names and admins, and messages in the group or topics you pick, plus messages that mention the bot or reply to it. For each message: the text, the author's Telegram ID and name, and the time. Telegram doesn't let bots read earlier messages, so there is no history import. What you write to the bot in your private chat becomes facts it uses in answers.
- From your Slack workspace: its name and address, the names of its channels and people (to pick channels and your team), which people are owners or admins, and messages in the channels you pick, plus messages that mention the bot. For each message: the text, files attached to it (screenshots and text files, which the bot reads to understand bug reports), the author's Slack ID and name, and the time. What your team writes in #cm-approvals becomes facts the bot uses in answers. The bot's Slack token is stored encrypted. There is no history import.
- What you give us: the docs you paste or link (we fetch public pages from the link), the product summary, your settings, and the bot's name and logo.
- What the bot makes: its answers, the facts it learns from your team's messages, bug reports and requests, links to the issues created, approval cards, a log of actions taken in the dashboard, and how much AI it used each day.
- How the product is used: once you're signed in, which dashboard pages you open and which actions you take (for example, approving a card or adding docs), tied to your account ID and kept in your browser so it stays the same between visits. For each workspace, counts of what the bot did: questions answered, issues filed, replies delivered, and AI cost. For visitors who aren't signed in, page views and clicks on our public pages, without a cookie. Recordings of the screen are made only on our landing page, the sign-in page and the setup steps, with everything you type hidden. None of this includes message text, answers, facts, docs, names or email addresses, and nothing is recorded about individual community members.
- Issue trackers: if you connect Linear, GitHub, Jira, GitLab, Asana or ClickUp, the connection is held by Composio. We keep only its ID, never your password.
Who processes it
We share data only with the services needed to run the product, and only what each one needs:
- Anthropic (Claude) reads message text, doc excerpts and facts to sort messages, write answers and learn facts.
- OpenAI turns message text, docs and facts into search vectors (embeddings) so the bot can find the right doc section.
- Under their API terms, Anthropic and OpenAI don't use this data to train their models by default. They may keep it for a limited time for safety and abuse checks; see their policies.
- Composio and the tracker you connect (Linear, GitHub, Jira, GitLab, Asana or ClickUp) receive the issues the bot files or you approve: a title, a summary and short quotes from the reports, with links back to Discord, Telegram or Slack. To spot duplicates, the bot reads the titles and descriptions of up to 100 open issues in the team, repo, project or list you picked.
- Discord, Telegram and Slack carry the bot's messages and your sign-in. Google carries your sign-in if you use it. Our email provider delivers invite emails: the address, the inviter's name, the workspace's name and the link.
- PostHog (EU cloud, Frankfurt) stores the usage data described above under “How the product is used”, so we can see where setup fails and whether the bot is helping. It gets IDs, counts and page addresses with their IDs removed, never your community's messages.
- Hetzner hosts our servers and database in Helsinki, Finland (EU).
We don't sell data, show ads, or use your community's messages for anything other than running the bot for your server.
How long we keep it
- While the bot is in your server, we keep the data above so it can keep answering and following up on issues.
- Delete all data in the dashboard's Settings erases every message, answer, fact, feedback item and document for that server at once, including your members' names and IDs. It also erases the usage data PostHog holds about what the bot did in that workspace. Issues already filed in Linear or GitHub stay there; delete them in those tools.
- If you remove the bot from your server, we erase everything for that server 7 days later. Adding it back within those 7 days keeps your setup.
- Usage data is kept for up to 12 months and screen recordings for 30 days.
- To delete your sign-in account, email us and we'll do it within 30 days, including the usage data tied to it.
Your community members
If you add the bot, tell your community that messages in the channels it reads are processed as described here. Members can ask you, as the server owner, to delete their data, or email us. We'll remove a member's messages from any server on request.
Children
The product isn't meant for anyone under 13, or the minimum age for Discord where they live.
Changes
If we change how we use data, we'll update this page and its date, and tell server owners in the dashboard before a significant change takes effect.