Focus: Only necessary account, source-check, and workflow data should be stored.
Account settings
TrustedQueue stores the identity, queue, lobby, and moderation information needed to operate the community while avoiding unnecessary raw third-party data.
Private reports, evidence, contact details, credentials, and admin notes never belong on a public player profile.
AUTHENTICATION
No Steam passwords
THIRD-PARTY DATA
Minimized by design
LOBBY CONTACTS
Private until preflight
REPORTS
Never public
WHAT WE KEEP
Data is tied to a clear account, safety, support, or operational purpose. Verified trust and skill fields cannot be manually edited by players.
When you register interest, we save your Steam name and ID, region, registration date and a short source label from your registration link, such as Discord. This private record helps administer leagues and understand which invitations lead to registrations. The interest flow adds no advertising cookies, stores no full referring URLs and sends no campaign data to an advertising service. You can withdraw your interest or include it in your account export.
SteamID64, display name, avatar, and profile URL identify the account and can be refreshed from Steam.
Source, result, timestamps, public-safe summaries, response hashes, and verified FACEIT skill context when linked.
Derived Steam account age, owned-game count, CS2 playtime, and private review signals help protect server access. TrustedQueue does not store the raw Steam game library or publish the internal score.
Preferences, lobby and clan invitations, memberships, readiness, reviews, and private contact details needed for community workflows.
Private reports, evidence, moderation cases, actions, appeals, support requests, privacy requests, and audit history.
INTEGRATION BOUNDARIES
API credentials stay server-side. Availability from an external provider can change, and optional services never become a requirement just because another player uses them.
Steam OpenID verifies identity. Server-side checks may derive account age, owned-game count, and CS2 playtime for private access review. The raw games list is not stored, and TrustedQueue never asks for a Steam password or personal API key.
When linked, public player details and verified CS2 skill or Elo may be stored as source-owned context.
Raw API payloads, metrics, and derived stat values are not stored. Current context is fetched when needed.
Raw responses are not stored permanently. Privacy suppression is respected and displayed context is attributed and short-lived.
Linked identity, verified-role sync, server ranking, VIP status, and operational events are limited to their stated feature.
Refresh public Steam profile data and verification checks.
Change queue preferences and private lobby contact details.
Create, join, leave, or manage a clan and its pending invitations.
Download the available account data export.
Submit a private data review, correction, export-support, or deletion-review request.
Diagnostic and source-check history can be pruned under configured retention rules. Core lobby, report, moderation, appeal, and audit records may need to remain for platform integrity, dispute handling, abuse prevention, or legal obligations.
A completed privacy outcome can anonymize account-facing data while retaining the minimum records needed to preserve those responsibilities.
