PRIVACY POLICY — UNOFFICIAL C-OPS BOT

SECTION 01

WHO WE ARE

This bot is developed and maintained as an unofficial community project for Critical Ops players. The bot is operated independently, and data collected by it is processed through a privately hosted backend API server.

If you have any questions about this policy or wish to request deletion of your data, you may reach out to the bot developers through the official support server.

SECTION 02

DATA WE COLLECT — ESSENTIAL (ALWAYS COLLECTED)

The following data is collected as a fundamental part of how the bot operates. Most of it is passed to us directly by Discord when you interact with the bot.

2.1 — DISCORD USER ID

Your Discord account's unique numeric identifier is collected whenever you run any command. It is used to associate your economy balance, inventory, moderation history, and game profile with your account. This data is stored in our backend API database.

2.2 — COMMAND USAGE METADATA

When any slash command is executed, the bot logs the command name, the user who ran it (by Discord ID and display name), and a timestamp.

2.3 — ERROR REPORTS

When a command triggers an unhandled error, the bot automatically captures and forwards an error report to developer channels. That report includes the command name, your Discord ID, your global display name, and a technical traceback. This is used solely for debugging purposes.

2.4 — ECONOMY ACCOUNT DATA

If you use any economy-related command (such as /balance, /daily, /shop, or /inventory), the following gets stored or retrieved from the backend:

Your Discord User ID
Your currency balance (current amount)
Your item inventory (item names, item types, and quantities)
Any balance changes resulting from daily rewards, purchases, or sales

These records are kept indefinitely unless a deletion request is submitted.

2.5 — MODERATION LOGS (PER-SERVER)

When a moderation action is taken against you in a server that uses this bot, the following is recorded and stored in the backend:

Your Discord User ID
The server (guild) ID where the action occurred
The moderator's Discord User ID
The type of action (ban, unban, kick, mute, or warn)
The reason provided by the moderator
Duration (for mutes — stored in seconds)
A timestamp of when the action was issued

These logs are retrievable by moderators and bot administrators and are kept indefinitely. Each action is assigned a unique case ID.

SECTION 03

DATA WE COLLECT — OPTIONAL / ON-DEMAND

This section covers data that is only collected or processed when you explicitly use specific features of the bot.

3.1 — CRITICAL OPS GAME PROFILE DATA

If you use /viewprofile or /link, the bot queries the Critical Ops public API (https://api-cops.criticalforce.fi) using an in-game username. The following game data is fetched and temporarily displayed:

In-game username and internal Critical Ops user ID
Player level and XP progress
Ranked and casual statistics (kills, deaths, K/D ratio)
Per-season performance data
MMR (matchmaking rating) and global rank position
Current rank tier and placement matches remaining
Active ban status (if any), including reason and duration
Clan name, clan tag, and your role within the clan

This data is fetched live from Critical Ops servers and is not stored by this bot unless you use the /link feature (see 3.2 below). The Critical Ops API is a public endpoint and subject to Critical Force Ltd.'s own privacy policy.

3.2 — PROFILE LINKING

The /link command creates a permanent association between your Discord User ID and your Critical Ops in-game account ID. This mapping is stored in our backend and is used to let others look up your profile by mentioning you on Discord. You can remove this link at any time using /unlink, which permanently deletes the record from our system.

3.3 — CASE OPENING DATA

When you open a case (/inventory → use item), the bot generates a random skin result and records it in your inventory. The resulting item name, its type ("skin"), and quantity are stored in the backend under your Discord User ID.

3.4 — SHOP TRANSACTIONS

Each time you buy or sell an item through the /shop command, the bot updates your balance and inventory in the backend. No detailed transaction history log is maintained beyond the resulting balance and inventory state.

SECTION 04

DATA COLLECTED AT THE SERVER (GUILD) LEVEL

If a server administrator has configured the bot's moderation logging features, the bot may collect and relay the following information to designated log channels within that server. This data is not stored in the bot's backend — it is sent to channels controlled by the server's administrators.

4.1 — MESSAGE DELETE LOGS

When a non-bot message is deleted in a monitored server, the bot posts an embed to the server's configured message log channel containing:

The deleted message's full text content (truncated at 1,024 characters)
The author's Discord ID, display name, and avatar
The channel where the message was posted

The bot does not store this content in its own database. Once sent to the log channel, it is held by Discord under Discord's own data retention rules.

4.2 — MESSAGE EDIT LOGS

Similarly, when a message is edited, both the original and the new content are posted to the message log channel. The same applies regarding storage — the bot does not retain this data itself.

4.3 — MEMBER JOIN AND LEAVE LOGS

When a member joins or leaves a server where the bot's user logging is configured, the bot posts an embed with:

The member's Discord User ID and mention
Their account creation date
Their server join date
Their avatar

4.4 — BAN LOGS

When a member is banned, the bot logs their ID, display name, avatar, and (where available from Discord's audit log) the reason for the ban. This is sent to the server's user log channel.

4.5 — SERVER CONFIGURATION

To enable moderation logging, server administrators provide the IDs of two channels (a user log channel and a message log channel). These channel IDs, along with the guild ID, are stored in the backend. Administrators can delete this configuration at any time using the /deleteconfig command, which removes all records for that server.

SECTION 05

DATA WE DO NOT COLLECT

To be clear about the boundaries of what this bot does and does not access:

We do not read or store messages that were not deleted or edited.
We do not monitor voice channels or collect voice-related data.
We do not access your email address, phone number, or password.
We do not collect payment information of any kind.
We do not track your activity on other Discord servers.
We do not sell, trade, or share your data with any third party beyond what is described in this document (i.e., queries to the public Critical Ops API when you voluntarily use game-related commands).

SECTION 06

HOW DATA IS STORED AND SECURED

All economy, moderation, and profile linking data is processed through a privately hosted backend API server. Communication between the bot and the backend is authenticated using a rotating token.

Local server logs (the .log files) are stored on the machine running the bot and are organized by date. Log entries are limited to command names, API endpoint paths, HTTP status codes, timestamps, and error identifiers. User IDs, usernames, query parameters, and API response bodies are not written to log files. These logs are not encrypted at rest. There is currently no automated log rotation or expiration policy.

SECTION 07

DATA RETENTION

Economy balances and inventories: Kept indefinitely.
Moderation logs: Kept indefinitely unless a case is manually deleted by a moderator with sufficient permissions using the /deletecase command.
Profile links: Kept until you run /unlink.
Local log files: Kept on disk indefinitely (no rotation policy in place).
Server configurations: Kept until a server administrator runs /deleteconfig.
Message/member event data: Held in Discord's own infrastructure once posted to log channels; the bot does not retain copies.

SECTION 08

YOUR RIGHTS

Depending on where you are located, you may have certain rights under applicable privacy laws (such as GDPR or CCPA). Regardless of jurisdiction, we aim to honor the following:

Right to Access: You can request a summary of the data we hold about you.
Right to Deletion: You can request deletion of your economy data, moderation history, or profile link. Note that moderation logs may be retained by server administrators independent of any request made to us directly.
Right to Correction: If your data is inaccurate, you can request that it be corrected.
Right to Object: You can object to specific types of data processing by simply not using the features that require it (e.g., not using /link if you do not want your game account associated with your Discord ID).

To exercise any of these rights, contact the bot developers via the support server or through direct message to one of the listed developers.

Note: Some data, particularly moderation logs, may be outside our ability to fully delete if the server where an action occurred retains independent records.

SECTION 09

THIRD-PARTY SERVICES

This bot interacts with the following third-party platforms:

9.1 — DISCORD

The bot runs on the Discord platform and is subject to Discord's own Terms of Service and Privacy Policy, available at discord.com/privacy. Discord provides us with user and guild data through their API when commands are invoked.

9.2 — CRITICAL FORCE LTD. (CRITICAL OPS API)

When game-profile features are used, the bot makes requests to the public Critical Ops API to retrieve player statistics and profile data. This data is handled according to Critical Force Ltd.'s own privacy terms. We do not have a data sharing agreement with Critical Force Ltd.

9.3 — OUR BACKEND API

Data is passed to and stored in a privately operated backend API server. This server is not affiliated with Discord or Critical Force Ltd. and is maintained solely by the bot's development team.

SECTION 10

CHANGES TO THIS POLICY

This policy may be updated from time to time as the bot gains new features or as legal requirements change. The date at the top of this document reflects the most recent revision. Significant changes will be announced in the bot's official support server where possible.

Continued use of the bot after an update to this policy constitutes acceptance of the revised terms.

SECTION 11

CONTACT

If you have questions, concerns, or data requests related to this privacy policy, please reach out through the official support server or contact the developers directly on Discord.

BOT DEVELOPERS — VYPER, NAIGEL, MALLE