Why does Steam need to be public?
Steam sign-in verifies identity, but richer stats and game-data checks need Steam profile and Game details visibility set to public.
Open visibility guideWhat matters: Get help privately without creating public accusations or exposing evidence.
Submit requestTrustedQueue routes support through the right private workflow. Verification, lobby setup, reports, appeals, and privacy requests are handled without exposing accusations or private evidence publicly.
Most problems are fastest through the exact product surface that owns them. Use private support for account-specific help, appeals for restrictions, and completed-lobby reports for serious player issues.
Refresh Steam checks, public profile visibility, and optional FACEIT linking.
LobbiesReview invites, preflight, contact reveal, and completed-lobby follow-up.
AppealsAppeal active queue restrictions or platform bans where policy allows.
PrivacyRequest data review, correction, export support, or deletion review privately.
Use this page as the support entry point. The cards below separate live help, restriction appeals, privacy information, and platform terms.
Start here before sending a support request. These answers cover setup, invites, contact reveal, reports, and appeals without exposing private moderation details.
Steam sign-in verifies identity, but richer stats and game-data checks need Steam profile and Game details visibility set to public.
Open visibility guideNo. FACEIT is optional because not every CS2 player uses it. Linking FACEIT can add verified CS2 skill/Elo and extra trust context when available.
Review FACEIT linkingInvites appear in notifications, dashboard, and the lobby hub. Contact details stay hidden until current lobby members pass preflight.
Open lobby hubReports are gated behind completed TrustedQueue lobby membership so serious claims stay tied to a real shared platform lobby and private evidence.
Open completed lobbiesQueue restrictions and bans can be appealed privately where policy allows. Reporter identity and private evidence are not shown publicly.
Open appealsStart with the page tied to the issue, then use private support only when the guided path does not clear it. Keep reports and appeals in their protected workflows.
You signed in, but a protected page still asks for Steam login or redirects unexpectedly.
TrustedQueue never asks for Steam passwords or personal Steam API keys.
Your profile shows limited verification, missing stats, or no FACEIT skill context.
FACEIT is optional. Linking it can strengthen context, but not having FACEIT is allowed.
Discovery is empty or filters return very few players.
Small early pools are normal; discovery only shows real eligible accounts.
A lobby exists, but invite or contact details are still hidden.
Contact reveal depends on fresh source and platform checks for every lobby member.
Something happened in a TrustedQueue lobby and you want it reviewed.
Reports, reporter identity, and evidence stay private and are not public profile content.
Your account cannot join queue or lobby flows because of a restriction.
Appeals are reviewed privately and moderation evidence remains protected.
These cover the most common Steam, FACEIT, queue, and lobby problems before you need a private support request.
Check service status first, then sign out and sign back in if the session looks stale after a deploy.
Check statusSteam profile and game details need to be public before richer public stats can be pulled reliably.
Open Steam visibility stepUse the guided verification page to refresh Steam checks and optional FACEIT context from the server.
Refresh checksFACEIT is optional. Linking it can improve trust context and show verified CS2 skill/Elo when available.
Open FACEIT linkingSave complete queue preferences and try broader region, language, role, or skill filters while the player pool grows.
Edit preferencesLobby contact reveal happens only after every member passes fresh Steam, linked FACEIT, and platform account checks.
Review lobbiesRefresh Steam checks, confirm Steam profile visibility, and optionally link FACEIT for stronger trust and verified CS2 skill context.
Common issues
Before submitting
Verification labels describe source checks and platform history. They do not promise perfect player safety.
Open verificationReview setup progress, queue preferences, active lobby invites, preflight status, and contact reveal requirements.
Common issues
Before submitting
Lobby safety messages use public-safe reasons and do not expose private reports or moderation notes.
Open dashboardReports are only available for players from the same completed TrustedQueue lobby. Serious reports require evidence and go to private moderation.
Common issues
Before submitting
Reports are never used as public accusation pages. Reporter identity and evidence stay private.
Open completed lobbiesQueue restrictions and bans can be appealed where policy allows. Reporter identity, evidence, and private moderation notes are not shown publicly.
Common issues
Before submitting
Appeals are reviewed privately and do not reveal protected moderation details.
Open appealsSigned-in users can request account data review, correction, export support, or privacy handling through a private admin case.
Common issues
Before submitting
Privacy requests are handled privately and API keys are never requested from users.
Open account privacyRead how TrustedQueue handles private reports, manual review, public-safe labels, and evidence without publishing accusation walls.
Common issues
Before submitting
TrustedQueue shows public-safe trust labels, not raw risk scores or public accusation feeds.
Read safety policyUse this for account, verification, FACEIT linking, queue, lobby, policy, or bug help. Player reports still need the completed-lobby report flow so evidence and membership checks stay attached.
Do not include passwords, personal Steam API keys, private credentials, or public accusations. SteamID, page name, lobby ID, and public-safe error details are enough to start.
Sign in with Steam to submit private account support. Public visitors can still read the support routes and safety policy.
This only shows public-safe status context for your own support cases.
No support requests yet.
Submitted support requests will appear here after you sign in and send one.
TrustedQueue does not publish public accusation pages, raw risk scores, private report history, reporter identity, or moderation evidence. Serious claims are reviewed privately and only confirmed source bans or admin-confirmed platform actions can restrict queue access.