Privacy Policy

Updated 2026-09-26

Tiny Pixel RTS is a strategy game published by Misaligned Games. This policy covers its Android app, browser version and support. We are responsible for the personal information described here. Contact liam.poli1@gmail.com for privacy enquiries. Misaligned Games is the trading name of Misaligned Games SAS, SIREN 982 145 740, registered at 204 B avenue Pasteur, 93170 Bagnolet, France.

Playing the game

You do not need an account. The game has no purchases, in-game adverts, text chat, login or mailing-list form. Settings, tutorial progress and privacy choices are stored on your device.

If you choose an online match, our server hosted by Fly.io receives connection information, room codes, temporary player/reconnection identifiers and gameplay commands to operate the match, reconnect players and protect the service from abuse. Opponents receive game state and readiness/connection status; they do not receive your analytics identifiers or reconnection token. Server logs contain room lifecycle events and operational metrics.

Optional gameplay analytics

Turning on Gameplay analytics allows PostHog to process sessions, tutorial completion and match outcomes, including game version, platform, game mode, map, player count, result and duration. It also receives technical information such as connection IP address, device/browser details, timestamps and session identifiers. Our project uses PostHog's EU service. IP-based location enrichment, screen recordings, automatic interaction capture, exception capture and performance capture are disabled in the game configuration.

Events use a random identifier stored on your installation. Withdrawing and later granting consent creates a new analytics identity. The game does not use Android's persistent device identifier (ANDROID_ID) for analytics or send the PostHog identifier to AppsFlyer. These identifiers are pseudonymous: they can distinguish installations even though we do not ask for your name.

Optional campaign measurement

Turning on Campaign measurement in the Android app allows AppsFlyer to measure installs and app opens, understand where installs come from and detect attribution fraud. It processes advertising and installation identifiers, IP-derived approximate location, device/app information and SDK diagnostics/performance information. The Android advertising ID is used when available. The game does not request precise GPS location.

Android ID and IMEI collection are disabled. No customer user ID is supplied to AppsFlyer and its attribution data is not copied into PostHog. The app instructs AppsFlyer to block sharing with all advertising partners and disables advertising personalization. There are no active advertising-partner integrations for this app.

Service providers and support

PostHog, AppsFlyer and Fly.io process information to provide the services above. If you choose to email support, Google Gmail processes your email address, message and any information you attach. Please do not send passwords, room reconnection tokens or unrelated sensitive information. The game itself does not read your email, contacts, photos or messages.

We do not sell your personal information. We may disclose information where required by law or necessary to protect users, our rights or the service. If our providers process information outside your country, applicable safeguards for international transfers apply. More information is available from PostHog, AppsFlyer, Fly.io and Google.

Security and retention

The production app uses encrypted HTTPS and secure WebSocket connections. Local settings and saved privacy references remain until you clear app storage or uninstall; browser storage can also be cleared in your browser.

Match state is held in server memory, without a player-account database. Disconnected seats have a one-minute reconnection reservation; waiting rooms expire after ten minutes and ended rooms after one minute. Server restarts also clear rooms. These timers do not delete operational logs. Fly.io's application log search retains logs for seven days; this is separate from any records retained to investigate an incident or meet a legal obligation.

Analytics and attribution records may remain after you stop tracking. We do not currently run an automatic per-player analytics deletion schedule. PostHog's plan-based reporting window is not a deletion guarantee. AppsFlyer's user-level retention depends on the data and applicable service requirements; access to a report is not the same as storage retention. Its published policy provides for aggregate reporting for up to 25 months. You can request deletion of identifiable records as described below.

We keep support correspondence while handling your request and afterwards only where necessary for follow-up, resolving disputes or meeting legal obligations. When considering retention, we take account of the purpose, sensitivity of the information, unresolved requests and applicable legal requirements. We do not promise that turning tracking off immediately removes historical records or provider backups.

Your choices and deletion requests

You can play without optional tracking. Gameplay analytics and Campaign measurement are independent and initially off. Open Settings → Privacy & tracking to change either choice. Closing that screen does not give consent. Turning an option off stops future collection through that option; it does not erase previously sent data. Android also provides advertising-ID reset/deletion controls.

To request access, correction or deletion for Tiny Pixel RTS:

Open Settings → Privacy & tracking → Privacy request references. Save the references for any relevant providers before clearing storage or uninstalling. You do not need to enable tracking to request deletion.
Email liam.poli1@gmail.com with the subject “Tiny Pixel RTS privacy request”, the action you want, your platform, approximate play dates and any saved references. If none are available, contact us anyway and explain this.
We will use the information to locate and verify the relevant records and respond to your request. We may ask for proportionate information to verify it. We will explain if we cannot identify a record or must retain particular information.

A deletion request can cover the matched PostHog person and associated events, AppsFlyer user-level records, and support correspondence. There is no game account to delete. The separate provider references cannot be substituted for one another. Records from an older installation may require a reference you previously saved. Clearing local storage does not delete provider records.

Provider processing and backup cycles mean deletion is not necessarily immediate. We may retain limited information where required for legal compliance, security or resolving a dispute, and explain the applicable reason and retention to you. Reports that no longer identify you may remain. Request handling follows applicable law; we do not impose an additional routine holding period on an approved deletion request.

Legal bases, audience and rights

Where applicable data-protection law requires a legal basis, optional analytics and campaign measurement rely on your consent. Online-match processing is necessary to provide the service you request. Service security and handling support enquiries rely on our legitimate interests, and we may process information to meet legal obligations. Withdrawing consent does not change the lawfulness of earlier processing.

The game is intended for players aged 13 and over and is not directed at children under 13. If you are below the age at which you can give valid consent where you live, leave optional tracking off unless a parent or guardian has provided the consent required by local law. A parent or guardian can contact us about a child's information.

Depending on your location, you may have rights to access, correct, erase, restrict or object to processing, obtain a portable copy, withdraw consent and complain to your data-protection authority. Contact us using the address above to exercise your rights.

Policy updates

We will update this page when our practices change and obtain any new consent required before enabling new optional uses. The date above identifies the current revision.