Space Conquest

Privacy Policy

This policy describes information processed by the current Space Conquest game code and configuration.

Developer and Data Controller

Space Conquest is developed and published under the Effipersonal brand by the individual rights holder. Effipersonal is a brand, not a separate legal entity.

Information We Process

The game processes settings and game-related information on your device. When online player features are available, it also sends an automatically created anonymous player account, a generated installation identifier, your player name, and player-state requests to the Supabase service used by Effipersonal. Supabase also receives the network connection information needed to handle those requests, such as the connecting IP address.

Nearby multiplayer exchanges lobby information, player names, identifiers, and game-state snapshots directly between participating devices. That peer-to-peer traffic is not gameplay traffic sent to an Effipersonal game server.

Local Game Data

Your device stores language, music and effects volume, and brightness preferences; a player display name and cached player balance; an installation identifier; and the local session material needed for online player features. Mobile builds use native secure-session storage integrations. These values are not all sent to the same place: the installation identifier is used when creating the anonymous online account, and the player name and player-state fields are synchronized with Supabase.

The game also keeps a local AI memory profile. It can contain completed match outcomes, map and duration values, bot difficulty, bounded summaries of bot decisions and observations, and aggregate counts. This memory is stored on the device and is used by the game's adaptive AI. The current code does not upload match history or this personal AI memory to the global knowledge service.

No persistent campaign-save or replay upload was found in the reviewed game code. This does not describe temporary in-memory gameplay state.

Multiplayer and Network Connections

Nearby multiplayer uses local discovery and direct device connections where supported. Discovery can expose a lobby name or identifier, game version, map, available slots, and network endpoint. Joining can exchange player-selected display names, temporary participant identifiers and connection credentials, followed by lobby and game-state messages. Devices on the local network may learn the other participant's local network address as part of connecting.

The game may write limited connection diagnostics to the platform log. The code reviewed does not send those diagnostics to an analytics or crash-reporting service.

Accounts and Cloud Services

When the game can reach its configured backend, it creates an anonymous Supabase Auth account without asking for an email address or password. A randomly generated installation identifier is sent during account creation. The game then synchronizes the player's display name and player-state information, including the bonus balance. Supabase processes these requests as the game's hosted backend provider.

The game contains code for downloading public Global AI Knowledge files from Supabase Storage, but remote knowledge updates are disabled in the current project configuration. The game uses its bundled knowledge data instead.

AI Bots and AI-related Data

Adaptive AI uses the local AI memory described above. The project does not send personal match history to train or update shared AI. Global AI Knowledge is authored game content; its remote update mechanism is currently disabled.

Third-Party Services

Supabase provides the configured authentication and player-state backend. The Android game integrates Google Mobile Ads for rewarded ads. Google handles information through its SDK under its own privacy terms; see Google's privacy information for details.

Device Permissions

Android exports request internet access for online features. On iOS, the included plugins declare local-network access for Bonjour lobby discovery and Bluetooth access for nearby lobby discovery. These nearby permissions are used only for the corresponding discovery features; declining them prevents those discovery methods from working. The game also uses a native screen-brightness interface where supported. No camera, microphone, contacts, or location permission is enabled in the inspected Android export preset or iOS plugin declarations.

Purposes and Legal Bases of Processing

Information is processed to provide the online player profile and bonus features you use, connect nearby multiplayer devices, save your preferences, and run adaptive AI on your device.

Data Storage and Security

Local settings, profile data, session material, and AI memory are stored in the game's app data area, with mobile session storage handled through the platform integrations. Supabase API requests use the configured HTTPS endpoint. Nearby multiplayer uses direct local connections; the reviewed code does not establish that every peer-to-peer transport is encrypted. No method can guarantee absolute security.

Data Retention and Deletion

Local data remains in the app's storage until it is removed through device controls or the app is uninstalled, subject to the operating system's behavior. The game has a Settings action that retires the current online player record, clears its local session and resets some local profile and preference data, then creates a new anonymous player account. The backend operation marks the player record as disabled; it does not delete the Supabase Auth user. The current flow does not clear the separately stored local AI memory. This action is therefore not a complete account and data deletion.

Contact Effipersonal to ask about data associated with an online player account.

International Data Transfers

The game sends online account and player-state requests to Supabase as described above. No separate international transfer is initiated by the game client.

Children's Privacy

The project materials reviewed do not establish an intended age range or an age-verification flow. The game does not ask for a date of birth. A parent or guardian with a privacy concern can contact Effipersonal using the details below.

User Privacy Rights

Depending on where you live, privacy laws may give you rights to access, correct, delete, restrict, or object to certain processing. Contact Effipersonal to make a request. The in-game retirement action described above does not delete all account or device data.

Changes to This Privacy Policy

This policy may be updated when the game's data practices change. The current version will be posted at this address.

Contact

For privacy questions or requests, email [email protected]. This address is currently listed by the Effipersonal website contact form.

effipersonal.com

Space Conquest Privacy Policy | Effipersonal