Privacy Policy

Local gameplay data

Pixel WarZone stores certain data locally on your device so the game can function without making you repeat setup steps every time you open it.

• Your saved board layout and unit positions.
• Board-orientation and head-position data used to restore your setup.
• Onboarding and tutorial flags, such as whether welcome flows were shown.
• Locally recorded online wins and total matches. Win percentage is calculated from those two values rather than stored separately.
• A randomly generated installation identifier stored in the iOS Keychain and used as the online matchmaking client ID.

Game Center authentication and leaderboards

Pixel WarZone uses Apple Game Center to authenticate the local player and submit online-play statistics to leaderboards: wins, total matches, and the win percentage calculated from those two locally stored values. Game Center is not used for online or nearby matchmaking.

• Apple handles the Game Center account and authentication process.
• Leaderboard values are submitted only when Game Center authentication succeeds.
• The app's custom matchmaking server does not receive your Game Center identity.

Cloudflare WebSocket matchmaking and gameplay relay

Online Battle opens an encrypted WebSocket connection to a matchmaking service we operate on Cloudflare Workers and Durable Objects. The connection includes:

• A random installation identifier, sent as the client ID.
• A generated display name in the form Commander XXXX, derived from the last four characters of that identifier.
• The requested game mode and protocol version.

The service first tries to pair you with another player. If another player is not available after about eight seconds, it starts a server-controlled challenger. During a match, it processes or relays gameplay messages such as readiness, target cells, hit or miss results, destroyed units, turn and timeout state, board reveal data, match outcomes, quitting, and disconnection state.

Analytics and advertising

The app uses Firebase Analytics and requests banner ads through Google Mobile Ads. Firebase receives app events for workflows such as board setup, mode selection, matchmaking, and match outcomes. These SDKs may also process:

• App opens, sessions, updates, and other app-usage metrics.
• Device model, operating system, approximate geography, and app-instance identifiers.
• Advertising-related data, ad requests, ad interactions, and performance signals.
• Device identifiers made available by the platform or SDK configuration, subject to availability and your device settings.

The exact data Google processes can vary based on SDK defaults, advertising settings, consent choices, regional requirements, and device settings. Google processes this information under its own terms as a third-party service provider.

Local network and Bluetooth

The app requests local network access for nearby offline matches. This feature is used to discover and connect another player over Bluetooth or local Wi-Fi.

• Nearby mode is used only for local discovery and local match communication.
• The app advertises a local Bonjour service for nearby connection setup.
• The app uses your current device name as its Multipeer Connectivity peer display name. Nearby players can see that name during discovery, and a connected player can see it during the match.
• Nearby match messages are sent directly between the connected devices.
• If you do not want to use nearby offline play, you can decline local network access or stop using that mode.

No in-app account registration

The app does not ask you to create a dedicated Pixel WarZone username, password, email account, or profile hosted by us. The random installation identifier and generated online display name are technical matchmaking identifiers, not an account.

How long information is kept

• Local gameplay data remains on your device until you overwrite it, clear the app, reset the device data, or uninstall the app.
• The Keychain installation identifier remains on the device until its Keychain entry is removed or the device is erased, and it may survive an app reinstall.
• The current online service does not intentionally retain a completed-match history. Active queue and match state is used for the live connection; Cloudflare operational data may follow Cloudflare's policies and our service configuration.
• Apple Game Center data is retained by Apple under Apple's own privacy and retention practices.
• Google Analytics and Google Mobile Ads data is retained by Google according to the account and product policies that apply to those services.

Controls available to you

• Do not sign in to Game Center if you do not want leaderboard submission.
• Do not start Online Battle if you do not want to use the Cloudflare service.
• Decline local network access if you do not want to use Nearby Offline Match.
• Manage advertising and privacy choices through your iPhone privacy settings and any consent or privacy notices provided by Apple or Google where applicable.
• Delete the app to remove ordinary locally stored gameplay data. The Keychain identifier may remain after an app reinstall as explained above.

Children's use

The app does not knowingly ask children to submit personal information directly to us. If a child uses Game Center features, Apple provides parental-control options through Screen Time and Game Center restrictions.

Policy updates

We may update this Privacy Policy when app features, SDKs, or legal requirements change. When that happens, we will update the "Last updated" date on this page.

Questions or requests

If you have questions about this policy or the app's data handling, contact:

Third-party privacy resources

For the third-party services mentioned above, you can review the following official pages: