1. DATA WE PROCESS
Depending on how you use the alpha, the service can process an account identifier and display name, guest alias and session identifier, profile preferences, game results, progression, visited or selected locations, current flight model, position, altitude, orientation and movement needed for nearby multiplayer, plus security and technical logs.
2. WHY
Data is used to provide the requested flight session, maintain identity and preferences, show nearby players, validate and rank game results, prevent abuse, diagnose failures and improve stability. Optional analytics or advertising are not currently active.
3. LEGAL BASIS
Processing necessary to deliver a requested session is based on providing the service. Security and reliability processing relies on legitimate interests. Optional processing will require consent where applicable and can be refused without blocking essential storage.
4. LIVE LOCATION AND MULTIPLAYER
While connected to the shared world, nearby players may receive a reduced network state containing your display name, flight model and approximate in-world pose. Exact position is not published as a permanent public profile by default. Leaving the session stops live presence; temporary network state should expire through disconnect and cleanup controls.
5. PROVIDERS AND TRANSFERS
Running the world can involve hosting, authentication, Cesium and Google photorealistic tiles, OpenStreetMap mapping, and public weather or live-Earth providers. Requests can disclose technical data such as IP address and the geographic area required for the feature. Each provider remains responsible for its own service and privacy terms.
6. RETENTION AND RIGHTS
Guest sessions currently expire after seven days. Preferences remain on the device until removed. Scores, profiles and security records are retained only for the period required by the alpha, legal duties and abuse prevention. Applicable rights can include access, correction, deletion, restriction, portability, objection and withdrawal of consent, as well as a complaint to the competent data-protection authority.
7. CONTROLLER CONTACT
The definitive controller identity and a monitored privacy contact must be inserted before commercial launch. Until that information is formally supplied, this alpha page records the actual processing design without inventing a legal entity or contact address.