Privacy & Terms

Last updated: 2026-05-06

Dragon Ball Calamity is a small, community-run fan project. The short version: we collect only what's needed to run the game, we don't sell anything, we don't track you across the web, and we'll delete your character on request.

TL;DR. A character file with your password hash, your in-game stats, your chat-channel mute preferences, and (if you linked one) your Discord user ID. That's it. Type delete character in-game to wipe it yourself, or ask us in Discord.

What we collect

Your character data

When you create a character we store a small JSON file on the server with the following fields, all under your character id:

Character name — the one you picked at creation.
Password hash — scrypt with a per-record salt. We never store your raw password and we never see it.
Game state — race, stats, power level, skills, equipment, current planet + grid coordinates, lifetime kill / death / streak counters, dragon ball collection history.
Chat-channel mute preferences — which channels you've toggled off, so they stay muted across sessions.
Linked Discord ID — only if you ran link discord in-game and completed the pairing flow. Cleared by unlink discord.
Admin role — empty for normal players; set to moderator / admin / owner for staff.

Bug + suggestion reports

When you run bug or suggest in-game (or /bug / /suggest in Discord), the text you submit is appended to a server-side append-only log file alongside your character name, the timestamp, and which surface it came from. The same content is mirrored to a Discord channel. Don't put secrets in bug reports.

Cycle history

Every calamity cycle's metadata (id, start time, dominant faction) is persisted to disk forever. This is gameplay history, not personal data — it doesn't reference individual players.

What we do not collect

No real name, no email (unless you choose to email us).
No IP address logging beyond the ephemeral connection logs the OS keeps.
One analytics tool, and it's a polite one: GoatCounter. Cookieless, no fingerprinting, no tracking across sessions. It logs that a page was viewed and roughly where the request came from (country, referrer URL). No Google Analytics, no Facebook Pixel, no ad networks, no behavioral profiling.
No cookies on the marketing site. The web client uses localStorage for command history and chat-mute preferences; both stay in your browser.
No telemetry sent off-server. The Discord bot is the only outbound integration, and it only sees data you explicitly opt into (Discord OOC chat, slash-command invocations, link codes you generate).

Where it lives

All persistent data lives on a single VPS in JSON files under data/players/, data/cycles/, data/leaderboards/, and data/feedback.log. Backups are taken nightly.

Who can see it

The operator (currently a single individual) and any staff with the admin or owner role have shell access to the server and can read raw character files. Players with the moderator role can run a narrow set of admin commands but can't read off-disk data.

Discord-linked accounts add the bot operator to the visibility surface for any Discord side-channel content (slash commands, OOC chat that bridges to the game).

Deleting your character

You control your own data. The fastest path is the in-game command:

delete character — shows a destructive-action warning and the exact follow-up to type. The follow-up is delete character CONFIRM <your-character-name>, which has to match verbatim (case-sensitive). On confirm, the JSON file is unlinked, the world detaches you, and your session closes. There is no recovery — make sure you mean it.

If you've lost access (forgot password, can't log in), ask us in Discord and we'll wipe the file from the server side after confirming the character is yours.

Cycle archive entries are not deleted — they don't reference your name. Bug-report and suggestion entries can be redacted to remove your name; ping us in Discord with the report ID (e.g. bug_2026_007) and we'll handle it.

The terms

Be excellent to each other

No harassment, no slurs, no targeted hostility, no spam. The OOC channel and Discord are moderated by humans; staff can mute, kick, or ban for any of the above. Operator discretion is final.

Play the game, not the server

No automation that issues commands you didn't type — no botting, no macroing the combat tick, no scripts that exploit timing windows. Hand-typed aliases / Mudlet triggers that fire on observed text are fine; software that plays the game while you're afk is not.

Don't try to break things

If you find a security bug, please tell us privately — DM the operator in Discord rather than posting a working exploit in a public channel or in-game OOC. Responsible disclosure earns thanks; weaponized abuse earns a ban.

Fan-project posture

Dragon Ball, Dragon Ball Z, and all related marks are property of Toei Animation Co., Ltd. DBC is a non-commercial fan work with no official relationship to the rights holder. If you represent the rights holder and would like us to take something down, please reach out via Discord (operator handle in the server description) and we'll comply.

Changes to this page

If we change this policy, the "last updated" date at the top will move forward. Material changes will be announced in Discord.

Questions

Type bug or suggest in-game (the report flows to the operator's triage queue) or ping the operator in Discord. We'll get back to you.