Space Explorer RPG Privacy Policy
Effective date: 1 October 2026
Developer: Lukhsa
Privacy contact: lukicnemanja11@gmail.com Public policy address: Space Explorer RPG Privacy Policy
This policy describes the Android game Space Explorer RPG, package com.spacecommute.rpg. It covers the app. For the website’s analytics information, see the separate website privacy notice. The game can be played without registering an account. Its save system is local; it does not provide a developer-operated cloud save or social account service.
Your game and journey information
The app stores the names you give your captain, carrier and other game characters or ships, your settings, progression, discoveries and journey reports in application storage on your device. Journey reports contain information such as distance, travel mode, start/end times, traffic and game rewards. These records support continued play, journey recovery and reports.
For optional ad rewards, the app also saves claim-attempt identifiers, the selected offer and associated local captain or journey identifiers, claim dates and awarded amounts. Journey-bonus attempts include the report reward amounts used to calculate the bonus. These local records prevent duplicate rewards and preserve completed claims after a restart. An unfinished attempt does not prove that an ad reward was earned. The records form part of the game save and its allowed Android backup; the app does not send these claim records to Unity.
When you start a real journey and grant Android location permission, the app uses precise device location through Google Play services to calculate movement and distance and validate travel. Recording can continue with the screen locked or the app in the background using an Android foreground service with a recording notification. Notification visibility depends on your Android settings: on Android 13 and later, if you deny notification permission, the service remains visible in Active apps (Task Manager), but its notification does not appear in the notification drawer. Use End Journey after arriving safely. You can manage Android location permission and turn off the app's Location setting after ending the active journey.
The app keeps the latest accepted coordinate, its time and accuracy, and accumulated movement statistics in private application storage while recording. It does not build a stored list of every GPS point. Finishing recording in this version removes that coordinate anchor; aggregate statistics remain available for report recovery. An unfinished recording, or an anchor left by an earlier internal version, can remain until recording is finished, reset by a new journey or removed by clearing app storage. Recording anchors are excluded from this version's Android backup rules. The game does not send GPS coordinates or routes as Firebase event or crash-report fields.
Optional usage analytics
Usage analytics is off by default. If you enable it, Google Analytics for Firebase processes selected actions such as screen visits, tutorial steps, journey start/completion and certain discoveries or progression actions. The app sends fixed categories such as travel mode or rarity, rather than player-entered names, route coordinates, raw save records or gameplay entity identifiers.
The SDK also processes an app-instance identifier and technical app/device and session information. Network IP information can be used to derive approximate geography such as country, region or city. This approximate geography is separate from the game's precise journey-location processing. The app does not set a user account ID for Analytics. Firebase advertising-ID collection is disabled, and Firebase advertising storage, ad user data and ad personalization consent are denied. Advertising-ID permissions are removed. Firebase diagnostics are not used to personalize Unity ads.
Optional rewarded test ads
Optional rewarded ads through the direct Unity Ads Android SDK are offered in Store Resources and on eligible completed-journey reports. The journey offer adds a one-time 25% bonus to eligible credits and resources; normal journey rewards remain available without an ad. Tap Watch to request, load and show an ad without a separate app consent dialog. The app blocks Watch during an active recorded journey; use it only when safely parked. On a fresh installation, Unity initialization and ad loading do not begin until you request an ad. Watch is not consent to personalized advertising and does not change Analytics or crash-reporting choices. Version 0.4.0 requests test ads in debug and release builds, sends signals declining personalized advertising and opting out of targeted-ad sale/sharing, and requests non-behavioral ads. This version removes the Google advertising-ID permission while targeting Android API 36, so Google Play services returns a zeroed advertising ID. Topics and advertising-attribution permissions are also removed. Other installation or provider identifiers may still be processed as described below.
After your first request, the app remembers that ad loading may run. It can preload on later visits to ad-offer screens and load a replacement after an ad closes, before another ad is displayed. Earlier saved ad-loading choices are preserved on upgrade. Showing another ad still requires Watch. Contextual ads and test mode do not mean no network traffic or data processing.
Unity and its service providers may process device and installation identifiers, technical app/device information, IP addresses and approximate location derived from them, ad views and interactions, and service diagnostics. These support ad delivery, measurement, service operation and fraud prevention. Unity's SDK data disclosure also lists personal identifiers and purchase history; app-usage collection depends on provider features and settings. The app does not provide Unity with player-entered names, precise journey coordinates, routes, save contents or purchase events, and does not assign a player identifier to Unity Ads. That does not disable identifiers or service data processed by the SDK itself. Firebase diagnostics choices do not control Unity's own service diagnostics. Refer to Unity's Game Player and App User Privacy Policy for its recipients, retention and privacy-request options.
You can leave Watch unused and continue playing without the optional Supplies rewards or journey bonus. Profile & Settings → Privacy policy → Pause ad loading stops future app-initiated ad loading; a later Watch request resumes it. Pausing does not unload SDK components already initialized during the session or erase information already processed by Unity. The ad-loading preference and Unity SDK files are excluded from Android backup allowlists; a restored installation waits for a new Watch request before initializing ads. The app does not ask for age or birth date. The saved preference records ad-loading state, not personalization consent. Unity's in-ad privacy controls provide further choices where available.
Optional crash reporting
Crash reporting is also off by default and can be enabled independently. If enabled, Firebase Crashlytics processes technical failure reports, stack traces, app/device information, installation identifiers, crash/session timing and limited game context such as the current screen, journey mode and tutorial stage. If Analytics is also enabled, recent Analytics actions may be attached as crash breadcrumbs.
The app removes messages, causes and suppressed exceptions from its custom Java/Kotlin failure reports to reduce accidental disclosure. SDK-generated diagnostics are separate; diagnostic reports are not described as anonymous. The app does not attach player names, GPS coordinates, routes, emails or database contents as custom crash-report fields. Firebase infrastructure may process technical network information when providing these services.
Your choices
You can accept or decline Analytics and crash reporting separately and change those choices in Profile & Settings → Privacy and diagnostics. Declining diagnostics does not remove game features. Rewarded-ad choices are separate, as described above. A new installation, or a cold start with both diagnostics choices off, does not initialize Firebase. Once initialized during a session, SDK components may remain present and produce technical service traffic even after optional reporting is disabled.
Turning a choice off closes the app's reporting gate and disables the associated optional reporting. It does not retract information already delivered to Google. The app requests deletion of pending local Crashlytics reports when crash reporting is declined; the SDK does not expose confirmation that deletion has completed. Prior non-consenting reports are not intentionally submitted when you later opt in. A consenting crash can be submitted after the next consenting launch.
Platform services, recipients and backup
Google provides Analytics and Crashlytics, including their supporting installation/session services. The developer uses these services to understand usage and diagnose faults. Unity provides the optional rewarded test ads described above. Firebase, Google Analytics and Unity services operate under their respective terms and privacy information linked below. The app has no payment-card collection, Firebase Authentication or developer cloud-save backend in this version. Its in-game store does not charge real money or collect payment details.
Google Play update checks are separate from optional diagnostics. Play processes technical device information, app version and this app's installed modules/asset packs to determine whether an update is available. Android/Google Play services operate under their own settings and terms. Following an external link opens the relevant service in another application, whose policy also applies.
Android application backup is enabled for the game database and selected ordinary game preferences. Depending on your device/account settings, Android may copy those records, including your game names, journey totals and reward-claim records, to your backup account or another device. The app's backup rules exclude precise recording anchors, Firebase and Unity SDK storage, optional telemetry consent and the ad-loading preference. Restoring an app backup does not restore your previous Analytics/crash choices or ad-loading state. The developer does not receive your backup. Android backups may restore the allowlisted game data on reinstallation.
Retention, deletion and security
Local game records and preferences are kept until replaced by gameplay or removed. To remove local application data, use Android Settings → Apps → Space Explorer RPG → Storage → Clear storage; wording varies by device. This permanently removes your local save. Uninstalling also removes local application storage, but backup copies and previously uploaded telemetry are separate. Manage backups in your device/account settings.
Analytics user/event data is retained according to the retention controls configured for the app's Google Analytics property. Aggregated reports can follow a different retention lifecycle. Google states Crashlytics starts removing crash traces and associated identifiers after 90 days; removal from all systems is not necessarily immediate. Other technical platform records follow the provider's retention rules. We do not claim that toggling diagnostics off deletes server records.
For privacy or deletion inquiries, contact Lukhsa at lukicnemanja11@gmail.com with the subject “Privacy request” and describe your request. We use your email address and message to respond, explain available options and take applicable action for records we can identify and control. Your name or email alone may not identify installation-based Analytics, crash or ad records. We may request the minimum additional non-sensitive information needed; do not send passwords, precise routes or your full save file. Records controlled by Google, Unity or your backup provider may need to be managed through that provider's tools. There is no game account to delete in this version.
The app uses Android's private application storage. Firebase/Analytics and Google Play use encrypted network transport for their services; Unity states that data collected by its Ads SDK is encrypted in transit. The local database does not add an app-managed encryption layer. No security measure is an absolute guarantee. Service processing may occur outside your country under the providers' applicable terms and safeguards.
Audience and policy changes
Space Explorer RPG is intended for players aged 13 and older and is not directed to children under 13. Rewarded ads are optional; players who do not request them can continue playing without ad rewards. If you believe a child under 13 has provided personal information through the game, contact us so we can review the situation and take appropriate action for information we can identify and control. We will update this policy when our data practices change and identify the effective date above.