Battle For Titan

Privacy Policy

What we collect, why, and how to opt out — stated plainly, no legalese.

What we collect

We run our own, home-built analytics — nothing from Google or any other third party. It answers two questions: where visitors come from, and how the game actually plays.

  • Public pageviews — which pages get visited, and how often.
  • Referrers and campaign tags (UTM), so we know which links actually bring people in.
  • Sessions — a visit's entry page and roughly how long it lasted, so we can tell a bounce from real browsing.
  • The registration funnel — how many visitors reach the register page, sign up, and verify their email.
  • Your country, resolved from a local lookup file — never sent anywhere, never joined to your name.
  • For signed-in Commanders: in-game activity events, tied to your account, so we can tune balance, timings and pacing.

What we don't do

  • No cookies are set for analytics — nothing is written to or read from your device for this.
  • No raw IP address is ever stored. When you register or sign in we keep only a scrambled fingerprint of your address for 90 days, so admins can spot duplicate accounts; the address itself is never written down.
  • No third-party analytics service sees your visit — the data lives only in our own database.
  • We never sell or share this data with anyone.

The Command Desk help chat

When you use the "?" help chat inside the game, what you write is sent to an AI helper so it can answer you. Along with your message it receives the page you raised it on (the screen name, your browser size, and the element you marked if you marked one) and the earlier messages in that same conversation.

It also receives a short summary of your own game state so its answer fits your situation: your House and rank, your bases with their coordinates and rounded resource totals, what each base is currently building or producing, and your last ten events.

It never receives another Commander's data — not their bases, position, mail or statistics. It has no access to the database and cannot change anything; it reads the Field Manual and answers.

Your conversation stays in your own mailbox and you can read it there any time. Admins can read it too — that is how a person takes over when the desk cannot help. If your message leads to a bug report, the report carries your words and the page you were on, and admins can see it on our internal board.

How anonymous visits are counted

An anonymous visitor is counted with a scrambled identifier built from your IP address and browser under a secret code that changes every day and is then thrown away — so we can tell "the same visitor came back later today" without ever storing who you are, and yesterday's visits can never be linked to today's.

Legal basis and your right to object

For signed-in Commanders, we rely on legitimate interest (GDPR Art. 6(1)(f)) — running and improving a game you chose to play. You have the right to object at any time (Art. 21).

Objecting is one click: open your account settings' Profile tab and turn on "Exclude my activity from analytics." From that moment your account produces no analytics rows at all — not filtered out later, never recorded in the first place.

How long we keep it

Individual, row-level records are kept for 90 days and then deleted. After that, only anonymous daily totals survive (e.g. "412 visitors on a given day") — never anything that identifies a person or a single visit.

Cookies

This site sets two cookies, and neither of them is for analytics: the session cookie that keeps you signed in, and a token that protects forms against cross-site abuse. Both are strictly necessary for the site to work — which is also why there is no cookie banner: there is nothing here that needs your consent.

Questions

If you have a question about any of this, reach us at admin@battlefortitan.com.