Legal

Privacy policy

Last updated 2026-09-20

Before launch: replace this box with the operator's name and postal address. Contact: margrave.bot@outlook.com.

The short version

Your Tribal Wars password never leaves your computer. The account service receives your e-mail address, an optional account name, an installation ID, operational data and the Tribal Wars player identity described below. The public information pages send a limited first-party page-view count without cookies or browser storage; the account dashboard uses cookies to keep you signed in and protect account actions.

What stays on your PC

• Your Tribal Wars password. It is stored in a configuration file on your own machine and is used only to log in to the game from your own browser. It is not transmitted to our servers.
• Bot settings and local state — module switches, per-village rules, the helper's log. All local files; the uninstaller removes them.

What our servers receive

• An anonymous installation ID (a random UUID created on first run). It is not derived from your hardware or your identity.
• Your Tribal Wars Bot account details: the e-mail address and optional name entered when you create an account.
• Your reported Tribal Wars identity: the current world, numeric player ID and player name reported by the installed bot. The service checks the ID and name against that world's public player registry and records the result and time. A report waiting for that check may also be stored.
• Trial-eligibility markers: keyed, one-way HMAC values derived from the validated world/player ID and regional normalized player name. They are used to prevent the same game identity from starting repeated free trials. These markers do not contain the plain player name or ID and remain after account deletion, with their account link removed.
• Operational data: the installed version, module activity and error logs, and game-state snapshots the bot works from (village coordinates, troop counts, timings). This is what lets us answer "why did it stop" and ship fixes.
• Update checks: standard web-server request data (IP address, time), used to deliver the download and updates, kept in ordinary short-lived server logs.
• Public-site page views: the allowlisted page path and a random event ID created for that page load. The server derives a daily HMAC and a second HMAC that remains stable while records are kept, using the request IP address and a coarse browser category. This estimates daily visitors and counts a returning browser/network combination once over a selected period of up to 90 days. Changing networks or browsers can count one person twice; sharing a network and browser category can combine people. Raw IP addresses and user-agent strings are not stored in the analytics table. Records older than 90 days are removed when the next eligible visit is recorded.
• Getting-started diagnostics: download clicks and fixed progress steps such as account creation, email verification, opening setup, connecting a world and starting a trial. Setup uses a random attempt ID so we can see which step an installation reached, plus a fixed error category if a step fails. These records contain no email address, passwords, licence keys, game names, full URLs or error-message text. They expire after 90 days. Website counts use the daily visitor estimate described above and respect Do Not Track and Global Privacy Control. Setup diagnostics do not connect an anonymous website visit to your game account.

This data is stored on a server operated by Hetzner Online GmbH in Germany (EU). It is not sold or used for advertising. Service providers receive only the data needed for the hosting, payment and password-reset delivery described on this page.

Payments

Paid access is bought 30 days at a time in Bitcoin, on-chain or over Lightning, through a BTCPay checkout. There is no card, no bank detail and no payment-provider account: what we hold is the invoice — its status, its reference, the amount and when it settled — linked to the e-mail address you signed up with. The payment itself happens on the Bitcoin network, which is public by design and is not ours to keep private.

If you ask for a refund you give us a receiving address (see the refund policy); we keep it with the record of that refund, and for nothing else.

This website

The public information pages use the limited first-party page-view count described above. It sends no query string or referrer, uses no analytics cookie or browser storage, and does not run when Global Privacy Control, Do Not Track, or browser automation is reported. These pages use no ad pixels, external fonts or CDNs. The account dashboard at /app/ sets a session cookie and a CSRF cookie after signup or login. A payment checkout opens only when you choose a displayed payment option. When Tribal Wars Bot sends an account-verification or requested password-reset message, your account e-mail address and a time-limited link are sent through Resend solely to deliver that message. Passwords and usable verification or reset tokens are not stored in ordinary application logs.

Retention and your rights

Operational data is kept while your installation is active and for a limited period afterwards. Account-linked identity records are removed when the account is deleted. The pseudonymous trial-eligibility markers described above are retained without the account link so deleting and recreating an account cannot reset trial eligibility. You can delete your account in Account settings at the bottom of the signed-in account page. Deleting an account also ends its access, revokes its licence keys and signs it out. Account deletion does not automatically refund a payment; use the separate refund process linked below if one applies. You can ask for a copy or correction of data linked to your account or installation using the contact address above and the installation ID shown in your dashboard. Support and privacy requests can be sent to margrave.bot@outlook.com.