# AshRust Discord Bots Privacy Policy

Last Updated: June 26, 2026

This Privacy Policy applies to Discord applications operated by AshRust, including:

* Ash_Verification

* Ash_Meet6

Ash_Verification is operated by AshRust for Rust server verification, Discord-to-Steam account linking, verification support, Discord role assignment, Rust server access workflows, and related administrator tools.

Ash_Meet6 is an AshRust-owned Discord application connected to the official MEE6 Bot Personalizer / Custom Bot service. Ash_Meet6 allows our Discord server to use MEE6-powered community management features through a custom-branded bot.

These applications are used to support Discord community management, Rust server verification, account linking, moderation, role management, welcome messages, custom commands, leveling, server activity tools, and related administrator workflows.

This Privacy Policy explains what data may be collected, how the data may be used, how long it may be stored, how data may be processed by service providers, and how users can request deletion of their data.

## 1. Data We May Collect

Depending on which bot features are used or enabled, our Discord applications may collect, receive, or process the following categories of data:

* Discord account identifiers, such as user IDs

* Discord server, channel, role, command, interaction, and message identifiers when required for bot features

* Discord profile information provided by Discord, such as username, display name, avatar, or locale

* Steam account identifiers used for Rust server verification

* Steam profile information used for verification or administrator lookup, such as Steam name or Steam ID

* Verification status and verification timestamps

* Server configuration settings

* Role assignment, role reward, and role synchronization records

* Moderation, administrator action, and server-management records

* Leveling, XP, activity, and role reward records where enabled

* Custom command, welcome message, goodbye message, auto-role, trigger, filter, and bot configuration records

* Limited technical data needed to operate, secure, and troubleshoot the verification website, bots, dashboard, hosting, database, or related services

* Authorization-related data where required for verification, role assignment, server access, or bot operation workflows

* Presence or activity state data only when presence-aware features are enabled or required for configured bot features

* Derived operational records, such as timestamps, rule triggers, configuration references, command usage records, error logs, audit records, or security records

Technical logs may include limited information such as IP address, user-agent, request timestamp, error details, security event information, or similar operational data where reasonably necessary to operate, secure, troubleshoot, or protect the verification website, bot services, and related infrastructure.

We do not ask users for Discord passwords, Discord login credentials, Discord tokens, Steam passwords, or private authentication secrets.

We aim to limit data collection to what is reasonably necessary to operate, secure, maintain, and provide the enabled bot features.

## 2. How We Use Data

We may use collected data for Discord community management, Rust server verification, moderation, security, and server administration purposes, including:

* Linking Discord accounts with Steam accounts

* Verifying users for Rust server-related access

* Assigning verified Discord roles

* Supporting Rust server access-control workflows

* Allowing authorized administrators to check verification status

* Sending verification instructions

* Preventing verification abuse or repeated verification misuse

* Maintaining server security and operational integrity

* Troubleshooting verification, role, access, or bot issues

* Sending welcome or goodbye messages where enabled

* Assigning auto roles where enabled

* Managing leveling, XP, activity records, and role rewards where enabled

* Running custom commands and message-based triggers where enabled

* Supporting moderation and auto-moderation workflows

* Detecting spam, prohibited words, invite links, links, configured keywords, or other configured rule triggers

* Maintaining server logs, moderation records, and administrator action records

* Supporting server activity tools and administrator utilities

* Protecting the bots, verification website, Discord server, Rust servers, and related services from abuse, fraud, unauthorized access, or misuse

We do not sell Discord API Data.

We do not use Discord API Data for advertising.

We do not share Discord API Data with advertising networks, data brokers, or unrelated monetization services.

We do not use Discord API Data for unrelated profiling.

We do not use message content or user data to train AI or machine learning models.

## 3. Ash_Verification

Ash_Verification may process Discord and Steam-related data to support Rust server verification and account linking.

Ash_Verification may use Discord member data to check whether a member is already verified, assign or remove verification-related roles, support administrator lookup tools, synchronize roles or nicknames where configured, check server-related status where configured, and maintain verification records.

Ash_Verification may process message content in configured Discord channels only when needed to detect verification-related messages, such as users asking how to verify, link, or authenticate their account. When such messages are detected, the bot may reply with or send verification instructions.

Ash_Verification may store Discord-to-Steam verification records for longer than 30 days because persistent account-link records are required to maintain verification status, role assignment, Rust server access-control workflows, and administrator verification tools.

## 4. Ash_Meet6 and MEE6 Custom Bot Service

Ash_Meet6 is an AshRust-owned Discord application connected to the official MEE6 Bot Personalizer / Custom Bot service.

For Ash_Meet6, certain bot features are provided through the official MEE6 Bot Personalizer / Custom Bot service. MEE6 may process Discord API Data as a service provider where reasonably necessary to provide configured MEE6-powered bot features, including moderation, welcome messages, goodbye messages, auto roles, leveling, role rewards, custom commands, message-based triggers, server activity tools, and administrator utilities.

Ash_Meet6 may use Discord member data to support MEE6-powered features such as welcome messages, goodbye messages, auto-role assignment, member logs, role rewards, onboarding workflows, moderation workflows, and administrator member-management tools.

Ash_Meet6 may process message content when required for configured MEE6-powered features such as moderation, auto-moderation, keyword filters, spam detection, invite or link filtering, custom commands, prefix commands, message-based triggers, leveling, XP, or administrator commands.

Ash_Meet6 may process presence or activity state data where MEE6-powered presence-aware or server activity features are enabled or required for configured bot features.

Ash_Meet6 is used only for Discord community management and server administration workflows in configured Discord servers.

## 5. Message Content

Some enabled bot features may require processing message content in configured Discord channels.

Ash_Verification may process message content to detect verification-related messages, such as users asking how to verify, link, or authenticate their account.

Ash_Meet6 may process message content when required for configured MEE6-powered features such as moderation, auto-moderation, keyword filters, spam detection, invite or link filtering, custom commands, prefix commands, message-based triggers, leveling, XP, or administrator commands.

Message content is processed only as reasonably necessary for configured bot features.

We do not retain raw message bodies for general message tracking, advertising, unrelated profiling, unrelated analytics, AI training, or machine learning training.

Depending on server configuration and enabled features, limited moderation or operational records may be stored, such as user ID, server ID, channel ID, role ID, message ID, timestamp, triggered rule, moderation action, administrator action, XP or leveling record, command usage record, or server configuration record.

Where a moderation, logging, security, or administrator review feature requires retaining limited message-related evidence, such retention is limited to what is reasonably necessary for moderation, security, abuse prevention, troubleshooting, administrator review, dispute resolution, or operational integrity.

Ash_Meet6’s MEE6 Bot Backstory or AI conversation feature is disabled unless explicitly enabled by server administrators. If enabled, messages directed to the bot may be processed to provide that AI-powered response feature. AshRust does not use message content or user data to train AI or machine learning models.

## 6. Server Member Data

Our Discord applications may use server member data to support features such as:

* Detecting when a member joins or leaves a Discord server

* Checking whether a member is verified

* Assigning or removing verification-related roles

* Sending welcome or goodbye messages where enabled

* Assigning auto roles where enabled

* Managing role rewards where enabled

* Maintaining member logs where enabled

* Supporting moderation workflows

* Supporting administrator member-management tools

* Synchronizing roles or nicknames where configured

* Checking server-related status where configured

Server member data may be used for verification, role synchronization, community management, moderation, onboarding, Rust server access control, abuse prevention, security, and administrator utilities.

## 7. Presence and Activity Data

Presence or activity state data may be processed only when presence-aware features are enabled or required for configured bot features.

Presence data may be used for operational server-management features such as online member statistics, server activity tools, administrator dashboards, activity-aware community management, or moderation workflows where real-time activity state is relevant.

Presence data is not used for advertising, unrelated profiling, unrelated analytics, AI training, or machine learning training.

Historical presence or activity data is not stored off-platform by default unless a configured feature requires limited operational logging for server activity, moderation, security, troubleshooting, administrator review, or operational integrity.

## 8. Data Storage and Retention

Some records may be stored for longer than 30 days because verification, moderation, leveling, role rewards, custom commands, auto roles, welcome messages, server configuration, and administrator tools often require persistent records.

Verification records may be kept for as long as reasonably necessary to maintain Discord-to-Steam account links, verification status, role assignment, Rust server-related access, abuse prevention, and administrator lookup tools.

Moderation, leveling, role reward, command configuration, server configuration, and administrator action records may be kept for as long as reasonably necessary to operate, secure, troubleshoot, and maintain the enabled bot features.

Data may be kept until one or more of the following applies:

* The user requests deletion and the request is verified

* The linked account is removed

* The relevant bot feature is disabled

* The relevant server configuration is deleted

* The bot is removed from the server

* The data is no longer reasonably needed for verification, moderation, security, abuse prevention, troubleshooting, administrator review, dispute resolution, legal compliance, or operational integrity

* Applicable law or platform requirements require deletion

We may retain limited records where reasonably necessary for moderation, security, abuse prevention, fraud prevention, dispute resolution, legal compliance, platform compliance, or operational integrity.

## 9. Data Sharing and Service Providers

We do not sell Discord API Data.

We do not share Discord API Data with third parties for advertising, unrelated profiling, unrelated analytics, data brokerage, or unrelated monetization.

Data may be processed by service providers only as reasonably necessary to operate, secure, maintain, and provide the bots, verification website, dashboard, database, hosting, infrastructure, MEE6-powered custom bot features, and related server-management services.

Service providers may include hosting providers, database providers, infrastructure providers, security providers, analytics or logging providers used for operational troubleshooting, and the official MEE6 Bot Personalizer / Custom Bot service for Ash_Meet6.

Service providers may process data only as reasonably necessary to provide the relevant services. We expect service providers to use reasonable safeguards and to process data only for the purpose of providing the requested services.

We may disclose data if reasonably necessary to comply with applicable law, enforce our rules, protect users, protect our Discord server, protect our Rust servers, investigate abuse, prevent fraud, respond to valid legal requests, or maintain operational integrity.

## 10. Data Security

We use reasonable technical and administrative safeguards designed to protect stored data.

Access to operational data is restricted to authorized administrators, authorized systems, and authorized service providers where necessary.

Administrative access and sensitive credentials are restricted.

Discord API Data stored outside Discord is protected using reasonable safeguards, including access controls, permission restrictions, administrative safeguards, and encryption at rest where stored under systems that process Discord API Data.

We do not publish or intentionally expose bot tokens, client secrets, database credentials, access tokens, private configuration files, or other sensitive security credentials.

No method of transmission or storage is completely secure, but we take reasonable steps designed to reduce unauthorized access, misuse, loss, alteration,