1. Who operates Milo
Milo, also known as the StoneHaven Discord Bot, is operated by Gage Olson, known as SwornHero, for the StoneHaven community (“we,” “us,” or “our”). Milo connects designated Discord channels with configured Minecraft Java servers.
This Policy explains how we handle information through the Milo service we operate. It also covers information provided directly to us for Milo support and privacy requests. Independently hosted copies have their own operators, who are responsible for explaining their practices. This Policy does not cover unrelated website analytics or separate applications, including a separate Discord website-login application.
Privacy contact: SwornHero@stonehavensmp.com
2. Information Milo processes
The information processed depends on enabled features, permissions, and connected server software.
| Category | Examples and purpose |
|---|---|
| Discord account and permission information | User IDs, usernames, display names, role membership, and relevant permissions used to identify command users, check access, and attribute bridged messages. |
| Discord server and channel information | Server, channel, role, and message identifiers used to route messages, apply permissions, and update the server-status post. |
| Bridged Discord messages | Message text, readable mentions, attachment counts, and sticker names from the configured bridge channel. Attachment files are not downloaded or forwarded by the current chat bridge; it sends a count or text marker. |
| Minecraft activity | Player names, chat, joins, departures, deaths, advancements, staff alerts, and former names or first-join indicators when included in server output. |
| Command information | Command names and arguments, target player names, moderation reasons, and responses from the Minecraft server. |
| Server status | Server address, version, message of the day, online player names and counts, uptime, latency, and available performance information. |
| Console and diagnostic information | Minecraft log lines, errors, command output, and bot diagnostics. Depending on the server and its plugins, logs may contain player UUIDs, IP addresses, coordinates, moderation information, or other personal information. |
| Configuration and credentials | Configured channel and role IDs, server connection details, bot credentials, RCON credentials, and optional hosting-panel credentials needed to run integrations. |
| Support correspondence | Your contact details and the information you choose to provide when contacting us. |
Discord supplies information according to the bot’s permissions and API behavior. The chat bridge processes eligible messages in its configured channel for forwarding; it is not designed to relay direct messages or unrelated channels. Minecraft information comes from server-status queries, RCON, and configured local logs or a hosting-panel console connection.
3. How information is used
We use information to relay chat, publish server status and gameplay notifications, deliver staff alerts, check permissions, execute authorized commands, troubleshoot failures, maintain service security, and respond to support and privacy requests.
We do not sell personal information, use it for targeted advertising, or use Discord message content to train AI or machine-learning models. Milo’s current implementation does not include advertising or behavioral-profiling features.
4. Where information is shared
Between Discord and Minecraft. The bridge sends Discord message text, the author’s display name, and their Discord handle to the connected Minecraft server. The handle may be visible when hovering over the author’s name. In-game chat, player names, and enabled gameplay notifications are sent to configured Discord channels. These audiences can differ from the audience of the original message.
With channel viewers and administrators. Anyone permitted to view a destination channel can see the information posted there. Console output and staff alerts may include sensitive information. If a dedicated destination is not configured, some log categories may fall back to the console channel. Authorized staff and system administrators may access information needed to operate and support the service.
With service providers. Discord processes bot interactions and messages on its platform. Bot hosting, Minecraft hosting, and a configured hosting-panel provider may process relevant information as needed to run those services. Their processing is also subject to their applicable terms and privacy practices. See Discord’s Privacy Policy.
When legally required. We may disclose information to comply with binding legal requirements. We limit disclosures to what is required and permitted by applicable law and Discord’s requirements.
We do not treat a server administrator’s installation of Milo as blanket permission to disclose every member’s information. Cross-platform sharing must be clearly disclosed and appropriately authorized. If you have concerns about a bridged channel or a disclosure, contact us before posting further information there.
5. Storage and retention
Milo’s current SQLite database stores operational settings, including the status-message ID, and the server’s online-since timestamp. It does not maintain a separate database archive of all chat messages or individual player histories. This does not mean that messages are never stored elsewhere.
| Location or record | Retention approach |
|---|---|
| Temporary processing | Messages and console lines may be buffered or cached in memory while Milo operates. This is separate from persistent copies described below. |
| Bot settings and server state | Kept while needed to operate the configured integration; updated or removed when no longer necessary. |
| Discord posts | Relayed chat, console posts, and notifications remain in channel history until removed. Milo does not automatically expire these posts or synchronize edits and deletions from the source. |
| Minecraft and hosting logs | Source logs and captured bot output follow the retention settings of the relevant server or hosting system. Failed RCON requests may cause the command text, including bridged chat, to appear in diagnostic logs. |
| Support records | Kept as needed to resolve the request and meet applicable legal obligations. |
| Backups, where used | Copies may remain within the applicable backup lifecycle. Removal requests include relevant backups under our control; deleted information must not be reintroduced into active use from a restored backup. |
We retain personal information only while necessary for the stated service functions or as required by law. Retention decisions consider whether an integration remains active, whether information is needed to resolve a current problem, and applicable legal requirements. The current bot does not enforce a single automatic retention period across these systems; cleanup may require administrator action.
Except where applicable law requires retention, we promptly delete Discord API data under our control when it is no longer needed for Milo’s permitted functionality, when we stop operating Milo, or when deletion is requested by the relevant user or Discord. Removing the bot from a server does not itself perform that cleanup.
6. Your choices and privacy requests
You can choose not to post in a bridged Discord channel or use Milo’s commands. Minecraft activity and server logs may still be processed while you use a connected server. The current bot does not provide an individual opt-out command for gameplay notifications or console mirroring. Contact us to discuss your options.
You may request access to, correction of, or deletion of personal information under our control by emailing SwornHero@stonehavensmp.com. Include your Discord user ID or Minecraft username, the relevant server, and enough context to locate the information, such as a message link or approximate date. You do not need to disclose your request publicly or remain a community member to contact us.
We may ask for proportionate information to verify that the request concerns your data. Do not send passwords, bot tokens, RCON credentials, or identity documents unless a specific lawful verification process requires them.
We will respond within applicable legal deadlines and handle requests for Discord API data promptly. If the law requires us to retain some information, we will explain the limitation where permitted. A deletion request does not automatically reverse a separate moderation decision or restore server access.
Deleting the original message does not automatically remove a bridged copy, server log entry, or screenshot. We will address copies under our control and explain when you need to contact Discord or an independent operator for information they control. We cannot delete copies held by unrelated users.
Depending on where you live and which laws apply, you may also have rights to restrict or object to processing, obtain portable data, withdraw consent where processing relies on it, or complain to a relevant data-protection authority. Contact us to exercise an applicable right.
7. Security
Milo checks configured roles and permissions for restricted functionality. Channel permissions and hosting access controls also affect who can see information. No security measure guarantees complete protection.
Console forwarding is not a privacy-redaction system: formatting cleanup does not remove all personal information or secrets from logs. Do not place credentials or sensitive personal information in chat or command arguments. Report suspected unauthorized access privately to SwornHero@stonehavensmp.com. We will investigate and provide notifications required by applicable law and platform requirements.
8. Children’s privacy
Milo is not intended for children under 13 or anyone below the applicable minimum age for Discord. We do not knowingly collect personal information from children below that threshold. If you believe such information has been processed, contact us so we can investigate and remove information under our control as required.
9. Processing locations
Information may be processed in countries where Discord and the relevant hosting providers operate, including outside your country of residence. Where applicable law requires safeguards for international transfers, those requirements apply to the processing involved. Contact us for information about the providers and processing locations used for the Milo service you use.
10. Changes and contact
We will update this Policy when our practices change and revise the date above. Material changes will be announced through this website or relevant community announcements. We will obtain consent where required before applying a change that requires it.
Gage Olson / SwornHero — Milo, StoneHaven
Email: SwornHero@stonehavensmp.com