bronx · privacy policy

1. data we collect

all data is keyed by your discord user ID (a numeric snowflake). we store gameplay and preference data only — never personal identity information.

economy & gameplay

data type	what's stored	why
economy balances	wallet, bank, bank limit, net worth, loan info	core economy system
fishing data	catches, active gear, autofisher state, fish ponds	fishing system progression
gambling stats	games played, total bet/won/lost per game type	stats display and leaderboards
inventory	items, rods, bait, tools, pets, mining claims	item ownership tracking
progression	XP, level, skill points, prestige, daily streaks	leveling and progression systems
challenges	daily challenge assignments and completion status	daily challenge system
marketplace	bazaar shares, trade history, wishlist	trading and marketplace

usage & moderation

data type	what's stored	why
command usage	which commands you run, when, and in which guild	anti-abuse detection, dashboard analytics
cooldowns	per-command cooldown timestamps	rate limiting gameplay commands
moderation flags	blacklist/whitelist status, anti-cheat records	abuse prevention
preferences	custom prefixes, passive mode, AFK status	user customization
submissions	bug reports and suggestions you voluntarily submit	community feedback

server-specific data

if a server has server economy enabled, a separate copy of economy data is maintained per-guild. this includes balances, inventory, fishing data, and gambling stats scoped to that server.

dashboard events

when the bot is in a server and the dashboard is active, we track aggregated server activity:

member join/leave events (user ID + guild ID + timestamp)
message event counts (user ID + channel ID — not message content)
command usage per channel per day
voice join/leave events
boost events

2. data we don't collect

we never store the following

this data is never written to our database or persisted anywhere.

data	status	notes
usernames / display names	never stored	fetched live from discord API when rendering embeds
nicknames	never stored	resolved from discord's guild member cache at runtime
avatar images / URLs	never stored	fetched from discord CDN when needed for embed footers
email addresses	never stored	we don't request the email OAuth2 scope
IP addresses	never stored	server logs may transiently contain IPs but they're never persisted to our database
message content	never stored	the bot reads messages for command prefixes only — content is never logged or saved
DM content	never stored	DMs are only used for captcha verification and notifications
voice audio	never stored	we only track join/leave events for dashboard stats

3. how data is stored

all data is stored in a MariaDB database. the database connection uses TLS encryption for remote connections.

primary key: discord user ID (numeric snowflake) — this is the only identifier linking data to your account
database host: self-hosted or Aiven cloud (with TLS)
connection pooling: connections are pooled and reused — credentials are never exposed to end users
no PII in database: the database contains zero personally identifiable information beyond your discord user ID

4. encryption & security

identity data encryption

when identity data (username, nickname, avatar hash) needs to be temporarily cached for display purposes, it is:

encrypted using AES-256-CBC before being written to the database
stored with a unique initialization vector (IV) per record
set to automatically expire after 30 days
purged on a regular schedule — expired entries are permanently deleted

encryption details

encryption keys are managed server-side and are never exposed to clients. the encryption key can be rotated without data loss. all cached identity data is encrypted at rest and decrypted only when needed for display.

transport security

database connections to remote hosts use TLS/SSL
the dashboard website uses HTTPS
discord API communication uses HTTPS exclusively
OAuth2 tokens are stored server-side in encrypted sessions

anti-abuse system (BAC)

the bronx anti-cheat system (BAC) monitors command timing patterns to detect automation. this data is:

stored in memory only — never persisted to disk or database
limited to the last 12 command timestamps per user
cleared when the bot restarts or when a user passes a captcha

5. dashboard & website

authentication

the dashboard uses discord OAuth2 with the following scopes:

identify — your user ID, username, avatar, and discriminator
guilds — list of servers you're in (to show ones where you have manage permissions)

we do not request the email, messages.read, or guilds.join scopes.

session data

your discord identity (ID, username, avatar) is stored in a server-side session
sessions expire after 24 hours
session data is stored in server memory — not in a database or on disk
session cookies are httpOnly and sameSite: lax

API data exposure

the dashboard API exposes:

your servers: only servers where you have manage/admin permissions AND the bot is present
server stats: aggregated message counts, command usage, active users — no individual user data
member lists: fetched live from discord API (cached 30 seconds) — not from our database
economy data: user search shows user_id, wallet, bank, last_active — no usernames or personal info

owner-only endpoints

certain API endpoints (blacklist management, suggestions, badge grants) are restricted to the bot owner only. these endpoints require both authentication and owner verification.

6. third-party services

bronx interacts with the following third-party services:

discord API — for bot functionality, OAuth2 authentication, and fetching user/guild data. governed by discord's privacy policy
Aiven (optional) — cloud database hosting with TLS. data is stored in Aiven's infrastructure when the remote database is configured

we do not use analytics services, advertising networks, or any other third-party data processors.

7. data retention

data type	retention
economy & gameplay data	retained until you opt out or request deletion
command usage logs	retained indefinitely for abuse detection
encrypted identity cache	automatically deleted after 30 days
dashboard sessions	automatically deleted after 24 hours
anti-cheat (BAC) data	in-memory only — cleared on restart
aggregated server stats	retained per-guild while the bot is in the server

8. your rights & opt-out

you have full control over your data. here's what you can do:

opt out of data collection

you can completely opt out at any time. this will:

permanently delete all your data across all tables (economy, fish, stats, inventory, everything)
block all commands — the bot will not process or respond to any of your commands
stop all data collection — no new data will be recorded about you

how to opt out

use the privacy command in any server where bronx is present:

b.privacy optout or /privacy optout

you'll be asked to confirm before any data is deleted.

opt back in

if you change your mind, you can opt back in at any time:

use b.privacy optin or /privacy optin
your previous data cannot be recovered — you'll start with a fresh account
all bot commands will work again immediately

view your data

you can see what data the bot has about you:

b.privacy info — summary of what data types are collected
b.bal — your economy balances
b.profile — your profile and stats
b.inv — your inventory
b.stats — your gambling and gameplay statistics

data deletion requests

the b.privacy optout command handles complete data deletion automatically. if you need assistance or have questions about your data, you can also contact us through our support server.

important: opt-out is irreversible

once you opt out, all your data is permanently deleted from our database. this includes economy balances, fish catches, gambling stats, inventory, XP, daily streaks, and everything else. this cannot be undone.

9. children's privacy

bronx does not knowingly collect data from users under 13 years of age. discord's own terms of service require users to be at least 13 (or the minimum age in their country). if you believe a child under 13 is using the bot, please contact us so we can delete their data.

10. changes to this policy

we may update this privacy policy from time to time. significant changes will be announced in our support server. the "last updated" date at the top of this page will always reflect the most recent revision.

11. contact

if you have questions about this privacy policy or your data:

join our support server and open a ticket
use b.privacy in any server to manage your preferences
view the source code on github