1. Scope and developer
This Privacy Policy applies to the game Warlords at the Gate: Tower Defense (the "Game") and this official website (the "Website"). It explains what information is processed when you use either service.
BlueOrbit is the developer responsible for the Game information described here. For this processing, we act as the data controller. Contact us at blue0orbit@gmail.com for privacy questions, security reports, or requests about your information.
Which version you use matters. Versions distributed before the optional analytics update do not send GameAnalytics reports. The optional reporting described below applies only to a version that offers the in-game analytics choice and only after you enable it. This notice does not turn on reporting in an existing installation or collect earlier gameplay retroactively.
2. Information we do not collect through analytics
The Game has no developer-operated accounts, advertising, advertising trackers, or personalized advertising. Our analytics does not receive your name, email address, store-account identifier, purchase receipt, payment details, contacts, voice, advertising identifier, device serial number, room imagery, hand-joint data, tracking poses, spatial anchors, or precise room geometry. We do not collect GPS location or match your analytics identity across different stores.
We do not sell your personal information or use it for targeted advertising. We send only defined gameplay and technical fields, rather than arbitrary text, complete save files, or diagnostic logs.
3. Information stored locally by the Game
Campaign progress, medals, settings, preferences, and tabletop placement information are stored locally on your device to operate the Game and restore your chosen setup. Your save files and board-placement coordinates are not uploaded. If you enable analytics, the separate gameplay summaries described in section 6 may be sent.
In a version with analytics, we also store your privacy choice locally, including its date, the notice version, and whether you confirmed eligibility. If you enable sharing, a separate local file contains a random analytics identifier, session count, and a session-status marker. These records are separate from campaign progress.
You can remove local information by using available in-game reset controls or by deleting the Game and its local data through your device. Removing the Game may permanently remove local progress.
4. Mixed-reality and input data
Your headset and platform runtime process tracking, passthrough, controller, and hand-tracking information to provide mixed-reality gameplay. The Game uses the resulting runtime data locally for interaction and board placement. The developer does not receive or remotely store passthrough imagery, room scans, hand joints, or controller transforms.
5. Optional diagnostic logs
Diagnostic logging is disabled by default and may be enabled manually in Options. When enabled, bounded local log files may contain the application version, general platform category, level and wave events, gameplay outcomes, and performance counters.
Diagnostic logs do not include room imagery, room geometry, hand joints, voice, contacts, advertising identifiers, or device serial numbers. The Game does not upload these logs. The developer receives a log only if you deliberately send it when requesting support.
The local diagnostic toggle is separate from online analytics. Enabling local logs does not authorize online sharing, and enabling analytics does not upload those files.
6. Optional gameplay and technical reporting
In an analytics-enabled version, the Game first asks whether you are aged 16 or older and then shows a separate notice describing sharing. Confirming your age group does not enable analytics. Reporting begins only after you explicitly choose to allow it. No exact birth date is collected. We rely on your consent for this optional reporting.
If you allow sharing, the Game sends the following to GameAnalytics to help us understand whether players can get into the game, improve gameplay and balance, and investigate reliability and performance:
- a randomly generated application-installation identifier, session identifiers and counts, event times, app/build version, store and release type;
- a general device category, supported headset model where recognized, operating-system platform and version;
- events such as reaching the menu, starting a game, loading a level, encountering the access screen, or choosing Retry, without store responses, account identifiers or authentication credentials;
- campaign or Skirmish mode, level number, difficulty or role, and whether an attempt was completed, lost or abandoned;
- session and active-playtime summaries, excluding pauses and background or focus loss reported to the Game;
- summaries of game-engine frame times, slow frames and engine memory, plus a limited set of known error categories; and
- supported Android exit/crash information described in section 7.
The random identifier lets the service relate sessions from the same consenting installation. This is pseudonymous information, not anonymous information. GameAnalytics also receives your IP address when the Game connects and may derive an approximate country from it. This is not GPS or precise location tracking.
The Game uses a limited connection to GameAnalytics' collection service. It does not install an advertising or attribution SDK, upload screenshots or recordings, or send free-text error messages and script logs automatically. The measurements are summaries of game-engine behavior, not a recording of your surroundings or a guarantee that every device problem can be diagnosed.
7. Crash and interrupted-session information
On supported Android versions, the Game can read this application's recent operating-system exit records after you have enabled reporting. It may send a limited reason such as a crash, an app-not-responding event, low memory, or another operating-system termination, together with the affected build when available.
For supported native crashes, the report may also contain a small number of filtered technical frames: the library filename, library build identifier, and relative code offset. The Game does not upload the raw crash dump, absolute file paths or memory addresses, raw system logs, script stack traces, room data, or account information.
These reports may be sent the next time you open the Game while sharing is still enabled. Only eligible recent exits from the current consent period are considered; reports from before you gave consent are excluded. Availability depends on the operating system and device. On desktop, reporting is limited to supported game-error categories and session status; an interrupted session alone is not treated as proof of a crash.
8. Your analytics choice and deletion requests
Choosing Keep analytics off leaves the complete Game available. You may review or change your choice through Options → Privacy & Analytics (the label is localized). Choosing Stop sharing stops future analytics requests, cancels pending transmission, clears unsent analytics, and removes the local analytics identifier. The Game retains the minimum local choice record needed to remember that sharing is off. This does not erase your game progress.
Withdrawal cannot recall information already delivered to GameAnalytics and is not a server-side deletion request. Before stopping sharing or removing the Game, keep the privacy reference displayed in the privacy settings if you want us to locate earlier reports. For access or deletion, email blue0orbit@gmail.com with that reference and the store/build if known. The reference identifies analytics records; it is not a password or a store account.
We will use the minimum information needed to verify and handle the request, and ask GameAnalytics to act on records it processes for us where applicable. We will explain the request's status and any lawful limitations. Removing an app, resetting an identifier, or sending a request does not itself prove that provider records have been deleted. If the reference has been lost, contact us; we may be unable to identify your records without it.
If you later enable sharing again, a new random identifier is created. Previous reports are not reattached to it. A material change to the analytics provider, purpose or data collected will require an updated notice and a new choice before the changed reporting begins.
9. GameAnalytics and international processing
GameAnalytics ApS and its affiliates provide the analytics service and process the reports on our behalf under their Data Processing Addendum. Their published processing arrangements identify cloud/database providers including AWS, Google Cloud and Imply. Information may be processed in Europe and the United States, including US cloud infrastructure, with applicable contractual safeguards such as EU Standard Contractual Clauses and the UK transfer addendum.
Under its terms, GameAnalytics may also use aggregated or de-identified information for benchmarks, service improvements and model development. We do not enable advertising integrations, cross-store identity matching, or third-party marketing through this reporting. You can request information about the applicable safeguards through our privacy contact.
10. Store and platform services
PICO, Meta, Steam, or another store provider may process purchase, download, entitlement, account, device, achievement, or payment information under that provider's own privacy policy. The developer does not operate those store systems and does not receive your complete payment details.
If optional platform features are enabled in a future Game update, this Policy will be updated before the developer begins receiving or remotely processing any additional information. Developer-operated cloud saving is not part of the current release.
11. Website hosting
The Website is a static GitHub Pages site. It does not use a contact form, advertising, developer-operated analytics, or non-essential cookies. GitHub states that a visitor's IP address is logged and stored for security purposes when a GitHub Pages site is visited. GitHub processes that information under the GitHub Privacy Statement.
12. Information you choose to provide
If you contact support, the developer may receive the information you choose to include, such as your email address, message, screenshots, an analytics privacy reference, or an attached diagnostic file. It is used to answer the request, investigate the issue, maintain necessary support records, and meet legal obligations. Where applicable, we rely on our legitimate interest in providing support and protecting the service, or on legal obligations, for that processing. Do not include passwords, payment information, room imagery, or other sensitive information in a support request.
13. Younger players
Optional online analytics is available only to players who confirm they are aged 16 or older and then consent. Sharing stays off for younger players or when eligibility is unknown. This is our rule for optional analytics; it is separate from the Game's content rating and each platform's rules about who may use a headset or the Game. We do not ask children to provide a parent's email address to enable analytics.
The Game has no social features, public profiles, user-generated content, or direct messaging. A parent or guardian who believes a child has sent personal information to us may contact blue0orbit@gmail.com to request review or deletion.
14. Retention and security
Local saves remain until reset or deleted through Game/device controls. A local privacy-choice record remains to remember your decision. The analytics identifier and unsent reports are cleared when you stop sharing. Unsent analytics has a bounded in-memory queue; queued events older than one hour are discarded before transmission. The Game does not keep a disk queue of events for later upload.
GameAnalytics' published Data Processing Addendum lists one month for raw and annotated data, one year for player warehouse data, and up to 18 months for player lookups used to calculate retention. Available dashboard detail can diminish sooner. Aggregated or de-identified information that no longer identifies you may remain for the provider's permitted purposes. Applicable legal retention and completed individual deletion requests may affect these periods. The provider's separate children's retention policy is not a promise that all adult analytics is deleted after 12 months.
Voluntary support communications and necessary records of privacy requests are retained only as reasonably necessary to respond, resolve the issue, maintain needed support history, establish or defend legal claims, or comply with law. Operating-system crash records are separately managed by the device platform; turning our analytics off does not delete the operating system's own records.
Analytics is sent over encrypted HTTPS connections. We limit the fields collected and access to the analytics account, and use reasonable safeguards. No storage or transmission method can be guaranteed completely secure.
15. Your rights
Depending on your location and the circumstances, you may have rights to information, access, correction, deletion, restriction, portability, or objection concerning your personal information. You can withdraw analytics consent at any time without affecting the lawfulness of processing before withdrawal. You may also complain to your local data-protection authority.
Use blue0orbit@gmail.com to exercise rights concerning information we process. We will respond within the applicable legal time limits and explain any extension or limitation. Store-account, payment and platform-service requests should be directed to the relevant provider.
16. Other international processing
Support communications, GitHub hosting and platform services may involve processing in countries other than your own under the relevant providers' arrangements. The optional analytics transfers are described in section 9. Local-only saves and room/input information are not transferred to GameAnalytics.
17. Changes to this Policy
This Policy may be updated when the Game, Website, or legal requirements change. The effective date above will be revised, and material changes will be communicated through the Website, storefront, or Game update where appropriate.
18. Contact
For privacy questions, data requests, or security reports concerning the Game, contact BlueOrbit at blue0orbit@gmail.com. Requests concerning a PICO, Meta, Steam, GitHub, or payment account should be sent to that provider.