Public visitors
You do not need an account to use Tierhall, and we do not use Battle.net login. We do not collect character profiles, gameplay histories or advertising identifiers. Our hosting providers may process standard request information, such as IP address, browser user agent, requested URL and timestamp, to deliver the site, keep it secure and keep short-lived operational logs.
Cookies and local storage
The public site does not set tracking or advertising cookies. The talent calculator saves the builds you name, and the Legacy page remembers the challenges you tick, in your own browser (local storage) so they are there when you come back. They stay on your device, are never sent to us, and you can delete them from the calculator, by unticking, or by clearing the site data in your browser. Payload CMS authentication cookies are strictly necessary for authorised editors and are only created when an editor uses the private admin area.
Visit statistics
We count visits with Cloudflare Web Analytics. It does not use cookies or local storage, does not fingerprint browsers and does not track visitors across sites or build individual profiles. We only see aggregate figures such as page views, countries, browsers and referring sites, plus page-speed measurements.
The “Online now” counter
The number in the top bar counts the tabs of this site that are open and in view. While a tab is in view it sends a random number, made when the tab was opened and kept in that tab’s session storage (not a cookie), to a small counter that runs on Cloudflare Workers every two minutes. The counter keeps only those random numbers, and only for about five minutes, so it can count them. It does not store your IP address, does not set a cookie and cannot tell who you are, and the number is gone when you close the tab.
Processors
Vercel hosts the web application, and Cloudflare provides the visit statistics and runs the counter behind “Online now”. Turso stores CMS content and short-lived normalized API cache records, and Cloudflare R2 stores original editorial media and encrypted backups, where production credentials are enabled. Blizzard processes the server-to-server API requests made by Tierhall; Blizzard credentials and access tokens are never sent to the browser.
Retention and contact
Blizzard-derived cache entries expire no later than 30 days. Operational logs follow the hosting providers’ configured retention. For a correction or a privacy request, follow the process on the Corrections page. We have not published a dedicated support address yet; until we do, requests are handled as that page describes.