Nyors Mods Discord Bot

Privacy Policy

A clear overview of the data the Nyors Mods bot needs to manage connected game servers, roles, rewards, and player accounts.

Last updated: July 25, 2026 Privacy contact

Server Members Intent

Used for role synchronization, access control, and account assignment.

No Message Content

The bot does not request Message Content and does not store ticket conversations.

Transient Voice State Data

Voice participation is evaluated only for enabled voice features and rewards.

Policy scope

What this policy covers

This policy applies to the Nyors Mods Discord bot and the game-server functions connected to it. It explains which personal data the bot processes, why that data is needed, and how users can exercise their rights.

Tickets v2 is separate. Ticket channels are provided by the external Tickets v2 Discord application. The Nyors Mods bot does not access or store the content of those ticket conversations. Processing by that service is governed by its operator and the affected game-server operator.

Responsible contact

Who operates the bot

Pascal Wagner pascalwagner1995@icloud.com

For data that belongs to a specific game-server community, the support team of that game-server operator is the first point of contact. The operator can identify the relevant account and coordinate access, correction, or deletion requests.

Data categories

Data the bot may process

Discord account data

User ID, guild ID, role IDs, display name, and account information required to identify a member.

Game account links

Linked Steam ID, in-game name, server assignment, and identifiers needed to connect Discord with a player account.

Game-server data

Progression, rewards, points, inventory, dinosaur tokens, permissions, and administrative records created while using enabled server features.

Interaction data

Slash-command selections, form values, button interactions, and identifiers submitted directly through Discord interactions.

Voice state data

Whether a member is connected to an eligible voice channel and whether mute, deaf, or AFK conditions affect an enabled reward.

Technical data

Error records, security events, timestamps, request metadata, and website access logs required to keep the service reliable and secure.

Purpose and legal basis

Why the data is processed

01
Account linking
Connect a Discord member with the correct game-server account.
02
Roles and access
Synchronize Discord roles, bot permissions, feature access, and server responsibilities.
03
Game features
Provide rewards, inventories, game-server management, and other requested community functions.
04
Security and support
Prevent abuse, investigate faults, maintain service availability, and answer verified requests.

Processing is based on Article 6(1)(b) GDPR where it is required to provide a requested bot or game-server function, and Article 6(1)(f) GDPR for secure, reliable, and abuse-resistant operation. Where another legal obligation applies, processing may also rely on Article 6(1)(c) GDPR.

Discord Gateway access

Intents used by the bot

Required

Server Members Intent

Receives member join, leave, and role-change information. It is needed to keep role-based permissions and connected game-server features synchronized.

Standard

Guild Voice States

Receives voice join, leave, move, mute, deaf, and AFK state changes for enabled voice rewards and voice functions.

Not requested

No Message Content

The bot does not request access to general message content and does not monitor or archive Discord conversations.

Not requested

No Presence Data

The bot does not request members' online status, client status, current activities, or games through the Presence Intent.

Voice processing

How voice state is handled

The bot does not record voice audio. It evaluates Discord voice-state events and Nyors Mods overlay voice activity only to determine whether an enabled voice function or reward condition is met.

Voice-state information is evaluated as operational state. The resulting reward balance may be stored, but voice audio and conversation content are not collected by the Nyors Mods bot.

Storage and recipients

Where data goes and how long it remains

Persistent bot and game data is stored on infrastructure used to operate Nyors Mods and the connected game-server service. Access is limited to authorized technical operators and the responsible team of the affected game server where access is required for operation or support.

Discord processes data independently when users access Discord or interact with applications on its platform. Discord's own terms and privacy information apply to that processing.

Data is kept only while it is needed for the linked account, requested game-server functions, security, support, or the establishment, exercise, or defense of legal claims. It is deleted or anonymized when the purpose no longer applies or after a verified valid deletion request, unless retention is legally required.

Personal data is not sold. Message or interaction data is not used to train machine-learning or artificial-intelligence models.

Data Subject Rights

Your privacy choices

Depending on the applicable law, users may request access, correction, deletion, restriction, portability, or object to processing. Users may also withdraw consent where processing is based on consent and may lodge a complaint with a competent data-protection authority.

Contact the support team of the affected game-server operator.

Provide the Discord ID and game account needed to identify the relevant record.

The operator verifies the request and coordinates the required action.

If the responsible server support cannot be reached, privacy questions can be sent to pascalwagner1995@icloud.com.

Protection and changes

Security and policy updates

Reasonable technical and organizational safeguards are used to protect stored data against unauthorized access, loss, alteration, and misuse. No internet service can guarantee absolute security.

This policy may be updated when the bot's features, data flows, or legal requirements change. The latest version is published on this page with its effective date.

Privacy contact Pascal Wagner

Send email