Privacy

At a glance

• No account needed
• No ads, analytics or trackers
• Your progress stays in your browser
• Votes use a pseudonymous ID, never your IP

When you vote on the tier list or on a build, publish a build, report one or create a short link, your browser receives a device cookie: a random ID that only these community requests read, never the pages. We store the vote or the build with a keyed hash (HMAC-SHA-256) of that ID, and we count actions per network with a keyed hash of the first part of your IP address (the /24 block, or /48 for IPv6). We never store or log the IP address itself. With our secret key the hashes can be computed again from a known cookie or network, so they are pseudonymous personal data, not anonymous data. We use them only to count one vote per device and to stop vote floods.

Some features remember things in your browser's local storage: favourites and recently viewed pages, recent searches, checklist and tracker progress, saved builds, timer alerts, your server region and display choices. This data stays on your device: clearing the site's data in your browser removes it, and every page works without it.

The site sets no tracking cookies. The community device cookie (__Secure-vt: a random ID, kept 400 days, not readable by scripts) is set only when you vote, publish, report or create a link. Only while the site is closed for a private test does a strictly necessary cookie remember that you entered the test password.

Pages are served by Vercel; pictures, 3D models and data files by UploadThing; votes are kept in a Neon database; the 3D viewers may load a texture decoder from jsDelivr, a public code CDN. These providers handle the technical data every website needs to answer a request, such as your IP address in their server logs, under their own privacy terms. Fonts are served by us, and we embed no videos or social widgets. We don't sell or share data. Links to NCSOFT, Steam, Twitch, Discord or YouTube open those sites, with their own rules.

We process the hashed device and network IDs for our legitimate interest in fair community votes without vote floods (Art. 6(1)(f) GDPR). Votes and published builds are kept as long as the community boards they count for are online; you can change your vote at any time. The rate-limit records (hashed IDs, kind and time of each action) are deleted after about 2 days. What the site keeps in your browser stays there until you clear it.

Under the GDPR you can ask for a copy of the data about you, have it corrected or erased, restrict or object to its processing, and complain to a data protection supervisory authority, for example the one where you live. A vote can only be matched to you through the device cookie of the browser you voted with, so a request must come from that browser.

Questions or requests about this page: contact us on Discord.

Last updated October 4, 2026