Privacy Policy.

Who runs this site

The QWTF Play project runs qwtfplay.com. For questions or a removal request, contact us in the QWTF Play Discord server. Tell us which public match or player entry you mean, or which site data you want removed.

Signing in

You can browse and use the public browser client without a QWTF Play account. If you sign in with Discord or Steam, the site gets your provider account ID, display name and avatar. It puts those fields, the provider name and issue time in a signed browser cookie; signing in alone creates no server-side account record, and the site never stores your email or password.

If you claim a record, the server stores your provider account ID with the claimed archive name until you remove it. A Discord claim may add the QWTF Play Veteran role.

The sign-in cookie lasts up to 30 days. Signing out removes it from your browser. Discord's one-click flow also uses a short-lived state cookie. If you use the Discord bot's one-time link or code, the site keeps that pending request in server memory for up to 10 minutes and uses a short-lived request cookie. The bot sends the link or code by Discord direct message.

On your device

The browser client uses local storage for your chosen server, player name, team, class, controls, custom configuration and, if you enter one, your QWTF Live login token. The site also remembers recent replays and a Discord sign-in name in local storage. These values stay in your browser until you clear them. A QWTF Live token you enter is sent to the selected game server when you join; the site does not put it in the QWTF Play account cookie.

Site counts

The site counts page views, downloads, plays, replay watches and selected link or feature clicks. To avoid counting the same visitor repeatedly, it combines the request IP address and browser user-agent with a random daily salt into a hash. The raw IP address and user-agent are not stored in the metrics database. The site removes previous days' hashes when a new day's salt is created; aggregate counters remain in the database without a set expiry in the code. Once per visitor per day it also notes which website sent you, as a hostname only (for example google or reddit, never the page address or any search words), and which part of the site you entered on. These counts do not use the sign-in cookie.

Public match record

The player record and replay archive present match and player information built from public QWTF Live match logs and archived match demos. Names, match participation and match statistics can remain in those published datasets; the site code does not set a deletion date for them. Long-term players also have their own career page, which search engines may list. Contact us on Discord with the specific entry if you want to ask for removal or correction, or to have your career page kept out of search results.

Other services

Discord and Steam handle sign-in on their own services. Opening a video or film link takes you to YouTube; the site's YouTube player loads only after you choose to play a video. Client downloads lead to GitHub Releases. QWTF Live provides the game servers and source match logs. Cloudflare carries traffic to this site. Those services handle data under their own terms and privacy information.

Google API services

A private production tool uses the YouTube Data API to manage the QWTF Play owner's own YouTube channel. It is separate from the public website and does not collect visitor data. Watching a YouTube video follows YouTube's own data practices described above.