Privacy information

Last updated: 1 November 2026

Site delivery and hosting

This website is hosted on a Hetzner Cloud server in Falkenstein, Germany. We have concluded a data-processing agreement with Hetzner for the hosting service. The server receives connection data, including your IP address, requested URL, time and browser information, to deliver the website and protect it against misuse. The legal basis is Article 6(1)(f) GDPR; our legitimate interests are operating and securing the website. No visitor accounts or advertising/analytics scripts are configured in this application. The German server location does not mean other providers process data only in Germany.

The site-specific Caddy configuration does not enable a per-request access log. The application logs upstream errors and startup messages to container stdout/stderr; upstream errors can contain information from a provider response. Docker rotates these logs by size (three files of up to 10 MB), not age; this does not guarantee deletion after a fixed period. Proxy, host, provider and backup systems may have separate logs or copies. Server-side source responses stop being reused after three minutes, though expired entries may remain in process memory until replaced or restart; discovered video records are pruned on feed refresh when older than 20 days.

Match schedule and video discovery

The application server retrieves public fixtures from LoL Esports and public channel feeds and video metadata from YouTube to assemble schedules and video choices. These are server-to-provider requests. Unlocked matchups include only a flag indicating whether a final result is available, not the result or score. Your browser requests a match's score only when you select its enabled eye icon labelled “Show result.” The purposes are showing fixtures and finding relevant videos, under the site's delivery interest described above. No visitor identity is intentionally passed to those feed providers by the application. Server responses are cached temporarily; provider-side handling of the server's connection data is subject to their own practices.

Aggregate audience measurement

To understand how many people use the site, the browser sends a first-party visit signal when the page becomes visible and reports estimated visible-tab time in short intervals. The server necessarily receives the IP address and browser information with these requests. For an approximate daily distinct-browser count, it briefly derives a keyed value from the IP address and browser information and updates a coarse count sketch. The key is held only in server memory and changes daily or when the process restarts. Stored daily totals and count sketches contain no raw IP addresses, browser strings, cookies, account identifiers or individual activity histories. This measurement is based on Article 6(1)(f) GDPR, our legitimate interest in assessing basic site usage without third-party analytics; the legal basis is subject to review.

Aggregate daily figures are kept on the server for a rolling 30 days while the application operates; separate host backups may have their own retention. Distinct-browser counts are estimates, not exact counts of people: shared networks, changing addresses, bots, blocked scripts and restarts can affect them. Visible-tab time is an estimate, not proof someone watched a video. No analytics information is saved in your browser.

Former watched-game history

This version no longer offers watched-game tracking. When you load it, the application removes only its previous watched-history key no-spoilers-worlds-watched-v1 from localStorage on this website's origin. It cannot remove a key saved under a different domain; you can clear that site's data in your browser. The current version does not write new watched-game choices.

YouTube embeds

Browsing matchups and opening the source chooser do not create a YouTube iframe or send your browser to Google. The connection notice appears beneath the source choices; selecting a source immediately loads its player. We use YouTube's Privacy Enhanced Mode at youtube-nocookie.com; according to YouTube's embedding guidance, views in this mode do not personalise the viewer's YouTube experience and any ads served in this mode are non-personalised. This mode does not eliminate connections or device-storage requirements. The relevant YouTube service provider in the EEA is Google Ireland Limited. When you select a source, your browser sends Google/YouTube your IP address, browser/device information, this site's origin as player identity, and information needed to request and play the selected video. Google may store or access device information and process playback data for purposes described in its Privacy Policy. Unverified videos undergo a covered length check before playback; the player itself may reveal spoilers.

The schedule and score controls work without YouTube. Closing the chooser before selecting a source loads no player; closing the player afterward removes its iframe and stops further loading from this page, but cannot undo information already transmitted. Each new video requires a new source selection; the choice is not saved. The source click is not a separate consent confirmation. Whether this interaction satisfies the requirements for consent to the connection under Article 6(1)(a) GDPR and non-essential device access under § 25(1) TDDDG requires assessment. Google's own processing is governed by Google's policies, not by a claim that all of its processing is covered by the source click.

Google says it may process information on servers outside the EEA, including in the USA, and describes its use of the EU-US Data Privacy Framework and standard contractual clauses where applicable in its transfer-framework information. Those are Google's published statements; they do not establish that a particular transfer by this site is covered by a particular mechanism. Google/YouTube's own retention practices are described in their policies; closing the player does not delete data already held by Google.

Email and telephone enquiries

Displaying our email address or telephone number does not itself collect your contact details. If you contact us, we process the contact details and information you supply (including your email address, message and attachments if you email us) to handle your enquiry. Ordinary enquiries are processed under Article 6(1)(f) GDPR, our legitimate interest in responding; Article 6(1)(b) applies where necessary for pre-contractual steps you request, and Article 6(1)(c) where necessary to fulfil legal obligations, including statutory data-protection requests.

Email is received in an ordinary consumer Gmail account provided by Google; no Google Workspace processing agreement is claimed. Google's Privacy Policy describes its processing, recipients and retention practices, and its transfer-framework information describes international processing and safeguards claimed by Google. We follow a practice of deleting individual emails one year after receipt, except when an unresolved matter or legal obligation requires longer retention. This is our chosen period, not a statutory or automatically enforced deletion deadline. Telephone-enquiry information is kept only as necessary to handle the enquiry or meet applicable legal obligations.

Your rights

You may object at any time to processing based on legitimate interests (Art. 21 GDPR), on grounds relating to your particular situation. You may stop optional YouTube loading for the future by closing the player and not selecting another source; it does not affect processing that occurred before it. Subject to applicable requirements, you can request access, correction, erasure, restriction or portability of your personal data. Contact the controller above. You can lodge a complaint with a data protection supervisory authority, including the Hamburg Commissioner for Data Protection and Freedom of Information.