Privacy Policy

Data and purpose

We store Discord and Roblox user IDs, the Roblox username, verification method and time, server IDs, staff actions and optional reasons, and staff-assigned verification settings. These are used to link accounts, manage roles, prevent duplicate links, and resolve ownership or abuse issues.

OAuth uses Roblox’s openid and profile permissions. Public group information is checked for role assignments. Approved description verification reads the profile to check a temporary code; the full description is not saved. Roblox passwords and OAuth tokens are not stored.

Storage and sharing

Verification records and recovery backups are kept on the operator’s servers. The account link is shared across servers using this bot, so an existing link can automatically verify you in another server where this is enabled. Each server assigns its own roles. Linked accounts and verification methods can be displayed in Discord through /whois and /user-info. Roblox, Discord and the hosting provider also process information under their own privacy terms.

Retention

Use /unverify in Discord to remove your Roblox link, verification history and personal verification-method settings. Verification and mapped group roles are removed across servers using this bot. Staff can perform the same removal for a member.

The bot also removes its verification messages and scrubs verification data from database backups and staging copies kept in its managed server directories. If Discord or a backup is unavailable, a temporary cleanup queue retains your Discord ID and outstanding cleanup targets until it succeeds. Other bot records, such as moderation cases, tickets and economy records, are handled separately. For other data requests, join our Discord server and open a support ticket.

Website and requests

You can sign in with Roblox or Discord. Roblox sign-in uses openid and profile; Discord sign-in uses identity, email and server-list permissions. We store the connected account IDs, username, display name and account activity dates. A verified email supplied by Discord can be used for your website profile. Connecting another sign-in method requires authenticating that account; matching email addresses alone do not merge accounts.

Your profile stores your contact email, its verification status and notification preferences. Email verification links expire after 30 minutes and work once. You can change or remove the address and turn off news or support emails from Account. Website sign-in does not itself verify you in a Discord server. Existing self-authorised bot links, current Discord roles and Roblox group roles can identify an account and apply configured access.

An essential, secure session cookie keeps you signed in and allows you to access support requests. Sessions expire after seven days. Temporary sign-in state expires after ten minutes. We use no analytics or advertising trackers. Short-lived hashed network identifiers help limit abusive requests. Security or error logs may contain IP addresses and request metadata.

The server dashboard checks your Discord identity and current server-management permissions. You can sign in with Discord or use the Discord account already linked to your Roblox account. Discord access tokens are held on the server for your session. Server administrators can view and edit only servers they currently manage. Roblox integration keys are encrypted at rest and are never included in settings exports.

Support requests store the selected topic, message, optional files, contact email, account ID if signed in, conversation history and status. Authorised support staff can read and answer requests. A private tracking link also grants access to its request; keep it private. Links expire after 90 days without an update. Contact email addresses are supplied by the requester; a tracking link does not verify email ownership. Completed requests and their files are deleted after 180 days without an update; active requests are kept while support is ongoing.

If you provide an email address, our configured email provider (Brevo or Resend) sends a tracking link and request updates. Support emails contain a private tracking link, request reference and status; they do not contain your support message or attachments. Eligible support staff receive new-request notifications, and later notifications for conversations they participated in. Staff links require sign-in and current support access.

New community news appears in website inboxes and, by default, is emailed to verified addresses. You can turn off news emails from Account or the link in an announcement email. Published news and its attachments are public. The website owner can send test emails containing their chosen message and files. The provider processes each recipient address and the email content. Test-email attachment copies are removed from the send queue after the provider accepts the message.

The bot keeps temporary encrypted game snapshots for the platform owner's private game inspector. They contain Discord player and message IDs, game progress and generated outcomes. Completed snapshots expire after 30 minutes; unrefreshed active snapshots expire after 16 minutes. A prepared next Keno draw can be kept for up to 24 hours. Loans, loan offers, role incomes, temporary roles and suggestions (with their votes) are stored per server to run those features. Sticky and temporary roles of a member who leaves are remembered for up to 180 days so they can be restored if the member returns.

Email delivery requires a configured sender; when unavailable, the website asks you to save your support link. Sending records are kept for 30 days after provider acceptance. Inbox notifications are kept for up to 180 days. Staff content and access changes are recorded for security.

For access, correction or other deletion requests, join our Discord server and open a support ticket. We may need to confirm account ownership. Applicable data-protection rights, including the right to complain to a supervisory authority, remain available.