Privacy policy

Playing the game

The game does not require a player account. The production iOS app can offer in-app purchases through Apple's App Store, with RevenueCat used to load products, validate transactions, deliver purchased content, and restore eligible non-consumable purchases. The production iOS app includes optional rewarded ads and limited interstitial ads at natural level boundaries. Development builds use Google-provided sample ads, which do not earn advertising revenue.

Information stored on your device

The game stores progress and preferences locally, including completed levels, settings, tutorial progress, virtual currency, lives, and analytics session records in builds that include analytics. Clearing the app's storage on Android removes local data. Removing the app and its data on iOS removes local data, subject to device backup and restoration settings. Removing local data does not automatically delete information already sent to an analytics or purchase service. The game also stores transaction identifiers locally after a successful purchase to prevent the same transaction from granting an item or virtual currency more than once.

Gameplay analytics

Analytics-enabled builds, including the production iOS app, use PostHog to help us understand progression, balance levels, and diagnose technical problems. Information sent can include an app-generated identifier, session and event identifiers, levels played, attempts, shots, wins and losses, time spent playing, feature use, virtual-currency changes, notification permission and interaction events, advertising opportunities and placement, availability and suppression reasons, impressions, clicks, completion or dismissal, estimated impression value and currency, whether play continued or the app was backgrounded shortly after an interstitial, app version, platform, device model, performance measurements, and error categories. On iOS, the app also records the operating system's tracking-permission status. Builds with access diagnostics also record when the review or developer code screen is opened or dismissed, the number and result of attempts, the number of digits entered, elapsed time, and when the developer menu is opened or closed. The entered code itself, its characters, and code hashes are not sent.

These records are not connected to a player account, but identifiers and technical data can still constitute personal information. Network requests also expose an IP address to the receiving service. The app is configured to send events to PostHog's US endpoint. PostHog person profiles are disabled; full error messages and stack traces are not included in the game's custom error event.

Builds with regional access checks also contact this website on launch and when returning to the game. Our hosting provider uses the connection's IP address to determine its approximate country and return an availability decision. This check sends no player, advertising, or device identifier and does not store the detected country in the game. Availability can vary by region.

Visual session replay is disabled. The game does not capture or send gameplay screenshots, audio, console logs, or network telemetry through PostHog Session Replay.

We use this information to improve the game, not to serve advertising. Contact us below to ask about access or deletion of data relating to your installation. Because there is no player account, we may need additional information to locate relevant records. Do not send passwords or sensitive information.

PostHog Privacy Policy

In-app purchases and RevenueCat

In the production iOS app, Apple processes the payment and account information associated with an App Store purchase. We do not receive your full payment-card details. RevenueCat acts as our purchase infrastructure provider and processor. It receives purchase history and transaction information needed to provide the store, including product identifiers, transaction status and dates, Apple receipt or signed transaction information, and the last time the app contacted the service. Network requests also expose an IP address, and the service can receive technical information such as device type, operating system, app version, and platform.

Android test builds may use RevenueCat and Google Play Billing to test product loading and purchases. If Google Play purchases are enabled, Google processes the payment and RevenueCat receives the purchase and transaction information needed to validate it. Live Google Play purchases are not currently enabled.

Because the game has no player account and we do not provide a custom account identifier to RevenueCat, its SDK generates a random anonymous App User ID and caches it on the device. This RevenueCat identifier is separate from the app-generated analytics identifier described above. We do not configure RevenueCat with your name, email address, phone number, or advertising identifier. Purchase history is used for app functionality, receipt validation, fraud prevention, customer support, restoration of eligible purchases, and aggregate store analytics. We do not use RevenueCat purchase data for targeted advertising and do not sell it.

RevenueCat Privacy Policy · RevenueCat Data Processing Addendum and sub-processor list

Advertising measurement in RevenueCat

Builds with ad measurement send RevenueCat ad loading, display, click, load-failure, and impression-revenue events under the same anonymous App User ID used for purchases. These events include the ad format, unit, impression identifier, network, placement, estimated value, currency, precision, and available error codes. We use them to understand advertising performance alongside aggregate store results. This does not provide RevenueCat with an advertising identifier or send purchase details to our attribution partners.

Notifications

On supported builds, you can choose whether to allow local game reminders through your device's permission controls. Reminders are scheduled on the device. You can turn them off in your device settings. Analytics-enabled builds record notification permission and interaction events as described above.

TikTok campaign measurement

The initial public version does not send data to TikTok. In versions that enable TikTok App Events SDK on iOS, the game requests permission through Apple's App Tracking Transparency prompt. The SDK does not initialize or send events unless the device reports authorization and the app's regional and privacy checks also permit tracking. The current rollout is limited to eligible US installations; enabling AdMob personalization in another country does not enable TikTok there. If permission is denied, restricted, or unavailable, TikTok campaign measurement remains off for that installation.

When authorized, the integration is used to attribute installs, measure advertising performance, and optimize campaigns for a player's first completion of Levels 5, 10, 15, 20, 25, 30, and 35. The SDK can automatically report app installation, app launch, and next-day retention. A selected level event contains the level number, level name, milestone label, app version, and a random event identifier used to prevent duplicate reporting.

TikTok may also receive technical and advertising-attribution information generated by the SDK, such as IP address, device and operating-system information, app information, event timestamps, mobile advertising identifiers where the platform permits them, and information about whether an install or event followed a TikTok ad. TikTok processes this information under its own policies and business-product terms.

We have disabled enhanced data postback and automatic purchase tracking. Our integration does not send a player's name, email address, phone number, game-account identifier, purchase details, individual shots or losses, messages, or text entered in the game to TikTok. It also does not run in the Unity Editor, development builds, or our internal iPhone builds.

TikTok Privacy Policy · TikTok Advertiser Tools and Related Terms

Tenjin and AppLovin campaign measurement

iOS builds with Tenjin use it to attribute installs and measure campaigns, including AppLovin campaigns. Tenjin initializes only for eligible US installations after the current Apple tracking purpose is authorized and the app's regional and privacy checks permit tracking. An earlier permission grant for other partners does not automatically enable Tenjin. Declining tracking leaves gameplay and purchases available. Internal and Friends builds and developer test activity do not send these events.

Our integration reports installation and app-open sessions, and first completions of Levels 5, 10, 15, 20, 25, 30, and 35. Tenjin may receive vendor and advertising identifiers where permitted, IP address, app and SDK versions, operating-system and device information, locale, country settings, timestamps, and advertising-attribution information. Campaign callbacks can share install and app-open attribution with AppLovin. Milestone callbacks may be added for the listed level completions. These records help measure and optimize campaigns. Our integration does not send purchase transactions, player names, email addresses, phone numbers, or individual shots to these partners.

These partners may process information outside your country. You can withdraw future tracking permission in iOS Settings and contact us about access or deletion of records relating to your installation. Already received records remain subject to the providers' retention practices and applicable legal obligations.

Tenjin Privacy Policy · AppLovin Privacy Policy

Test participation and feedback

We use the Google account email address supplied for testing to manage access to the closed test in Google Play Console. If you email feedback, we receive your email address, message, and any attachments you choose to send. We use this information to manage testing, respond, and investigate problems. Please avoid sending sensitive information.

We do not sell your information. Testing and support information is kept while needed for those purposes; you can ask us to remove you from the test or delete your correspondence by contacting us below, subject to legal retention obligations.

App stores

Google and Apple may process information when you download, update, or test the app or make an in-app purchase, according to their own privacy policies and your account settings. Apple independently keeps App Store and transaction records under its policies and legal obligations.

Google Privacy Policy · Apple Privacy Policy

Children and families

Our Terms require players to be at least 13 years old, or older where local law requires it. The Android app's declared target audience on Google Play is also ages 13 and older. We do not ask for a date of birth or verify every player's age, so this requirement does not establish the age of each person using the game. Parents and guardians should manage minors' access and contact support on their behalf. Analytics-enabled builds do not distinguish children from older players.

A parent or guardian can contact us to ask about information relating to their child, request deletion, or raise a concern. If you believe a child has provided personal information, please contact us so we can investigate and address it.

TikTok campaign measurement remains disabled when Apple restricts or does not authorize tracking. We do not ask for a date of birth or age in the game. TikTok does not permit sharing children's data through its advertising tools; parents and guardians can contact us about any concern or request deletion using the contact details below.

Advertising

The production iOS app includes Google Mobile Ads and Google User Messaging Platform. A player can choose to watch a clearly labeled rewarded ad for an extra life or progress toward an eligible cosmetic ball. These optional rewarded ads are not removed by the Remove Ads purchase. Starting at Level 15, a full-screen interstitial may appear only at a natural level boundary, such as after completing a level or before retrying a failed level. Interstitials have a two-minute session grace period, an eight-minute cooldown, a maximum of two per session, and a seven-minute quiet period after a rewarded ad. A stable control group does not receive interstitials. A verified Remove Ads purchase suppresses interstitials.

When the app requests or displays an ad, Google may receive technical and ad-event information such as IP address, device and app information, consent signals, ad requests, impressions, clicks, completion or dismissal, estimated impression value, and errors. Google's SDK may also collect device identifiers, crash and performance information, and app interactions; IP addresses can indicate approximate location. Ad content is configured for a general audience. Development builds use Google-provided sample ad units. See the Google Privacy Policy and Google's information about partner apps.

Earlier builds disable ad personalization. New iOS builds may allow personalized ads in selected regions when the app's privacy checks permit them and you authorize the current Apple tracking prompt. Google AdMob may combine your advertising identifier and app activity with information from other apps and services to personalize ads and measure their performance. Device permission alone does not override regional consent requirements, an opt-out, or known age restrictions. Current builds do not enable personalized ads where Google identifies European consent requirements, including the EEA, United Kingdom, and Switzerland. Android test builds keep personalization disabled.

You can decline tracking and continue playing. Ads without personalization may still process information for delivery, security, measurement, and other permitted purposes; they do not mean that no data is collected. Ad availability depends on the applicable privacy requirements and your choices. Google's advertising information explains its advertising practices and controls.

Service providers, sub-processors, and transfers

We share information only with service providers needed to operate the services described above, when you ask us to, or when required to comply with law, protect rights and safety, investigate abuse, or complete a business transfer. These providers process information under their agreements and privacy commitments. PostHog processes the analytics data described above. RevenueCat processes purchase data on our behalf and may use the sub-processors listed in its Data Processing Addendum, including providers of cloud hosting, databases, logging, security, and service monitoring. RevenueCat states that customer data is stored in the United States, including on Amazon Web Services. Information may therefore be processed outside the country where you live, subject to applicable safeguards.

Google handles advertising information under its own privacy policies and applicable advertising terms. Advertising data may be processed outside your country, including outside Japan and in the United States. Google's business privacy information and advertising transfer information describe its practices and applicable transfer arrangements. These links do not mean that the same transfer mechanism applies in every country. You can contact us about recipients or overseas processing relating to the app.

Retention and deletion

Local game progress, purchase grants, and transaction identifiers are kept on the device until you clear the app's data or remove the app, subject to device backup and restoration settings. PostHog analytics, attribution records, and RevenueCat purchase and advertising records are retained for as long as reasonably needed to provide and restore game features, prevent duplicate grants and fraud, analyze and support the service, resolve disputes, and meet accounting or other legal obligations. Aggregated or de-identified information may be retained longer where it no longer identifies an installation or person.

You may contact us to request access, correction, or deletion of data associated with your installation. Because there is no player account, we may ask for the anonymous identifier or transaction information needed to locate the record. Where applicable, we can instruct RevenueCat, PostHog, or Tenjin to delete the associated record, subject to legal exceptions. Deleting a RevenueCat record does not cancel a purchase or erase records independently maintained by Apple, and restoring a purchase may cause the App Store transaction to be sent to RevenueCat again. Do not send passwords, full payment-card details, or other sensitive information with a request.

Your choices

In builds with Ad Privacy, open Settings on the game's Home screen and select Ad Privacy. Where Google requires privacy options, this opens those options; otherwise it opens device settings. On iOS, you can also review or withdraw the game's tracking permission in Settings → Privacy & Security → Tracking. On Android, available advertising controls depend on your device and Google Play services. Changing a permission affects future collection; it does not erase information already received by a provider.

You can manage notifications and applicable device permissions in system settings. You can also use your device's privacy and advertising settings to manage available advertising choices. You may contact us to ask about access, correction, or deletion of information associated with you or your installation, as described in Retention and deletion above. Some information may be retained where required for security, accounting, dispute resolution, or other legal obligations.

Changes

We will update this page when the game's data practices change. Live advertising or additional data collection will require updated disclosures before those features are enabled.

Contact

Ben Hertzel Fadlon (Benfad)
bouncefest.support@gmail.com