How Saiki Uses Riot Match Data

No archive request or ZIP upload

Saiki uses Riot’s supported developer APIs when you enter a Riot ID and region. You do not need to make a personal-data access request to Riot, wait for an archive, or upload a ZIP file.

This is not Riot Sign On. Saiki does not redirect you to Riot for authentication or receive proof that the Riot account belongs to you. The profile-selection step helps confirm that the lookup returned the intended account, but it is not strong ownership verification.

The API sequence

Saiki’s Riot API key remains on the server. The browser sends the game name, tag line, and selected platform to Saiki’s authenticated server route.

The current sequence is:

1. Account-V1 by Riot ID: resolves gameName + tagLine to a PUUID.
2. Summoner-V4 by PUUID: retrieves League profile information for the selected platform.
3. Champion-Mastery-V4 by PUUID: retrieves champion mastery records.
4. Match-V5 match IDs by PUUID: requests recent match IDs, prioritising ranked Solo/Duo queue 420 and falling back to other queues if needed.
5. Match-V5 match details: retrieves selected match records and calculates aggregate metrics.
6. Older sample: searches the available Match-V5 history and selects up to 50 older matches, preferring ranked Solo/Duo when enough are present.

Riot’s current League documentation directs third-party products to use Riot ID and PUUID endpoints rather than the deprecated summoner-name lookup. Saiki’s local implementation now follows that route.

Read Riot’s League API guidance and general developer policies for the source rules.

What Saiki stores

After you select the intended profile, Saiki stores data on your Saiki user record, including:

• Riot ID fields and selected region;
• account and summoner fields returned by Riot;
• profile icon, summoner level, and selected top champion;
• champion mastery records;
• processed aggregate metrics from the recent and older samples;
• the number of selected recent and older matches;
• fetch and connection timestamps;
• periodic snapshots used by the paid Evolution view;
• questionnaire answers, calculated scores, report data, and purchase entitlement elsewhere on the same account.

The gaming-profile route stores processed metrics and sample counts, not the complete raw match objects it fetched during that request. Riot can change API fields, availability, retention, or access rules, which may affect future refreshes.

What Saiki does not receive

Through this flow, Saiki does not receive:

• your Riot password or private login username;
• Riot Sign On tokens;
• chat logs or post-game messages;
• voice communications;
• purchase or payment history from Riot;
• your Riot support tickets;
• a Riot personal-data archive;
• files from your computer.

Saiki does not receive chat logs through Match-V5, so it cannot validly claim to analyse communication style, toxicity, encouragement, or conflict language.

The Match-V5 records do include many gameplay fields for participants in the selected matches. Other players’ match data is therefore part of the fetched record. Saiki should use it only as needed to calculate the connected player’s context and must continue to follow Riot’s policies.

How the metrics become indicators

The product aggregates selected fields such as champion and role variety, vision, wards, kills, assists, healing, deaths, KDA variation, surrender state, gold, and creep score.

Hand-set anchors normalize those values. The resulting indicators are experimental. Riot supplies game data, not personality conclusions, and Riot does not endorse Saiki’s mappings.

Read how to interpret the report for the exact mapping table and alternative explanations.

Delete or export your Saiki data

Use Saiki’s account controls to request an export or deletion of the data held by Saiki. These controls do not delete a Riot account or alter Riot’s own records.

Review the Saiki privacy policy for controller identity, purposes, legal bases, retention, recipients, rights, and contact details. If the embedded policy and the implementation disagree, deployment should stop until the legal text and data flow are reconciled.

Riot relationship

Saiki 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.