Privacy Policy
This Privacy Policy describes how The Overlord Discord bot (the “Bot”), the public website for the Bot (the “Site”), the optional web dashboard and admin panel, and any related operator tooling (together, the “Service”) collect, use, store, share, and delete information. The Service is provided by the Bot’s operator (“we,” “us,” “our,” or the “Operator”).
By adding the Bot to a Discord server, using commands, visiting the Site, or signing in to the dashboard, you acknowledge this policy. If you do not agree, do not use the Service.
The Bot runs on Discord. Discord is a separate company. Their platform rules and Privacy Policy apply to everything that happens inside Discord itself. This document only covers information the Operator’s Service processes in connection with the Bot and Site.
In-Bot currencies, items, stocks, raid rewards, and similar assets have no real-world monetary value and cannot be redeemed for money. This policy is informational and is not legal advice.
1. Scope
This policy covers:
- The Discord bot known as The Overlord and its command, event, and background systems
- The public website (documentation, leaderboards, stocks pages, status, changelog, FAQ, about, terms, privacy, cookie notice)
- Discord OAuth login for the user dashboard and the allowlisted operator admin panel
- Optional bridges (for example a Cloudflare Worker or similar) used to complete login or serve API data for the dashboard
- Published data files (for example JSON on GitHub) used to power public Site pages
It does not control Discord’s own processing, third-party invite links, or external sites you choose to open.
2. Categories of information we process
2.1 Account and Discord identifiers
Depending on how you interact with the Service, we may process:
- Discord user snowflake IDs
- Usernames, global names, nicknames, and avatar URLs as Discord exposes them to the Bot or OAuth
- Discord guild (server) IDs and names, channel IDs and names, role IDs and names needed for features
- Whether you are a bot or human account (to refuse invalid targets)
- Approximate permissions Discord reports for you in a guild (for example “Manage Guild”) when building the dashboard server list
2.2 Message and interaction content
- Command text you send that invokes the Bot (prefix or slash), including arguments and mentions
- Button, select menu, and modal interaction payloads tied to Bot sessions (work, rob, raids, games, shop, settings, and similar)
- Content in Bot-managed channels such as temporary raid channels, including text that is relayed to a paired server during a raid
- Reactions used for Bot features (for example reaction roles, Wordle, or raid report reactions)
- Optional report and feedback submissions you explicitly send to the Operator
The Bot requests Discord’s Message Content Intent where required for prefix commands. The Bot is not designed to store the full chat history of ordinary non-command channels, but command usage and feature-specific messages may be processed and, where needed for the feature, stored.
2.3 Gameplay, economy, and progression data (primarily per server)
Most gameplay state is stored separately for each Discord server the Bot is in. Examples include:
- Coin balances, inventories, equipment, titles, pets, guards/muscle, quest progress, prestige, streaks
- Work, daily, fish, mine, rob statistics, heat, ranks, cooldowns, and per-user preferences such as legacy command mode
- Shop purchases, crafted items, forge/loadout loadouts
- Stock portfolios, orders or positions as implemented, and server market state
- Lottery entries, duel/ranked records, war participation, tournament state
- Raid opt-outs, raid stats for the server, raid configuration (category, ping role, cooldowns)
- Admin settings: event and level channels, gambling/rob toggles, disabled commands, ignored channels, game channels, reaction-role panels, custom title shop entries and linked Discord roles
- Realm board channel configuration and related overview content
2.4 Cross-server and global features
- Raids: matching two guilds, creating temporary channels, relaying participant chat, scoring, and writing summary stats. Participants on either side may see display names and messages from the other side for the duration of the raid.
- Global leaderboards and similar rankings may combine user IDs and display names across guilds.
- Website exports may publish ranked or aggregate statistics, listed servers, war outcomes, bot online status, command catalogs, changelog entries, and wiki-style reference data.
2.5 Website, cookies, and local storage
The Site may store or read:
- A cookie-notice / consent choice (so the banner is not shown on every page load)
- OAuth session tokens or related session material after “Log in with Discord” (often in
localStorageor similar) - Short-lived UI preferences for the dashboard or admin panel
Essential storage is required for login sessions to work. The cookie banner explains that cookies and similar technologies are used and links to this policy.
2.6 OAuth and dashboard data
When you authorize the Site with Discord, we may receive:
- Basic identity (user id, username, avatar) from Discord’s OAuth scopes in use (typically identify and guilds)
- The list of guilds Discord returns for your account, used to show servers you can manage and to intersect with guilds where the Bot is present
The operator admin panel is limited to the Operator and Discord user IDs explicitly allowlisted by the Operator. Admin tools may display operational logs and configuration controls; they are not open to the general public.
2.7 AI-related data
If AI-powered features are enabled (for example Gazette-style generated text), limited prompts may be sent to a third-party AI provider (for example via OpenRouter). Prompts may include gameplay context required to produce a response. Do not submit sensitive personal information through those features. Third-party AI providers process data under their own terms and policies. Usage may be rate-limited (for example a daily request cap).
2.8 Logs, security, and abuse records
- Application logs: errors, failed commands, reconnect events, warnings
- Operator moderation: user or guild blacklist / block entries
- Report and feedback ticket content and metadata (author id, guild, timestamps, message links when provided)
- Optional usage statistics for operator diagnostics
2.9 Information we do not intentionally collect
- Payment card numbers (the Bot does not sell paid currency)
- Government ID numbers
- Precise GPS location from your device (Discord may have its own location features unrelated to us)
- Advertising profiles for third-party ad networks on the Site (we do not run third-party ad trackers as part of the Bot’s design)
3. How we use information
- To operate Bot features you or server admins request (economy, games, raids, stocks, settings, and the rest of the command set)
- To keep per-server progress consistent across sessions and host restarts
- To run matchmaking and safety rules for raids and PvP
- To provide the Site, dashboard, and allowlisted admin panel
- To publish optional public data exports for leaderboards and status pages
- To investigate abuse, spam, exploits, and security incidents
- To improve reliability (debugging, soft-fail load logs, uptime)
- To comply with law and enforceable legal requests
We do not sell personal data. We do not use Bot gameplay databases for third-party advertising.
4. Legal bases (where GDPR / UK GDPR applies)
- Contract / requested service: providing the Bot and Site features you choose to use
- Legitimate interests: securing the Service, preventing abuse, operating multiplayer features, maintaining public game leaderboards that are part of the product
- Consent: where required for non-essential browser storage, or for optional AI features, as applicable
- Legal obligation: when we must retain or disclose information under law
5. Processors and international transfers
Depending on deployment, processors may include:
- Discord, Inc. — platform delivery of messages, interactions, and OAuth
- Bot hosting providers — run the Node.js process
- Turso or other libSQL/SQL hosts — persistent economy and settings storage
- Cloudflare (or similar) — Workers/KV for OAuth callbacks or API if configured
- OpenRouter or other AI APIs — only when AI features are used
- GitHub / GitHub Pages — Site hosting and optional public JSON data hosting
These providers may store or process data in the United States or other countries. If you access the Service from elsewhere, you understand that transfers may occur to those locations.
6. Retention and deletion
- Active servers: gameplay and settings remain while the Bot is used in that guild, until changed or deleted.
- Bot removed from a guild: we schedule deletion of that guild’s stored Bot data after approximately 30 days, unless we must keep data longer for security, abuse, dispute, or legal reasons.
- Admin wipe: users with the required permissions can run the Bot’s data-deletion command to wipe that server’s Bot data after confirmation.
- Raid channels: temporary; deleted after the raid ends. Summary statistics may remain in guild records.
- OAuth sessions: until logout, expiry, or clearing site data.
- Cookie notice choice: until you clear storage.
- Blacklist / blocks: until the Operator removes them.
- Reports / feedback: retained as long as needed to handle the submission and related safety issues.
- Logs: retained only as long as reasonably useful for operations and security.
Deleting a single server’s data does not always remove global leaderboard rows, operator blacklists, or copies already published to public website data files until those systems are updated or regenerated.
7. Sharing and visibility
- Other Discord users can see normal Bot output in channels they can view, including raid relay text during a raid.
- Service providers process data only to host or operate the Service.
- Public website visitors can see information included in published exports (leaderboards, listed servers, status, and similar).
- Legal and safety: we may disclose information if required by law or to protect people, the Service, or rights.
- Project transfer: if the Operator transfers the project, data may transfer under continued protection commitments.
8. Your choices and rights
- Control Discord permissions and which channels the Bot can read.
- Server admins: configure features; run data deletion for that guild when available.
- Raid participants: use the Bot’s raid opt-out command.
- Website users: use the cookie banner choices; clear site data; log out of the dashboard.
- Leaderboard visibility: use any in-Bot opt-out (for example web-hide style commands) where offered.
- Contact the Operator (section 13) to request access, correction, or deletion of personal data we hold, subject to technical limits (we cannot change Discord’s own databases) and legal exceptions.
If you are in the EEA or UK, you may have rights of access, rectification, erasure, restriction, objection, portability, and the right to complain to a supervisory authority. You may also withdraw consent where processing is consent-based, without affecting earlier lawful processing.
9. Security
We use reasonable measures appropriate to a small bot project: restricted host and database credentials, least-privilege bot invites where practical, and allowlisting for the admin panel. No online service is perfectly secure. You use the Service at your own risk.
10. Children and age-restricted features
The Service is intended only for users who are allowed to use Discord under Discord’s Terms and applicable law (including minimum age rules, often 13+). We do not knowingly collect personal information from children below that age. Some optional operator-only tools may involve adult content; those must only be used in compliance with Discord’s NSFW rules and local law. Contact us if you believe we have data from a child so we can delete it.
11. Automated decision-making
Game systems use automated rules (random rolls, matchmaking, cooldowns, anti-abuse checks). These decisions affect virtual gameplay only, not legal or similarly significant real-world rights.
12. Changes to this policy
We may update this Privacy Policy. The “Last updated” date will change when we do. Continued use after an update constitutes acknowledgment of the revised policy. Material changes may also be mentioned in the Bot changelog or Site when practical.
13. Contact
Privacy questions, concerns, or deletion requests:
- Support server: https://discord.gg/vZrsPCMHys
- Discord: TheFallenStarGG
- Email: DarkstarGaming2326@proton.me
- GitHub: https://github.com/TheFallenStarGG/OverLord-Bot
- Website: https://thefallenstargg.github.io/Overlord-Website/
Related documents: Terms of Service.