Rocket Run

This policy explains how Rocket Run, developed by Canis Studio, handles information. The Android package is com.canis_studio.rocket.

1. Information stored on your device

The game stores personal bests, control and haptic preferences, a random installation identifier, account-session information, cached profile and leaderboard information, and pending Arcade run submissions. Pending submissions are associated with the correct player and retried when a connection is available.

For development and troubleshooting, the game keeps up to six recent local run reports. These may contain route seeds, game and engine versions, device model, platform, screen size, control mode, run timing, altitude, fuel, collisions, and sampled rocket movement and input. These detailed reports rotate as new runs are recorded and are not automatically uploaded. The cloud run summaries and Firebase diagnostics described below are separate data.

2. Guest profiles, sign-in, and synchronized progress

Online features use Firebase Authentication and our developer-operated backend on Google Firebase and Google Cloud. A guest identity lets you use online features without choosing an external sign-in provider. We store an authentication identifier, player identifier, account type, sign-in provider information, a generated pilot name, selected built-in avatar, profile timestamps, synchronized Arcade statistics, and your device operating-system type (Android or iOS). Newer builds may also send an optional two-letter country code, taken from your SIM card country, mobile network country, or device region setting (in that order). It does not use GPS, request location permission, or identify a precise location, and it is omitted when your device does not provide one. If a later report has no country, the last known country is kept.

Arcade run summaries include a run and installation identifier, a run counter for that installation, route seed, app and generator versions, rules version, peak altitude, boosts collected, active play time, completion state, and end reason. We use these summaries to validate submissions, calculate best scores and aggregate activity, prevent duplicate records, and restore linked progress. Retention of these summaries is described in section 7.

You can sign in with Google or Apple where supported. Firebase Authentication processes the identity information supplied by that provider, which can include your provider account identifier, email address, display name, and profile photo. Our gameplay backend stores provider identifiers and a verified email address when supplied. The current game uses a generated pilot name and built-in avatar for its public profile rather than publishing your provider name or photo. We do not receive your Google or Apple password or request access to your contacts, email messages, or files.

Linking a guest to a new account preserves its progress. If the sign-in belongs to an existing game account, guest progress is merged into that account, including eligible records and best scores. The source guest is marked as merged and is no longer a separate active player. We retain source-account references to keep the merge consistent and support account deletion.

Signing out does not delete the linked account. The game switches to a fresh guest identity; it does not reactivate a previously merged guest. Signing back in restores the linked account's synchronized records. An unlinked guest may become inaccessible after uninstalling, clearing app storage, or losing its session.

3. Public leaderboard and private administration

Every player with an accepted Arcade score can appear on the public leaderboard. Public fields are the game player identifier, pilot name, built-in avatar, best accepted altitude, country (shown as a flag or two-letter code, only when reported), and provider-type icons indicating guest, Google, or Apple. Your device operating-system type is not public. Your email address and authentication-provider account identifiers are not included in public leaderboard responses.

An access-controlled owner dashboard lets authorized administrators inspect profiles, account/provider status, country (where reported), device operating-system type, synchronized activity, run history, and account email addresses for support and operation of the game. These private administration records are not a public player directory.

4. Analytics, crash reporting, and service security

The game uses Google Firebase Analytics and Firebase Crashlytics to understand gameplay and diagnose crashes and freezes. Analytics includes automatic app events and device/app information, together with run starts and endings, game and control mode, steering sensitivity, altitude, score, boosts, duration, setting changes, and leaderboard use. Crash reports may include stack traces, device and operating-system details, installation identifiers, route seeds, and short gameplay breadcrumbs.

These identifiers are pseudonymous and should not be treated as a guarantee of anonymity. Our custom gameplay analytics events do not intentionally include your email address, provider display name, or password.

Our online services also process authentication and Firebase App Check tokens, request timestamps, technical request information, and operational/error logs to verify legitimate requests, enforce access controls, investigate failures, and prevent abuse. Google infrastructure may process IP addresses and device or app integrity information for these purposes. See Firebase privacy and security information and Google's Privacy Policy.

5. Advertising, permissions, and purchases

The game integrates Google AdMob (Google Mobile Ads) and may show full-screen ads between completed runs. Development builds use test ads. Google and advertising partners may process IP addresses and approximate location, device or advertising identifiers where available, ad views and interactions, and SDK diagnostics to deliver and measure ads and detect fraud. Depending on your region, consent choices, and device settings, ads may be personalized, non-personalized, or limited.

The app uses Google's consent flow where required. When available, open Settings → Ad Privacy Choices to review or change your choices. You can also manage advertising identifiers through your device settings. See How Google uses information for advertising and Google Mobile Ads data disclosures. The current game does not offer in-app purchases.

Touch input and optional motion sensors support steering; haptics use device vibration. Gameplay does not request camera, microphone, contacts, photos, or precise-location access. Network access supports account authentication, progress synchronization, leaderboards, security checks, diagnostics, ads, and opening this policy.

6. How information is used and shared

We use information to operate the game, save and restore progress, link and merge accounts, validate scores, display leaderboards, provide support, diagnose problems, and protect the service. Firebase and Google Cloud process account and gameplay information for these services; Google Analytics, Crashlytics, and AdMob handle their respective analytics, diagnostic, and advertising data. Google or Apple processes sign-in under its own policies. See Apple's Privacy Policy.

We do not sell your account or gameplay records. Advertising-related processing is described in section 5. Service providers may process information outside your country under their applicable safeguards and terms.

If you contact support, we use your email address, message, and attachments to respond and investigate. Please do not send passwords or unnecessary personal information. This policy page is hosted on GitHub Pages, subject to GitHub's Privacy Statement.

7. Retention, deletion, and your choices

Cloud profiles, synchronized statistics, and best scores are retained to provide the service until deletion is requested. Your profile keeps your 20 most recent run summaries, and the latest run counter for each installation, to prevent duplicate submissions and support troubleshooting; these are kept until the account is deleted. Run records sent by older app versions are kept for about 90 days, then deleted automatically. Your best-scoring run summary and any run held for review are kept until the account is deleted, so leaderboard scores can be verified. Signing out, clearing device storage, or uninstalling does not request cloud deletion. Local information can be removed by clearing app storage or uninstalling; operating-system backups may retain or restore local data according to your settings. Settings no longer includes a Reset Progress control.

To request deletion, open Settings → My Profile → Delete Cloud Profile (or open My Profile from the main screen), review the confirmation, and choose Delete Permanently. The request removes the leaderboard entry and starts deletion of the cloud profile, run history, and associated Firebase game-authentication records, including merged source profiles. Processing may continue in the background with retries. This deletes the game's account records; it does not delete your Google or Apple account.

Limited deletion-operation and security records may remain temporarily to prevent old tokens from recreating deleted profiles and to complete cleanup. Our cleanup process retains deletion-token markers for at least 24 hours and schedules completed deletion-operation records for cleanup after 30 days. Provider logs, backups, analytics, and ad records have separate retention schedules; profile deletion does not automatically erase all such data.

You may contact us below to request access, correction, or deletion, or to raise an objection or other privacy-rights request available in your region. If you cannot access the in-game deletion control, email us with enough information to identify the game profile; we may need to verify ownership. Do not send passwords. Support correspondence is retained as needed to address the request.

8. Teenagers and children

Rocket Run is intended for players aged 13 and older and is not directed to children under 13. If you believe a child has provided personal information to us, contact us so we can investigate and address it.

9. Security and policy changes

Online services use encrypted connections, authenticated requests, and access controls. No storage or transmission method is completely secure. We update this policy and its effective date when data practices change, and provide additional notice when appropriate.

10. Contact