CustomQueue

Built for smarter players

Competitive match insight for players who want more structure, clearer feedback, and less noise around the games they already enjoy with friends.

Public routes stay read-only. Member routes such as `Member Matches` and `Member Login` require existing access.

Public Privacy

Privacy

CustomQueue keeps the privacy story dry, clear, and aligned with the product that actually exists today.

Current state

The internal workflow already operates privately. These public routes exist so reviewers can understand the product without logging in first.

Riot scope

Standard API lookup exists where useful. Riot account linking and Tournament API creation are intentionally outside this public surface.

What the current app stores

The current protected workflow stores the operational data needed to run the product, review results, and recover from local issues.

CustomQueue stores local user records, match records created inside the product, participant rows, audit entries, leaderboard snapshots, and optional recovery payloads such as backup/export data.

Result completion can also store post-game detail when operators use Riot JSON import or quick manual import for private custom matches.

Only matches intentionally created through this application are intended to count toward tracked history and ranking views.

Built for smarter players does not mean broader data collection. The current implementation remains mock-first and does not rely on live Riot account linking for the existing workflow.

What this page does not claim

This public surface is for staging and reviewer context. It is not a statement that the app is already operating as a public live service.

No public self-service registration is available in the current phase, even though public player-access pages now exist for review context.

Authentication remains a temporary local development bridge for internal testing only.

Standard Riot API validation exists only on the server side for limited fetch and health-check use. Tournament API creation and live Riot account linking are intentionally not part of the current scope.

If live Riot-linked identity is added in a later phase, this page should be expanded before any real-user rollout.

Questions and operator contact

Policy, demo, or staging questions should go through the configured support channel.

Support and policy questions can be directed to info@customqueue.com.

This address is intended for product/review communication, not open public player support.