Privacy
What the launcher sends to zerohour.gg and what a player account keeps, written out in full.
01Who keeps this data
zerohour.gg and the Zero Hour Reforged launcher are run by Olcay Seygan, a private individual, as a free fan project of Command & Conquer Generals Zero Hour. There is no company behind it and Electronic Arts has no part in it. He is the data controller for everything on this page under the GDPR and under the KVKK, Turkey's data protection law, and the address for it is info@zerohour.gg.
02Each time you press Play
When the game closes, the launcher sends one record of that session. It holds the time the game started and the time it closed, whether it closed cleanly or on a fault, the launcher's version and the game's, how the game was started (by the launcher or through Steam) and the language of the game text. Your Windows version goes with it.
Two random identifiers tie the records together. One is made when the launcher is installed, the other each time you press Play. Neither is built from your name or your computer, and neither is tied to an account on this site.
03Errors
When the launcher itself fails, while updating or installing for example, it sends the error message and the place in its code where it happened, with the launcher and game versions and your Windows version.
Crash reports are older than this page and work as they did before. When the game crashes or a network match goes out of sync, the launcher sends the game's own crash log, the end of the game log, your graphics card and the renderer in use. Your Windows user name, the computer's name and IP addresses are taken out of the text before it leaves your machine.
04Feedback you send
The launcher's feedback form sends what you write, its kind (bug, balance, idea or other), the launcher and game versions, your Windows version and the launcher's language. A contact name or address goes only if you type one, a screenshot only if you attach one, and the end of the game log only if you tick its box. With "Send play data" on, the install identifier goes with it, so the feedback can be matched to that install's crash reports.
05A player account
An account holds the email address, the nick and the password you chose. The password is stored only as a hash. The email address is never shown to anyone, and it is used only to send the password reset link you ask for, which works for an hour.
The nick is public, and so is what online play adds to it: the rating, the games, wins and losses, and each rated match with the opponent and the result, on the ladder and on the player's page. Online play has not opened yet, so no account has a match.
Creating an account and signing in are limited per address: a counter under your IP address is kept for an hour at most, then expires. While you are signed in, the session cookie below also says which account is yours.
06Switching it off
The launcher's settings have a switch called "Send play data". It is on after an install. Turned off, the launcher sends no sessions and no launcher errors. Crash and mismatch reports do not depend on the switch and are still sent.
07Your IP address
The site reads the address a request came from to limit how many requests one address can make, and does not store it with anything the launcher sends.
The visit counter below does not keep the address either. It mixes it with the browser's name and the date into a code and keeps only the code.
08This website
The site counts its own visits, without a cookie. When a page opens, the site's script reports the page's address, the name of the site you came from and nothing more of it, the page language and whether the screen is a phone's, a tablet's or a computer's. While you read, it adds how long the page was on screen, how far down you scrolled and which links and buttons you pressed. One day's pages are grouped by a code made from your IP address, your browser's name and the date. The code changes every day and the address is not kept. These records are deleted after 90 days.
Google Analytics counts visits as well, but only after you allow it in the cookie banner. A message sent through the contact form keeps the name and email address you typed, so it can be answered.
09Cookies and browser storage
The site sets two cookies of its own, and its pages need both to work. zero-hour-reforged-session holds the language you picked, the token that proves a form was sent from this site and, while you are signed in, your account. XSRF-TOKEN carries the same token for the page's scripts. Both expire two hours after your last request, and neither is used to count visits.
Two answers are kept in your browser's local storage and never sent anywhere: zhr-consent is your choice in the cookie banner, and zhr-lang-hint is written when you close the bar that offers the page in another language.
Google Analytics sets its own cookies, _ga and one whose name starts with _ga_, only after you press "Allow analytics". "Cookie settings" in the footer changes the answer.
10Other services
Google Analytics belongs to Google. Its script loads on every page so that it can wait for your answer. Until you allow it, it sets no cookie and what it sends Google carries no cookie identifier, though your browser still connects to Google to fetch the script. Google may process this data outside Turkey and the EU.
Links to GitHub and Discord, and the donate buttons that go to Buy Me a Coffee and ByNoGame, take you to those sites, and what you do there falls under their rules. A donation is paid on one of those two; ByNoGame takes it through its payment provider, iyzico. This site never sees your card or your name. The fund's total on the download page is the sum of the donations the owner records by hand; a donation in dollars is converted to lira at the Central Bank of Türkiye's rate for the day it was made.
The site, its database and the launcher's update files sit on a rented server, and the company that runs the server has access to it as part of that job.
11Legal basis
The visit counter, the launcher's session records and launcher errors, and crash reports rest on legitimate interest. They are how a one-person project finds out which build crashes and which page nobody reads, and they are built to hold no name, no account and no stored IP address. You can object at any time. In the launcher, the "Send play data" switch does it for sessions and launcher errors.
Google Analytics runs on your consent, given in the cookie banner and taken back under "Cookie settings". The two site cookies are strictly necessary, so they need none. A contact form message, and feedback sent from the launcher, is kept so it can be read and answered, which is what you asked for by sending it. An account is kept because you asked for one, and the account is the service.
12How long it is kept
Page views and their clicks: 90 days. Launcher sessions, launcher errors and crash reports: one year. Contact form messages and launcher feedback, screenshots included: one year. An account and its match history: until you ask for it to be deleted, from the address it was made with.
The next record of the same kind enforces each period: a new one deletes everything past its period, so on a quiet week a record can outlive its period by those days. Mail sent straight to info@zerohour.gg stays in that mailbox until it is deleted, and it will be on request.
13Your rights
You can ask what is held about you, have it corrected or deleted, and object to its use. Write to info@zerohour.gg or use the contact page. Launcher records carry no name, so finding yours needs something that points to them, such as the date and time of a crash.
An answer comes within 30 days. If you think your data is handled wrongly, you can complain to Turkey's Personal Data Protection Authority or, in the EU, to the data protection authority of your country.