Information Aestron processes
To operate Discord features, Aestron may process Discord user, guild, role, channel, message, command, and voice-state identifiers; configuration chosen by server administrators; moderation, leveling, ticket, giveaway, and command-usage records; and content deliberately supplied to a command or feedback form. Processing depends on the feature used.
Why it is used
Data is used to execute requested commands, enforce server configuration, protect communities, maintain queues and progress, provide support, measure aggregate bot activity, prevent abuse, and diagnose failures. Aestron does not sell personal data.
Optional integrations
Some commands contact third-party services such as Discord, Lavalink nodes, translation providers, game APIs, or server-status services. These features are disabled when their required configuration is absent and remain subject to those providers' policies.
VALORANT account linking
VALORANT features require explicit Riot Sign On consent. Aestron stores the linked Discord ID, Riot PUUID, game name, tag line, routing shard, consent time, and official match data needed for requested statistics. Riot passwords are never received, and OAuth access, identity, and refresh tokens are not persisted. Unlinked players are not searched or analyzed.
Feedback and operational logs
Suggestions and bug reports contain the text and optional contact information a user submits. Operational logs record command names, identifiers, timings, and error context; secrets and message content are excluded unless that content is necessary for the requested feature or deliberately included in a report.
Retention and deletion
Records are retained only while needed for the feature, security, support, or legal obligations. Users can unlink Riot data with /unlinkaccount. Server administrators can remove bot-managed configuration by removing the bot or requesting deletion through support. Feedback and moderation records may be retained where needed to resolve reports or protect a community.
Security and contact
Credentials are kept in server-side environment variables, service endpoints require authentication, and sensitive account linking uses signed, expiring state. Use the website feedback form or configured support server for access, correction, privacy, or deletion requests.