TrustedQueue CS2Sign in with Steam
Privacy

What matters: Only necessary account, source-check, and workflow data should be stored.

Account settings
Privacy boundaries

Store what the queue needs, avoid the rest

TrustedQueue keeps verified identity and moderation history necessary for queue safety while avoiding unnecessary raw third-party API data.

No Steam passwords or personal API keys

Players authenticate with Steam OpenID. Browser code never receives Steam, FACEIT, or Leetify API keys.

Minimal third-party storage

The platform stores check status, timestamps, public summaries, private moderation notes, and response hashes.

Private contact data stays private

Lobby contact handles and private contact notes are used only for the private lobby flow they were provided for.

Leetify is live-check first

Leetify support is designed as an optional live adapter with short-lived cache only when permitted.

Privacy | TrustedQueue CS2