Statistics Bot Verification Policy
What is a statistics bot? It's a Discord bot whose primary purpose is to display statistics about a guild, or the members of that guild. This information can range from how many members a guild has over time, to how active certain channels are, to who are the most active guild members.
We know that people who run communities love to know about what's going on in their server. This article is the policy that we ask all verified Statics Bots to adhere to in order to uphold Discord's commitment to user safety and data privacy.
Guild Data Access
"Guild Data" is anonymous, aggregate data about the guild as a whole or channels within the guild. It includes but is not limited to:
- Growth/memberflow charts
- Activity of individual channels
- Voice/message velocity
- "Activity" data, like popular games
Access to Guild Data must meet the following criteria:
- Any data or dashboards must be default-private. This means that a user must be a member of the guild in order to see them.
- You may give server owners and admins the ability to mark their guild data as public. This allows aggregated, anonymous data about the guild or guild channels to be visible without being a member.
Member Data Access
"Member Data" is non-anonymous data about a member of the guild. It includes but is not limited to:
- Leaderboards
- User activity over time
- User message velocity/voice activity over time
Access to Member Data must meet the following criteria:
- Any data or dashboards must be default-private. This means that a user must be a member of the guild in order to see them.
- Global aggregate member data may be public
- This includes global EXP/game score leaderboards
- Server-specific aggregate member data may not be made public.
- This includes guild-specific voice, message, EXP, and other leaderboards
- Time-series member data must always be private to the guild, and must have limited access to guild owners or members with "Administrator" or "Manage Server" or "View Server Insights" permissions.
- This includes member "drill-downs" that show individual user activity over time
Furthermore, a user must be allowed an easy way to opt-out of any member data collection via a bot command. Opting out via a web dashboard is insufficient.
Remember, not all use cases are the same. You may see some bots that have been verified that toe the line; verification is a manual review process, and therefore a human has laid on eyes on every bot that passes through. Therefore, we have deemed that individual use case alright.