Data & privacy

RIVALFRONT · ranked real-time strategy in the browser

Who is responsible

Terra-Handelsportal UG (haftungsbeschränkt), Sauerbruchstraße 8, 44801 Bochum, Germany. E-mail: info@zechware.de; telephone: +49 173 9837012.

What the game processes today

• Guest sign-in. On first visit you are signed in anonymously through Firebase Authentication. This creates a random user id (uid) stored in your browser; it carries no name, e-mail or device identifier. Legal basis: performance of the service.
• Display name. If you set a name it is stored under profiles/<uid> in Cloud Firestore together with two timestamps, and it is visible to every other signed-in player — that is what a display name is for. Choose one that does not identify you. Legal basis: performance of the service.
• Linked Google account. Linking a guest to Google keeps the existing player id. Firebase Authentication stores the provider identity and account details needed for sign-in and recovery. Signing into an existing account switches players; guest progress is not automatically merged.
• Purchases. Stripe hosts checkout and handles payment details and billing addresses. The game stores your player id, product, amount, currency, purchase terms version and consent time, order status and provider references in private orders. Stripe receives the player and order references to match a payment to its purchase. We store ownership privately and the equipped supporter decoration in your public profile. Card details are never stored in the game. Contract confirmations and withdrawal acknowledgements are sent to the e-mail address supplied at checkout or in the form. Legal basis: performance of the purchase contract and compliance with legal obligations.
• Anonymous gameplay statistics — only with your consent. If you accept the banner, Google Analytics for Firebase records events such as game_boot and name_set (the length of the name, never the name) with your platform. Collection views and interest in future offers use shop_view and shop_interest, without payment details or player names. No personalized ads, no data sold. Without a decision, or after declining, the analytics module is never loaded and nothing is sent. Withdraw at any time via this link. Legal basis: consent.

Payments and transactional e-mail

Stripe receives billing details and payment information to process a purchase and calculate applicable tax. We receive the order and payment references, amount, status, billing e-mail and invoice link, but no full card number. Withdrawal requests contain the name, contract reference, reply e-mail, declaration and receipt time. For live purchases, we use Resend to send contract and withdrawal confirmations. Resend receives the recipient address and message content for that purpose. This processing is necessary for the purchase and for legal obligations. Stripe privacy information and Resend GDPR information explain those providers' processing.

Playing online

• Matchmaking. Entering a queue stores a ticket under queue/<uid> with your player id, your rating, your display name, the side you chose and the maps you crossed off. Only you can read it; it is deleted when the match ends or the ticket expires. Legal basis: performance of the service.
• Matches and results. A finished match is stored under matches/<matchId> with both player ids, both display names, both ratings, the map, the seed, the outcome and the rating change; each player also gets one line under their own profile. Finished matches are readable by every signed-in player — that is what a ladder is. They are NOT deleted when an account is deleted, because they are also the other player's record. Legal basis: performance of the service.
• The match server. While you play, a server in europe-west3 holds the match in memory and exchanges game state with your browser over a WebSocket. Your IP address is visible to it as it is to any web server, and appears in Google Cloud's request logs, which are kept for 30 days. The server writes one structured summary line per finished match (duration, outcome, map, sides, no free text) to Cloud Logging, also kept for 30 days.
• Match results. Before a finished online match is rated, its result — the two player ids, sides, map, outcome and length — is written to a private store in europe-west3, so that a server restart cannot lose it. The entry is deleted once the result is rated, and at the latest after 30 days. What remains is a receipt that a match was rated, without any player id, deleted after 180 days.
• Replays. The command log of a match — what was ordered and when, never chat and never anything you typed — can be re-simulated into a replay. Replays of your own local and training matches are stored IN YOUR BROWSER and never uploaded. Online match replays are held by the match server only for as long as the match room lives (about half a minute after the end) and are offered to the two participants. Replays are not archived beyond that today.
• Private duels. A duel code stores the host's player id and display name for up to ten minutes, and a seat document per player until the match ends. Duels are not rated and produce no ladder record.
• Closed-alpha access requests. While matches against other players are open to invited accounts only, a player signed in with a verified identity (Google, or a confirmed e-mail address) can press Request access. We then store, under alphaRequests/<uid>, your player id, your display name if you have set one, when you asked, the status of the request (pending, approved or declined) and when it was decided — and nothing else: no e-mail address and no message. To review a request an operator looks up the e-mail address of the verified identity in Firebase Authentication, where it is already stored. Only you can read your request; it is shown to you in the game so you can see the answer. Why: so the team can decide who joins the closed alpha. How long: an open request is kept until it is decided; a decided request is deleted automatically 14 days after the decision, by a job that runs once a day, so at the latest one day after that; once the closed alpha has ended, every remaining request is deleted 14 days after it was made. An approval is recorded as the invitation on the private half of your account, not in the request. Legal basis: performance of the service, at your request.
• Reports. If you report another player from a match, we store who reported whom, in which match, the reason you picked and any note you wrote. Only operators can read reports; the reported player is not told who filed one, and a report causes no automatic consequence. Legal basis: legitimate interest in a usable service. Reports are scheduled for removal 180 days after filing. The current system does not yet erase them automatically; the operator must remove them manually.

Deleting your account

Under Shop & collection → Supporter shop → Account & purchases the game deletes your account on request. Removed: your sign-in, the private half of your account (settings, invitations, entitlements), your closed-alpha access request, your matchmaking ticket, your open duel codes and your own match-history lines. Kept: the finished matches you played, and your profile as an empty Deleted player entry, because the results of the people you played against refer to it. Deletion is immediate and cannot be undone. If you have purchased anything, order and payment records are kept separately for the applicable tax and accounting retention periods.

Where

Firestore and our server functions run on Google Cloud / Firebase in europe-west3 (Frankfurt); web hosting is delivered through a content delivery network. Authentication and analytics may involve processing outside this region. Stripe and Resend also process data in other countries, including the United States. Resend describes Standard Contractual Clauses and the EU–US Data Privacy Framework in its data processing agreement. A data processing agreement with Google applies to our Firebase processing.

What is NOT collected

• No chat, no voice, no free-text messaging between players — the game has none.
• No advertising identifiers; the game runs no ads and sells no data.
• No analytics before an explicit grant, and none at all after you decline.
• No card details: Stripe handles payment data.

Your rights

Access, rectification, erasure, restriction, portability and objection under the GDPR; withdrawal of consent with effect for the future; a complaint to a supervisory authority. Erasure of your account is available in the game itself under Shop & collection → Supporter shop → Account & purchases. For anything else, write to info@zechware.de and include your uid (shown on the start screen).

Changes

Version 0.6 · 2026-09-23 · closed-alpha access requests, online play, result-store and report retention, account deletion and live commerce described.