Your data.
Your say.
This policy explains what information Neon may handle when people use the bot, why it’s needed, and the choices available to server teams and members.
The short version
Neon processes the Discord context it needs to respond to commands and run the features a server chooses to use. What gets involved depends on the feature. Visitors to this website are not asked to sign in or connect their Discord account. The profile page shows the creator’s public Discord and GitHub details. A separate, optional owner-only Discord authorization can keep the creator’s public profile appearance in sync; it does not authorize website visitors.
Information involved
When a command, interaction, or bot feature runs, Neon may process information from Discord that is necessary to complete that request. Depending on what your server uses, that can include:
- Discord identifiers: user, server (guild), channel, and role IDs, used to address the right server configuration or respond to the right person.
- Server settings: preferences such as a configured prefix, feature settings, channel choices, or moderation and welcome configuration.
- Music preferences: saved favourites and playlists can contain a Discord user ID and music track details such as title, artist, and track link.
- Voice connection details: for music and voice features, the bot can store a server ID and voice-channel ID while tracking an active connection.
- Invite tracking: if enabled and available, records can include a joining member’s ID, invite code, inviter ID, join time, and related server or channel details.
- Tickets and moderation: the information needed to create or manage a ticket or carry out a moderation command, based on the feature and how the server uses it.
Discord message or interaction content may be processed when necessary to respond to a command or provide a requested feature. This list describes categories that the bot’s features can use; it does not mean every category is collected for every user or server.
The profile page loads the creator’s public Discord profile and live presence from Lanyard, and the creator’s public profile and account statistics from GitHub. Your browser makes these requests directly to the providers; they may receive standard connection data such as your IP address and request metadata. The browser also keeps a small local cache of public Discord profile details so the profile appears immediately on later visits; it is replaced when fresh profile data loads and can be cleared with the browser’s site data. The profile page displays only a small Discord-style presence indicator over the creator’s avatar; it does not request or read a visitor’s Discord account. If the creator authorizes appearance sync, Discord returns the creator’s public profile appearance to a server-side callback. The site stores public appearance fields such as banner and accent color, plus OAuth refresh credentials used only by server-side functions to periodically refresh those fields.
How information is used
Information is used to provide and operate bot features, apply a server’s chosen configuration, respond to requests, maintain music and community tools, and troubleshoot the service. For example, a saved music favourite helps a member find that track again; a saved server setting helps the related feature work consistently.
The policy website does not request or store visitor Discord sign-in details. The optional owner-only authorization uses Discord’s identify scope to sync the creator’s profile appearance.
Storage & retention
Some settings and feature records are stored in the bot operator’s database so that features can work across commands and restarts. Active voice connection records relate to the bot’s current server connection; other configuration or feature records can remain until they are changed or removed.
The website does not store visitor Discord sign-in sessions. If the creator enables appearance sync, Netlify Blobs stores the creator’s public appearance fields and a separate server-side OAuth access/refresh token pair. These credentials are used only by Netlify Functions to fetch updated appearance data from Discord; tokens are never sent to site visitors. Discord may rotate refresh tokens, and the stored pair is replaced when refreshed. The data remains until replaced or removed by the site operator. Revoking authorization in Discord prevents continued API access, but the operator should also remove the stored sync data. There is no published, fixed deletion schedule for every bot record in this project. Actual retention, backups, and deletion depend on the operator’s hosting and database practices. Avoid sharing sensitive information in commands or tickets unless it is necessary for support.
Discord, GitHub & other services
Discord processes account and platform data under its own privacy policy when people use the bot. The separate profile page uses Lanyard’s public API to display the creator’s Discord profile and presence indicator, and GitHub’s public API to display the creator’s profile and public account statistics. Your browser sends these requests directly to the providers, which handle connection data under their own policies. If the creator opts into appearance sync, server-side functions make OAuth requests to Discord using the creator’s authorization and store only allowlisted public appearance data and server-side refresh credentials in Netlify Blobs. That owner-only flow does not ask visitors to authenticate. Neon’s music or hosting features may also depend on third-party services. Those services handle relevant information under their own terms and privacy policies.
The bot operator does not sell personal information through the features described on this page. Information may also be disclosed where required by applicable law or to address abuse, security, or service integrity concerns.
Your choices
Server administrators can choose which features to enable, configure their settings, and remove Neon from a server. Some saved preferences may be manageable through the bot’s commands. If you have a question about a record or want to ask for it to be removed, contact the person or team that operates Neon through the support channel where the bot was provided. The operator may need enough detail to locate the relevant server or feature record.
Discord account, privacy, and data requests concerning Discord itself should be directed to Discord.
Security & policy updates
The bot operator should use appropriate safeguards for their deployment, but no internet service can promise absolute security. This policy may be updated as Neon’s features or operation change. The “last updated” date above shows the date of the current version.
Questions about privacy? Reach out to the Neon bot operator through the support channel where you found the bot.