Privacy Policy
Last updated:
1. Scope and operator
This notice describes Gapper's current player search, profile and statistics features. A Riot identifier can relate to an identifiable person; game data is not treated as anonymous merely because it uses a screen name or PUUID.
Gapper is an independently operated project, not a registered company. Its operator is responsible for the service and the personal data processing described in the Privacy Policy.
For service questions or privacy requests, email support@gapper.lol. Never send a Riot password or API key.
2. Riot IDs and player searches
When someone searches for or visits a player profile, Gapper processes the Riot game name and tag line in the request. The searched player may be someone other than the visitor. A successful lookup retrieves the canonical Riot ID, PUUID (Riot's player identifier), profile icon, summoner level, ranked information and recent match data from Riot Games.
After a successful profile lookup, Gapper saves or refreshes the player's PUUID, game name, tag line, profile icon ID and last lookup timestamp in its known-player database. Names, tags and icons can then appear publicly in autocomplete. This is an index of looked-up players, not a record identifying who searched for them.
Partial-name autocomplete queries Gapper's database, not Riot's API on every keystroke. Profile URLs contain the searched Riot ID and may appear in browser history and hosting request logs.
3. Match data and statistics
Gapper retrieves match histories to display results, champions, kills, deaths, assists, minion counts, queues and durations. Loaded history is held in page memory; match responses may also be cached temporarily in server memory.
A separate collector obtains matches involving currently Emerald+ EUW Ranked Solo/Duo seed players. Stored records include match IDs, patch, queue, creation time, duration, participant PUUIDs, champion, team, role, win/loss, summoner spells, item information and complete rune/perk data. All participants in an accepted match may be stored, whether or not anyone has searched for them on Gapper.
These records support aggregated champion, role, matchup, item, rune and summoner-spell statistics. Current-patch display filters do not delete older stored matches. Source information comes from Riot Games APIs; static game metadata and assets also come from Data Dragon and CommunityDragon.
4. Purposes and legal basis
Optional Gapper accounts use Supabase Auth for email/password sign-in and Google sign-in. Account data includes your email, authentication identifiers, linked sign-in providers, Gapper username, chosen avatar and account timestamps. Passwords submitted through Gapper are passed securely to Supabase Auth; Gapper does not store plaintext passwords in its profile database. Google sign-in supplies identity information such as your email and profile details to Supabase. Linking Google or adding a password keeps the same Gapper user ID. Gapper sign-in alone does not prove Riot account ownership.
When Riot verification is enabled, you can separately sign in through Riot Sign On to link accounts. Gapper stores the verified Riot account identifier, PUUID, Riot ID, region and verification timestamps. Linked Riot accounts, your Gapper @username and selected profile icon are public and searchable, including the owner link on player profiles. Riot access tokens are used only during verification and are not stored. A short-lived essential cookie and hashed verification state protect the linking flow. You can unlink accounts in account settings; this removes the ownership claim but does not remove independently collected game statistics.
While Riot verification is pending, you may provisionally claim a League profile by declaring that you own the account. These claims are not Riot verification. Gapper stores the PUUID, Riot ID, region, your declaration timestamp, claim status and expiration. Your Gapper username and active claimed profiles are public. Claims may expire, be disputed, or be revoked; verified Riot ownership takes priority. Dispute reasons, reporter identifiers and administrator decisions are stored for resolving abuse and are not public. Claim attempts and reports are rate limited. Unlinking removes public ownership; inactive claims and dispute records may remain for abuse prevention until account deletion or a reviewed removal request.
Account information and essential session storage are used to provide the account you request and secure access to it. Where the GDPR applies, providing the requested account relies on performance of a contract, and proportionate abuse prevention and security processing relies on legitimate interests. Creating an account is optional and is not consent to advertising. All existing statistics, profiles and searches remain available without signing in.
Player identifiers are used to resolve profiles, provide known-player search and associate match records. Match data supports the statistics service. Technical request information supports delivery, troubleshooting and security. Gapper does not make decisions with legal or similarly significant effects about players using these statistics.
Where the GDPR applies, the basis for this processing is legitimate interests in providing and maintaining a community game-statistics service, helping users find player information, and keeping the service reliable and secure. This basis applies only where processing is necessary for those interests and is not overridden by the rights and freedoms of the people concerned. You may object to processing based on legitimate interests as described below. Visiting Gapper or searching for a player is not treated as consent to the processing of that player's data.
Support notifications
When you submit a support ticket or reply, Gapper may send the ticket subject, message content and creator?s Gapper username to the support team through Discord. Discord processes that notification content. Your account email, authentication credentials and session tokens are not included in these Discord notifications.
5. Hosting, recipients and international processing
Vercel hosts the website and Supabase stores the known-player and match databases. These providers process information needed to operate their services. Hosting infrastructure may process IP addresses, request URLs, browser information, timestamps and diagnostic logs. Exact logging and backup retention depend on deployment settings.
Riot receives identifiers needed for server-side API requests. Browsers request game images from Riot's asset servers and may expose their IP address and ordinary request headers to those servers. CommunityDragon supplies game data to Gapper's server.
Riot Games, Supabase, Vercel and CommunityDragon may process information in countries other than your own, including outside the European Economic Area. Locations depend on the provider, configured regions and infrastructure. This notice does not represent that all information stays in the EU. Contact Gapper for information about the arrangements and safeguards applicable to your data.
Provider notices: Riot Games, Supabase, and Vercel.
6. Cookies and browser storage
The application does not implement separate analytics trackers. Optional account sign-in uses Supabase session and authentication-flow cookies to keep you signed in, refresh your session, and complete verification, recovery or Google sign-in. These essential account cookies are separate from optional advertising consent. Signing out ends the session on this device. Player searches and loaded match history continue to use page memory rather than account cookies or browser storage to save that history. Ordinary browser caching and infrastructure-level behaviour are separate and depend on the browser and deployment.
Gapper loads Google AdSense to support automatic advertising. Whether ads are displayed depends on Google's site approval, advertising settings and applicable consent choices. Google Privacy & Messaging provides the European consent message for eligible visitors; loading the integration does not mean that every visitor will see an advertisement.
If advertising is enabled, Google and selected advertising partners may process IP addresses, browser and device information, page interactions, cookies, advertising identifiers and similar technologies to deliver, measure and secure ads. Personalised ads may use previous activity or interests; non-personalised ads use contextual information but can still require consent for cookies or device access. Non-personalised does not mean cookie-free.
Google Privacy & Messaging is the selected Google-certified consent management platform, supporting the applicable IAB Transparency and Consent Framework for the EEA, United Kingdom and Switzerland. Its European message must be published before this integration is enabled. Where required, consent is needed before advertising storage or access on your device and before personal data is used for personalised advertising. Any processing on another legal basis must be identified for the relevant purpose and provider; legitimate interests are not a substitute for required consent.
When the published Google consent message is available, you can accept, reject or manage optional purposes and advertising partners, and use Google's privacy and cookie settings link to revisit your choices and withdraw consent. These controls are supplied by Google's CMP, not a separate Gapper banner. Declining optional advertising consent does not prevent access to the statistics service.
Google and advertising partners may process data outside your country, including outside the EEA. Before activation, this notice and the consent interface will identify the configured recipients, purposes, retention information and applicable transfer safeguards. Read Google's Privacy Policy, how Google uses information from partner sites, and Google's advertising technologies policy. My Ad Center provides Google advertising controls; these do not replace site-specific consent choices.
7. Retention
Gapper account and profile records remain while the account exists, unless removed following a valid deletion request. There is no automatic account expiry in the application. To request account deletion, contact support using your account email. Deleting the Supabase Auth user also removes its Gapper profile and any future linked-account records; it does not automatically delete independently collected Riot match statistics. Supabase authentication logs, email delivery records and backups follow the provider configuration and applicable retention arrangements.
Known-player and collected match records currently remain in the database until removed; there is no automatic expiry in the application. Revisiting a profile refreshes its indexed details. Server match caches are bounded by entry count and expire automatically after five minutes. Page-memory history resets when the page is reloaded.
Database records support the operation and maintenance of the statistics and search services. There is currently no fixed automatic deletion period. You can request deletion or object to processing using the contact below, subject to applicable rights and legal requirements. Provider logs and backups follow the relevant provider settings and arrangements; deletion from the active database does not necessarily remove backup copies immediately.
8. Your rights
Where the GDPR applies, you may have rights to access and obtain a copy of your personal data, correct inaccuracies, request erasure or restriction, object to processing, and receive portable data where the relevant conditions apply. These rights are subject to legal conditions and exceptions. If processing relies on consent, you can withdraw it without affecting the lawfulness of earlier processing.
You can also complain to a competent data protection authority, including in the EU country where you live or work. Gapper cannot change Riot's source records; requests concerning Riot's own processing should be addressed to Riot. Removal of a Gapper record alone does not remove the underlying Riot data.
For a Gapper privacy or data-rights request, email support@gapper.lol, identify the relevant Riot ID and describe your request. Proportionate identity verification may be needed to protect another player's information; never send a Riot password.
9. Changes to this notice
Changes to features or processing will be reflected here with an updated date. Material changes will be communicated where required by law. Review this notice for the current description of the service.
