Privacy

Last updated 16 October 2026. Remote assistance described below is planned and is not yet enabled.

What is collected, and why

What	Why	Where
Your Google e-mail address and Google's account identifier for you	To know which game account is yours, and to keep one person to one account	The realm's account database
Your game account name, characters and the things characters do	It is a game; this is the save file	The realm's character database
How many times you have pressed Play, and when you last did	So the operator can see the realm is being used	The realm's account database
Your IP address, with the time, page or file requested, and your browser's user-agent string	Ordinary server logs: working out what broke, and noticing abuse	Web server logs, the realm's login server, and an action ledger
A record of each sign-in, account creation, refusal or throttle, with your e-mail address and IP	So that a refusal is never silent and can be explained	The action ledger on the server

What is deliberately not collected

• Your Google password. Signing in happens on Google's own pages. We receive a signed statement that it was you, and nothing else.
• Anything else from your Google account. We ask for your e-mail address and an identifier. Not your name, photo, contacts, calendar or anything further.
• A game password. Each time you press Play the realm issues a single-use ticket that is replaced with an unusable random value the moment your session ends. Between sessions no working password for your account exists.
• Payment details. Nothing is sold and nothing is asked for.
• Unrelated personal files. Download auditing records server requests, not the contents of your computer. Optional assistance, when available, will be limited to the installation and diagnostic information disclosed before you enable it. Do not include passwords, tokens or unrelated personal files in a support report.

Download audit records

When the launcher requests files, we record the observed client IP address, request time, endpoint and requested file, request identifier, response status, bytes sent and elapsed time. These records help us identify interrupted downloads, refusals, slow transfers and service faults. An IP address identifies a network connection, not necessarily a person. Server-side delivery does not prove that a file passed verification or was installed.

The dedicated portal transfer log rotates at 10 MiB and retains up to five rotated files plus the active file. Gateway access logs rotate separately. Support records are accessible to authorized administrators; they are not published in the public simulator or website.

Optional remote assistance — planned

Remote assistance is not enabled by this policy update. When offered, it will require a separate, explicit launcher consent step identifying the device, session duration, diagnostic scope and any AI provider. Local AI integration settings do not by themselves authorize remote support.

With your consent, support may collect launcher and operating-system versions, game-installation version and verification results, available disk space, download progress and retry information, relevant error codes, selected installation paths, and limited launcher/game logs. Paths and logs can contain personal information; the collection preview will identify the selected data and filter credentials. Administrators and an identified AI provider may use that information to explain problems and propose repairs.

Permission to diagnose will be separate from permission to repair. File changes, retries, configuration resets or process restarts will require the repair permissions shown to you. You will be able to end the session; ending it prevents new commands but does not undo completed changes. A session record will identify consent, commands, results and operator actions. The session notice must specify retention and deletion rules before this feature is enabled. Requests to access or delete support information can be sent to the contact below, subject to applicable retention obligations.

Who else sees it

• Google — because you sign in with them. What they see is governed by their own policy.
• Cloudflare — this website is served through their network, so they see requests to it, including your IP address. The game itself and the client download do not go through them.
• Hetzner — the server is hosted in their data centre.
• Support personnel and AI service providers. Authorized administrators can review operational records to diagnose failures. If you choose AI-assisted support when available, the session notice will identify the AI provider and the diagnostic information to be shared before transmission. Declining optional AI support does not prevent ordinary play. We do not sell diagnostic data or provide it to advertisers.

How long it is kept

• Account and character data — until you ask for it to be deleted.
• Database backups — kept on the server for 14 days, then removed.
• Web and game server logs — rotated as they fill, a few files deep.
• The action ledger — kept, because it is the record of what the operator's tools did.

Cookies

The public site does not use advertising cookies. The simulator runs scripts for combat calculations and character previews and saves scenarios in your browser storage. Submitted scenarios are processed by the simulator service. Infrastructure providers may process request metadata as described above. The launcher keeps a sign-in token on your own computer so that you are not asked to sign in every time; on Windows that token is protected by the operating system and bound to your Windows user.

Having your data deleted

Ask, and your account, characters and the link to your Google identity are removed. The realm is run by one person, so there is no form — write to [email protected] from the address you signed in with and say what you want removed. Backups made before the deletion age out within 14 days.

Children

Signing in requires a Google account, which Google requires a minimum age for. If a child has been given an account by a parent, that parent can have it removed at any time by writing to the address above.

Live file verification diagnostics

From launcher 2.8.19, signed-in file verification and transfer activity sends structured events to the portal while the launcher is active. Events include relative file names, check method and outcome, byte counts, timing and error codes. They are associated with the authenticated account and accessible to authorized administrators. File contents, full local destination paths, free-form logs and credentials are excluded. Local destination paths remain visible only in the launcher UI.

Live logs rotate at 5 MiB with two backups per account; records older than seven days are removed on subsequent uploads. Queues and service storage are bounded, so interruptions or limits can lose live events; local logs and Submit logs remain available. Account profiles separately retain the last attempt and last successful verification for up to 20 installation identifiers per account. These are client-reported diagnostics, not a security attestation. Bypassing repair never records verification success. Contact us below for account-data access or deletion.

Launcher diagnostic reports

Launcher 2.8.18 adds a Submit logs button beside the game-files warning. Clicking it sends up to 150 recent verification and download diagnostic events, with timestamps, operation IDs, file names, progress, error codes and launcher version/platform. Reports are associated with your signed-in account and visible only to authorized administrators. Free-form logs and configuration are excluded; credential-like strings are filtered on the launcher and server. This manual upload does not enable remote control. Launcher 2.8.19 additionally sends the bounded live file-verification diagnostics described below.

Reports are capped at 1,000 stored submissions; reports older than 30 days are removed when the next report is submitted. Local launcher logs rotate at 5 MiB with three older files retained. A report ID appears after successful submission.

Changes

If this changes, the date at the top changes with it.