PACKET™
Sign in

Terms of Service

Last updated: 2026-11-09 · Packet is in active alpha.

These terms govern your use of Packet ("Packet," "we," "us"). By signing in and using Packet, you agree to them. If you don't agree, don't use the service.

What Packet is

Packet is a Discord bot that runs your community — moderation, leveling and coins, games, game-server status boards, support tickets, alerts, self-serve roles, and voice channels — and can also manage your server's structure (channels, categories, and permissions) as an editable, version-controlled blueprint you apply to your server on demand. Packet is an independent project and is not affiliated with or endorsed by Discord.

Who can use it

  • You must meet Discord's own minimum age and eligibility requirements and comply with the Discord Terms of Service and Community Guidelines.
  • You may only use Packet to manage servers you own or are authorized to administer. You are responsible for having permission to make the changes you apply.

The bot's permissions

To create, edit, reorder, and delete roles, channels, categories, and permission overwrites, the Packet bot requests the Administrator permission when you invite it. This is because structural management touches nearly every part of a server. Packet also uses Discord's Server Members access to assign roles automatically when a member joins (the Role Caller's auto-role feature), and — where a server enables the optional Activity roles feature — Discord's Presence access to assign a member a role based on their current activity (for example a game they're playing, or another app shown in their Discord status), and, where a server uses LFG's status tag, to check a member's custom status for that tag, where a server rewards time spent in a game it picked, to see that a member is playing it, and, where a server runs temporary voice channels, to name a room after the game its creator is playing, and, where a server adds an active-members counter channel, to count who is online, or a counter channel for one game, to count who is playing it. A member can turn all of this off for themselves with /level privacy. Where a server also picks a channel for an activity role, Packet posts a short message there when a member gets that role. It names the member and the game, goes out at most once an hour for each member and rule, and pings no one. It is off unless the server turns it on, and it never names a member who turned this off. Where a server's owner turns on raid protection, Packet also uses its Server Members access to notice a flood of new accounts joining and to hold the accounts that joined during it (by default in a role that can see no channel), or, where the owner chooses, to time out accounts younger than a set number of days when they join. Where a server's admins turn on the optional ticket conversation view, Packet uses Discord's Message Content access to read a ticket channel's messages live, on demand, so support staff can view and reply to the thread from the dashboard, for easy management and record-keeping. It stores none of the content. Where a desk turns them on, closed tickets' transcripts are built from the same access and posted to the server's own channel; Packet keeps no copy. Highlight previews show a highlighted message's text only where the server turns them on and the member allows it in /privacy. Those three, and the short excerpt of a message a member reports to staff (which Discord sends with the report), are the only places Packet shows anyone a member's message. Because Discord grants that access to Packet as a whole rather than channel by channel, other parts of Packet read message text without showing it. When it applies a server structure, it compares a pinned message or forum starter post it created itself against a marker in its own message, so that applying the same setup twice does not post duplicates; that check discards what it reads and keeps nothing. Where a server's admins turn on spam watch, Packet compares each new message's text with the same member's recent messages to catch one message posted in several channels, or again and again in one; it keeps only a short-lived fingerprint, never the text. Where they turn them on, purging messages by what they say, custom commands that answer a message, and the swear jar compare the text, in memory, with words the server chose; they keep none of it, and the swear jar keeps only a count. The Privacy Policy describes each one. Scam-link protection and message filters work inside Discord's own AutoMod, so Discord checks those messages and Packet does not read them. You can remove the bot from a server at any time to revoke its access.

Applying changes — important

Packet makes real changes to live Discord servers. When you apply a blueprint, Packet can create, rename, move, and delete roles, channels, and their contents.

  • Review the preview (the plan / diff) before you apply. You are responsible for the changes you choose to apply.
  • Packet automatically takes a snapshot before an apply where it can, but you should keep your own backups of anything important.
  • Packet is provided "as is," without warranties of any kind. To the maximum extent permitted by law, we are not liable for lost channels, messages, roles, coins, balances, or other data, or for any indirect or consequential damages arising from your use of the service.

Coins, games, and other virtual items

Some servers turn on Packet's optional economy. Members earn by chatting, by being in voice, by claiming a daily or hourly reward, by playing, and in ways a server chooses, such as reactions to their messages, forum posts that make or win the server's poll, time in a game the server picked, or an award from the server's staff. Where a server also turns on games, coins can be wagered on games whose outcome is decided by chance, and in duels against another member. A server can also run its own currency, spent in its own shop. It stays in that server, even when the server runs the shared economy, and every rule below applies to it too. Outside a server, in Packet's Activity, no server chooses. Packet's own settings decide (see The Discord Activity and play outside a server).

Coins are not money, and they never become money.

  • You can't buy them. Packet has no way to take a payment. There is no store, no checkout, no subscription, and no path by which real money becomes coins. Nobody can buy an advantage.
  • You can't cash them out. Coins can't be withdrawn, sold, exchanged for money, or converted into anything outside Packet.
  • You can send them to another member, but only inside Packet. Where a server's admins turn on payments, you can send coins to another member of that server with /economy pay. In a server that runs the shared economy, what you send is shared coins. A server's own currency can be sent too, if its admins allow it, but only to another member of that server. Outside a server, coins move between two people only in a duel for coins (see The Discord Activity and play outside a server). You can't send coins to anyone or anything outside Packet, and you can't sell them or buy them for real money. Packet and a server's admins can limit payments or turn them off. A payment can't be undone.
  • Duels, rewards, and goals. You can wager against another member in a duel, where both of you stake the same amount. A coin flip or rock paper scissors duel is decided by chance. A trivia duel goes to whoever answers correctly first, and if neither of you does, you both get your stake back. Rewards for reactions and awards from a server's staff don't come out of anyone's balance. The server's settings create them. A server can also run a shared goal that members spend toward together. What you put in is spent, not sent. It doesn't reach another member's balance and nobody collects it. If the server's staff cancel a goal before it's reached, Packet puts back what you put in.
  • They have no cash value. Coins and anything you buy with them are virtual items with no monetary value, inside or outside Packet.

What you have is permission to use them, not property. Coins, levels, ranks, streaks, and items bought with coins are a limited, personal license to use a feature of the service. You can't transfer that license, except that you can send coins to another member through Packet where a server allows payments. You don't own them. Packet may change how the economy works, adjust earning and payout rates, or reset balances.

Balances can go away, and you should expect that. Specifically:

  • You can delete your own economy data at any time by running /level privacy in any server. That permanently deletes your coins along with the rest of it. It can't be undone and Packet can't restore it.
  • Coins you earned in a server's own economy are that server's. If Packet is removed from a server, that server's balances are deleted after 90 quiet days. Shared coins belong to no server. They stay in your wallet when Packet leaves a server or a server leaves the shared economy, and you can still spend them on any other server that runs the shared economy, and outside a server.
  • Packet is in active alpha. Features can change, break, or be removed, and that includes the economy.

The games are games. Where a server enables them, the games you wager on are decided by chance, except a trivia duel, which goes to whoever answers correctly first. Packet's house games are built to pay true odds, so the service isn't taking a cut of what's wagered. Some coins are created on purpose when a wager is lost, at a fixed rate, to fund the prize pools. None of this involves money.

What coins buy is up to the server, not Packet. A server's admins decide what appears in their shop, what a role there gets you, and whether it lasts a set time. Packet grants the Discord role, removes it when a timed item runs out, and applies any Packet feature the server ties to that role, such as a faster earn rate. Anything a server promises beyond that is between you and that server.

Don't try to break it. Exploiting a bug to create coins, using extra accounts to claim rewards more than once or to send them to one account, selling coins or buying them for real money, and automating play with scripts or self-bots are all violations of these terms. We may reverse balances, reset an economy, or block an account for any of these.

The shared economy

A server's admins can choose to run Packet's shared economy instead of their own. In a server that does, your coins live in one wallet that works at every server running the shared economy, rather than a separate balance per server.

A few things worth knowing before a server enrolls:

  • In a server, the server chooses, not you. You don't pick a wallet. You play in whatever economy the server you're in is running. Outside a server, you always play with shared coins.
  • Your XP, level, and place on that server's leaderboard don't change. Those stay the server's. The shared economy is about coins. Outside a server, games and some of Packet's quests earn XP toward a global level instead, which no server's own level or leaderboard counts.
  • Packet sets the rates in the shared economy. Earning amounts, bet limits, and payout rates come from Packet rather than from the server's own settings. A server's own settings aren't erased, and they come back exactly as they were if the server switches back.
  • You start with a fresh wallet. Coins you earned in that server's own economy aren't converted. They aren't deleted either. They're still there if the server switches back.
  • You're anonymous on shared leaderboards unless you say otherwise. Run /level privacy to choose.

The same rules in the section above apply to shared coins. They can't be bought, can't be cashed out, and have no cash value. Where a server allows payments, you can send shared coins to another member of that server, only inside Packet. Packet can limit these payments or turn them off across the shared economy.

The Discord Activity and play outside a server

Packet also runs as an Activity inside Discord, where you can play its games. You can open it in a server, or outside one: in a DM, a group DM, or a server Packet is not in. Packet decides who can open the Activity.

  • In a server Packet is in, that server's settings apply, as they do in chat. The server's admins can turn the Activity off there, or open it only to some roles.
  • Outside a server, Packet sets the rules. No server chooses. You play with shared coins, from the same wallet the shared economy uses, at Packet's rates, bet limits, and waits, the same ones a server running the shared economy uses. Your games there count toward the same shared tournament and prize pot. A server's own currency never reaches there.
  • Duels for coins move coins between the two players. Outside a server, a duel for coins (trivia, coin flip, rock paper scissors, mines, tower, or poker) moves shared coins from one player to the other, even if you share no server. It follows the same bet limits as a duel on a server that uses the shared economy.
  • Games and quests there count toward a global level. Most games you finish outside a server earn XP toward your global level, not toward any server's level or leaderboard. Packet's own quests run there too. Depending on the quest, they pay shared coins, XP toward your global level, or a badge.
  • Packet can turn any of it off. Packet can switch off any game, duels for coins, XP, or quests outside a server, or close the Activity, at any time. When Packet switches a game off, a round already in play still finishes.

Everything in Coins, games, and other virtual items applies here too. Shared coins can't be bought, can't be cashed out, and have no cash value.

Features that keep records about members

Some optional features create records about the people in a server. Support tickets record who opened a ticket and how it was handled. Moderation tools record warnings, mutes, isolations, kicks, and bans along with the reason a moderator typed, and, for an isolation, the roles Packet took so it can give them back. Automatic protections a server turns on, such as flood guard and spam watch, record the timeouts they give and the counts that set them off. Raid protection records which accounts it held and the roles it took from them so it can give them back, which staff member started, kept, released or ended their hold or banned them, and the invite most of a raid came through and who made it. A server owner can also keep a ban list of their own, which bans each account on it in the servers they choose. Where a server turns on the ticket conversation view, staff can read and reply to a ticket's messages from the dashboard.

  • These records belong to the server, not to you personally. A server's admins and staff can see them. Deleting your own personal data doesn't remove a server's moderation history, because other admins of that server rely on it.
  • An owner's own ban list belongs to that owner. Only they can see or change it, and they're responsible for who they put on it. Packet doesn't review it.
  • If you run a server, you're responsible for how your staff use them. That includes telling your members what you've turned on where the law requires it, and not using a record to harass someone.
  • Packet isn't the arbiter of a server's moderation. We don't review, reverse, or mediate a server's decisions about its own members. Take it up with that server.
  • Automatic protections can make mistakes. One may time out someone who was only chatting fast, block a message that was harmless, or slow down a channel that was fine. Staff can undo a timeout or end a slow-mode with one click, and every automatic timeout and slow-mode ends on its own.

The Privacy Policy says exactly what each of these stores and for how long.

Information from outside Discord

Some features display live information from a service outside Discord, such as a status board for a game server you run. You give Packet the address, and Packet asks that service for its status on a schedule and posts what comes back.

  • Only add an address you're allowed to query. By adding one you're confirming you own that service or have permission to query it.
  • What's shown is what that service reported. A name, a map, a player count, and similar details are claims the service makes about itself. Packet doesn't verify them and can't guarantee they're accurate or current.
  • Some boards read a public list instead. A game that can't be asked directly, such as Palworld, is looked up in the game's own public server list. What's shown is what that list reports, and a server that isn't in the list reads as unreachable.
  • A board that can't reach a service says so. It won't tell you a service is offline, because a failed query can't tell the difference between a stopped service, a firewall, and a network problem on our side.

YouTube

Packet's YouTube alerts use YouTube API Services to check when a channel goes live. Watch together plays videos in YouTube's own embedded player. It uses YouTube API Services to look up a video's title, length and picture, to read the videos of a YouTube playlist someone adds, and to search YouTube for a song someone types by name. By using a Packet feature that uses YouTube, including watching a video in a watch together room, you agree to be bound by the YouTube Terms of Service. Packet is not affiliated with or endorsed by YouTube or Google. The Privacy Policy says what Packet sends to YouTube and what it keeps.

YouTube's player, its controls and its ads belong to YouTube. Packet does not change, cover or block them, and it never downloads or keeps a copy of any video or its sound.

Watch together is free, and Packet never pays or rewards anyone, in coins or anything else, for watching, adding a video or starting a room. A room can end at any time, and Packet may turn watch together off.

Rewards for voting

Packet is listed on bot-listing sites, and you can run /vote to claim coins for voting for it there. One vote pays once. Repeating the command against the same vote doesn't pay again. Packet may also find your vote on its own and pay it without you running the command.

Those sites are independent of Packet and have their own terms. We can only pay a reward when a site confirms your vote, so if a site is down or changes how it works, a reward may be delayed or unavailable. The Privacy Policy says what we send to those sites and what we get back.

Sharing templates

You can share a template you made with other Packet users in the Community library, and use templates other people shared.

  • You keep ownership. When you share a template, you let Packet store it and show it, and you let anyone who uses Packet use, copy and change it for their own servers, for free. You choose whether your template shows a name or is shared anonymously. You can stop sharing it at any time. Copies other people already made stay theirs.
  • Only share what you have the right to share. Nothing that breaks these terms or Discord's rules: no invite links, ads, scams, hateful or sexual content, and nothing meant to harm a server that uses it.
  • We review shared templates. We look at every shared template before it is listed. We may refuse, hide or remove a template at any time, and we may stop you from sharing. Removing a template never changes a server that already used it.
  • Templates in the library are made by other users, not by Packet. Look at what a template sets up before you apply it. Everything under "Applying changes" applies to them too.
  • Report a problem with the Report button on the template. The person who shared it never sees who reported it.

Acceptable use

Don't use Packet to:

  • break Discord's Terms of Service, Developer Terms, or Community Guidelines;
  • manage a server you aren't authorized to administer;
  • abuse, overload, probe, or attempt to gain unauthorized access to the service or its infrastructure;
  • exploit a bug, or use extra accounts or automated tools, to gain coins, levels, or rewards you wouldn't otherwise get;
  • use Packet's economy or games to run anything that involves real money, real-world prizes, or anything of monetary value;
  • sell or buy coins for real money, or trade them for anything outside Packet;
  • present Packet's coins or games as gambling, as an investment, or as something that can be cashed out;
  • share a template that advertises, scams, or is built to harm the servers that use it;
  • do anything illegal or that harms others.

Images a server uploads to Packet are that server's responsibility, and we may remove an image that is reported to us.

We may rate-limit, suspend, or block accounts or IP addresses that abuse the service.

Availability

Packet is in active alpha. Features may change, break, or be removed, and the service may be unavailable at times. There is no service-level guarantee.

Termination

You can stop using Packet at any time by removing the bot from your servers and signing out. We may suspend or terminate access for abuse or violation of these terms. Some records (such as security/abuse records) may be retained as described in the Privacy Policy. If we terminate your access, or if you delete your data, your coins and other virtual items go with it and aren't refundable, because nothing was paid for them.

Changes to these terms

We may update these terms as the service evolves. We'll update the date at the top when we do; continued use after a change means you accept the updated terms.

Contact