Explore the build.
Understand the plan.

1. Player reads the data-use notice and explicitly opts into linking their Riot account. Any public display of gameplay data will be disclosed before consent.
2. Player is redirected to Riot Sign On; credentials are entered only on Riot’s service.
3. A server verifies the authenticated player and retrieves that player’s completed match history through supported official APIs.
4. The dashboard shows post-match summaries. Non-opted-in players are not exposed through profiles, searches, or opponent statistics.
5. Player can disconnect and request removal of stored account data before the live integration is released.

These steps describe intended behavior, not a working OAuth flow. Retention, consent, access controls, and deletion must be implemented and documented before live player data is enabled.

This prototype has no opponent scouting, hidden-player identification, real-time gameplay overlay, MMR estimates, wagering, or monetization. The RR chart adds supplied sample changes; it does not estimate skill or replace Riot’s ranking system.

No account is needed to inspect the public prototype. The sample dataset is bundled with the application and contains no real player identities. Existing local entries remain on the visitor’s own browser and are not published to others. The demo link displays samples in memory without overwriting those entries.

Riot reviewers can use the product’s Developer Portal application thread to communicate with the applicant. A public support address has not yet been established.

VALORANT developer policies · Riot general policies