Privacy Policy

1. Data we use

We process the Riot ID and region you enter, plus account, rank, match history, champion mastery, challenges, and other game data available through the Riot Games API.

2. Why we use it

We use this data to show player statistics, playstyle analysis, match autopsies, ally synergy, comparisons, and growth history, and to maintain service quality, security, and performance.

3. Data storage

• Search history and favorites are normally stored only in your browser.
• To improve response time and protect the Riot API, exact Riot ID checks and transformed player analyses may be reused for up to 6 hours, and match-timeline analyses for up to 30 days. Expired physical rows are removed when that cache is accessed again or during maintenance, so physical deletion can occur later. API keys, cookies, IP addresses, and signed tokens are not stored in this cache.
• For player suggestions, public Riot IDs verified by a successful Riot analysis may be retained without automatic expiry in a minimal search directory with region, profile icon, rank, and role display fields. They are removed when a valid removal request is completed or the directory is discontinued. Suggestions do not include the visitor, lookup time, PUUID, match data, or growth records.
• Community features may store signed analysis snapshots, growth missions, session records, and decision-quiz answers on the service.
• For full-history comparisons, the service may also store normalized Ranked Solo match summaries from Riot Match-V5, including match ID, match time, champion, result, and aggregate KDA, gold, damage, vision, and related values.
• To build Rank Journey, the service may store Ranked Solo tier, division, LP, W/L counters, and observation times verified through Riot League-V4, linked only to a server-side pseudonymous account key. The rank-observation table does not store the visitor, Riot ID, PUUID, or match details, and values from before tracking began are not reconstructed.
• Each browser that uses community features receives a separate signed owner identity to distinguish community records.
• Riot API keys and service-side secrets are never sent to the browser.

4. Third-party services

ANALOL uses the Riot Games API and Data Dragon. Their terms and privacy policies apply to data handled by those services.

5. Anonymous service-quality measurements

• We aggregate page views, search attempts and outcomes, and LCP, INP, and CLS using only mobile/desktop classes and hourly counts, sums, and maximums.
• These aggregates do not store Riot IDs, search text, URLs, IP addresses, cookies, user IDs, email addresses, or referrers. Rows older than 90 days are progressively removed by subsequent measurement activity or operational maintenance.
• To prevent abuse, we derive a salted one-way fingerprint from an account ID when available or a network address and store only short-window request counts. Raw values are not stored; expired rows are progressively removed by later processing or maintenance.

6. Support and deletion controls

• The Support and data controls page can clear browser search history and favorites, delete growth missions, sessions, and decision answers linked to this browser, and submit a request to remove shared player data.
• A support request stores its type, Riot ID and region when needed, the text you enter, status, receipt/update times, and a hash of a random receipt key. There is no dedicated email field. Do not enter secrets. Resolved or closed requests older than 180 days are progressively removed during later support activity or maintenance; open requests remain until handled.
• The operator reviews shared-player removal requests. A minimal normalized Riot ID and region suppression record is retained to prevent the removed data from being saved again.

7. Policy updates

This policy may be updated when features, laws, or Riot Games developer policies change. Material updates will be announced in the service.