Who operates the service
Laning Lab is operated by Ibrahim Mammadov, an individual based in Singapore, who is responsible for the personal data described here under Singapore's Personal Data Protection Act. Contact for privacy questions and requests: ibrahimmemmedov9a@gmail.com.
Data used for a player report
When you submit a Riot ID, Laning Lab resolves it through Riot to a PUUID and regional route. For matches in any game mode Riot provides (ranked, normal, ARAM, Arena, and others) it stores the match identifier, platform, queue, champion, role, result, start time, duration, KDA, CS, vision score, gold, level, final item identifiers, summoner spell identifiers, and rune identifiers. It does not store chat, friends, passwords, payment details, precise location, or the identities of teammates for the player report.
Lookup jobs store the PUUID, route, tag line, progress, completion state, and whether extended history was requested. The Riot ID-to-PUUID and route caches expire after 30 days.
When you expand a recent match, the service fetches the ten-player scoreboard from Riot on demand. It is returned to the browser and may remain in an in-process cache for up to 30 seconds, but other players' details are not written to player-history storage.
Purpose and source
The data is used only to build the report requested by the visitor, operate and secure the service, diagnose failures, and produce clearly labelled aggregate statistics. Match and account data comes from Riot's official APIs. Laning Lab does not sell player data or use it for advertising.
Optional performance measurement
If you allow performance data, the browser sends LCP, INP, CLS, rating, and the current path to Laning Lab. The application does not attach a Riot ID, PUUID, account identifier, or advertising identifier. Samples are deleted after 30 days. No measurement is sent before opt-in.
Retention and minimisation
New player collection keeps only the requested player's row, not all ten participants. Public lookup data is limited to fields used in the visible report. Completed or failed lookup jobs are deleted after 90 days, player match details after 365 days, and optional performance samples after 30 days. Rank tracking, which is optional and starts only when someone presses the button, checks that player's rank with Riot about every 10 minutes and when the page opens, keeps the snapshots for up to 90 days, and switches off after 30 days without a visit from the browser that started it. The optional “Wrong? Tell me” form stores the message you write, the page it came from and a contact only if you add one, for 180 days, and is used only to fix mistakes; please do not include personal details. Encrypted backups of the database are kept for about 14 days (daily), 6 weeks (weekly) and 13 months (monthly), so data removed from the live service can remain in a backup for that long; backups are used only to recover from a failure.
Service providers and transfers
The service uses AWS Lightsail and Amazon S3 in Singapore for hosting and encrypted backups, Riot Games APIs and Data Dragon for game data and static assets, and the domain's DNS provider. The browser does not load advertising, behavioural analytics, payment, review, chat, or social-login SDKs.
Your choices and rights
You may refuse optional performance measurement and reopen Privacy choices from the footer. You may also ask for access, correction, withdrawal, or deletion as described on the data rights page. Some public match data may later be collected again if another visitor requests a fresh report.
Children
The service is for a general audience and account creation will not be offered to children under 13. No age, parent contact, or child profile is collected today. Before accounts launch, the age screen and any required parent or guardian consent must be implemented and reviewed for each supported jurisdiction.
Security and changes
HTTPS is enforced. Application secrets remain server-side, backups are encrypted and restore-tested, and public API requests are rate-limited. No internet service can promise absolute security. Material policy changes will update the effective date and, where required, request a new choice.