Privacy aboard policy

Arrr, lookup data

When ye run a lookup, th' service processes th' Riot ID and League platform ye submit. Public profile, ranked, mastery, and clash data returned by Riot may be cached briefly to make repeated lookups faster and reduce unnecessary Riot API traffic. Custom-clash captain's log be excluded from public results unless a future Riot-approved sign-in flow obtains th' sailor's explicit opt-in.

Arrr, technical records

Th' web harbour may record standard request ship's intelligence such as IP address, time, requested course, response status, and browser user agent fer security, reliability, and abuse prevention. These records be nay used to loadout advertising profiles.

The Companion page offers optional Hype and Read buttons. To limit repeat inflation, the server converts the requesting public network address into a keyed one-way digest scoped to the selected response and stores only that digest with the response time. It does not store the readable address in the engagement table, set a tracking cookie, or treat a button press as proof of one unique person. People sharing one public network share the same allowance.

Arrr, riot credentials

VRC.LOL will ne'er ask fer yer Riot Games password. API credentials be held only in private harbour configuration and be nay sent to browsers. Future Riot sailor record linking would use Riot Sign On and would receive its own consent and retention captain's particulars afore release.

Th' API use and rate limits chart explains how requests be paced, capped, cached and paused while Production access remains under inspect.

Arrr, desktop companion

Th' Windows companion be currently an invited test loadout. It reads sailor-visible League Client, Live Client, and delayed spectator data from Riot services running on th' local computer. Spectator ship's intelligence can arrive late or omit assignments and action captain's log. Th' companion labels inferred roles and does nay claim delayed spectator data be live.

Th' League lockfile, its local password, and shipshape local-client responses remain on that computer and be ne'er sent to VRC.LOL. Th' companion does nay read League process memory, inject code, or include a Riot API key. Th' present loadout does nay write runes, summoner spells, picks, bans, chat, pings, purchases or other actions into League.

Invitation codes be checked agin' one-way password hashes held in private harbour configuration. Successful entry creates a short-lived, single-use browser haul aboard token; th' plain code be nay stored in th' URL or harbour rate-limit record. Failed attempts be counted agin' a temporary network-address hash to limit guessing.

Afore opening, th' invited loadout contacts VRC.LOL to retrieve a guarded release manifest. That request includes th' installed companion version and loadout number in its user agent. Required ship's bulletins be downloaded from VRC.LOL, checked agin' th' published file size and SHA-256, and installed locally. Standard short-lived harbour security logs may record th' request IP address and user agent.

Local clash captain's log

Completed non-custom clash summaries may be stowed on th' computer fer private post-clash inspect. Each Riot sailor record receives a separate local captain's log identified by a one-way sailor record fingerprint. Stored records exclude sailor names, Riot IDs, and sailor record identifiers; they retain only th' champions, roles, final scoreboard facts, gear, and prize totals used by th' inspect.

Finished non-custom matches be saved aboard this PC for each Riot account till ye clear ’em. Switching accounts switches this log.

History is protected with Windows account-bound encryption. Records can span game patches and retain their recorded patch when known. The app initially shows 20 matches; showing older matches does not remove saved records. History can be deleted at any time from inside the companion. By default, this history is not uploaded to VRC.LOL.

Optional private clash verification

The invited build contains an opt-in client for private completed-match verification. Go service integration, central VRC.LOL identity authorization and Riot registration review remain release gates; the local control does not establish service availability. The existing client sends a provisional, anonymous completed-match record, canonical Match ID, routing region and token-keyed one-way participant proof when separately enabled and configured. It does not send a Riot ID, player name or raw PUUID.

The intended verified flow keeps the record private and labelled pending until the server retrieves the completed match through Riot Match-v5. Riot-returned result, participants, score, items, objectives, queue, patch and duration replace the provisional factual fields. Unverified Companion records are never used for public statistics or aggregate build evidence. If the completed timeline is delayed, statistics can remain verified while event timing is pending. Timeline retries are limited to six attempts within 24 hours. The worker discards the participant proof when verification and timeline recovery complete, expire or are rejected.

Optional live-chart connection

Th' connection be off by default and requires a private token. When th' tester enables it during their own active clash, th' companion can send a restricted factual snapshot containing champion, role, queue, clash clock, level, K/D/A, present doubloons, anonymous crew champion composition, completed prize totals, and structure events reduced to side, course, tier, and clash time.

Th' upload contract rejects spectator mode, sailor names, Riot IDs, sailor record identifiers, champion positions, local captain's log, inventory, loadout advice, foe rankings, th' League lockfile, and shipshape local-client responses. Detailed structure events be limited to th' token owner, th' active feed expires, and disabling th' connection stops future snapshots.

Arrr, retention and control

Short-lived web caches and standard security logs be retained only fer service operation, abuse prevention, and Riot rate-limit protection. Local companion captain's log be controlled on th' tester's computer as described above. Questions or requests concerning harbour-held data can be raised through th' contact below.

Contact

Privacy aboard questions can be raised through th' VRC.LOL community at vrc.lol/discord.