Bot Guidelines
Data disclosure requirements and what gets a bot listing rejected or delisted.
These guidelines cover what’s specific to bot listings. They apply on top of the general Community Guidelines. Read this before you submit your bot.
Behaviour rules
- Accurate description and tags. The short description must say what the bot really does, and tags must reflect actual functionality.
- No unsolicited messages. No unprompted DMs, mass pings, or posts when the bot joins a server.
Privacy and data disclosures
Fluxer bots receive all message content by default, with no intent gating. Transparency about data handling is a hard requirement.
You must disclose
If you collect data
On your submission, state:
- Whether your bot collects any user data, such as IDs, usernames, or message content.
- Whether it stores message content, and for how long.
- Every external API or service it connects to.
- Whether it uses voice features.
Automatic rejection
Any of these ends the review, regardless of anything else. These are in addition to the general conduct rules that apply to every listing type.
- Scraping or exporting community member lists.
- Collecting or storing user data, or reading and storing message content, without disclosure.
- Attempting to escalate its own permissions.
- Sending unsolicited DMs to community members.
- Requests to unidentified or suspicious external endpoints.
- Being a reskin of a banned or previously rejected bot.
- Advertising external products or services unprompted.
- Recording or transmitting voice audio without explicit disclosure.
- The developer providing false information on the submission form.