This policy covers the Nozie Discord bot specifically — what it collects from a Discord
server, why, and how to make it stop. It supplements our
main Privacy Policy, which continues to apply to your Nozie account, dashboard,
and the nozie agent. Where the two differ on Discord data, this page governs.
The bot is added to a server by a Nozie account holder and posts incident alerts into a channel they choose. It is not a general-purpose chat bot and has no function outside that alerting relationship.
1. What the Bot Collects
Server and channel configuration. When you add the bot, we store the server (guild) ID, server name and icon hash, the IDs and names of the channels you select for alerts and deploys, and the ID and name of the role you optionally select for pings.
Installer identity. The Discord user ID and username of the person who added the bot. This is what enforces the rule that only that person can merge a Pull Request or trigger a restart from Discord — it is an authorization record, not a marketing profile.
Messages addressed to the bot. The bot uses Discord's Message Content intent, but it only reads and acts on messages that are directed at it: a message that @mentions the bot, a reply to one of the bot's own messages, or a direct message to it. The text of those messages, the Discord user ID of the sender, and the classified intent are stored in an inbound event log.
Interactions. When someone presses a button on an alert (Merge PR, Rollback, Restart now), we record which incident it referred to and which Discord user pressed it.
2. What the Bot Does Not Collect
- We do not read, store, or process ordinary conversation in your channels. Messages that are not addressed to the bot are discarded in memory without leaving the process.
- We do not collect your member list, roles of individual members, voice activity, attachments, or message history.
- We do not use anything from Discord to train AI models, and we do not sell any of it.
3. Why We Collect It
Server and channel configuration is what makes delivery possible at all. Installer identity is what keeps a stranger in your server from merging code or restarting production. Message and interaction data is what lets the bot answer a question or resolve a restart confirmation, and is retained briefly so an action taken against your infrastructure can be traced to the person who requested it.
4. Sharing and Third Parties
A message you address to the bot is sent to Anthropic to generate the answer, together with a summary of your own containers and incidents. Configuration and logs are stored in our database at Supabase. Delivery itself necessarily passes through Discord, whose own privacy policy governs everything on their side. We share Discord data with no one else.
5. Retention
- Server, channel and role configuration: kept while the integration is connected
- Inbound message logs (text addressed to the bot): 30 days
- Interaction and restart-confirmation records: 90 days
6. How to Remove the Bot and Delete the Data
Either of these ends the relationship, and doing both is cleanest:
- Disconnect in the Nozie dashboard (Integrations → Discord → Disconnect). This deletes the stored server, channel, role and installer records immediately, and moves your alerts back to email.
- Remove the bot from your Discord server (Server Settings → Integrations, or kick the bot). Discord revokes its access instantly. Note that removing the bot on Discord's side does not by itself delete the configuration we hold — use the dashboard for that, or email us.
To request deletion of the inbound message logs before their retention period expires, email us and include the server ID.
7. Children's Privacy
The bot is not directed at individuals under 16, and we do not knowingly collect data from children.
8. Changes to This Policy
We may update this policy from time to time. Material changes will be reflected by updating the effective date above.
9. Contact Us
Questions about the bot or your data: nozie@yerikov.tech · Discord Bot Terms of Service