This policy explains what information the bots may process, why it is used, and the choices available to server members, server owners, and other people who interact with them.
01 / Coverage
Which applications does this cover?
This single policy covers Discord applications operated or maintained by Charles Naig, including Tambayan 24/7, the Pinoy Lang server and Pinoy Lang Guilds Bot, Slash Filipino, Hiraya, BMY, Ambition, music bots, and other related community or utility bots. A bot may have features that are not enabled in every server.
02 / Information processed
What the bots may handle
- Discord identifiers such as user, guild, channel, role, and message identifiers.
- Display names, usernames, server membership, roles, preferences, and command or interaction details.
- Configuration and operational records, such as enabled features, moderation settings, queues, points, schedules, or error logs.
- Content you intentionally submit to a bot, such as a command argument, profile value, song request, or support message.
- For voice or music features, connection and queue information needed to operate the feature. The bots are not intended to record private voice conversations.
03 / Privileged Gateway Intents
How member, presence, and message content data are used
Some applications use Discord’s privileged Gateway Intents only when the related feature is enabled in a server. The intents are not used to build advertising profiles or train AI or machine-learning models.
Server Members Intent
Guild membership and member identifiers are used for member-specific automation, role eligibility, XP and level features, and community workflows. Relevant operational records may be stored in MongoDB. Members can ask to opt out of applicable tracking or request deletion as described below.
Presence Intent
Presence updates are used only for the optional vanity-link role feature. When a member chooses to place a configured server invite or vanity link in their Discord status, the bot can grant or maintain the related server role. Members can opt out by removing or changing that status, or by disabling the feature where the server provides that option.
Message Content Intent
Message content is processed to respond to text commands and configured automations, and to support opt-in message-count, XP, or level features where enabled. Relevant operational records may be stored in MongoDB. Message content is not used to train AI or machine-learning models, and users can opt out of message tracking through their server’s available controls or by contacting us.
04 / Use
Why information is processed
Information is used to respond to commands, provide requested features, remember server configuration, support moderation and safety, prevent abuse, troubleshoot failures, and improve reliability. Information is not sold, rented, or used for advertising profiles.
05 / Sharing
Who may receive it
Access is limited to the operator and service providers needed to host, store, monitor, or deliver the bot. Information may also be disclosed when required by law, to protect a person or service, or during a security incident. Discord’s own processing is governed by Discord’s policies and is outside this policy.
06 / Retention and deletion
How long records remain
Retention depends on the feature and the server’s configuration. Operational records are kept only as long as reasonably needed for the stated purpose, security, troubleshooting, or legal obligations. A server owner or affected user may request deletion of bot-held information by contacting privacy@naig.me. Some records may need to be retained temporarily for security or legal reasons.
07 / Your choices
Questions, access, or removal
You can stop using a bot, remove it from a server through the server’s authorized administrators, or ask what information is associated with your Discord account or server. Include the bot name, server name or ID, your Discord user ID, and the request you want handled. Do not send passwords, tokens, or sensitive personal information.
08 / Changes
Updates to this policy
This policy may change when the bot family, features, or legal requirements change. The effective date above will be updated when a material revision is published.