> For the complete documentation index, see [llms.txt](https://stitch-bot.gitbook.io/mlb-bot/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://stitch-bot.gitbook.io/mlb-bot/mlb-bot-documentation/privacy-policy.md). # Privacy Policy Last Updated: 10-04-2026 **Bot Name:** MLB Bot **Bot ID:** 1511391727154368592 This Privacy Policy covers **MLB Bot** and [**The Baseball Exchange**](https://baseballexchange.app/). It explains the data used when you interact with the bot, sign in to the website, play games, or manage a server. References to bot data include the same records accessed through the website. #### 1. Data the Bot May Collect To operate correctly, MLB Bot may collect and store Discord-related data, including: * User IDs. * Discord usernames, global and server display names, and avatar references. * Guild IDs. * Server names, icons, membership information, and roles or permission information needed to check access. * Channel IDs. * Role IDs. * Message IDs where needed for bot features. * Command usage records. * Bot configuration settings. * Alert settings. * Watchlist settings. * Scheduled post settings. * Permission settings. * Economy-related data. * Prediction and bet history. * Prediction transfer records and transfer-code status. * Mission progress. * Profile and shop settings. * Leaderboard data. * Error logs and diagnostic logs. Website requests and hosting logs may also include IP addresses, browser or device information, requested pages, timestamps, response status, and technical error details. Hosting providers may derive an approximate location from connection information. The bot stores this data so features can work correctly across Discord servers. #### 1.1. Discord Sign-In and Website Sessions The website uses Discord sign-in to obtain your basic Discord profile and server list. It uses the `identify` and `guilds` scopes; it does not request your Discord password or email address. The website compares server membership with the bot’s available servers to show the profiles you can access. A limited-life Discord access token, basic profile details, eligible server IDs, and session-security values are held in an encrypted session cookie. In production, the session cookie is restricted to HTTPS and is not readable by page scripts. Sessions expire no later than seven days after issue, and earlier if the Discord access token expires. Signing out clears the website’s session cookie. Temporary sign-in cookies hold security values and the local return page for up to ten minutes. Cookies and browser storage also remember settings such as the selected server, team theme, color mode, and ticker speed. Public game viewing uses a viewer cookie to support view counting. Blocking these controls can prevent sign-in or some features from working. Server Management checks current Discord membership, roles, and permissions when handling requests and actions. It does not rely solely on permissions recorded at sign-in. #### 2. Alert and Watchlist Data The bot may store alert-related settings so it can send game updates correctly. This may include: * Teams selected for play-by-play alerts. * Channels selected for alerts. * Alert configuration settings. * Watchlisted players. * User IDs connected to watchlist alert preferences. * Direct-message alert preferences. * Alert delivery logs or error logs. Watchlist alerts may be sent by direct message when enabled or when the feature requires DM delivery. The bot uses stored user IDs and watchlist settings to deliver those alerts. #### 3. Virtual Economy and Game Data The bot may store virtual economy and entertainment-feature data, including: * Stubs balances. * Prediction history. * Bet history. * Mission progress. * Season pass progress. * Bingo progress. * Trivia results. * Guess results. * Wordle results. * Diamond Dynasty collection data. * Card ownership data. * Team loadout data. * Archived team versions, card definitions, and discarded draft boards where history is preserved. * Batting-order data. * Diamond Dynasty challenge records. * Simulation game logs, broadcasts, and viewer counts. * Diamond Dynasty market listings and sales. * Leaderboard rankings. * Shop purchases made with virtual Stubs. * Profile customization settings. This data supports gameplay, server statistics, historical views, reward accounting, and investigation of errors or abuse. Discord and the website use the same server-scoped records. Stubs have no real-world cash value and are not payment data. #### 4. Command, Usage, and Error Logs The bot may store command usage logs, interaction logs, and error logs to: * Fix bugs. * Prevent abuse. * Investigate crashes. * Improve bot performance. * Enforce cooldowns and limits. * Prevent spam or exploitation. * Maintain service stability. Logs may include Discord IDs, guild IDs, channel IDs, command names and relevant supplied options, website actions, timestamps, results, error messages, and technical details. Management records may include the acting member, the setting before and after a change, and the status of queued work. Activity totals can include attempts that did not complete successfully. Avoid entering secrets or unrelated personal information into commands, profile fields, or support requests. Information you provide for a feature or support may be stored with the related record. #### 5. Data the Bot Does Not Intentionally Collect MLB Bot does not intentionally collect: * Credit card numbers. * Bank account numbers. * Government ID numbers. * Social Security numbers. * Personal addresses. * Private Discord message content unrelated to bot features. * Real-money gambling information. * Biometric data. The bot may receive limited Discord metadata when users interact with commands, buttons, menus, or alerts. #### 6. How Data Is Used Collected data may be used to: * Provide bot features. * Save server settings. * Send alerts. * Deliver watchlist notifications. * Track virtual economy progress. * Display leaderboards. * Prevent abuse. * Debug errors. * Improve reliability. * Enforce Terms of Service. * Maintain backups and service integrity. #### 7. Third-Party Services The bot may rely on third-party services, including: * Discord. * Cloudflare and other hosting providers. * Database providers. * MLB-related data sources or APIs. * Monitoring or logging tools. * Top.gg or other bot-listing services, where applicable. * GitBook for this documentation. * Ko-fi and its payment providers when you choose to donate. When a user votes through Top.gg, MLB Bot may receive and store limited vote data such as the Discord user ID, vote time, reward status, and webhook-delivery information. This is used to verify the vote, enforce the reward cooldown, and award eligible server-scoped Stubs and Season Pass XP. Discord controls the information associated with your Discord account under its [Privacy Policy](https://discord.com/privacy). Cloudflare handles website delivery and related request, security, and diagnostic information under its [Privacy Policy](https://www.cloudflare.com/privacypolicy/). Images, videos, and other resources may load from third-party providers, which receive the requests needed to serve them. Optional donations take place outside the bot and website. Ko-fi and its payment providers process payment details under their own policies. The services do not directly collect or store card numbers or bank details; information you choose to share with the operator through a donation or support request may still be received. #### 8. Data Sharing MLB Bot does not sell personal data. Data may be shared or disclosed only when reasonably necessary to: * Operate the bot. * Provide hosting or database services. * Debug technical issues. * Investigate abuse or security incidents. * Enforce the Terms of Service. * Comply with legal obligations. * Respond to platform, safety, or Discord policy requirements. Some features are visible to other people by design. Discord posts, server leaderboards, public website profiles, shared results, market activity, and public Diamond Dynasty broadcasts can show your Discord display name or avatar and relevant gameplay records. Public profile and game links can be viewed outside your server. These displays are not private merely because the underlying progress belongs to one server. Authorized server managers and staff can view the server statistics and management activity available to their role. The operator uses command, website-action, error, and server join/leave/rejoin logs for support and operation. Hosting and database providers process data needed to run the services. Discord access tokens and session cookies are not part of public profiles or leaderboards. #### 9. Data Retention Bot-related data may be stored for as long as needed to provide the bot's features, maintain records, prevent abuse, debug issues, or protect service integrity. Progress is stored by server and season. A new season does not automatically erase old balances, stats, award history, inventories, or game records. Viewing an old season is read-only. Replacing a team or discarding a draft can leave an archived version so history is preserved; removing an item from the current interface is not necessarily permanent erasure of every copy. Some data may remain in backups, logs, or archived records for a limited time after deletion from active systems. Certain records may be retained longer when necessary for: * Abuse prevention. * Security. * Debugging. * Moderation. * Legal compliance. * Service integrity. #### 10. Data Removal Requests You may request access, correction, or deletion of your personal data through the support contact below. Server owners may also request help with their server’s records. We may verify your identity or server authority and clarify the requested scope before acting. Applicable privacy rights and legal requirements take precedence over ordinary history-retention behavior. Some data or backup copies may need to be retained where necessary and permitted for: * Security. * Abuse prevention. * Debugging. * Backups. * Legal compliance. * Service integrity. To request data deletion, join the support server, open a support request, state that the request concerns privacy or data deletion, and provide your Discord user ID so the affected records can be located and account ownership can be verified. You can also contact `pavy.` on Discord, ID `191757417782968320`. Do not send passwords, access tokens, or session cookies. We will explain any records that must be retained and why. Signing out, clearing browser storage, or removing the bot does not itself submit a deletion request. #### 11. Removing the Bot Server owners may remove MLB Bot from their server at any time. Removing the bot may stop future data collection for that server, but it may not automatically delete all previously stored records. #### 12. Security Reasonable technical and administrative measures are used to protect stored bot data. The website uses encrypted sign-in sessions, request validation, and server-side permission checks for protected actions. These controls reduce risk but do not make all stored information anonymous or eliminate the possibility of a security incident. However, no online service, database, Discord bot, or hosting system can be guaranteed to be completely secure. #### 13. Children and Minors The services are intended for people who meet Discord’s minimum age and account requirements and any higher minimum age required by applicable law. If you believe a child below the applicable minimum age has provided personal data, contact the operator so the records can be reviewed and addressed. #### 14. Server Member Lifecycle Data MLB Bot uses Discord server-member join and removal events to maintain limited membership context for persistent server-scoped features. The bot may store: * Guild ID * Discord user ID * Username * Global display name * Server display name * Bot-account status * Server join date, when available * Departure date * Active or inactive status * First-seen timestamp * Last-seen timestamp This information is used to distinguish active, departed, and rejoining members; maintain accurate historical membership context for support involving persistent server-scoped progression; and provide a latest-known server display name when a live member record is unavailable. The bot also keeps its own server join, departure, and rejoin history. These records and operator notifications may include server identity, owner and member information, dates, and usage totals. They support server activity history, support, and rejoin summaries; removing and re-adding the bot does not automatically erase earlier visits. Users may request deletion through the MLB Bot support server: #### 15. Changes to This Privacy Policy This Privacy Policy may be updated at any time. The date above identifies the latest update. Material changes will be communicated through the documentation, website, bot, or support server as appropriate, with any additional notice or consent required by applicable law. #### 16. Contact For privacy questions, support, bug reports, or data requests, contact: **Operator/contact:** `pavy.` on Discord · ID `191757417782968320`\ **Support Server:** [MLB Bot support](https://discord.gg/wc2vbmXSGZ) See also the [Terms of Service](/mlb-bot/mlb-bot-documentation/terms-of-service.md) and [Legal Disclaimer](/mlb-bot/mlb-bot-documentation/legal-disclaimer.md).