Privacy Policy
Last updated 2026-09-19 · Effective date: 2026-09-18 (previous version: 2026-08-22)
The Internal Conflict Discord app (“the bot”, “we”, “us”) is the official community app for the game Internal Conflict. This policy explains exactly what the bot stores, why, and how you control it. It is written to be honest and specific, not boilerplate. It is not legal advice.
What changed on 2026-09-18. This policy now also covers the features added since the last version: the giveaway, the game-profile link, support tickets, the press-camera queue and the radio queue. The giveaway is the one that changes the shape of this policy, because entering connects your Discord account to an Internal Conflict website account, which does hold an email address. See Giveaways and your game account.
What changed on 2026-08-22. The bot keeps a copy of server message content for 7 days so its deletion log can show what a deleted message said. Before that date it stored no message content at all. See Deleted-message log for exactly what is kept, what is not, and how to be excluded.
Who operates the bot
The app is self-hosted and operated by HappyDale Holding LLC (the Internal Conflict team). Contact: admin@happydale.net, or the Internal Conflict Discord — the same server the bot runs in — at discord.gg/happydale.
What the bot stores
The bot only stores the minimum needed to run its features. Records are keyed by numeric Discord IDs. One feature, the activity log below, also stores your Discord display name alongside your ID so the operator’s audit view is readable.
The bot never asks you for your real name, your phone number or your payment details, and it has no way to read them. Two things do reach past Discord, and both only if you choose them: linking a game account, and entering a giveaway. Both are described under Giveaways and your game account. A third is inherent rather than chosen: stored message text contains whatever a member typed, so if somebody types their own email into a channel, that text is what is briefly stored. Please do not post sensitive personal information — about yourself or anyone else — in a server.
| Data | Where used | Fields |
|---|---|---|
| Server + user IDs | every feature | Discord guild & user IDs (numeric snowflakes) |
| Leveling (XP) | /rank, /leaderboard | XP total and the timestamp of your last counted message, per server |
| Currency (scrap) | /balance, /daily, games, /range | balance and last-daily timestamp, per server |
| Moderation cases | /warn, /timeout, /kick, /ban | action type, the moderator’s ID, an optional reason typed by the moderator, and a timestamp |
| Custom commands | /cc | command name, its responses, and the ID of the staff member who created it |
| War game | /war | your faction, supply, contribution, and timestamps, per server |
| Activity log | operator audit trail | which slash command was used, by whom (Discord ID + display name), in which server, whether it succeeded, a timestamp, and a short summary of the options given, which for moderation commands can include the reason typed by the moderator (truncated) |
| Game profile link | /me rank, the Activity | your callsign, rank, cosmetic XP, an Epic Games id if you linked one, and when the link was made; plus what you own, your loadout and your drill scores |
| Support tickets | /ticket | the thread, your ID, the reason you typed, when it was opened and closed, and who closed it |
| Press camera queue | press cameras | the camera, the in-game callsign, the side, who requested it, and timestamps |
| Radio queue | /radio | which station you asked for and when, per server |
| Giveaway DM ledger | giveaways | the entry ID and your Discord ID, so we DM you about an entry exactly once. See below. |
| Games in progress | casino and card games | your open stake and a daily win tally, so a crashed game refunds correctly |
| Server configuration | /admin, /verify, /serverlog | channel IDs, role IDs, XP rate, welcome text a server sets (no personal data) |
Deleted-message log
Server staff can turn on a log that records when messages are deleted. So that the log can show what was deleted rather than only a message ID, the bot keeps a short-lived copy of message content.
- A rolling 7-day window, with cleanup at startup and every six hours. Message content is excluded from recovery backups; the operator checks cleanup and handles erasure requests.
- Stored: the message text, the filenames of any attachments, the author’s Discord ID, the channel ID, and when it was sent.
- Never stored: direct messages, the attachment files themselves, and messages sent by bots.
- Exemptable per channel. A server admin can exclude any channel, and nothing sent in it is ever recorded. Ask your admin if you want a channel exempted.
- Erasure applies.
/admin forgetuserdeletes your stored message copies along with the rest of your data. - Who can see it: only staff who can read the server’s configured log channel.
Giveaways and your game account
Two optional things connect your Discord account to Internal Conflict’s own website, and it is worth being exact about them because they are the only places the bot reaches past Discord.
- Linking a game account. If you link, the bot asks the website for your callsign, what cosmetics you own and your loadout, using your Discord ID. It does not receive the email address on that account.
- Entering a giveaway. Pressing Enter giveaway gives you a private link valid for fifteen minutes. Signing in on that link is what records the entry, and the entry is stored on the website, not in the bot. That entry row holds your Discord ID, your website account and the email address on it, so that a prize can be sent to a real person. The bot itself keeps only a note that it has already DMed you about that entry.
What the website holds, who it shares it with and how long it keeps it is in the Internal Conflict privacy policy. The terms of a giveaway are in its Official Rules, which also set a minimum age to enter that is higher than Discord’s.
We will never DM you first asking for payment or account details. If a message claiming to be us does that, it is not us.
What the bot does NOT do
It does not read your direct messages. Only messages sent in a server the bot is in are ever stored, and only for the 7-day window described under Deleted-message log.
It does not keep a permanent record of anything you say. Message content outside the 7-day window is removed by the scheduled cleanup described above. It is excluded from recovery backups. If a deleted-message notice has already been posted to a Discord moderation channel, that notice is a separate Discord message controlled by server staff; ask them to remove it as part of an erasure request.
It does not store the files you upload — only their filenames, so a moderator can see what kind of attachment was removed.
It does not collect real names, phone numbers, payment information, IP addresses, or your direct messages. It does not ask for your email address, and the only case where an email address ends up attached to your Discord ID is a giveaway entry, which lives on the website and which you have to choose to make (see Giveaways and your game account). It does not track you across servers for advertising or build a profile of you beyond the per-server feature data above. It does not sell, rent, or share your data, and there are no third-party analytics or ad SDKs.
How the data is stored and secured
Records live in a local SQLite database on a single access-controlled server (an EU-based VPS). The activity log above is additionally copied to a private operator dashboard, gated behind a password and emailed-code two-factor sign-in, run by the same operator (HappyDale) on managed infrastructure, so the operator can review what the bot did. That copy holds the same fields, is not public, is not shared with anyone else, and is deleted on the same 90-day window (see Retention and deletion below for who runs that sweep). The host is hardened (key-only SSH, restricted by a firewall, automatic security updates), the bot runs under an OS sandbox with least privilege, and its Discord token is held in the operating system’s credential store, never in the code or a config file.
Retention and deletion
Operational recovery backups protect other bot records and are rotated. They must not be used to restore erased personal data; erasure requests need to cover recovery copies as well as active records.
Feature data persists while the bot is active in your server so your progress survives restarts.
Activity-log entries are kept for 90 days and then deleted. In the bot’s own
database that happens on a schedule and nobody has to ask. In the operator dashboard copy it is the
same 90-day window, but the sweep is run by the operator rather than by a timer: the
code that performs it ships switched off, and a scheduled run is not enabled today. If you want your
entries removed before that sweep, you do not have to wait for it: ask a server administrator to run
/admin forgetuser, which erases them from both places immediately, or write to
admin@happydale.net.
A server administrator can erase a specific member’s stored data with /admin forgetuser.
This erases it in both places: the bot’s database and the operator dashboard
copy of the activity log. If the dashboard cannot be reached, the command reports the erasure as
INCOMPLETE rather than claiming success, so it can be retried.
/admin forgetuser covers the bot’s own data, and since 18 September 2026 it
covers it completely: the author of any custom command and activity-log rows where you were the
target of somebody else’s command are erased too. One thing is deliberately kept:
your Discord ID where you were the acting moderator on another member’s case record,
because erasing that damages a record other people rely on.
It does not touch anything on the website — not your Internal Conflict
account, your email address, your callsign, your loadout, your purchases, or a
giveaway entry. Those live in the website’s own database and the bot has no
key to it, which is deliberate: a server administrator is not you, and a chat command that could
delete somebody’s game account would be a worse problem than the one it solves. The command
now says all of this to the administrator every time it runs. To erase website data, use
Delete your account on your
account page, or
email the operator from the address on the account. If you want both, ask for both.
Removing the bot from a server, or contacting the operator, will have that server’s data purged
on request. The /purge tool deletes messages from Discord itself. Where the bot holds a
copy under the 7-day window above, that copy is shown in the server’s deletion log and is
deleted with the rest of the window; nothing purged is retained beyond it.
Your choices and rights
You may ask for a copy of the data the bot holds about you, ask for it to be corrected, ask
for it to be deleted, ask us to restrict or stop a particular use of it, or ask for it in a
portable form. Contact a server administrator (who can use /admin forgetuser or
/admin show) or the operator at the address above. Because records are per-server,
requests are handled per server, and we will respond within one month.
If you are in the UK or the EU and you believe we have handled your data wrongly, you also have the right to complain to your national data protection authority. We would rather you told us first so we can put it right.
Legal basis, and who is responsible
Our bot infrastructure includes European hosting. The privacy laws that apply depend on the service and the people it serves, not simply the server location. Where EU or UK data protection law applies, the following describes our purposes and responsibilities.
- Legal basis. Feature data (XP, scrap, war state) is processed to provide the service you asked for by running the command. Moderation records, the activity log and the deleted-message log are processed under legitimate interests — running a safe, accountable community server — balanced against the limits described above: short retention, no content beyond 7 days, per-channel exemption, and erasure on request.
- Who is responsible for what. Each server’s administrators decide whether to switch the deletion log on and which channels are exempt, so they determine how it is used in their server. HappyDale Holding LLC operates the software and the server it runs on. For questions about a specific server, ask its admins first; for the bot itself, contact us.
- Where the data goes. Data is stored in Germany. The operator is a US company, so it is accessed from the United States by the operator for support and maintenance. It is not transferred to anyone else.
If something goes wrong
If a breach affects your data and is likely to be a risk to you, we will notify the affected servers’ administrators and, where the law requires it, the relevant authority, without undue delay.
Children
The bot is intended for Discord users who meet Discord’s minimum age (13+, or older where local law requires). It is not directed at children under 13 and does not knowingly store their data.
Changes
If this policy changes, the effective date above is updated and the current version is kept at
this URL, which is linked from the bot’s Discord App Directory listing and its /botinfo output.
Contact
admin@happydale.net, or the Internal Conflict Discord — the same server the bot runs in — at discord.gg/happydale.