Privacy Policy

What the site collects

A draft, when you build one

The champions you place on the board, the rank tier you selected, and the probability and rankings the model returned. These are stored so the model's published accuracy can be measured against predictions that were made before the games were played rather than reconstructed afterwards — that is the whole argument of the metrics page, and it is not possible without keeping them.

A per-draft token

Your browser mints a random opaque string per draft and sends it with each update, so that a sequence of boards can be recognised as one champion select rather than several people drafting at once. It contains nothing and is derived from nothing about you, it is hashed before it reaches disk, it lives in sessionStorage rather than a cookie, and it is discarded when you close the tab.

A Riot ID, only if you type one

Identity is optional on every page that offers it. When you provide a Riot ID, the server resolves it to a PUUID through Riot's API in order to read your rank, your champion mastery, or your current game, and then:

A raw PUUID exists briefly in a short-lived, non-public queue while a prediction is waiting to be matched against the game you actually played, and is dropped once it is.

What is kept, and for how long

The values below are the shape of the policy. The current settings of the running service are printed under “What we keep” on the metrics page, read from the service itself, so they cannot drift from what the software actually does.

Pseudonymous is not anonymous. A salted handle attached to a stored draft is not identifying on its own, but someone holding a large corpus of match data could in principle link it back to an account. Saying “anonymised” would overstate it, so this page does not.

Separately: the public match data behind the model

The model and the tier list are built from completed ranked games collected from Riot's public Match API — the same games Riot already publishes to any client, and the same data every match-history site is built on. That corpus is used in aggregate to train and to compute champion statistics. Nothing on the site exposes an individual player's match history, and no page will tell you anything about a player other than the visitor who typed their own name in.

Who else is involved

Your choices

The simplest control is the one built into the product: do not enter a Riot ID. Every prediction works without one; identity adds your rank and mastery to the estimate and is offered, never required.

To have stored predictions associated with your handle deleted, email contact@kaylol.gg with the Riot ID you used. Deletion is performed by hand by the operator: because the site stores no account and no raw identifier, it cannot offer a self-serve delete button without first asking you to prove the account is yours, which would mean collecting more about you rather than less.

If you are in a jurisdiction that grants rights of access, correction, deletion or objection over personal data — the UK and EU among them — those requests go to the same address and are honoured. Data is stored on a server in the United States.

Children

KayLoL is not directed at children under 13, collects no age information, and has no account system. It should be used in line with Riot's own age requirements for League of Legends.

Changes and contact

The date at the top is the date of the last change. If what is stored ever expands, this page changes before the collection starts, not after.

Anything at all: contact@kaylol.gg. See also the Terms of Service.