Privacy policy

Vox Tank · effective 24 October 2026 · Русский · Čeština · Deutsch

This is a translation of the Russian original. If the two differ, the Russian version prevails.

Who is responsible for the data

Anton Tkachenko, Czech Republic — the developer of Vox Tank and operator of the voxtank.com site and the game server. Contact: antoniostkach@gmail.com.

What we store

• Account. The login you chose and the date you signed up. The e-mail address you gave when signing up or linked later in your account on the site: we send the confirmation code there, and only one account can be made per address. If you change the address, the old one receives a letter about it. We send nothing else there and show it to nobody; only the game's team can see it. Accounts made before 21 October 2026 have no e-mail until one is linked. We do not store your password — only its hash (salted PBKDF2-SHA256), from which the password cannot be recovered. To sign you in without a password, the game and the site receive a token; on the server it, too, is kept only as a hash, and it stops working after 90 days without use.
• Progress. XP and level, rating, voxes and rubies, the hulls, turrets, upgrades and paints you have bought, the battle pass, battle statistics.
• Friends and messages. Your list of friends and friend requests. Private messages between friends are stored on the server — the last 50 of each conversation — so they reach a friend who is offline at the moment. Battle chat is not written to disk: it is seen by the players in the battle (and by a moderator if one is watching that battle — such watching is recorded in the moderation log), and the server remembers each player's last 20 lines in memory only, until it restarts, so they can be attached to a complaint.
• Blocks and complaints. The list of players you have blocked (a player you block is not told). If you report a player, the server keeps the complaint: who, about whom, the reason and your comment, together with that player's last 20 battle-chat lines and the last 20 messages of your conversation with them. Complaints are read only by the game's team, to deal with the violation; the reported player is not shown who filed it.
• Bug reports. If you report a bug from the game (Settings → Report a bug), the server keeps your text, your login, the time, the game's version and the name and version of the system it runs on. Only the game's team reads them, to find and fix the bug; the latest 2000 reports are kept.
• Battle records. Every battle has a number. When a battle ends, the server records the map, mode, time, who played (the login at that moment), on which tank, with what score, kills, deaths and assists, and who left early. The records are kept for 30 days and deleted automatically. The game's team uses them to look into complaints: a complaint remembers which battle it came from.
• Punishments and the moderation log. If the game's team has barred you from chat or banned your account, the server stores for how long, why, by whom and when. Every action of the team — a punishment and lifting it, a decision on a complaint, a name reset, a kick from a battle, an announcement, assigning a role, a balance change — is written to a log: who, to whom, when and for what reason. Only the game's team sees the log; it exists so that punishments can be checked and appealed.
• Notifications. Messages from the game to you personally — such as the outcome of your complaint or a name reset — are kept on the account, the last 20, and shown in the garage and in your account on the site.
• Former logins. If a moderator reset your name and you chose a new one, the old one is kept on the account and stays taken for good: nobody else can take it, and the game's team can see that it is the same player. The server also remembers when you last came into the game.
• Ruby purchases. The Stripe payment number, the amount, how many rubies were credited, and whether there was a refund or a dispute. You enter your card details and the e-mail for the receipt on Stripe's page — we do not receive or store them.
• Technical data. The IP address of your connection to the game server and failed sign-in attempts are written to the server log. It is needed to protect accounts from password guessing and to investigate failures, and it is cleared automatically. In addition, the server briefly holds IP addresses in memory to limit the number of sign-in and sign-up attempts.
• Device and sign-in addresses. On first launch the game creates a random device identifier — just a set of random characters, with no serial numbers or computer name — and sends it to the server when you sign in. The server keeps the last 5 device identifiers and the last 5 IP addresses you signed in from, in the game or on the site, on the account. This is to fight cheaters and ban evasion: the game's team can see which accounts came in from the same device or address and can bar sign-in from a violator's device or address. If you delete the game together with its files, the identifier is gone.

What other players see

Your login, level, rating, statistics and your tank's looks — in battle, in player search and on your profile page. Only the two of you can see your conversation with a friend.

What is stored on your device

The game's settings, the selected tank and the sign-in token — in the game's data folder on your computer or phone. After you sign in on the site, a single cookie, vt_session, is set with the sign-in token: it is only there to keep you signed in to your account and is not used for tracking. The site also remembers the language you chose in your browser's local storage; this never leaves your browser.

Why, and on what legal basis

• To make the game work: the account, progress, battles, friends, messages and crediting rubies — performance of a contract with you (Art. 6(1)(b) GDPR).
• To protect accounts and the server from hacking and abuse: logs and limits on attempts — our legitimate interest (Art. 6(1)(f) GDPR). The same applies to fixing bugs from bug reports, handling complaints about players and the lines and messages attached to them, battle records, punishments and the moderation log, device identifiers and sign-in addresses.
• We keep payment records for as long as tax and accounting law requires (Art. 6(1)(c) GDPR).

Who the data is shared with

• Hosting. The game and site server is in a data centre in Prague (Czech Republic); the provider stores the data on our behalf and does not use it itself.
• Mail hosting. Letters with codes go out through our hosting's mail server (HOSTiQ, Ukraine): it receives the address and the text of the letter only to deliver it.
• Stripe takes payments for rubies and processes payment data under its own privacy policy. We pass to Stripe only the login of the account to credit the rubies to, and the amount.
• The Microsoft Store and other app stores, if you downloaded the game from one, process download data under their own rules; we receive none of your personal data from them.

Nobody else, except where the law requires it.

How long we keep it

The account, progress, friends and messages, notifications, former logins, punishments and the moderation log — for as long as the account exists. Battle records — 30 days. E-mail us with your login and we will delete the account with all its data within 30 days. Payment records remain after deletion, de-personalised, for as long as the law requires.

Your rights

You can find out what data about you is stored, get a copy of it, correct it, delete it, restrict its processing or object to it. Write to antoniostkach@gmail.com — we will answer within 30 days. If you believe we are violating your rights, you can complain to a supervisory authority — in the Czech Republic that is the Úřad pro ochranu osobních údajů — or to the authority of your own country.

Children

The game is not meant for children under 13, and we do not knowingly collect their data. If you are a parent and your child has made an account, write to us and we will delete it.

Changes

If we start storing anything new, this page is updated before the change takes effect, and the date at the top changes.