Privacy policy.

Who this policy covers

This policy covers Rocket Roadster for iOS and the website at rocketroadster.com.pl. The developer and person responsible for personal information handled through these services is Bartłomiej Bocian. For privacy questions, email support@rocketroadster.com.pl.

Playing on iOS

You can play without signing in or providing personal details. The game does not send gameplay, scores, or saved settings to the developer or a game server. It includes no advertising, analytics, or tracking SDKs and does not access your location, contacts, camera, or microphone.

Your personal best and sound preference are saved locally on your device. The iOS app has no Rocket Roadster account, online leaderboard, or developer-operated cloud save.

Local storage and deletion

Saved scores and settings remain until the app or browser data is removed. On iOS, deleting the app removes its local game data; offloading the app preserves its data. Device backups may retain copies according to your Apple settings. On the web, clear this website’s site data in your browser to remove the saved personal best. Web and iOS scores are stored separately.

The browser game uses local storage for its personal best in each mode and a plain remembered nickname. The personal best belongs to that browser and is independent of the nickname. Leaving the nickname blank skips online submission; the browser personal best still saves normally. Clearing site data removes the remembered nickname and local scores, but does not delete entries already shared with a leaderboard. The developer cannot retrieve or erase scores stored only on your device. There are no advertising or analytics cookies. Web leaderboard request security uses the essential session cookie explained below.

Optional web leaderboards

The web leaderboard works like an arcade score table. Anyone can enter an optional nickname, including existing and early supporters. A nickname is a label for an entry, not an account or proof of identity. Duplicate names, capitalization variants and identical scores from different games are allowed. No name is reserved, and no email address, password, recovery code or ownership key is needed. Use a nickname rather than personal information you do not want others to see.

Nickname entry appears on the results screen after a ride. A completed game is submitted only when you enter a nickname and choose Save score. The browser may prefill the last nickname, but this does not submit a score automatically. An empty or whitespace-only nickname creates no online score entry. Historical browser personal bests and abandoned games are not uploaded. Each mode retains its best 100 entries; separate completed games can occupy separate places with the same nickname. Your nickname, result, rank and acceptance order can appear on the board. Displaced entries are removed from the active score table. Both Run and Train leaderboards are public.

The active score store contains no player profile registry, ownership credential or private per-person best. The obsolete RRPLAYER ownership cookie is expired when the leaderboard endpoint is used. Existing public results from the earlier profile-based release are converted into ordinary nickname entries. Before conversion, a private backup retains the old data for rollback; this backup can contain earlier profile names, credential hashes and submitted bests until it is deliberately removed. These backups remain outside the public document root.

Run and Train use point scores for personal bests and public rankings, with higher scores first. Train uses the same distance, height and remaining-air total shown after a successful escape. Older Train millisecond entries remain separately in private storage; they are not converted, published as points, or deleted by the leaderboard clear command. Old browser time records also remain locally until site data is cleared.

Leaderboard requests use the essential RRACCESS session for CSRF protection. A separate random RRCONTRIBUTOR cookie lasts 365 days and is HttpOnly. The server derives an anonymous contributor ID from that cookie and a private application key. The public leaderboard API includes this pseudonymous ID with new entries; legacy entries have no contributor ID. The ID is publicly retrievable through the API. Clearing site data can reset the contributor identity, which may evade a contributor block.

Each new completed result uses a UUID receipt stored with the accepted entry under a private file lock. A matching retry for up to one hour returns the existing result instead of adding another entry; changing its score, mode, nickname or outcome returns a conflict. Receipts contain a fingerprint and acceptance reference, not the raw nickname or score. The keyed IP identifier limits score submissions to 600 per hour. Reports are deduplicated, limited to 20 per IP per hour and kept in live storage for 30 days. Playing and publishing scores do not require supporter verification or an email.

Leaderboard rules are available at rocketroadster.com.pl/leaderboard-rules/. Before the first submission for a rules version, the web game asks you to accept that version and stores the accepted version in local browser storage. Use Report beside an entry to flag a nickname for moderation. The site owner may remove entries or block a contributor.

For Web score verification, each ride requests a random seed and a signed, one-hour challenge from the server. The browser records controls at fixed simulation steps in memory and sends the compressed recording with the score only when you choose Save score. The server replays the ride to check its result. It does not persist the control recording or challenge: the private receipt holds a fingerprint, and a verified entry retains a verification version. Recordings are discarded when you leave the result or start another ride. A ride without a valid recording can still save a local personal best but cannot publish a Web score. Older native clients use the unverified API during migration.

Rankings are requested when the main menu or board opens, when refreshed, or when a result is submitted. During play, the HUD shows the current nickname, browser personal best and latest loaded top-three snapshot. There is no background leaderboard polling during play and no third-party leaderboard or analytics service. A nickname can be changed or cleared without affecting already published entries.

Published entries are retained while they remain in the top 100 and the leaderboard operates, unless removed separately. When the site owner resets rankings, a private backup can retain the previous leaderboard state, including entries and keyed rate-limit records, until that backup is deliberately removed. Clearing browser data does not delete published entries or private backups. For questions or requests about server-held information, contact support@rocketroadster.com.pl and identify the entry concerned. Nicknames alone cannot establish who submitted an entry. These web features do not change offline iOS gameplay or its local scores.

Contributions and legacy supporter records

Run and Train are public. The game no longer asks for a Buy Me a Coffee checkout email or verification code, and contributions do not control access to gameplay or leaderboards. Existing supporter records are not deleted by this change.

The optional Buy Me a Coffee integration still receives signed contribution notifications or private historical imports. Its private store keeps a keyed hash of the normalized email, payment identifier, payment status, relevant payment or subscription times and event time. It does not retain plaintext supporter emails or payment-card details.

Eligible supporters may receive one thank-you email with the public Train link. A private contact export may supply delivery addresses for an existing-supporter announcement. A keyed email identifier and queue-acceptance time prevent duplicate messages. The message includes inline artwork and has no tracking pixel or remote-image request. Hosting and email providers process delivery addresses.

Older versions offered email-code verification. Its legacy endpoints and private records remain for compatibility; codes expire after 10 minutes, permit five guesses and use keyed request limits. The essential RRACCESS session cookie also secures leaderboard requests, can last up to 30 days and is removed by clearing site data or server cleanup. Supporter status, refunds and subscription expiry no longer block either game mode. Contact support about removal of server-held supporter records; separate payment records remain subject to the payment service and applicable requirements.

When you contact support

If you email support, the developer receives your email address, message, and anything you choose to attach, such as a screenshot or device details. These details are used to answer your request and investigate the issue. The app does not automatically attach diagnostics or device information.

Email services process the correspondence to deliver and store it. Support messages are kept only as long as needed to resolve the request, handle relevant follow-up, and meet any applicable legal obligations. You can request deletion by emailing the same address. Please do not send passwords or payment-card details.

Website hosting

Opening the website or these help pages sends a normal web request to the hosting service, seoHOST. The host may keep technical access and security logs, including your IP address, requested page, browser information, and request time. These records support website delivery, security, and troubleshooting; they are separate from offline iOS gameplay.

Log retention follows the hosting configuration and the provider’s operational and legal requirements. Contact the developer with questions about these records. The website includes no third-party analytics scripts or advertising trackers.

External services and optional tips

External links open another website or app. That service handles information under its own privacy policy.

• Buy Me a Coffee: optional contributions are handled by Buy Me a Coffee and its payment providers. The creator may receive supporter details such as your name, email address, message, and contribution details. Rocket Roadster does not process or store payment-card details. See the Buy Me a Coffee privacy policy.
• Apple: App Store services, device backups, and any diagnostics you choose to share through Apple are governed by your Apple settings and Apple’s privacy policy.

Supporter information received by the developer is used to recognise contributions, maintain legacy supporter records, respond to messages, and keep any legally required payment records. It is retained only as needed for those purposes and any required accounting period.

Personal information is not sold or used for targeted advertising. Service providers handle information as needed to provide hosting, email, or the external services you choose to use. Information may also be disclosed where required by law.

Your choices and rights

You can play iOS and both web modes without sending a support email, joining a leaderboard or making a contribution. Local scores can be removed as described above. Leaving the nickname blank does not remove existing published entries; contact support for server-record questions. For personal information held by the developer, you may request access, correction, deletion, or a copy, and object to or request restriction of processing, as applicable under data protection law.

Support correspondence and essential website security records are handled for the legitimate interests of answering requests and operating a secure service, or to meet legal obligations. Where processing relies on consent, you can withdraw that consent. You can also complain to your local data protection authority; in Poland this is the President of the Personal Data Protection Office (UODO).

Send requests to support@rocketroadster.com.pl. Only information needed to handle and verify your request will be requested.

Children’s privacy

The iOS game does not ask players for their age or personal details. Both web modes can be played without providing details; joining an optional leaderboard asks for a public nickname. If a child has sent personal information through a leaderboard, verification, support or an external service, a parent or guardian can contact the developer about information the developer holds. Requests concerning an external service should also be directed to that service.

Changes and contact

This policy will be updated if the game’s data practices change. The date above identifies the latest version.

Bartłomiej Bocian
support@rocketroadster.com.pl

Need help playing? Visit Rocket Roadster support.