Terms of use

Informational service

Stats, match summaries, and general matchup guidance are informational. They may be delayed, incomplete, or affected by Riot API availability and game patches. No result is a guarantee of rank, performance, or match outcome.

Fair use

Do not automate excessive requests, bypass rate limits, probe private routes, or use the service to harass or identify players beyond information reasonably visible through Riot services. Access may be limited to protect the service and Riot APIs.

VRC.LOL documents its server-side pacing, response-header monitoring, 429 handling and Production approval boundary on the API use and rate limits page.

Riot data and assets

VRC.LOL is an end-user learning product, not a data broker. It does not sell, license, or provide raw Riot API responses or API access to another company. Public features present transformed player information and educational references for the person using the product.

League names, champion artwork, item artwork, icons, and other game-specific static data are used from Riot-supported sources such as Data Dragon or permitted Riot materials. VRC.LOL does not use Riot branding to imply that the product is official, approved, or operated by Riot.

Registration and credentials

Riot API credentials are kept in private server configuration and are not placed in browser code, URLs, downloads, or the Windows Companion. A Production key is used only for the registered product it belongs to. Material product features and Riot data uses must remain accurately described in the Riot Developer Portal.

The VRC.LOL League Tools Production application is currently Pending Review. Riot-backed public player lookups and publication of private Match-v5 research remain disabled until Riot approves the relevant use. The invited Companion remains a private prototype and contains no Riot API key.

Private verification records

When an invited tester explicitly enables completed-match verification, Companion observations are treated as provisional and untrusted. They remain private while a paced server-side queue requests the corresponding Match-v5 record. Only Riot-returned fields are labelled verified; unavailable or rejected records remain clearly identified and are not promoted into public or aggregate evidence.

Competitive integrity

The product does not expose hidden information, create unofficial MMR or ELO ratings, shame or report players, or automate game actions. Pre-game references may show visible draft information and multiple choices. During play, the companion keeps that plan fixed and may display player-visible facts, but it does not use live score, gold, levels, inventory, or objectives to select a target, reorder a build, prescribe a purchase, or calculate a win chance.

The current build does not track or share unavailable enemy ultimate or spell cooldowns. A proposed champion-select rune or summoner-spell application flow remains disabled unless its exact Preview, Confirm and Apply behavior is recorded and audited as a material product change.

The desktop companion remains a private review build while its League Client and Live Client usage is disclosed to and reviewed by Riot. A private review build is not evidence of Riot approval and must not be represented as endorsed or safe for public distribution until that review is complete.

Local client and spectator data

The companion uses local League Client and Game Client interfaces that Riot documents as local and unsupported for third-party support guarantees. It may also display delayed spectator information made available by Riot. These interfaces can change, omit fields, or stop working without notice.

Spectator mode is read only. It cannot pick, ban, swap, send chat, control another account, or remove Riot's spectator delay. Inferred lanes are labelled as likely rather than confirmed.

Local storage

Completed non-custom matches are saved locally for each Riot account until you clear them. Switching accounts switches this history.

The companion's history is encrypted and separated by Riot account for private post-match review. Records from another Riot account are not shown in the active account's history. Records can span game patches; each record retains its own patch when known. The tester can delete the active history in the app.

Explicit local recovery runs between matches and reads up to 20 recent entries from the active account's local League client per request. This request limit does not delete older saved matches. Recovery preserves existing saved plans and does not enable uploading or private verification. Missing historical roles, saved plans and unavailable event timestamps are not inferred.

Custom matches

Custom-match history is not included in public player lookups. It may only be shown in a future feature when the affected player explicitly opts in through a Riot-approved account flow.

Availability and changes

Features may change, pause, or be withdrawn when Riot endpoints, policies, rate limits, game behaviour, or product-review requirements change. Cached and spectator information can be older than the live account state. Continued use after a published update means using the product under the revised terms.

The invited Windows build uses a required update channel. It may refuse to open until it can verify the current release and install a mandatory replacement. The update process verifies the download size and SHA-256 before replacing the executable and preserves the existing file when verification or replacement fails.

Riot notice

VRC.LOL League Tools is not endorsed by Riot Games and does not reflect the views or opinions of Riot Games or anyone officially involved in producing or managing Riot Games properties. Riot Games and all associated properties are trademarks or registered trademarks of Riot Games, Inc.