Privacy Policy

Effective date: August 11, 2026 · Last updated: October 12, 2026

1. Introduction

This Privacy Policy explains how Guardians RPG (“Guardians RPG,” “the Application,” “the Bot,” “we,” “us,” or “our”) collects, uses, stores, and shares information when you interact with the Guardians RPG Discord application or visit https://guardiansrpg.com.

Guardians RPG is operated by:

• Operator: Maximiliano Marino
• Country: AR
• Contact email: contact@guardiansrpg.com
• Discord Application ID: 1465051746861711460

By using the Application, you acknowledge the practices described in this Privacy Policy. If you do not agree with this Policy, you should discontinue use of the Application.

2. Scope

This Privacy Policy applies to information processed through:

• The Guardians RPG Discord bot.
• Commands, buttons, select menus, modals, and other Discord interactions.
• RPG profiles, multiplayer sessions, events, and community features operated by the Application.
• The Guardians RPG website, authenticated game interfaces, and shared combat chats.
• Support and data-related requests sent to us.

Discord separately processes information under its own privacy policy. We do not control Discord’s independent processing of your information.

3. Information We Collect

3.1 Discord account information

When you use the Application, we may receive and store information supplied by Discord, including:

• Your Discord user ID.
• Your username, display name, and other public Discord profile information.
• Your interactions with the Application.
• Role and permission information when necessary to authorize a command or feature.
• Information about the Discord server in which an interaction occurs.

We use Discord IDs to associate your Discord account with your Guardians RPG game profile. Discord sign-in supplies the public identity needed to link your account. We do not request access to your email address or ask you for your Discord password, account token, or other private login credentials.

3.2 Discord server and channel information

To operate the Application, we may process and store:

• Discord server IDs.
• Channel and thread IDs.
• Role IDs.
• Message IDs associated with game panels, events, lobbies, and messages relayed through shared combat chat.
• Server-specific configuration.
• Permissions relevant to the use or administration of the Application.

The Application does not request complete server member lists and does not use the privileged Guild Members Intent.

3.3 Game profile and progression data

Guardians RPG is a persistent multiplayer RPG. We may store information such as:

• Character attributes, level, experience, health, and combat statistics.
• Inventory, equipment, weapons, consumables, companions, and collectibles.
• In-game currencies and transaction history.
• Quest, mission, achievement, dungeon, raid, and event progress.
• Clan membership, clan roles, diplomacy, territories, and contributions.
• Tournament, leaderboard, battle, and seasonal results.
• Cooldowns, reward eligibility, and daily activity progress.
• Player-selected names, titles, loadouts, and other custom game settings.
• Records needed to restore interrupted multiplayer sessions or resolve support issues.

This data is associated with your Discord user ID so your progress can persist between sessions.

3.4 Message content and shared combat chat

When message content is available through Discord, the Application may process it to recognize commands and arguments, distinguish commands from other messages, apply activity-validation and repeated-text checks, and detect configured narrative phrases. Some gameplay features can operate through mentions, interactions, or message metadata without access to ordinary message text.

Supported multiplayer sessions connect the conversation in the session’s Discord thread with its web combat chat. Human messages from that specific thread may be displayed to web participants and spectators. Messages submitted to the global web combat chat are posted to the associated Discord thread with player attribution. The bridge ignores bot, webhook, and system messages and does not fetch historical Discord conversations.

To display and synchronize this chat, we process:

• Message text and, when available, the Discord message ID.
• The author’s Discord user ID and display name.
• The associated server, thread, and game-room identifiers.
• Message timestamps, source (Discord or web), delivery status, and edit status.
• Team association for web-only team chat, where that feature is available.

Chat text is retained temporarily in the application server’s memory outside Discord. The displayed rolling history is limited to 100 messages per room; delivery queues, retry-deduplication records, and room caches may hold additional temporary copies. The chat bridge does not write its conversation buffers to the game database or create a permanent conversation archive. Browser clients also receive message text to display the chat. Section 6.3 explains who can read it, and Section 8 explains retention limitations.

For activity validation, user IDs, counters, and relevant timestamps may be stored persistently. A fingerprint of the most recently counted normalized message is held in volatile memory for repeated-text comparison within a 10-minute window. That comparison window is not an automatic deletion deadline: the fingerprint may remain until replaced or the process restarts. Current activity fingerprints are not written to the database.

Values intentionally submitted through commands, forms, or game settings, such as character names, companion names, and configuration values, may be stored as persistent game data. These inputs are distinct from temporary combat-chat buffers.

3.5 Attachments and uploaded files

Certain authorized administrative or import features may allow a user to upload an attachment through Discord. When such a feature is used, the Application may temporarily access and process the attachment to perform the requested import, configuration, or administrative action. Information extracted from the file may be stored as application configuration or game content. We do not use uploaded files for unrelated purposes or AI model training.

3.6 Wallet addresses and reward information

If you voluntarily use a wallet-related or digital reward feature, we may collect and store:

• A public blockchain wallet address.
• Your Discord user ID.
• Reward amounts and redemption records.
• In-game transaction status.
• Dates and sources associated with rewards or redemptions.

We do not request or store wallet private keys, seed phrases, wallet passwords, or similar credentials. You should never provide such credentials to the Application or its operators. Public blockchain transactions may be permanently visible on the applicable blockchain. We cannot delete or alter information independently recorded on a public blockchain.

3.7 Technical and operational information

We may process limited technical information necessary to operate and secure the Application, including:

• Command and interaction timestamps.
• Error and diagnostic logs.
• Cooldown and rate-limit information.
• Database backup and restoration records.
• Records relating to abuse prevention, security incidents, or administrative actions.

We do not use this information for advertising or cross-service tracking.

3.8 Presence information

Guardians RPG does not request or use the privileged Guild Presences Intent. We do not track individual users’ online status, Discord activity, Rich Presence information, or client platform information.

3.9 Website information and sign-in

Website and game-portal infrastructure may process IP addresses, browser and device information, requested pages, request times, and operational or security logs. The public compendium uses GoatCounter to measure page visits and navigation; the website sends page paths and titles to this analytics service. The browser’s requests also expose connection information to the receiving provider.

The compendium stores language and theme preferences in your browser’s local storage. You can remove these preferences through your browser settings. Authenticated game interfaces use Discord OAuth to identify your account and use session and sign-in cookies. The current game portal issues signed session cookies with a 12-hour lifetime; signing prevents tampering and does not itself encrypt the cookie contents. We do not ask you to provide your Discord password.

Website analytics is separate from combat chat. We do not use message text for advertising or send combat-chat text as part of the compendium’s page-view analytics.

4. How We Use Information

We use collected information to:

• Create and maintain player accounts and game profiles.
• Provide RPG progression, combat, exploration, quests, clans, and events.
• Process commands and Discord interactions.
• Match players, operate multiplayer sessions, and relay conversations between their Discord and web interfaces.
• Maintain inventories, rewards, leaderboards, and achievements.
• Detect spam, repeated messages, abuse, cheating, and technical misuse.
• Determine eligibility for activity-based gameplay features.
• Restore interrupted game sessions.
• Process voluntary reward and wallet-redemption requests.
• Configure the Application for individual Discord servers.
• Respond to support, privacy, and security requests.
• Maintain, debug, secure, and improve the Application.
• Comply with applicable legal obligations and Discord’s requirements.

We use Discord API data as necessary for the stated functionality. Any use for product improvement must be aggregated or de-identified so it cannot identify an individual.

5. Legal Bases for Processing

Where applicable law requires a legal basis, we process information based on one or more of the following:

• Performance of a service: Processing is necessary to provide the game features you request.
• Legitimate interests: Processing is necessary to operate, secure, maintain, and prevent abuse of the Application.
• Consent: You voluntarily provide information or choose to use an optional feature, such as linking a public wallet address.
• Legal obligations: Processing is necessary to comply with applicable laws, regulations, valid legal requests, or platform requirements.

Where processing is based on consent, you may withdraw that consent. Withdrawal does not affect processing that was lawful before the withdrawal.

6. How We Share Information

We do not sell personal information. We do not share Discord API data with advertisers or data brokers. Information may be disclosed in the following limited circumstances:

6.1 Discord

The Application operates through Discord, and interactions with the Bot necessarily involve Discord’s services and infrastructure.

6.2 Hosting and service providers

We may use hosting, storage, security, backup, domain, and infrastructure providers to operate the Application and website. The Bot is currently hosted using Discloud infrastructure. These providers may process data on our behalf as necessary to provide their services. The public compendium also uses GoatCounter for website analytics, as described in Section 3.9.

6.3 Multiplayer participants, spectators, and server administrators

Public game features may display your username, character statistics, rankings, clan information, achievements, participation, and results to other users. Server administrators may access configuration and administrative information needed to operate the Application.

In supported sessions, messages in the associated Discord thread may also appear in the web combat chat with the author’s display name and user identifier. Global messages sent through the web chat are posted to Discord and become visible to people who can read that thread.

The global web combat chat can be read by signed-in spectators who can access the room. In some current modes, spectator access through a room link is not checked against the original Discord thread’s permissions. Do not assume that the web audience is limited to Discord thread members. Spectators have read-only access to the global web chat. Where web-only team chat is available, it is filtered to current teammates and is not relayed to Discord.

Other people may copy or capture messages they can see. Avoid sharing sensitive information in combat chat. Contact us using Section 11 if you need help identifying the audience of a room or removing a retained message.

6.4 Reward fulfillment and blockchain services

If you request a wallet-based reward or redemption, the public wallet address and transaction information may be used with the relevant blockchain network or reward-fulfillment process. Blockchain records are public and may be permanent.

6.5 Legal and safety reasons

We may disclose information when reasonably necessary to:

• Comply with applicable law or a valid legal request.
• Protect users, the public, Discord, or the Application.
• Investigate fraud, abuse, security incidents, or violations.
• Establish, exercise, or defend legal claims.

6.6 Business changes

If the Application is transferred to a different operator, information may be transferred as part of that change, subject to this Privacy Policy and applicable law. Users will be notified where legally required.

7. Public Information

Guardians RPG is a multiplayer application. Public profiles, leaderboards, game results, and shared combat chat can reveal information to other users. The audiences for Discord and web chat may differ, as described in Section 6.3.

Do not submit passwords, wallet secrets, or other sensitive personal information in chat, character or companion names, clan names, command arguments, or other public fields.

8. Data Retention

Retention depends on the data type and the operation of the relevant cleanup routines:

• Combat-chat buffers: held in server memory while the room and its chat caches remain available. Older entries leave the displayed 100-message history as newer ones arrive, but additional temporary copies may remain in delivery or deduplication records. Closed rooms are cleaned up by mode-specific routines; some routines run when the service is used again. Related caches can outlive the source room until their own cleanup runs. A process restart clears volatile buffers. The current implementation does not guarantee a fixed maximum age for every in-memory copy, including a universal 30-day limit.
• Repeated-text fingerprints: compared within a 10-minute window, but may remain in memory until replaced or the process restarts. They are not automatically erased solely because the comparison window has elapsed.
• Game profiles, activity counters, and settings: retained to provide persistent progression and account functionality until no longer needed or deletion is requested, subject to applicable legal obligations.
• Reward, transaction, and administrative records: retained as necessary for the stated service and applicable legal obligations. These records are separate from the conversation buffer.
• Backups: copies of persistent data may remain until their backup copies are removed or rotated. The current backup process does not establish a universal calendar-based deletion deadline. Temporary chat buffers are not part of the game database backup.
• Discord and recipient copies: messages posted to Discord remain subject to Discord’s storage and deletion behavior. Removing a server-side buffer does not retract copies already received or captured by other users.
• Blockchain records: public records cannot be deleted or modified by us.

Automatic edit and deletion synchronization operates while the corresponding chat session is active. Editing or deleting a Discord message after that session closes may not update a retained web copy. For deletion assistance, contact us as described in Section 11. A game ending or a user closing the browser should not be taken as confirmation that every copy has been deleted.

9. Data Security

Application safeguards include authorization for administrative actions, signed web sessions, request validation, chat rate limits, and access checks for supported game actions. Read-access limitations for spectators are described in Section 6.3. Access to application databases, backups, and hosting accounts must be restricted to authorized operators and service providers.

The current application does not itself encrypt its SQLite databases or database backups. Any encryption of hosting volumes or provider-managed backups depends on the provider’s configuration; we do not currently make a verified guarantee that all stored data is encrypted at rest. HTTPS transport protection and signed sessions do not establish encryption of stored databases or backups.

No online service can guarantee absolute security. Never send passwords, Discord account tokens, wallet private keys, or seed phrases to the Bot or its operators. Report suspected unauthorized access or disclosure to contact@guardiansrpg.com.

10. Message Processing and Your Choices

The Application does not currently provide an automated individual opt-out from message processing or from the relay of messages in a bridged combat thread. Opening or closing the web interface does not control whether messages in the associated Discord thread are processed.

To limit future processing, you can avoid posting in bridged combat threads, ask a server administrator to restrict the Bot’s channel access, and contact us to request restriction or deletion of data associated with your account. Avoiding commands alone does not stop activity processing of ordinary messages in channels the Bot can access. Removing a game profile does not by itself establish an exclusion from future message processing.

You can request deletion of retained chat or activity data without necessarily requesting deletion of your entire game profile. Deleting a full profile may permanently remove progression, inventory, currencies, achievements, and related game data. We will explain the scope of the requested action and any applicable legal retention requirement.

11. Your Privacy Rights and Deletion Requests

Depending on your location, you may have rights to access, correct, delete, restrict, or obtain a portable copy of your information, to object to processing, to withdraw consent where applicable, and to complain to an applicable data protection authority.

Email contact@guardiansrpg.com with the subject Privacy Request — Guardians RPG. Include your Discord user ID and the scope of your request, such as a specific chat message, activity records, or your complete game profile. For chat requests, a message link or ID, room link, and approximate date help us locate retained copies; do not send sensitive message text unless it is necessary to identify the record.

We may ask you to verify control of the relevant Discord account. We will handle requests within the period required by applicable law and explain any data we must retain under a legal obligation. Deletion requests cover retained application data associated with your request, including relevant caches and backup copies where present. They are handled by the operator rather than an automated self-service command. We will explain any backup handling needed and limitations involving Discord, recipients’ copies, or public blockchain records.

You never need to provide a Discord password, account token, wallet private key, or seed phrase to verify a privacy request.

12. Children’s Privacy

Guardians RPG is not directed to children under 13 or anyone below the minimum age required to use Discord in their country. We do not knowingly collect personal information from anyone who is not permitted to use Discord. If you believe an ineligible child has provided information to the Application, contact us so we can investigate and delete the information where appropriate.

13. International Data Processing

The Application and its service providers may process information in countries other than your country of residence. Where required, we will use appropriate safeguards for international transfers of personal information. Privacy protections and government access rules may differ between jurisdictions.

14. Automated Decision-Making and AI Training

Message content and other Discord API data are not used to train, fine-tune, evaluate, or otherwise develop machine learning or generative AI models. The Application may use deterministic rules, random game mechanics, configured probabilities, or rule-based combat decision logic. These systems do not learn from users’ messages and are not used to make legal, employment, credit, housing, insurance, or similarly significant decisions about users.

15. Changes to This Privacy Policy

We may update this Privacy Policy when the Application, its data practices, applicable law, or Discord’s requirements change. The updated version will be published at the same public URL with a revised “Last updated” date. Where a change is material, we may also provide notice through Discord or the Application’s public channels. Continued use of the Application after an update is subject to the revised Privacy Policy.

16. Contact Us

For privacy questions, deletion requests, complaints, or security concerns, contact:

• Guardians RPG
• Operator: Maximiliano Marino
• Email: contact@guardiansrpg.com
• Website: https://guardiansrpg.com