Privacy Policy
Last updated: October 27, 2026
This policy covers the AQWorlds Discord bot and this dashboard. AQWorlds is the legacy bot. It is separate from AQW Helper and is not an official Discord or Artix Entertainment service.
What the bot processes and stores
- Discord information: user, server, channel, and role IDs; names; permissions; configured nicknames; and server settings. Discord membership and role information are used to check dashboard access.
- AQW account details: the username and password registered for your server, registration status, and an email address where one is provided through account setup. Credentials are stored so the client can log in and reconnect. Do not provide a Discord password.
- Character and guild information: character IDs, current and recorded names, guild rosters, ranks, levels, online status, activity counts and timestamps, and character or wiki lookup counts. Older records may include Discord-to-character links and character notification requests.
- Messages and diagnostics: commands and messages needed for configured chat relays, plus connection, action, and error logs. Logs can include Discord IDs, usernames, command names, timestamps, and technical error details. The web server processes connection information such as IP addresses to handle requests and limit abuse.
This information is used to run the bot, check access, relay messages, display character history and guild activity, and investigate failures or abuse.
Who can see the information
Character details and recorded aliases can appear in Discord command results. Guild information and activity appear in the channels where commands or logging are used. Messages sent through guild, zone, global, or alliance relays can be visible to people in the destination Discord servers or AQW chats, including people outside your original server.
Dashboard settings are available to the server owner and members with Administrator or Manage Server permission. Slash-command access is controlled separately by Discord's command permissions. Saved passwords and email addresses are not displayed on the dashboard. The bot operator can access stored data to maintain the service and handle support requests.
Discord processes sign-in and bot messages. AQW services receive game login requests and character queries. The configured character-image service receives character appearance data to render images. Images loaded from Discord's CDN and links opened on other sites are subject to those services' own policies.
Website cookies
The dashboard uses cookies for sign-in, login security, form protection, and short-lived notices. The authentication cookie contains your Discord ID, username, and avatar URL when available, and expires after eight hours. Sign-in requests your identity and server list so the dashboard can show servers you manage, including ones where the bot has not joined. A random session reference is stored in the cookie; the OAuth access token is kept only in server memory for up to eight hours to load your server list, never in the cookie or database. Logging out removes that token from memory and ends the dashboard session. Restarting the bot clears those tokens. The website does not include advertising or analytics trackers.
Retention and deletion
Server settings, character aliases, guild history, and account records do not have a fixed automatic expiry. Removing the bot from a server stops its client but does not automatically delete those records.
Unregistering an AQW account clears its saved username, password, and email from the active account record. It keeps the server configuration and existing character and guild history. Removing stored data does not automatically remove messages already posted in Discord or AQW, or copies held by others.
To request access, correction, or deletion of your information, contact the developer through the support server. Include the relevant Discord user or server ID, or AQW character name and ID. Do not post passwords. Verification may be needed before changing or deleting records belonging to a person or server.
Security and updates
The dashboard restricts access and protects its sign-in cookies and forms. AQW credentials must remain usable by the bot to sign in; no service can guarantee that stored information will never be exposed. Use an account you are authorized to register and do not reuse its password for unrelated services.
Changes to this policy will be posted here with an updated date. Questions or privacy concerns can be raised in the support server.