Elemental XYZ

Verification, clans, tickets, rewards

Privacy Policy

Last updated: 24 October 2026. This policy covers the Elemental XYZ Assistance bot, elementalxyz.com, verify.elementalxyz.com, and their enabled community features.

1. What “OAuth” and “API data” mean

OAuth is the official “sign in and allow this app” screen provided by Discord or Roblox. We receive the information and permissions listed on that screen, not your password. An API is a service that lets the bot request that permitted information. An access token is a temporary permission credential; a refresh token can renew it. These are sensitive credentials and are not public profile information.

2. Information used for verification

• Discord identity: your user ID, username, display name, avatar/profile fields returned by Discord, sign-in/session records, and verification attempts and results.
• Your Discord server list: server IDs, names and related server metadata returned with your permission. Stored lists are snapshots and may become out of date. Authorized owner tools can inspect them for support and stated moderation/safety features. They may be compared with the server-safety catalogue and rechecked later using your permission.
• Discord connections: where the connections permission is granted, Discord may return linked services/accounts, their names and identifiers, verification/revocation flags, and whether they are shown on your Discord profile. A connection hidden from your public profile is not necessarily hidden from an app you authorize. These stored snapshots are not published as a public list of your connections.
• Roblox identity and account links: Roblox ID, username, display name, profile/avatar information, your selected main account, any additionally linked accounts, and the dates and methods used to link them.
• Permission credentials: OAuth tokens and session/state records needed to complete or maintain approved sign-in, refreshes, linking and role synchronization.

We no longer request the Discord permission to read your individual membership details, such as roles, in every server on your OAuth server list. This is different from the bot reading roles and permissions in a participating server where it is installed, which it needs to manage verification, tickets and configured features.

A failed attempt can still leave data. For example, Discord sign-in may finish while Roblox sign-in does not. In that case a Discord session, permitted snapshots, and failure/timing records can exist without a successful Roblox link.

3. Other enabled bot and website features

Depending on the server and features used, records can include:

• Server, channel, role and message IDs; configured permissions; join/leave and invite records; verification/access status; nickname/role changes; and relevant activity or reward counters.
• Support questions, verification failure cases, staff replies, ticket claim/status records, transcripts, submitted attachments/links, and bug-report or suggestion follow-ups and button answers. An automatic failure ticket may be created even if you are no longer in its support server; it remains restricted to the normal authorized support audience.
• Moderation evidence and outcomes, game bans, appeals, configured Do Not Chat enforcement, and the server IDs, names, classifications, reasons and evidence in the server-safety catalogue.
• Roblox game statistics, clan observations, badges, group membership, inventory/gamepass checks and ownership results available through the relevant permitted/public game interfaces. OAuth does not give us unrestricted access to everything in a private Roblox account.
• Messages needed for configured moderation, ticket transcripts, global chat, counting, bot conversations, and enabled edit/deletion logs. An edit/deletion log can retain an earlier message and its author after it changes or disappears from the original channel; uncached content is not always recoverable. Messages sent directly to this bot may be logged for support/safety. This does not give the bot access to your unrelated private conversations with other people.

We do not operate a general searchable archive of every message in every server. Message handling depends on the enabled feature, and some features deliberately retain content.

4. What changes when you verify

The bot can grant/remove configured roles and update your server nickname. Your main Roblox account is used for identity and main-account perks; saving an additional account does not make it your main. Your verified status can be synchronized to other participating servers where you are a member and verification is enabled. Unlinking, a verification restriction, or removal of eligibility can remove verification-related roles and reset managed nicknames. Server owners can configure nickname choices and exemptions.

Safety checks and recorded moderation outcomes may affect access to configured games or community features. Automated checks can be wrong or incomplete. Ask staff to review an error; a stored snapshot is not proof that you are still in a particular server today.

5. Website cookies and technical logs

The website uses session cookies and temporary sign-in/security state to keep you signed in and match authorization responses to the correct request. Cookies are small pieces of browser data; they are not your Discord or Roblox password. Blocking them or changing browsers during sign-in can stop verification working.

Website and reliability records can include IP addresses, browser/device information (the User-Agent), route names, timestamps, response/error status, Cloudflare request metadata, and your Discord identity when signed in. Traffic/visitor metrics and verification timing/failure logs help diagnose problems and abuse. Access logs omit OAuth callback query strings so those logs do not deliberately retain one-time authorization codes. Do not share callback links or tokens.

6. Who can see or receive information

Access is limited by the feature and server permissions. Owner-only tools are not available to every staff member. Support staff can see tickets/transcripts they are authorized to access; moderation logs can be visible to the configured staff audience. Game/clan leaderboards, public profiles, announcements and forum posts can show relevant information to their audience.

Global chat: a message sent in an enabled global-chat channel can be relayed, with its author details, to other participating servers. Those viewers can read or copy it.

Discord and Roblox process requests made through their services. Cloudflare handles website traffic/security and the connection to our host. When an AI-response feature is enabled, relevant prompts, message/context content and feature instructions can be sent to OpenAI to generate a response. AI-generated replies are not private advice. We do not use Discord message content to train AI models. Automatic AI server research is currently disabled; this does not mean all AI-assisted bot replies are disabled.

We do not sell Discord API data, give it to advertising networks, or use it for targeted ads. Sponsored clan placements are general placements, not ads selected from your private server list or messages. Disclosure beyond the authorized feature audience/service providers must follow applicable law and platform requirements; this policy does not authorize unrestricted sharing.

7. Retention and recovery backups

Live records are kept for their operating, support, security or moderation purpose, subject to applicable platform and legal requirements. Different records have different lifecycles; there is not one automatic deletion deadline for every database row, transcript and log.

Recovery backups: we keep encrypted, access-restricted copies to recover the service after a failure. These copies are kept separately from the live service and may contain older personal information, including information later deleted from the live service. Ordinary recovery archives containing user data are kept for up to 14 days.

When a deletion is processed, a separate recovery checkpoint makes earlier user-data backups ineligible for restoration. The maintenance worker removes those affected archives, including the pre-deletion recovery copy, on its next successful cleanup. This is not an additional 14-day waiting period for deleted information. Recovery tools require a current checkpoint and refuse an expired or invalidated archive, so those copies cannot be used through the supported recovery process to reintroduce deleted information.

Cleanup normally runs every five minutes while the maintenance PC and backup storage are available. If either is unavailable or a cleanup fails, the system retries when available; a switched-off or disconnected device cannot erase files at an exact time. Code-only backups and separately maintained server-research records are not ordinary user-data recovery archives.

A separate, temporary recovery snapshot is required before staff executes a deletion. The maintenance system checks that this snapshot was received and verified; a failed backup can delay processing. This special deletion-recovery snapshot has a maximum 24-hour validity and is also removed following the deletion checkpoint as described above. It is not kept for the full ordinary recovery period.

8. Your choices, corrections and deletion

You can revoke the app's authorization through Discord or Roblox, unlink an account through supported tools, or request deletion below. Revoking authorization stops future authorized access but does not itself erase records already stored. Unlinking removes verification/access; it is not the same as a full deletion request.

The deletion request is available without a prior successful verification. Sign in to identify the account, review the confirmation, and type the requested confirmation text. A reason is optional and leaving it blank does not reduce your deletion rights. Never include a password, token or recovery code in your explanation.

The current deletion workflow removes eligible account links, OAuth tokens and sessions (including stored server/connection snapshots), profile/settings and user-owned feature records, verification logs, stored global-chat copies, and requester-owned ticket transcripts. It makes you unverified; re-verifying later creates new records.

The workflow does not automatically erase every existing Discord message/log-channel post, another person's retained copy, independent public Roblox game/clan observation, moderation outcome or active game ban. Recovery archives are handled as explained in section 7. A minimal deletion audit and server-only safety catalogue entries can remain; the deleted user's stored OAuth membership link is removed. Ask staff to review any remaining personal information, correction, access, or deletion concern. Retention is subject to platform obligations and applicable law, not a blanket exception created by this policy. Deletion is not automatically an unban or appeal acceptance.

The published processing target is five business days. If a request is delayed or you cannot use the website, contact Elemental XYZ staff through the participating server's ticket system and ask for privacy/data support. You do not need to reveal additional unrelated personal data. Applicable privacy rights and complaint options are not waived by using this service.

9. Security, age requirements and updates

We use HTTPS, restricted maintenance/staff access and encrypted storage/backups for sensitive service data. No system can guarantee perfect security. Report suspected exposure privately to staff without posting tokens or private evidence publicly. We will handle incidents under the notification and response requirements that apply.

You must meet Discord's and Roblox's age/account requirements, including any higher regional minimum. Do not send age documents or sensitive personal information through ordinary tickets.

We may update this policy as features change. The date above identifies this version. A policy update does not itself add OAuth permissions or waive Discord/Roblox requirements. See also our Terms of Service.