PRIVACY POLICY

Device identifier, connection and admin check

On first use, Orbit generates a random UUID and stores it on the device. The same persistent UID is reused unless the app's stored data is cleared. During game initialization, Orbit automatically sends the UID to its backend for an admin-status lookup and sends a heartbeat containing the UID, app version and platform. The backend records the connection time. Normal requests also expose network information such as an IP address and user-agent to hosting and network infrastructure. These requests are not controlled by the gameplay-statistics choice.

Optional gameplay statistics

Orbit can send the complete serialized level/code, whether it is an official or user-created level, its level number, and the number of attempts. This helps assess level difficulty and gameplay. The current choice is available only through the first-run opt-out checkbox: continuing without selecting it leaves statistics enabled. There is no normal in-app toggle to change this choice later. Clearing Orbit's app storage resets the preference so you can opt out when prompted again, but it also clears local progress and preferences and may generate a new UID.

Level sharing and feedback

Sharing a user-created level is an explicit action. Orbit sends the full custom level and solution data to its backend. You may add a creator name; if supplied, Orbit stores that name on the device for reuse and sends it with the shared level. If you explicitly submit feedback, Orbit sends the feedback text, persistent UID, client timestamp and platform to a feedback endpoint.

The Orbit heartbeat connection table keeps the 50 most recent rows and removes older rows as new connections arrive. Source code does not define a fixed retention period for most other first-party data, including gameplay statistics, shared levels and feedback. Vendor, infrastructure-log and backup retention is also not established by the audited source; provider policies and settings may apply.

Your choices and requests

• Statistics: The opt-out checkbox is available only when the first-run statistics prompt appears; there is no normal in-app toggle later. Clearing Orbit's app storage resets the preference so you can opt out when prompted again, but it also clears local progress and preferences and may generate a new UID. Opting out stops future statistics uploads; it does not itself remove records already sent.
• Local data: Your operating system may let you clear Orbit's storage or uninstall the app. This can remove local preferences, including the UID, and a later launch can generate a different UID. Clearing local data does not by itself delete data already sent to Orbit or a provider.
• Correction or deletion: Email [email protected] with the persistent UID and enough details to locate the relevant record. The UID is available to the app but is not currently shown in a normal player-facing account screen, so we may need to help identify it. The backend has an administrative method to delete heartbeat rows by UID, but source code does not establish a general UID-based deletion method for every data type.
• Shared levels: To request correction or removal, provide the share link or QR code, level number/code, creator name if supplied, and the requested change. We will review whether the level can be located and corrected or removed. We cannot promise that deleting a backend copy deletes copies already received by other players, provider records, logs or backups.

Orbit does not ask for an age or birth date and does not currently screen users by age. The data flows described above therefore can also occur when a child uses Orbit, including the persistent UID and automatic backend requests, advertising and attribution SDKs, crash reporting, optional gameplay statistics, and information a child chooses to submit through level sharing or feedback. This section does not claim compliance with a particular children's privacy or platform regime. Parents or guardians can use the choices above and contact us with questions or requests; the applicable requirements and provider settings need qualified jurisdiction and platform review.