Privacy Policy
A plain-language rundown of what Shockwave collects, why, and how to get it deleted. Last updated August 21, 2026.
What Shockwave collects
Everything below comes directly from the commands you or your server run. Nothing is collected passively or in the background.
| Data | Where it comes from |
|---|---|
| Discord IDs & names | Server (guild) ID and name, channel IDs/names you configure, and the Discord user ID and display name of anyone whose commands or button presses the bot processes. |
| Team & roster data | Rosters built with /make-teams, /captains,
persistent teams from /team-create: names, captains, and members. |
| Competitive stats | Elo rating, win/loss record, and betting record. Tracked per-server, never shared across servers. |
| In-app currency | A fictional gold balance and wager history (see the Terms of Service, it has no real-world value). |
| Tournament data | Brackets, registrations, and match history for servers running /tournament-create. |
| Team logo choice | Which built-in logo (see /team-set) was picked.
No user-uploaded images are collected. |
| Role preferences | Which lanes you've marked as liked or disliked via /setup, used
for role-aware team balancing. |
| Trading card & achievements | Your equipped card title, color scheme, and font (/card-set),
which cosmetics you've unlocked or bought (/shop-buy), and which
achievements you've earned. |
What Shockwave does not collect
- Message content: Shockwave only ever sees the slash-command inputs Discord delivers directly to it, never the rest of a channel's chat.
- Voice audio: The bot moves people between voice channels; it never joins a call, listens to, or records anything spoken in one.
- Email addresses, real names, phone numbers, or payment information: Discord doesn't expose these to bots, and Shockwave never asks for them.
- Direct-message content: the only DM Shockwave ever sends is a one-time voice-channel
invite link via
/notify, and it doesn't read DMs sent to it.
How this data is used
Solely to run the feature you invoked: forming and announcing teams, moving voice channels, tracking elo/records, settling bets in the fictional-gold economy, and playing out tournament brackets. It's never used for advertising, profiling, or anything outside what's documented on the command reference.
Storage & retention
Data lives in a database maintained by whichever operator's instance you're using. There's no central, project-wide database shared across every server running Shockwave.
Removing the bot from a server deletes that server's live session/configuration state
automatically. Historical records tied to that server (i.e., past game results, elo, team rosters,
tournament history) are not automatically erased
when the bot is removed; they persist until an admin clears them or the operator purges them
directly. A server admin (Manage Server permission) can wipe this data at any time with
/clear, see its
clear_tournament, clear_elo, and
clear_economy options for exactly what each one erases.
The reference instance also keeps its own automatic daily database backup, retained for 7 days
before being deleted. Data cleared with /clear can still exist in one
of these backups for up to a week afterward, even though it's gone from the live database
immediately. A self-hosted instance may keep backups on the same schedule (see the
self-hosting guide) or a
different one entirely, depending on how its operator has configured it.
Sharing
Shockwave does not sell or share the data above with third parties. It's necessarily visible to Discord itself (governed by Discord's own Privacy Policy), and to the administrators/members of any server the bot occupies, since team, bracket, and economy data is posted directly into that server's own channels as part of how the features work.
Children's privacy
Discord requires users to meet its own minimum age requirement. Shockwave doesn't independently verify age and relies entirely on Discord's own enforcement of that requirement. It does not knowingly collect data from anyone who doesn't meet it.
Self-hosted instances
Anyone can run their own copy of Shockwave (see the self-hosting guide). If the instance in your server isn't operated by this project's maintainer, that operator controls the database, decides how long data is kept, and is who you should contact about it. This policy describes what the software itself does with data, not what any specific third-party operator chooses to do beyond that.
Your choices & requesting deletion
The fastest path is /clear (Manage Server permission). It can wipe
channel config, the tournament, elo, or the entire economy for your server immediately. For
anything that doesn't cover, contact the operator of your server's Shockwave instance directly.
For the project's own reference instance, open an issue on
its GitHub repository, or send an email to shockwavelolbot@gmail.com
Security
Reasonable technical measures are used to protect stored data, but no method of storage or transmission over the internet is completely secure. Shockwave makes no guarantee of absolute security of your data.
Changes to this policy
This policy may be updated as Shockwave's features change. The "last updated" date at the top of this page always reflects the current version.