Local play has a specific meaning
The game’s movement, scoring and discovery progress are computed on the device. After offline preparation, the browser can provide the game files from its cache. ORBIT does not need to contact a player-account service to approve each run or retrieve a cloud save.
This explains why a disconnected session can still earn local progress. It also explains the limitation: if that browser’s saved data is erased, the publisher does not have a remote player record from which to restore the missing discoveries.
Keep the timeline clear
Preparing the game first involves an online visit and downloading files. Public pages also include the analytics integration described in the privacy policy. Going offline afterward should not be treated as a claim that the earlier visit made no network requests.
Returning online allows normal loading and update behavior again. ORBIT does not provide a special privacy mode promising that the browser or other installed software has no network activity. Its narrower promise is about how this game stores progress and can use already prepared files.
Separate sharing and support from gameplay
A score image and message can be generated locally, but choosing another app to send them introduces that app and its destination. Being offline when a result was earned does not make a later public post private. Review the score, best and trail details before sending.
Likewise, contacting support voluntarily sends the email content and attachments you choose. Include only information useful to the issue. For a local-data question, identify the game address and browser without assuming support can inspect your saved scores. Use the privacy policy for current processing details rather than treating offline availability as a complete privacy statement.