Privacy Policy — Halpo Police

This notice describes what data this bot collects, why, where it is stored, who it is shared with, and how to request deletion. The bot is operated by the Mobile Legends: Bang Bang Global Team as internal tooling inside the MLBB Global Discord server and any affiliated servers the team operates. It is written for every member of any server the bot is installed in, not only for the staff who operate it.

What this bot is

This is a moderation and community management bot installed on Discord servers operated by the MLBB Global Team. It is not a public bot and is not listed in any app directory. Members cannot add it to other servers.

Two of the Discord permissions this bot requests are classified as “privileged intents” by Discord: Guild Members (so the bot can look up server members, see nickname changes, and maintain a local copy of the member list) and Message Content (so the bot can read the text of messages in channels where it operates, including to parse legacy text-prefix commands and to log edited and deleted messages). A third privileged intent, Guild Presences, is requested in the bot’s configuration but is not currently used by any feature. The bot also reads additional user information from direct messages sent to it.

Data the bot collects, by feature

Moderation Tools

Used to record bans, unbans, mutes, unmutes, warnings, deletions of moderation records, and user reports.

For each action:

Discord user ID of the affected member
Discord user ID of the moderator performing the action
Guild ID
Action type (ban, mute, warn, report, and similar)
Reason text entered by the moderator (free-form, up to Discord’s per-command limit)
Evidence image URL, when an image is attached
For mutes: mute duration in milliseconds
For event disqualifications: the event names and channel IDs the disqualification applies to
Timestamp of each action

A user report filed through the in-server reporting flow (a slash command, the legacy text-prefix command, or the message context-menu report option) records the reporter’s Discord user ID, the reported user’s Discord user ID, the reason text, and a Log row marked as a report. When a user reports a specific message through the message context-menu option, the full text and any attachment URLs of the reported message are also copied into the staff-only report channel as part of the report entry.

Appeal System

Used when a banned member submits a ban appeal from an appeal server and when community members vote on appeals.

Discord user ID of the appellant and of each voter
Guild ID and appeal-message ID
Three free-text fields the appellant fills in: their understanding of the original ban reason, why they should be unbanned, and an agreement to follow the rules
For each vote: which user voted with which emoji, when they voted, and the fact that the vote was later removed (the moment of removal is logged in the bot’s output but is not stored as a separate timestamp)
A per-user 30-day appeal cooldown so the same user cannot re-appeal immediately after a denial

When the staff team finishes reviewing an appeal, the appeal text record and the vote records associated with that appeal are deleted. Other appeals records remain until manually reviewed.

Member Management

Used for channel locks and unlocks, nickname changes, role additions and removals, and free-form staff notes attached to members.

Discord user ID of the affected member and of the acting moderator
Guild ID
For staff notes: free-form note text entered by staff, plus an optional attached image URL
For nickname and role changes: the action taken and who performed it (the new nickname value itself is mirrored into the staff-only logs channel for the change but is not persisted to a database column)
For channel locks and unlocks: the channel ID affected

Message Logging

When the team enables it for a category of channels, the bot records every message edit and message delete in those channels to a staff-only logs channel.

Discord message ID, channel ID, and author ID
The full text of the message as it was before an edit and after the edit, or as it was at the moment of deletion
URLs of any image or file attachments that were on the message
Edit and delete timestamps

The text and attachment URLs of logged messages are kept in the staff-only logs channel and are not written to the bot’s database.

Reaction-Role Tracker

When configured, the bot logs when a member who holds a configured role reacts to a message with a configured emoji. The source message’s text and any image attachments are copied into the log entry for context.

Discord user ID of the reactor, message ID, channel ID, and guild ID
The category label the operator assigned to that reaction
The source message’s text and any image attachments, mirrored into the log entry

News Message Tracking

When configured, the bot records messages posted in configured News channels by members who hold a configured News role. The records exist so the staff activity dashboard can count news output accurately.

Discord user ID of the author, message ID, channel ID, and the configured source channel ID
No message content is stored

Staff Profile

Staff members can store a personal timezone preference so staff-only commands can show times in their local zone.

Discord user ID of the staff member
IANA timezone string (for example, Asia/Manila)

Guild Settings

Per-server configuration: channel IDs, role IDs, invite links used by the bot’s appeal flow, module on/off toggles. This is operator configuration, not member data.

Where data is stored and how long it is kept

All structured data above is stored in a SQL database (MariaDB, MySQL, or PostgreSQL, selected by the operator) running on the machine hosting the bot. The database is owned and operated by the MLBB Global Team and is not shared with any outside party.

The relevant database tables, by feature:

Moderation Tools: the log table.
Appeal System: the appeal and appeal_vote tables; appeal cooldowns are kept in a local file named data/cooldowns.json.
Member Management: the log and note tables.
News Message Tracking: the news_message table.
Reaction-Role Tracker: the reaction table.
Staff Profile: the timezone table.
Guild Settings: the setting table.

Retention, by feature:

Moderation audit records: kept indefinitely until an authorized staff member deletes them.
Staff notes: kept indefinitely until an authorized staff member deletes them.
Ban appeal text and appeal votes: deleted when the staff team concludes a review of that appeal. Vote rows that are not tied to a closed appeal remain.
Reaction tracker records: kept indefinitely until the original reactor or a staff member removes the entry from the staff-only log channel.
News message tracking records: deleted automatically when the underlying Discord message is deleted.
Appeal cooldown: kept in data/cooldowns.json for 30 days from the user’s last appeal submission, then removed.
Staff timezone preference: kept indefinitely until the staff member changes or removes it.
Guild settings: kept for as long as the bot is installed on the server.
Short-lived vote-removal confirmation messages: discarded automatically after 30 seconds and never written to disk.

The bot does not back up or archive any of this data outside of its own database.

Security

The database is protected by commercial-grade password authentication on the database user account. Database credentials are stored in the bot’s local config file (data/config.json) and are not transmitted outside the bot’s host. The host machine is operated by the MLBB Global Team and is access-controlled. The database is not directly reachable from outside the host.

If the bot becomes aware of any unauthorized access to the data it has stored, the MLBB Global Team will notify Discord and affected members in accordance with Discord’s Developer Policy.

The bot does not sell, license, or trade any of the data it collects. It does not share data with advertising networks, data brokers, or any monetization service. It does not use any of the data it collects to train machine learning or AI models. It does not contact users outside Discord.

The bot does send a narrow set of information to internal, operator-controlled services in order to power the staff activity dashboard:

A moderator ticket-counting service: receives the moderator’s Discord user ID, the guild ID, and a date range, and returns aggregated ticket counts.
A moderator profile service: receives the moderator’s Discord user ID and a date range, and returns aggregated action counts for that period.

These services are operated by the MLBB Global Team. They receive Discord user IDs only. They do not receive message content, nicknames, notes, or any other data covered above. The data they receive is used to render the staff activity dashboard and is not used to discriminate against any member on the basis of protected characteristics.

The bot also fetches copies of image attachments from Discord’s content network and stores them with the relevant log entry. This stays within Discord’s infrastructure and is not a third-party transmission.

The bot does not transmit data outside its own infrastructure except as described in this section.

Sensitive data

The bot’s free-text fields (moderation reasons, staff notes, appeal answers, reported message content) can in principle contain any text. The bot is not designed to collect health, financial, or other categories of sensitive personal data. If a member believes the bot has stored sensitive personal data about them through any of these fields, the data will be removed on request using the deletion process below.

Children

The bot is not intended for use by anyone under 13 years old or below the minimum age required in their country. If you believe the bot has stored data about anyone under that age, contact the address below so it can be removed.

How to request deletion

A member may ask for any data the bot has stored about them to be deleted by emailing privacy@mlbb.dev or by opening a ticket in the MLBB Global Discord server. The request will be handled by a member of the MLBB Global Team staff.

For most features, the bot provides authorized staff with a way to delete individual records. When a member files a deletion request, staff will use those tools where possible. For data that cannot be deleted record by record (for example, an unclosed appeal vote, or a staff timezone entry), staff will remove the records directly from the database.

What happens when the bot is removed from a server

If the bot is removed from a server, the data it has stored for that server is not automatically deleted. The records remain in the SQL database the bot’s host operates. To have that data removed, the server owner or a member can contact the addresses above and staff will delete the relevant rows.

What happens if the bot stops operating entirely

If the bot is decommissioned, the MLBB Global Team will delete the stored data in accordance with Discord’s Developer Terms of Service.

Compliance

The MLBB Global Team operates the bot in accordance with applicable privacy laws, including where applicable the European Union’s General Data Protection Regulation (GDPR), the ePrivacy Directive, the UK General Data Protection Regulation, Brazil’s Lei Geral de Proteção de Dados (LGPD), the California Consumer Privacy Act (CCPA), and the California Privacy Rights Act (CPRA).

Changes to this notice

If the bot’s data practices change, this notice will be updated and the new version will be published in the same place as this one. Material changes will be announced in the MLBB Global Discord server.

Contact

MLBB Global Discord: https://discord.gg/mobilelegendsbangbang
Email: privacy@mlbb.dev

See the Terms of Service for the rules governing use of the bot.