Privacy Policy

What the website uses, why it uses it, and what you can control.

Who is responsible

Operator: Amadou Ba Araman. Individual publisher based in France.

Amadou Ba Araman is the controller responsible for personal data processed for this website. This policy covers nextqueue.win and its Cloudflare Workers address. The real-lookup section below describes the separate private prototype and the intended public service. This policy does not cover a desktop app.

Information used by the public website

Browser preferences: your chosen theme and the last Riot ID and region submitted in the demo form stay in local storage on your device. The form checks the format and loads fictional players. It does not send the entered ID to our server or to Riot. You can explore the demo without entering a real ID.
Connection information: Cloudflare receives your IP address, requested URL and technical request information to deliver and protect the website. Workers application log storage is disabled. This does not disable Cloudflare’s own infrastructure and security processing.
Contact messages: if you email us, we receive your email address, message and any attachments you choose to send. Include only what is needed for your request. Never send passwords, API keys or identity documents unless proportionate verification is specifically needed and agreed.

The site has no user accounts, advertising, analytics tools, tracking cookies or player database. Images, icons and fonts are served with the website. No real match records are fetched by the public demo.

Purpose and legal basis

We use connection information to provide and secure the website, and contact details to answer messages and resolve follow-up questions. Our basis is our legitimate interest in running a free website and responding to people who contact us. Browser storage remembers the preferences you choose; it is not used to profile you. We process information needed to handle data-protection requests to comply with our legal obligations. We do not sell personal data or make automated decisions with legal or similarly significant effects.

How long information is kept

Browser preferences: these have no automatic expiry. They remain until replaced or until you clear this site’s data in your browser settings. A displayed result disappears when you replace or close the page.
Contact messages: we keep a conversation while handling the request and any related follow-up. We delete it when it is no longer needed for those purposes. If specific information must be retained to meet a legal obligation or resolve a dispute, we keep only what is necessary for as long as that reason applies. There is no automated mailbox deletion rule.
Hosting metadata: the application does not keep request logs or submitted demo IDs on the server. Cloudflare’s separate operational and security retention is governed by its published policy and service obligations; disabling application logs does not imply that all hosting metadata is immediately erased.

Your choices and rights

You can browse without entering a Riot ID, clear browser preferences, and choose whether to contact us. Under the GDPR, you may request access, correction, erasure or restriction of your personal data, and object to processing based on legitimate interests. Portability applies where its legal conditions are met.

Email contact@nextqueue.win with enough information to identify your request. We do not routinely ask for identity documents; we may request proportionate verification if there is a reasonable doubt about identity. We aim to respond within one month and will explain any lawful extension. You may complain to the CNIL or your competent data-protection authority.

Real Riot lookups and temporary storage

Public live lookup is disabled. The following describes the implemented private EUW prototype and the intended public lookup flow. The public demo does not perform this processing.

What a real search uses

When a real lookup is enabled, the Riot ID and region you submit go to our server. It requests information from Riot Games’ official APIs: account identifiers and visible Riot IDs, level, current Solo/Duo rank, champion mastery, an available active match, and up to five recent eligible completed Solo/Duo games per visible player. Match responses can also include other participants who did not request the lookup. Missing information stays unavailable and anonymous players are not identified.

Our server uses the records to display the requested profile or match and calculate small-sample summaries and comparisons. The person making the search receives the available display information; internal account identifiers and the Riot API key stay on the server. Riot receives the requested identifiers and requests from our server, rather than directly from your browser. Riot’s own handling is described in its Privacy Notice. The intended hosted service uses Cloudflare for request processing; its international processing is described above.

No permanent player database

We retrieve history from Riot when it is needed. The prototype keeps temporary copies in bounded server memory to avoid repeated API calls; it does not save player profiles or build a permanent match-history archive. Its cache reuse periods are:

Available active matches: 15 seconds.
Account identities and recent-match lists: one minute.
Rank, champion mastery and account level: five minutes.
Completed-match responses: 30 minutes.

Temporary lookup sessions link a result to its history request and remain usable for five minutes. Expired cache entries and sessions are removed on subsequent activity; they can remain in idle memory until then. Restarting the process clears that memory. These are reuse limits, not a promise of erasure at the exact expiry time. Completed-match copies may contain the other participants returned by Riot. The browser remembers your last search and theme as described above; results remain in the open page until replaced or closed.

Purpose, safeguards and your rights

The intended purpose is to answer a requested EUW game-statistics lookup and explain the participants through limited historical context. The proposed basis for public lookups and caching is legitimate interests in providing that service, subject to completing the assessment of affected players’ rights before launch. Entering a Riot ID does not provide consent on behalf of other players, and Riot API access is not itself a privacy legal basis.

The service does not create advertising profiles, sell player data, reconstruct hidden identities or maintain a separate skill ranking. Crowns describe the displayed sample; they are not predictions or decisions with legal or similarly significant effects. See the methodology for sample limits and calculations.

The rights and contact procedure above also apply to people whose information appears in another person’s lookup. Contact us about access, correction, erasure, restriction or objection. Clearing our temporary copies does not change Riot’s records or automatically prevent a future lookup. There is no automated player opt-out system in the prototype; any objection or restriction requiring prevention of future processing must be addressed before public live launch.

Before activation, we will confirm that hosted caches, request protection and rights handling match this notice and update any changed processing details. Publishing this description does not activate live lookup or claim Riot approval.

Changes and publication details

This page carries its effective date. Changes in the service or its data use will be reflected here before the new processing begins. See the publisher and hosting details for the website’s legal notice.