Privacy Policy
1. General provisions
This Privacy Policy describes what data the internal Discord bots of the RMRP game project (the “Bots”) process, for what purpose, how it is stored, and how a user can exercise their rights.
- Controller: the RMRP game project team — rmrp.ru (“we”, “us”).
- Scope: the Bots operate only on the RMRP project's internal Discord servers and its game servers (prod0–prod5). They do not process data from unrelated servers or their members.
- Purpose: the Bots were built exclusively for the RMRP game project and are used only for its internal operations. They are not offered to third parties, do not sell services and are not listed in public bot directories.
- Discord's role: messages, profiles and other content live on the Discord platform and are governed by Discord's policies. The Bots use only the official Discord API.
By using the Bots (interacting with their commands, buttons, forms and panels) you confirm that you have read this Policy. If you disagree with it, please do not use the Bots.
2. Bots covered by this Policy
| Bot | Purpose | Where data is stored | Section |
|---|---|---|---|
| RMRP BackUp | Backup and restore of Discord server structure | Our MongoDB database + JSON exports on our servers | 4.1 |
| RMRP Staff | Staff position records: roles, nicknames, operation log | JSON state and log files on our servers | 4.2 |
| RMRP API Google | Technical bridge Google Sheets (Apps Script) → Discord | No database of its own: data passes through | 4.3 |
| RMRP Tickets | Player support ticket system, ratings, dialogue logs | Our MySQL/MariaDB database | 4.4 |
3. General categories of data
| Category | Examples | Source |
|---|---|---|
| Discord identifiers and profile | user ID, username, display name, server nickname, avatar, roles | Discord API, user actions |
| Service attributes of a project member | department, position, rank, in-game static ID and character name, “on leave / blacklisted” status | the Bots' forms and commands, staff actions |
| Content of requests | ticket and message text, attachments and images, selected menu options, ratings | user input |
| Server structure (BackUp only) | channel names and settings, roles and their permissions, bans with reasons, threads, recent channel messages | Discord API on a staff member's command |
| Service metadata and logs | channel, message and role IDs, timestamps, who did what, technical errors | Discord API, the Bots' logs |
The Bots do not process: direct messages (DMs), data from unrelated Discord servers, payment or biometric data, health data, location data, the Presence intent, or voice data.
4. Data per bot
4.1. RMRP BackUp — bot page
| Data | Why | Retention |
|---|---|---|
| Server structure snapshot: channels (names, topics, order, permission overwrites, slowmode), roles (names, colours, icons, permissions), bans (user IDs and reasons) | restoring a server after a failure or an unsuccessful structural change | manual backups — 180 days by default (configurable; 0 disables automatic deletion); interval backups — the last 3 per server |
| Member nicknames and the most recent messages of channels and threads (100 per channel by default, up to 1000; can be disabled) | restoring channel content | together with the backup they were captured in |
| Per-server bot settings, role and ban synchronisation definitions, technical logs | operating the bot's features, diagnosing errors | until the feature is disabled or the bot is removed; logs — up to 7 days |
Data is kept in our MongoDB database (backup documents are compressed) and duplicated as JSON files on our servers. Only authorised project administrators can access backups, and a restore only happens on an explicit administrator command.
4.2. RMRP Staff — bot page
| Data | Why | Retention |
|---|---|---|
| Member IDs with the positions/roles granted to them, position, department, server nickname | granting and revoking staff positions, recalculating roles and nicknames | while the member takes part in the project and as long as the records are needed |
| Operation log: who granted or revoked which position, when, and with what result | internal audit, resolving disputes, recovery after a crash | up to 12 months from the operation date |
| Deferred grants (roles and nicknames for members temporarily absent from the server) | applying the grant once the member returns | 14 days, then the record is deleted |
Data is stored in service JSON files on our servers; technical logs rotate after 14 days and daily backups are kept for 7 days. The bot's local status page is reachable only inside our server and is not published on the internet.
4.3. RMRP API Google — bot page
| Data | Why | Retention |
|---|---|---|
| Texts, embeds and attachments of service messages prepared by project staff in a Google Sheet | publishing and editing service messages in Discord | not stored: written into Discord and returned to the caller (in transit) |
| IDs of the servers, channels, messages, users and roles involved in a request | performing actions: adding and removing roles, changing a nickname, editing a message | not stored (beyond ordinary technical logs) |
| The guild member list (ID, username, nickname, roles, join date) when the corresponding action is called | reconciling staff data between the Google Sheet and Discord | not stored: the result is returned to the caller |
| Images from Google Drive links referenced in a service message | downloading and re-uploading the image so it renders in Discord | not stored after the message is published |
The service has no database of its own and keeps no user profiles — only ordinary technical logs. Its HTTP interface is protected by an access key and by default accepts connections only from the local address of our server. Requests originate from a Google Apps Script automation working with the project's service Google Sheets (see section 8).
4.4. RMRP Tickets — bot page
| Data | Why | Retention |
|---|---|---|
| Ticket author's Discord ID and profile (username, server nickname, account creation date) and a snapshot of their roles at the time of the request | creating the private ticket channel, granting access, identifying the player | while the ticket and its history are needed to handle requests and for analytics |
| Ticket content: message text, attachments, dialogue history, assigned staff member, status, closing time and reason | handling the request, quality control, resolving disputes | up to 12 months from closure, unless a longer period is required to resolve a dispute |
| The rating submitted by the player after the ticket is closed | analytics of the quality of the project's support work | aggregated for analytics; deleted on a user's request |
| Ticket hub configuration and the list of trusted administrators (IDs) | running the system and deploying hubs | until the hub is removed or the bot is disabled |
Closed ticket channels are deleted automatically 3 days after closing (configurable). Ticket histories and workload metrics are kept in our MySQL/MariaDB database. Ticket messages may be mirrored into an internal staff channel or staff server through a Discord webhook so that support work can be reviewed.
5. Purposes of processing
- performing the Bots' service functions: backing up and restoring servers, keeping staff position and role records, handling player requests, publishing service messages;
- granting and revoking Discord roles, updating nicknames, running the ticket system and assigning responsible staff;
- internal auditing of the actions of administrators and project staff;
- keeping the Bots available and secure (error diagnostics, crash recovery).
We do not use the data for advertising, do not build marketing profiles, do not apply automated decision-making with legal effect, and do not sell data to third parties.
6. Legal basis
Processing is based on the user's consent expressed by an action (voluntarily contacting support, participating in the project's processes, using the Bots' interfaces) and on our legitimate interest in operating and accounting for our own game project.
7. Storage and security
- Data is stored on our servers (in our own MongoDB and MySQL/MariaDB databases and in service JSON files); access to those servers is restricted with technical credentials.
- Only the project's technical administrators and authorised staff have access, limited to what their tasks require.
- Data in transit is protected (HTTPS/TLS). The API Google service's HTTP interface is protected by an access key and is not published on the internet.
- Some bot actions are mirrored into internal Discord channels (audit) accessible only to server staff.
- Server structure backups contain member data (nicknames, channel messages) and are protected by the same access rules as the servers themselves.
8. Sharing with third parties
We do not sell or share data with third parties for marketing purposes. Limited sharing is possible only with:
- Discord Inc. — to the extent required for the Bots to work through the official Discord API (without it the Bots cannot function);
- Google (Google Ireland / Google LLC) — only for the RMRP API Google bot: requests are produced by the project's service Google Sheets and Apps Script, and images for service messages may be downloaded from Google Drive links; processing on Google's side is governed by Google's policies;
- our hosting and infrastructure provider — solely to host and maintain the servers the Bots run on;
- where required by law — to respond to a lawful request from a competent authority.
9. Your rights
You have the right to:
- learn what data about you the Bots store;
- request correction of inaccurate data;
- request deletion of your data (the “right to be forgotten”);
- withdraw consent by no longer using the Bots;
- file a complaint with the project's administration.
Requests can be sent to any contact in section 12. We reply within 30 calendar days. To protect the data we may ask you to confirm that the request comes from the account owner. Deleting game data may make it impossible to take part in the project's internal processes (staff records, roles, supplies, support requests).
10. Minors
The Bots are not intended for people below the minimum age for using Discord in their country (usually 13, and higher in some regions). We do not knowingly process their data; if such data comes to our attention it is deleted on request.
11. Changes to this Policy
We may update this Policy. The current version is always available at
https://dis.rmrp-tech.ru/privacy.en.html and the effective date is stated at the top. Material
changes are additionally announced on the project's staff server. Continued use of the Bots after a new version
is published means you accept it.
12. Contact
- Official project Discord: discord.gg/6Az63EPEAA
- Player support (forum): forum.rmrp.ru/forums/pomosch.56
- E-mail: donate@rmrp.ru
- Project website: rmrp.ru
Русская версия: Политика конфиденциальности · Terms of Use