This Privacy Policy explains what personal data Discord.Network collects, why we collect it, how we use and share it, and the rights you have over it. We serve a global audience and aim to honor the protections of the GDPR, the UK GDPR, and the CCPA/CPRA for all users regardless of location.
Data we collect from Discord
When you sign in with Discord (OAuth), Discord shares the following data with us based on the scopes you authorize:
- Discord user ID — your unique account identifier;
- Username — your Discord username;
- Global (display) name — your chosen display name;
- Avatar — your profile image reference;
- Email address — the email associated with your Discord account;
- Guild list — the list of Discord servers you belong to, used to verify that you can manage a server you wish to list.
Purpose and legal basis
- Account creation and authentication (Discord ID, username, global name, avatar) — to operate your account. Basis: performance of a contract.
- Verifying server ownership (guild list) — to confirm you may list and manage a given server. Basis: performance of a contract.
- Transactional communication (email) — receipts, security and service notices. Basis: contract and legitimate interest.
- Security, fraud prevention, and abuse moderation. Basis: legitimate interest and legal obligation.
- Running the Network bot (Discord user and server IDs, and the records described in Discord bot (Network)) — to provide the features a server’s managers turn on. Basis: legitimate interest.
Discord bot (Network)
Discord.Network also operates Network, a Discord bot. A server’s owner, or a member with the Manage Server permission, adds it to a server and chooses which of its plugins to turn on from our web dashboard. This section explains what the bot can access, what it keeps, and for how long. It applies to everyone in a server that uses the bot, whether or not they have a Discord.Network account.
What the bot can access
The bot only receives information from servers it has been added to, and only from channels Discord lets it see. A plugin acts on that information only in servers where it is turned on (the Directory plugin, which handles /bump and the server’s listing, is always on). Discord treats two kinds of access as privileged (“privileged intents”), and features that need one only run while Discord grants it to the bot:
- Server Members tells the bot when members join or leave a server and when their roles, nickname or membership-screening status change. It is used by Welcome (welcome, direct-message and goodbye messages), Auto Roles (roles on joining or after membership screening), Server Logs (join and leave entries, and on Network Pro role and nickname changes). The bot also uses it to keep the member count on a server’s Discord.Network listing current and to notice changes to its own roles.
- Message Content lets the bot read the text, embeds and attachments of messages. It is used by Auto-Moderator (checking new and edited messages against the filters the server turned on), Custom Commands (prefix commands such as
!rules; the/cslash command works without it), Server Logs (on Network Pro, the text of edited and deleted messages), Starboard (copying a starred message’s text and images into the starboard post) and Tickets (on Network Pro, an optional transcript when a ticket is closed). Leveling awards XP for sending messages but does not read what they say.
The bot does not use Discord’s Presence intent, so it never sees an individual member’s online status or activity, and it never requests a server’s full member list. Its other features use standard information Discord sends to bots: slash commands and button clicks, reactions (Starboard), bans (Moderation and Server Logs), channel changes (Tickets, and Server Logs on Network Pro) and, on Network Pro, voice-channel joins and leaves (Server Logs).
What is processed but not stored
Message text is handled as it arrives and is not saved in our database:
- Auto-Moderator checks each message and keeps nothing from it except the short detail recorded in a moderation case (see below). When it removes a message, it may post a copy of the text to the log channel the server chose, so the server’s moderators can review it.
- Server Logs posts edits and deletions, including the earlier text, to the server’s log channel. To know the earlier text, the bot holds up to the 200 most recent messages of each channel in memory. This cache is never written to our database and is cleared whenever the bot restarts.
- Starboard posts a copy of a starred message to the server’s starboard channel. We store only IDs and the star count.
- A ticket transcript is created when the ticket is closed and posted as a file to the server’s ticket log channel. We don’t keep a copy.
- Text given to a custom command is used to build its reply and then discarded.
Anything the bot posts into a server becomes an ordinary Discord message, stored by Discord and controlled by that server’s moderators.
What the bot stores
We store the following, each tied to the Discord server it came from. People are identified by their Discord user ID.
- Settings — which plugins are on and how they are configured (channels, roles, message templates, blocked words and so on), as entered by the server’s managers, plus a snapshot of the server’s name, icon, owner’s user ID, member count and the bot’s permissions for the dashboard.
- Directory — when someone uses
/bump, a basic Discord.Network account record (Discord user ID, username, display name and avatar) and a record of the bump, so that bump limits apply. - Moderation and Auto-Moderator — a numbered case for each warning, timeout, kick, ban and unban: the member’s and the moderator’s user IDs and usernames, the reason, any duration, and the time. For automatic cases the reason names the filter and a short detail: the blocked-word entry that matched, the invite links or website domains found, or a measurement such as the share of capital letters or the number of emoji, mentions or messages. The rest of the message is not stored.
- Leveling — each member’s XP, level, the number of messages that earned XP, when XP was last earned, and their display name and avatar at that time (for the leaderboard).
- Giveaways — the prize and description, the host’s user ID, the end time, the winners, and the user ID of everyone who entered.
- Tickets — each ticket’s number and thread, who opened and who closed it, the close reason, and the times. Not the conversation.
- Starboard — for each starred message, its ID and channel, the author’s user ID, the star count and the ID of the starboard post. Not the message text.
- Custom Commands, Role Panels, Timed Messages and Social Alerts — what the server’s managers wrote (responses, panel text, scheduled and alert messages), the YouTube channels or Twitch usernames to follow, and run status. Custom Commands also counts how often each command is used.
Welcome and Auto Roles store nothing beyond their settings.
Who decides how it’s used
A server’s owner and members with the Manage Server permission decide which plugins run and how. They can see that server’s moderation cases, tickets, giveaways and leaderboard in our dashboard; our support staff can view the same information, read-only, to help with problems. Members can’t turn plugins off for themselves. If you don’t want a server’s bot features to apply to you, ask that server’s managers, leave the server, or contact us.
Leveling can publish a leaderboard web page that shows ranked members’ display names, avatars, levels and XP. It is off unless a server’s managers turn it on; once published, anyone with the link can see it and search engines may index it. Managers can take it down at any time, and can stop chosen channels or roles from earning XP.
How long it’s kept, and deleting it
- Turning a plugin off stops it from acting. Its settings and the records it created are kept, so turning it back on picks up where it left off.
- Removing the bot from a server stops it receiving anything from that server. We delete the server snapshot described above, and the server’s public leaderboard page goes offline. The server’s settings and records are kept for 30 days so that adding the bot back restores them; after that we delete them automatically (billing records for Network Pro are kept as described under Payments). The server’s owner can ask us to delete them sooner.
- Server managers can delete a member’s XP or the whole leaderboard, custom commands, role panels, timed messages, alert feeds and ticket panels, and can cancel a running giveaway along with its entries. A starboard record is deleted when the original message is deleted. Moderation cases, ended giveaways and closed tickets stay in the server’s history: case reasons can be edited, but cases can’t be deleted from the dashboard.
- Leaving a server doesn’t delete what the bot stored about you there.
- Deleting your Discord.Network account anonymizes your website account but doesn’t remove the records servers keep about you through the bot, because those are tied to your Discord user ID rather than to your account.
To ask us to delete bot data about you or about your server, email [email protected] or use our Contact page. Include your Discord user ID, and the server ID if the request is about one server. We will verify the request and respond within the timeframe required by applicable law.
Sharing and other uses
- We don’t sell data the bot receives, including message content, and we don’t share it with anyone except as this policy describes.
- We don’t use it to train artificial-intelligence or machine-learning models, don’t send it to AI services, and don’t use it for advertising or profiling. We use it only to run the bot’s features for the server it came from, including keeping that server’s Discord.Network listing up to date.
- The bot doesn’t send message text to anyone outside Discord; it only posts it back into the same server.
- Social Alerts checks YouTube’s public video feeds and Twitch’s API for the channels a server follows. Only the YouTube channel ID or Twitch username is sent to them, never Discord data.
Payments
Paid subscriptions are processed by Stripe, our payment processor. Stripe collects and processes your payment details directly. We never receive or store your full card number, CVC, or other complete card data. We retain limited billing metadata (such as subscription status, plan, and the last four digits or card brand surfaced by Stripe) to manage your subscription. Stripe’s handling of your data is governed by Stripe’s own privacy policy.
When you buy Network Pro for a server, Stripe also receives the server’s name and ID so the subscription is attached to the right server.
Sub-processors
We share data with the following service providers to operate:
- Discord — authentication and OAuth identity data, and the platform the Network bot runs on;
- Stripe — payment processing and subscription billing;
- Hosting and edge/CDN providers (including Cloudflare) — application hosting, delivery, and security.
International data transfers
Our providers may process data in countries other than yours, including the United States. Where required, such transfers rely on appropriate safeguards such as the EU Standard Contractual Clauses or equivalent mechanisms offered by those providers.
Data retention
We keep your account data for as long as your account is active. If you delete your account, we remove or anonymize your personal data within a reasonable period, except where we must retain certain records (for example, billing and transaction records) to comply with legal, tax, or accounting obligations. Data the Network bot keeps for Discord servers follows the rules in Discord bot (Network).
Your rights (GDPR / UK GDPR)
If you are in the EEA or UK, you have the right to access, rectify, and erase your personal data, to receive a portable copy, to restrict or object to certain processing, and to withdraw consent where processing is based on consent. You may also lodge a complaint with your local supervisory authority.
Your rights (CCPA / CPRA)
If you are a California resident, you have the right to know what personal information we collect, to access and delete it, and to correct inaccuracies. You also have the right to opt out of any “sale” or “sharing” of personal information. We do not sell your personal information, and we do not share it for cross-context behavioral advertising. We will not discriminate against you for exercising any of these rights.
How to exercise your rights
To make any privacy request, email us at [email protected] or use our Contact page. We will verify your request and respond within the timeframe required by applicable law.