Discord's intents review for a custom bot

https://flavibot.xyz/docs/privileged-intents/01-use-cases

[your bot's name] is the custom bot of the [your server's name] Discord server, powered by FlaviBot (https://flavibot.xyz). It runs FlaviBot's features under the server's own name and avatar, and it is configured from FlaviBot's web dashboard (https://flavibot.xyz/dashboard).

FlaviBot is a multipurpose Discord bot that brings music, member onboarding, moderation, automations, community features and support tools together in one bot. Each module is turned on and configured per server from the dashboard:
- Music: a music player that supports Spotify, Apple Music, Deezer, Tidal and Amazon Music, plus direct links, radio and uploaded audio files, with a web player and a music controller channel.
- Members: welcome and goodbye messages with image cards, auto-roles, persistent roles (given back when a member rejoins), invite tracking, and rewards for members who boost the server or wear its server tag.
- Moderation: moderation commands with a case history, Discord AutoMod integration and server logs.
- Automations: a rule builder that reacts to messages, reactions, member joins and other events, for example to delete scam links or to kick accounts that are too new.
- Community: levels, economy, giveaways, starboard, counting channels, sticky messages, temporary voice channels and counter channels.
- Support and organisation: tickets with transcripts, forms, suggestions, events, tasks, an embed builder and optional AI characters.

Documentation: https://flavibot.xyz/docs
What it uses each privileged intent for, with screenshots: https://flavibot.xyz/docs/privileged-intents/01-use-cases

FlaviBot's privacy policy applies to this bot. It is linked in the footer of every page of FlaviBot's website, https://flavibot.xyz, and from FlaviBot's page in Discord's App Directory. In Discord, the /privacy command tells each member privately which statistics are collected about them, lets them turn that collection off, and explains how to request the deletion of their data.

https://flavibot.xyz/legal/privacy-policy

This bot runs FlaviBot, which uses the Server Members intent for features that server managers turn on from its dashboard.

1. Member join, update and leave events
- Welcome: welcome messages and image cards, auto-roles, and an optional welcome DM.
- Goodbye messages when a member leaves.
- Persistent roles: the roles a member had when they left are given back if they rejoin, for a period the server chooses (365 days at most).
- Invite tracking: credits the member who invited a newcomer, with fake-invite and rejoin detection.
- Boost and server tag rewards: roles and messages for members who boost the server or wear its server tag.
- Server logs: joins, leaves, and nickname, role, avatar and timeout changes.
- Automations: rules triggered when a member joins or leaves, gains or loses a role, boosts, or is timed out. Servers use them against raids and scams, for example to kick or ban accounts younger than a set age.
- Clean-up when a member leaves: a notice is posted in the tickets they opened, the tickets they had claimed are released, they are removed from the server's teams, and their access to that server's dashboard and ticket chat ends.
- Server statistics: daily joins and leaves, and the member count shown on the dashboard and in counter channels.

2. The full member list, only for actions a server manager starts or turns on
- /mass-role add: gives a role to every human member of the server who does not have it yet.
- Economy role income: pays coins to every member who holds a configured role.
- /info boost, /info server-tag and /badge-count, and the dashboard buttons that give the boost and server tag rewards to members who already qualified before the feature was turned on.

3. Up-to-date roles
Member update events keep the bot's copy of each member's roles current. The dashboard and the moderation commands check those roles to decide who may change a server's settings or moderate its members. Without these updates, a member who lost a staff role could keep powers they no longer have.

https://flavibot.xyz/docs/privileged-intents/01-use-cases#server-members

Discord IDs, usernames and avatars, to show members on the dashboard; the roles a member had when they left, for persistent roles (for the period the server chooses, 365 days at most); who invited whom, kept while the bot is used on the server so rejoin and fake-invite detection keep working; join and leave events linked to a member (90 days; the per-server hourly join and leave counts carry no member identity); and the levels, XP, economy balances and moderation cases the server's features produce, kept while the bot is used on the server. Technical caches expire within 14 days.

Any member can run /privacy in Discord: it shows the statistics kept about them, turns their collection off, and its "Delete my data" button explains how to request the deletion of everything else. Requests are made on FlaviBot's support server (https://discord.gg/flavibot) or by email at contact@flavibot.xyz. FlaviBot checks that the person controls the Discord account, then deletes their data from its databases and caches after a grace period of about 30 days, during which they can cancel. Server owners can request the deletion of all of their server's data the same way. Details: https://flavibot.xyz/legal/privacy-policy

Only for features a server turns on. For servers with message logs or with automation rules on edited or deleted messages, recent messages go into a temporary cache (text cut at 1,500 characters) that expires automatically after 48 hours, so a log can show what an edited or deleted message said. For AI characters, the channel's last messages are held in a temporary cache for 2 hours so the character can reply in context. Ticket staff notes are stored with the ticket. When the AI ticket assistant is on, the summary it writes is stored with the ticket, and the knowledge base entries it proposes are stored with names and personal details removed; the ticket's messages themselves are not stored. Ticket transcripts are generated when a ticket closes and delivered on Discord; no copy is kept. When a server manager turns on an automation rule's debug mode, a 200-character excerpt of each message the rule checked is kept for about one hour.

No. FlaviBot does not train or fine-tune any machine-learning or AI model, and does not let anyone else do so with this data. Two optional features, which a server manager must turn on, send message content to Anthropic's API for inference only: the AI ticket assistant, which drafts an answer to a support ticket from the server's own knowledge base and summarises the ticket when it closes, and AI characters, which reply in a channel using its recent messages as context. Anthropic does not use this data to train its models. Apart from the 2-hour context window of AI characters, only the generated reply, summary or knowledge base entry is kept, not the messages sent to the model.

This bot runs FlaviBot, which reads message content only for features a server manager turns on, and only in channels the bot can see.

- Automations: rules that match the text of new and edited messages (contains, starts with, exact match, or a regular expression run with RE2) and act on it. Servers use them to delete scam and phishing links, filter banned words and answer frequently asked questions.
- Server logs: when a message is edited or deleted, the log channel shows what it said before and after. Discord does not resend the old text with these events, so for servers with message logs or edit/delete rules enabled, recent messages go into a temporary cache that expires automatically after 48 hours.
- Discord AutoMod logs: show the message AutoMod blocked and the part that matched.
- Counting channels: each message is checked to be the next number.
- Music controller channel: members type a song name or link to add it to the queue.
- Starboard: popular messages are reposted with their text and images.
- Tickets: the ticket's live view on the dashboard, the transcript generated when a ticket closes, staff notes written in the ticket, and, when enabled, the AI ticket assistant.
- AI characters: a character set up by the server replies when a message contains its trigger word, using the channel's recent messages as context.

FlaviBot also answers prefix commands. They are being retired: every prefix command already tells members to use the slash command instead, and commands that mention the bot keep working without this intent.

https://flavibot.xyz/docs/privileged-intents/01-use-cases#message-content

This bot does not use presence data. FlaviBot, which it runs, does not request the Guild Presences intent when it connects to Discord, and no feature reads presence or activity data. Online-member figures come from approximate_presence_count. We are not applying for this intent and it can be removed from the application.