Effective date: February 12, 2026
This Privacy Policy explains what data the Turbot Discord bot ("Turbot", "the Bot") collects, how it is used, and how it is stored.
When you @mention the Bot, the text of your message (with the mention stripped) is processed to generate a response. The Bot maintains a per-channel conversation history of the last 20 messages in memory to provide conversational context. This history is:
- Stored only in application memory (RAM)
- Lost when the Bot restarts
- Never written to disk or a database
- Never shared with third parties beyond what is described below
The Bot detects feature request intent during normal chat — no additional API call is made for intent detection. When a feature request is identified (either through natural language detection or an explicit prefix), the Bot creates a Discord thread for a collaborative planning conversation. During this process:
- Your request description and all follow-up messages in the thread are sent to the Anthropic Claude API for planning and code generation
- The conversation history for the thread is stored in application memory (RAM) for the duration of the session (up to 30 minutes of inactivity) and is lost on Bot restart
- The final feature description is included in git commit messages and pull request descriptions on GitHub
- Feature request activity is logged to the designated admin channel on Discord
The Bot processes the following Discord metadata during normal operation:
- Your Discord user ID and username (to check roles and attribute requests)
- Channel IDs (to route messages and maintain conversation history)
- Server/guild membership and role information (for permission checks)
This metadata is not stored persistently by the Bot.
The Bot relies on the following third-party services, each with their own privacy policies:
| Service | Purpose | Data Sent |
|---|---|---|
| Discord | Bot platform | Messages, user metadata (per Discord Privacy Policy) |
| Anthropic Claude API | AI responses, planning conversations, and code generation | Message text, conversation history, feature request thread messages |
| GitHub | Pull request creation, deploy webhooks | Feature request descriptions, generated code, commit messages |
We encourage you to review the privacy policies of these services.
- In-memory only: Conversation history is held in RAM and is not persisted to disk. It is cleared on every Bot restart.
- Plugin data: Plugins may store data in isolated JSON files under
data/<plugin_name>/. This data is local to the server hosting the Bot. - Admin logs: Feature request activity, errors, and deploy events are posted to a designated Discord admin channel.
- Conversation history: retained in memory only, cleared on restart
- Feature request thread sessions: retained in memory for up to 30 minutes of inactivity, cleared on restart
- Feature request descriptions: retained in GitHub PRs and git history indefinitely
- Admin log messages: retained in Discord per Discord's data retention policies
- Plugin data: retained until manually deleted or the plugin is removed
We do not sell or share your data with third parties beyond the services listed in Section 2, which are necessary for the Bot's core functionality.
- Webhook payloads are verified using HMAC-SHA256 signatures
- Plugin code is sandboxed and scanned for policy violations before execution
- API keys and secrets are stored in environment variables, not in source code
- The Bot operates with the minimum Discord permissions required for its functionality
Since the Bot does not maintain a persistent user database:
- Conversation history is automatically cleared on restart
- Feature request data in GitHub PRs can be managed through GitHub's tools
- Admin log messages in Discord can be managed by server administrators
Server administrators who self-host the Bot have full control over all data processed by their instance.
The Bot is not directed at children under 13. We do not knowingly collect data from children under 13. Use of the Bot is subject to Discord's age requirements.
We may update this Privacy Policy from time to time. Changes will be reflected by updating the effective date at the top of this document.
For questions about this Privacy Policy, open an issue on the project's GitHub repository.