Privacy Policy

Last updated: August 4, 2026

QuakeHub is built to collect as little as possible. We do not sell data, run advertising trackers, or build profiles of users. Here’s exactly what happens.

Website

• No accounts, no third-party trackers. The site sets no advertising or cross-site tracking cookies, and loads no analytics scripts - nothing about you is sent to Google, Plausible, or anyone else.
• Aggregate traffic counts. So we can see how the site is doing, our own server tallies each page view: the page you landed on, the domain that linked you (never the full URL), and an approximate country. To avoid counting the same visitor twice in a day we use a one-way, salted hash of your IP and browser string - your IP is never stored, the hash cannot be reversed, and it deliberately changes every day, so it can’t follow you over time or across sites. To keep automated traffic out of these counts, the requests the page itself makes to our own data endpoints are hashed the same way and matched against page views within the same day - a visitor only counts as real when both appear; nothing extra about you is collected. For arrivals from an outside site we also count which hour of the day that site sent visitors - an aggregate per-site tally that says nothing about any individual.
• API requests. Calls to the public /api/v1 endpoints are counted the same way, so we can tell whether anyone uses it: which endpoint was called, the domain of the page that called it (hostname only, never the full URL - this is how we can see that somebody has embedded one of our badges or the live world map), and the same one-way daily hash to count distinct callers. We also record the kind of client from the browser string - “a browser”, “curl”, “python”, or a bot’s own self-declared name - but never the full user-agent text itself.
• Ping estimate & map centering. To estimate your latency to each server, and to start the live world map near you, we look up an approximate location from your IP address (via an offline GeoIP dataset) at request time. This lookup is computed on the fly and not stored.
• Local preferences. Your favorite servers and last-used game are saved in your browser’s local storage, on your device only - never sent to us.
• Browser alerts. If you turn on a bell to be told when a server or game becomes active, we store the push endpoint your browser gives us (an opaque URL issued by Google, Mozilla or Apple) and which game or server you asked about. That is the one thing on this site stored per person, so to be plain about it: it is not linked to a name, an email or an IP address, we cannot use it to identify you, and it is deleted the moment you turn the bell off or your browser revokes it. Notifications carry no payload - the alert says nothing to the push service about which server woke up; your browser asks us separately. Turn alerts off in the site, or revoke notifications for quakehub.net in your browser, and the record is gone.
• Standard server logs. Like any website, our host may briefly process request metadata (IP, user-agent) to serve traffic and prevent abuse.

Discord bot

• Slash commands. When you run a command, Discord sends us the interaction so we can reply. We process it to respond and do not log or retain the request, and we do not read your messages.
• /track alerts. When you set up a track, we store only what’s needed to deliver alerts to that channel: the Discord channel ID, and your tracking choice (a player name, a server, or a game and mode). We do not store your Discord user ID, your messages, or any profile information.
• Removal. Tracks are deleted when you run /track remove, or automatically if the bot loses access to the channel. Removing the bot from your server stops all processing for it.

Game & player data

Server names, maps, scores, and the in-game player names you see are public information broadcast by the game servers themselves. QuakeHub queries public game master servers and displays this data; it is not personal data we collect about you.

We also keep long-term statistics about servers - hourly and monthly player counts per server, which power the trends charts and the monthly archive. Player names are never stored in any historical record; they exist only in the live snapshot and are gone when the next poll replaces it.

Quake 4 master server

We run a public master server for Quake 4 at master.quakehub.net, so that a game whose official master servers stopped answering can find games again. It is about server operators, not players: if you point a Quake 4 server at it, we record that server’s address and port, and we send it a standard getInfo query to confirm it is really there before listing it for anyone. Nothing about the people playing on it is stored, an address that stops answering is dropped automatically, and the whole thing is open source so you can run your own instead.

Third-party services

To provide certain features, QuakeHub reads public data from a few services: the Steam Web API (Quake Live server lists and Quake Champions concurrent-player counts), the Twitch API (live streams), QLStats (Quake Live skill ratings), and public tournament listings from Toornament, Plus Forward, and Church of Quake. These are requests our server makes; none of them receive anything about you. The site is hosted on Fly.io. These providers have their own privacy policies.

Children

QuakeHub is not directed at children under 13 and does not knowingly collect information from them.

Changes & contact

This policy may be updated from time to time. Questions? Reach the creator via booskibro.com.