Privacy Policy

Astranox Faceit / ASX Faceit · Effective 24 September 2026

What this covers

This policy explains how Astranox Faceit handles information through its Discord bot and this website. The bot runs competitive Standoff 2 matches, player registration, ratings, moderation, and support and order tickets inside the ASX Faceit Discord community.

Information the bot uses

Discord user and server IDs, usernames, display names, nicknames, roles, and member join or role changes needed for registration, access checks, moderation, and premium features.
Player-provided Standoff 2 identifiers and names; match participation, results, statistics, ratings, rewards, and related transaction or moderation records.
Scoreboard images posted for a pending match submission in the designated results channel, plus the information extracted from those images.
Messages, embeds, and attachment links in report, shop, and marketplace tickets when a ticket is archived at closure. The transcript includes message authors and timestamps.
Voice channel participation used for relevant bot features, including voice activity rewards. The bot does not request Discord Presence status updates.

These data are used to operate the features above, resolve disputes, enforce server rules, and respond to support or deletion requests. The bot also reads limited message history in channels when a feature or staff action requires it.

Where information goes

Player, match, reward, order, and moderation data are stored in a local database outside Discord. Rolling database backups are also kept. Ticket transcripts are posted as HTML attachments in designated Discord archive channels, where members with the relevant channel permissions can access them.

For scoreboard processing, the bot downloads the image attachment from Discord and sends the image to the Google Gemini API for optical character recognition. The bot uses the returned data to calculate and record match results. We do not train our own AI model on Discord messages or images.

The current Gemini API integration uses an unpaid tier outside the EEA, UK, and Switzerland. Under Google's Gemini API terms, Google may use submitted content and responses to improve its products and machine learning technologies, and human reviewers may process API input and output. Do not put private or sensitive information in a scoreboard submission.

This website is hosted by Vercel. Normal website requests may be processed by the hosting provider. The site also loads fonts from Google Fonts. The website does not provide a player account or submission form.

How long information is kept

Player profiles and match histories can remain in the database while they are needed for the competitive ladder and recordkeeping; they are not automatically deleted within 30 days. Moderation and order records may also remain while needed to administer the community and resolve disputes. Ticket transcripts remain in Discord archive channels until staff remove them. Database backups rotate, but a deleted record may remain in an older backup until that backup is replaced. Google's handling of submitted scoreboard images follows its own terms.

We review deletion requests individually and remove information we no longer need where reasonably possible. Some match or moderation records may need to be retained to preserve other players' results or resolve an active dispute.

Your choices and deletion requests

There is no general per-user opt-out switch for message processing in the current bot. You can avoid submitting a scoreboard image or opening a ticket. If you participate in a ticket, messages in that ticket may be included in its transcript.

To request access to or deletion of data linked to your account, email [email protected]. Include your Discord user ID and describe your request. We may ask you to verify that the account is yours before acting. You can also contact us about an archived ticket or a scoreboard image.

Security

Bot operators and authorized server staff handle data for the purposes described here. Access to Discord ticket archives depends on the archive channels' permissions. The current local database and its backups are not encrypted at rest by the bot; we do not claim that they are. No method of storing or transmitting data is completely secure.

Changes and contact

We may update this policy as the bot or its providers change. The effective date at the top shows the current version. For questions, contact [email protected].