YOUR INFORMATION & CHOICES
Your information.
Your choices.
Last updated:
This policy includes the Player ID, support-gift and device-wallet features prepared for version 1.1. These features are available when that update is installed.
Mahmudul Hasan operates Bounce Courier. This page describes the information used by the iOS game and its optional support services. Ordinary gameplay does not require a game or support account.
Apple provides iCloud, Game Center and App Store purchases. Google provides advertising and Firebase services. Player IDs and support gifts use Firebase Authentication, Cloud Firestore, Cloud Functions and App Check. Optional analytics and crash reporting have separate controls. The referral and downloadable-level services are not currently connected.
Game progress and local records
The game keeps progress and preferences on your device, including completed routes, scores, stars, times, checkpoints, badges, collection coins, cosmetic selections and difficulty. This information supports gameplay and saved progress.
A local playtest log can record route and mode, starts, completions, reached stages and elapsed time. Its CSV is not automatically uploaded. Settings lets you clear the log or export it to a recipient you choose. Optional Firebase analytics is a separate reporting feature.
iCloud progress
Supported progress can sync using Apple's iCloud key-value storage. Progress sync starts enabled and can be turned off in Settings. Turning it off does not erase an existing cloud copy. Reset progress clears the game's local progress and requests the same reset in iCloud; an offline reset may wait until iCloud is available.
We do not receive your Apple Account password or have direct access to your private iCloud storage. Apple controls its services under its own terms and privacy practices.
Courier Gems and Apple purchases
Gems can be purchased and used without signing in to iCloud. An independent device wallet is stored in the iOS Keychain. When iCloud becomes available, it can be transferred once into this game's private CloudKit wallet using checks against duplicate credit. Cloud wallet data uses encrypted CloudKit fields. Gem-wallet sync is separate from the gameplay-progress sync setting.
Cloud transactions need access to the original iCloud account. If that wallet or an ongoing transfer cannot be verified, the game may ask you to reconnect before spending or completing a delivery. It does not copy existing cloud funds into a second independent offline wallet. Paid-continuation state stays local.
Apple handles payments. The game uses Apple-signed transaction details to verify products, unlock benefits, deliver gems and apply refunds. We do not receive complete payment-card details. Minimal transaction references and refund safeguards remain in the wallet to prevent an old purchase from adding gems again. Restoring purchases does not refill spent consumables.
Keychain data can remain after uninstalling, but recovery after device loss or reset is not guaranteed. A Player ID does not replace your gem wallet or its iCloud recovery.
Game Center
When Game Center is enabled and connected, eligible scores and achievements are sent to Apple. Your Game Center name and results may be visible under Apple's sharing and privacy settings. Connecting Game Center for scores does not by itself create a Bounce Courier support profile.
Optional Player IDs and support gifts
Choose Get Player ID in Settings to connect the support feature to your existing Game Center account. Firebase Authentication receives Game Center identifiers, your Game Center display name, and signed identity-verification information. It creates a Firebase account identifier. Our service assigns a public BC Player ID to that account.
The display name comes from Game Center and may contain information you chose to include there. This feature does not ask you to enter a player email address, password, phone number or payment-card details. We do not receive your Apple Account password or your contacts.
You can tap the Player ID to copy it, then share it with Support. Copying alone does not send it to another person. The public code is a support reference, not a sign-in credential. While your support account remains active, the same connected Game Center identity can recover that Player ID on another device.
Our support database stores the public Player ID, Firebase account identifier, creation and delivery times, gift identifiers, gift type and amount, the original wallet identifier, signed delivery records, and an internal owner note. A note may refer to information you supplied in a support request. Access to player lookup and gift issuance is restricted to authorized owners.
Support gifts are free and do not charge your Apple account or create an App Store purchase. Signed records and duplicate-delivery checks allow interrupted delivery to be retried. Gem gifts stay bound to the original wallet or its recorded import into iCloud. Gifted non-consumable benefits can restore for the same support account. Restoring a starter gift does not award another starter coin bonus or restart its temporary ad-free period.
Player ID and gift data are used for account functionality, support, delivery verification and abuse prevention. The app does not attach these IDs, wallet identifiers or signed gift records to its optional analytics or crash reports. We do not use these support records for cross-app advertising or share them with data brokers.
App integrity and service security
Firebase App Check checks that service requests come from the genuine app. On supported devices it processes Apple's App Attest attestation and assertion evidence. Where a configured DeviceCheck fallback is used, it processes a DeviceCheck token. These security checks are separate from the optional analytics and crash-reporting choices.
Firebase and Google Cloud may also handle IP addresses, request times, app/device information and other technical metadata for operation and security. The support database runs in the US Central region. Authentication, security and other provider services may process data in other countries under their applicable terms.
The owner dashboard uses Google sign-in for its operators. Firebase Authentication can receive the operator's Google account identifier, email address, display name and any profile photo link returned by Google. The dashboard uses reCAPTCHA Enterprise through App Check for browser-integrity checks. Players do not need a dashboard account to play or receive a gift.
Advertising and ad choices
Releases with advertising use Google AdMob and User Messaging Platform. Ads can appear between eligible runs; rewarded videos are optional offers for an in-game benefit.
The advertising SDK may process IP addresses and inferred approximate location, available device or advertising identifiers, app/ad interactions, diagnostics and performance information. The integration requests non-personalized ads, which still involve data processing. UMP presents applicable consent or privacy choices, and an available ad-privacy control can appear in Settings.
Read Google's Privacy Policy and Google's AdMob iOS data disclosures for provider information. Ad choices are separate from optional gameplay reporting.
Firebase settings, analytics and diagnostics
Remote settings
Firebase Remote Config supplies operational settings, such as ad timing, availability and update prompts. It can process installation/app identifiers, country and language codes, time zone, OS and SDK information. It operates independently of optional analytics and crash sharing; cached settings remain available when offline. An update check may contact Apple's public App Store lookup service with the app identifier and a country code, without game-account or wallet details.
Optional gameplay analytics
If you enable analytics, Google Analytics for Firebase receives app/session information and selected events, such as level starts, failures, completions, loading times, ad outcomes and gems earned or spent. The SDK can also measure StoreKit purchase events, including product IDs and prices. It uses an app-instance identifier and may derive general location from masked IP addresses. We use the reports to understand and improve the game.
The Analytics configuration disables advertising-identifier and vendor-identifier collection, denies advertising-use and personalization consent, and does not attach your name, email, Game Center identity, Player ID, iCloud account, wallet ID or payment receipt to those events.
Optional crash reports
If you enable crash sharing, Firebase Crashlytics receives crash traces, device/OS details, diagnostic information and game context such as level and tier. Selected handled errors are reported without raw error messages or private transaction details. Analytics may supply event breadcrumbs when both choices are enabled. Crash reports can be cached locally; saved reports are sent on a later launch only while crash sharing is enabled.
Your reporting choices
Analytics and crash sharing start off. They can be changed separately during the welcome flow or in Settings → Help → Privacy & improvements. Declining does not remove gameplay, purchases or available rewarded videos. These choices do not disable iCloud, Game Center, Remote Config or security checks needed by the support service.
Stop sharing & reset local analytics stops future optional reporting, resets the local Analytics identifier and removes queued crash reports. It does not erase information already uploaded to Google. Contact us about a request concerning uploaded data; we may need information that identifies the relevant installation. Aggregated reports or information required for security or legal purposes may remain under the service's retention practices.
Provider information: Firebase privacy and security, Firebase Apple SDK data disclosures, and Google's Privacy Policy.
Services not currently connected
The referral service and downloadable-level endpoint are not configured in this update. The app does not send new referral-profile or additional-route download data to those services. Their data practices will be disclosed before they are activated. Bundled levels remain playable offline.
Resetting or deleting game data
Reset progress clears route progress, scores, stars, times, checkpoints, coins and badges locally, and requests the same reset for this game's iCloud progress. Gems and Apple purchases are preserved. Scores or achievements already submitted to Game Center are not removed by this action.
Delete game account & data removes a connected Player ID support account before erasing the described game data. Use the Game Center account associated with that Player ID. The server disables the profile and its public lookup, removes private support notes and signed gift payloads, and deletes the Firebase Authentication account. A failed server request remains retryable; the app does not report it as a completed deletion.
The game then clears local progress and playtest data, clears the device gem wallet or its connected iCloud wallet, resets preferences, stops optional reporting, resets local Analytics data, removes queued crash reports and disables progress syncing. Clearing a cloud wallet requires a successful online update. The iCloud progress reset can remain queued while offline. Unspent gems are forfeited. Any previously connected referral profile also has to complete its deletion request.
Minimal purchase and gift-delivery safeguards remain so old receipts cannot restore deleted or spent gems. Previously uploaded analytics and diagnostic reports are not erased by this button. Your Apple Account, Apple purchases and other games are unaffected. Existing Game Center records require a separate request through Support.
Uninstalling the app does not necessarily erase Keychain records or copies held by Apple. Apple provides its own controls and retention practices for iCloud, Game Center and purchases.
Retention and security
Active support-account and gift-delivery records remain available to provide the feature and restore eligible benefits. On support-account deletion, private notes and signed payloads are removed. Restricted, minimized records used to prevent duplicate gifts and handle disputes have a 365-day retention deadline, after which the scheduled daily cleanup removes them. These records include a private account-identifier tombstone, gift type/amount, timestamps, prior delivery state and request fingerprints.
A retired public-code reservation keeps no account identifier and is retained to prevent that same code being assigned to someone else. Local wallet receipt safeguards remain with the wallet's anti-duplication history.
The project's default operational-log bucket is configured for 30 days. Google Cloud's required audit-log bucket retains required audit records for 400 days. Firebase Analytics, Crashlytics and other provider data follow their respective retention settings and deletion controls. Removing a support profile does not instantly erase provider logs.
When you contact us, your message is kept for as long as reasonably needed to respond, maintain necessary support records and meet legal obligations. Device-only records remain until cleared through the game or device controls. Apple manages retention within its own services.
We use iOS protections, restricted cloud access, signed gift records and the safeguards provided by Apple and Google. Private gift-signing keys are not distributed in the app, this website or the owner dashboard. No storage or transmission method can promise absolute security.
Children's privacy
Ordinary play does not ask for a name, email address, birth date or profile form. The optional Player ID feature receives the Game Center identifiers and display name described above. Parents or guardians with a privacy concern can contact us below.
Privacy requests and policy changes
Your location may give you rights to request access, correction or deletion of personal information we control. Contact us using the address below. We handle requests concerning our records, including our Firebase project, when we can identify the relevant information. Data independently controlled by Apple or Google is also subject to their privacy tools and request processes.
This policy may change as the game and its services change. A revised policy will be published with an updated effective date.
This website
These public game pages are hosted on GitHub Pages. They do not add advertising or analytics scripts, tracking cookies or a sign-in form. GitHub may process visitor IP addresses and technical request data to provide and secure hosting, as described in GitHub’s privacy statement. Following an App Store, email or other external link uses that provider’s service.
Contact
Operator: Mahmudul Hasan
Email: mm@letstangerine.com
Game website: www.mahmudulhasan.me/games/bounce-courier/
Apple provider information: Apple Privacy Policy.