Discord Bot Policy

InviteManager Privacy Policy

This policy explains what the InviteManager Discord bot collects and how bot data is used. Last updated: May 10, 2026.

ReadTerms BackInviteManager

1. Scope This Privacy Policy applies to the InviteManager Discord bot. It does not automatically apply to unrelated LFGPAL website account, Forum, Market, game guide, LFGPAL bot, or StickyPin data. Bot-specific policy

2. Discord Identifiers InviteManager may store Discord server IDs, channel IDs, message IDs, user IDs, role IDs, invite codes, inviter IDs, and related Discord metadata needed to run invite tracking, logs, leaderboards, rewards, diagnostics, and giveaways. Discord IDs and metadata

3. Invite And Join Records InviteManager may store invite cache records, invite use counts, invite source labels, inviter relationships, member join records, member leave records, account creation timestamps, fake invite flags, fake invite reasons, and counted or uncounted tracking status. Invite tracking data

4. Server Settings InviteManager may store join and leave log channels, log message templates, fake invite thresholds, hidden bot settings, private command response settings, leaderboard behavior, blacklists, role rewards, fixed leaderboard message references, and diagnostic state. Server configuration

5. Rewards, Exports, And Giveaways InviteManager may store bonus invite events, reward thresholds, source role mappings, reset archives, giveaway prizes, host IDs, required roles, end times, entry records, and winner selection data needed to run configured server features. Community feature data

6. Message Content InviteManager does not require Discord Message Content Intent for its core tracking. It may store server-provided log templates, giveaway prize text, source labels, and command inputs needed to perform requested actions. Limited text storage

7. Storage And Processing InviteManager uses PostgreSQL for bot operational data. Data may be processed by Discord APIs, hosting infrastructure, and database services needed to run the bot. The website does not copy this operational bot data into D1 during the static information-center phase. Bot database boundary

8. What Is Not Collected InviteManager does not need payment card data, government IDs, account passwords, or Discord bot tokens from users. Bot secrets, Discord tokens, OAuth secrets, database URLs, and API keys must never be placed in frontend code or public repositories. Secret safety

9. Retention And Removal InviteManager data may remain while the bot is installed or until server staff resets, exports, removes, or requests cleanup through an approved process. Removing the bot from a server stops new bot activity there, but existing records may remain until cleaned up. Server-managed data

10. Choices And Controls Server owners and administrators can control whether InviteManager is installed, what permissions it has, which log channels are used, how fake invite checks behave, which rewards exist, which leaderboards refresh, and whether giveaways are created. Server-level controls

11. Sharing InviteManager does not sell bot user data. Some bot outputs, such as logs, leaderboards, exports, giveaway messages, and reward assignments, may be visible to Discord server members depending on server configuration and staff choices. Server visibility

12. Changes And Contact This Privacy Policy may be updated as InviteManager changes. Privacy questions or removal requests should be routed through the server administrator who added InviteManager or through the official LFGPAL support path when one is available. Terms of Service