Privacy Policy

1. Controller

The controller responsible for this service under the General Data Protection Regulation (“GDPR”) is:

2. Current preview status

The current early preview accepts replay uploads for analysis. After you actively accept the current Terms and acknowledge this Privacy Policy, your browser uploads the selected replay directly to non-public Cloudflare R2 storage using a short-lived signed URL. A processing job is then queued and made available through a randomly generated status URL. Completed analyses are available without authentication to anyone who has the report URL.

3. Data we process

4. Purposes and legal bases

• Provide the requested analysis and report under Article 6(1)(b) GDPR where processing concerns the uploader.
• Process limited data about other match participants, secure the service, prevent abuse, improve reliability and analysis methods, and create comparison benchmarks and aggregate statistics under our legitimate interests in Article 6(1)(f) GDPR.
• Meet binding legal obligations under Article 6(1)(c) GDPR where required.

Our safeguards include data minimisation, short retention for raw replay files, non-public replay storage, randomly generated report URLs, search-engine exclusion instructions, and a prohibition on using this data to make decisions with legal or similarly significant effects about individual players. You may object to legitimate-interest processing for reasons relating to your particular situation.

5. Retention

Raw replay

Deleted immediately after successful parsing and within 24 hours of a failed or abandoned job.

Analysis reports and extracted data

Retained indefinitely with no scheduled automatic deletion. This includes retained player and match identifiers, gameplay events, measurements, and report data used to provide analyses and improve the service.

Aggregate statistics

Retained indefinitely with no scheduled automatic deletion. These statistics may be used for comparison benchmarks displayed by the service.

Security logs

Normally deleted after 14 days. Relevant records may be isolated for longer when needed to investigate a specific incident or meet a legal obligation.

6. Browser match history

When you successfully view a match analysis, this browser may save a local history entry so you can open it again. The entry contains the report’s public token, map, mode, score, region, match date, and your latest analysis selection. It does not contain the replay file, player statistics, or a copy of the report.

This history is stored only in your browser and is not sent to our servers or synced between devices. It keeps up to 25 recently viewed matches and remains until you remove entries, clear browser storage, or use the Clear history control. Removing an entry from browser history does not delete the corresponding report or analysis data from the service.

7. Service providers and locations

• Netcup: website, API, and associated hosting in Germany.
• Cloudflare: non-public replay object storage in the EU and related delivery and security services.
• Plausible Analytics: aggregated, cookie-free website statistics processed and stored in the EU when analytics is enabled.

We enter into data-processing agreements with processors. Cloudflare are US-headquartered providers. Where their support, subprocessors, or legal structure involves an international transfer, we rely on the safeguards stated in their data-processing agreements, including applicable adequacy mechanisms or Standard Contractual Clauses. You may request information about these safeguards using the contact details above.

8. Privacy-friendly usage statistics

When enabled, Plausible measures page views and fixed events such as “Replay selected”, “Replay rejected”, and “Analysis completed”. We do not send filenames, Riot IDs, match IDs, report URLs, file properties, replay-derived values, or free-text properties to Plausible. Plausible states that its hosted service uses no cookies or persistent visitor identifiers and does not store IP addresses. We do not use analytics for advertising or cross-site tracking.

9. Access and security

Raw replay files are stored in non-public object storage. The uploader and processing systems access them through short-lived signed URLs. Analysis reports are different: they do not require an account, password, or other authentication, and anyone with a report URL can view them. Report URLs use random public tokens, are marked not to be indexed by search engines, and are sent with a restrictive referrer policy, but those measures are not access controls.

10. Your rights

Depending on the circumstances, you may request access, correction, deletion, restriction, portability, or object to processing based on legitimate interests. Because the service has no accounts, please include the report URL or public report token and, where relevant, your Riot ID or match details so that we can locate the record. We may request additional information where needed to verify your identity and protect the rights of other match participants.

You may also complain to Der Landesbeauftragte für den Datenschutz und die Informationsfreiheit Baden-Württemberg, Heilbronner Straße 35 70191 Stuttgart (poststelle@lfdi.bwl.de) or another competent data-protection authority in the EEA/UK country where you live or work.

11. Data received indirectly

Replay information about other match participants is provided by the uploader rather than directly by those participants. Replays may include in-game identifiers, but they do not ordinarily provide reliable direct contact details for every participant. We therefore cannot ordinarily notify every participant individually. We make this notice publicly available, and a participant may contact us to exercise applicable rights.

12. Changes

We will update the effective date and version when this notice changes. Material changes will be shown before the next upload. We do not make decisions producing legal or similarly significant effects through automated processing.