How Zenko analyzes League of Legends

Zenko reads match history and account data from the Riot Games API using the documented endpoints:

• Account and Summoner to link your Riot ID and summoner profile.
• Match V5 to fetch detailed per-match stats: kills, deaths, assists, CS (creep score), vision score, objective participation (towers and dragons), role and lane assignment, and win or loss.
• League and Ranked Data to read your current tier, division, and LP for calibration, and champion mastery scores.
• Data Dragon (static assets) to display champion and item artwork. Data Dragon is served directly by Riot and requires no API key.

We do not use any undocumented endpoints. All data is read-only public data tied to your bound League account; Zenko never makes changes to your account or sends commands.

Each League challenge is lane-scoped (top, jungle, mid, ADC, or support) and settles per-match using detailed metrics from Riot Match V5.

When you accept a challenge:Zenko records the challenge target (e.g. "get 8+ kills in 5 games as mid lane"). As you play matches in your assigned role, Zenko checks the post-game data to see if that match counts toward the challenge window and whether you met the target.

Three ways a challenge settles:

• Auto-settle at 12 hours. If you forget to manually settle, the challenge auto-settles at the 12-hour mark using whatever matches you played in your assigned role during that window. Same window as Fortnite and TFT.
• "Refresh progress" button (optional). Tap to see updated kill and match counters mid-session. Has a cooldown per challenge so the button cannot hammer the API.
• Manual settlement. Once you finish playing, you can click to settle immediately and see the result.

Zenko does not poll the Riot API in the background. Match checks happen only when you accept a challenge, refresh, or the 12-hour timer ticks. This keeps Zenko a respectful client of the Riot API and avoids opaque background traffic on your account.

Each League challenge is tied to one lane (top, jungle, mid, ADC, support). Only matches in your assigned role count. If you take a mid lane challenge and you queue for solo/duo, the challenge only checks your mid lane matches, not top lane or support games.

Targets can include lane-specific metrics:

• Kills, deaths, assists. Your raw KDA in that lane.
• CS or CS advantage. Creep score in that lane, or your CS per minute relative to the lane opponent.
• Vision or objective metrics. Ward coverage or participation in drakes and towers.

On the challenge hub, daily picks are mixed across lanes. Cards carry a lane tag (Mid / Top / Jungle / ADC / Support) so you know which role a challenge is scoped to. If a lane does not suit you, reroll the card.

Zenko surfaces an optional champion add-on that layers a meta-tier difficulty modifier on top of core targets. This is a pure calibration signal derived from the current patch meta-tier ranking (how strong a champion is in the current game patch), not a Riot endorsement or official tier list.

How it works: when you take a challenge, if the champion you play is in a higher meta tier, the target stretches a little to reflect that stronger champions have more impact on the game. Conversely, playing a lower meta-tier champion relaxes the target slightly.

Add-ons are completely optional. You can disable the champion modifier in your settings and take challenges without it, settling on raw KDA or CS targets instead. The core challenge remains the same, the add-on just tunes the difficulty number.

Targets re-tune to your recent per-lane performance history. If you average 5 kills per mid lane game, a Kill-Mid challenge might call for 19 kills across 3 games (roughly 1.2x your mean). If you go on a hot streak averaging 8 kills per game, the next Kill-Mid challenge stretches to match. Cold streaks relax it.

This is personal calibration, not an alternate ranking system. Zenko does not publish a public leaderboard, and does not re-rank Riot's Ranked ladder. The difficulty tuning is internal to Zenko and invisible to other players. The performance percentile on your profile is a personal signal: it reflects how your play compares within the Zenko player cohort, derived from your own match history. It is not a skill rating, an MMR or ELO estimate, or a ranking of all League players.

Each lane has its own performance baselines. Your mid mean and your jungle mean are tracked separately, so a Kill-Mid target reflects your mid skill, not your jungle skill, even though they both use the same metric definition.

What we store: we persist your League account binding, match history snapshots (for settlement), ranked tier, and aggregated analysis metrics (average KDA, CS, win rate per lane). All of this is derived from public match data from the Riot API.

What we do not store: passwords, email addresses tied to your League account, or any data from your Epic/Riot account besides what the public API returns.

On unbind: if you disconnect your League account from Zenko, we delete your stored analysis, match cache, and rank snapshots for that account. Only the account binding record itself is soft-deleted for audit purposes.

For detailed privacy and data retention policies, see /privacy and /legal.