Privacy Policy

This Privacy Policy explains how Carl Johnson Bot ("we," "us," or "our") collects, uses, and protects information when you use our Discord bot and this website (collectively, the "Service").

By using the Service, you acknowledge the practices described in this policy.

We collect only what is necessary to operate the Bot and this website. The categories below describe what is stored in our database, what is processed temporarily, and what we do not collect.

Discord server data (stored in PostgreSQL)

• Discord guild (server) ID, server name, owner user ID, and member count
• Bot join/leave timestamps and activity timestamps (e.g. last seen)
• Bot status in that server (active, left, unavailable, disabled, or blocklisted)
• Server locale preference (e.g. English or Spanish)
• Optional game server configuration set by a server administrator: platform (SA-MP or MTA), host/IP, port, and server query mode

Usage data (aggregated — no individual user identification)

• Daily aggregated command usage per guild: command name, date, and count
• We do not store which user ran each command

User data (limited)

• Discord user ID only in specific cases: when a command fails and an error is logged, or when authorized staff add a user to a blocklist
• Command cooldowns use user IDs in memory only — they are not saved to the database and are lost when the Bot restarts
• We do not store usernames, display names, avatars, email addresses, or message content

Operational and administrative data (internal)

• Maintenance mode settings (message, activity text, who enabled it, and when)
• Bot presence settings (status/activity configured by authorized staff)
• Blocklist entries (user or guild ID, reason, status, and staff audit fields)
• Technical error logs (see Section 8) — may include command name, guild ID, user ID, error message, and stack trace

Processed but not stored in our database

• Game server query results (SA-MP/MTA via Gamedig): player names, scores, and server info — shown in Discord embeds only and not saved
• Command options typed by users (e.g. a host/IP for a one-off status check) — processed for that request and not stored unless saved through server configuration by a guild administrator
• Discord interaction context needed to reply to a command

Website visits

• This website hosts static legal and informational pages on Vercel. Standard server logs from the hosting provider may include IP address, browser type, and similar technical data for website visits only — not for Discord bot usage
• This website does not use analytics tools at this time

We do not persist channel IDs, role IDs, or Bot response content in our database.

We use collected data to:

• Provide, operate, and maintain Bot features
• Respond to commands and apply server-specific configuration
• Monitor performance, diagnose errors, and prevent abuse
• Communicate support responses and service notices when needed

We do not sell your personal data.

The Bot operates through Discord's API under the permissions granted when the Bot is invited to a server. It uses the Guilds Gateway intent only and does not use the Message Content intent. The Bot does not read channel messages or monitor conversations.

The Bot processes slash commands, modals, autocomplete, and UI interactions required to deliver its features. It is designed for server use only and does not accept direct messages (DMs).

Discord's own privacy practices apply to data handled by Discord. We encourage you to review Discord's Privacy Policy.

Server administrators may configure the Bot for their Discord guild — for example, a default SA-MP or MTA server host, port, and query settings. These preferences are stored so the Bot can apply them on future commands.

Administrators control whether members can query arbitrary game server hosts or only a locked, configured server. Removing the Bot from a server does not automatically delete stored configuration; see Section 10 (Data Retention).

When users or server administrators use server status features, the Bot sends queries to third-party SA-MP or MTA game servers using IP addresses or hostnames provided in a command or saved in server configuration.

Query results — including online player names and server details — may be displayed in Discord temporarily. Those results are not stored in our database, except for optional saved default host, port, and related settings in guild configuration.

Server administrators are responsible for ensuring they have permission to query the game servers they configure or request.

When the Bot encounters a technical error, we may log details such as the error message, stack trace, command name, guild ID, and user ID to diagnose and fix issues.

Authorized staff may review recent errors through internal administrative tools. These logs are used for troubleshooting and service reliability — not for marketing or sale.

Authorized staff may block specific Discord user IDs or guild IDs from using the Bot. A blocklist entry may include the reason, status, and audit metadata about who applied it and when.

If a blocklisted guild adds the Bot, the Bot may automatically leave that server to enforce the block.

We retain data for as long as needed to operate the Service, maintain records, resolve issues, comply with legal obligations, and enforce our policies.

When the Bot is removed from a server, associated data may be retained for a period after removal for operational, security, or legal purposes. Data is not automatically deleted upon removal unless we implement and disclose that process separately.

Guild administrators or users may contact us to request access, correction, or deletion where applicable under their jurisdiction. See Section 11 (User Rights).

The Service relies on third-party providers, including:

• Discord — bot platform and API
• Vercel — website hosting
• Cloud hosting provider (e.g. Railway) — Bot application hosting
• PostgreSQL — database (via our hosting provider)
• Cloudinary — CDN for static catalog and game images (URLs served to Discord; the Bot does not accept user image uploads)
• Third-party game servers — queried via Gamedig when using server status or player list commands

Each provider has its own privacy practices. We encourage you to review their policies where relevant.

Depending on your location, you may have rights to access, correct, delete, or restrict processing of personal data related to you.

To exercise these rights, contact us as described in Section 12 (Contact / Support) below. We will respond within a reasonable timeframe.

For privacy-related questions or requests, reach out through our Support Server or email rramix010@gmail.com.

See also our Terms of Service.