Brawlpixel provides Don't Wake the Gorilla! (the "game"). This policy explains how the game uses information and the choices available to you. For privacy questions or requests, email brawlpixeldeveloper@gmail.com.
You can play without connecting to Google Play Games. The current game requires an internet connection, but a Play Games profile, purchases, optional Gameplay Analytics and optional Crash Diagnostics are not required to play. You do not create a separate Brawlpixel account in this version.
Game progress is saved on your device. Google separately processes the Play Games, purchase, advertising and optional Firebase data described below. Brawlpixel does not operate a server-side player database or cloud-save service.
1. Progress and settings on your device
The game stores scores, survival records, banana-coins, missions, daily results, unlocked content, inventory, upgrades, boosts, preferences and discoveries in app storage. It also stores privacy choices and purchase-fulfillment history to avoid granting the same purchase twice. Recovery copies and integrity checks help protect against accidental save corruption.
These records are used to run the game and preserve your progress. The game does not upload your complete save, coin balance or purchase ledger to a Brawlpixel game server. The Google services described below process their own service data.
Android backup or device transfer may include app data, depending on your device, account and backup settings. This may include local saves, purchase-fulfillment records, privacy choices and Play Games record associations. Android backup is separate from Play Games and is controlled through Android and Google settings. The game does not guarantee recovery after reinstalling, clearing storage or changing devices.
2. Google Play Games
Google Play Games Services provides optional player identity, achievements and leaderboards. The game uses your Play Games gamer name and available profile picture, and a Google-issued player identifier to keep records associated with the correct player. It does not request your Google password or use your email address as your gamer name.
The SDK checks authentication when the game starts and returns to the foreground. Your existing Google Play Games settings may allow automatic sign-in; otherwise you can use Connect to Play. Google provides the authentication interface. Your Google account and Play Games settings control the account used and automatic sign-in behavior.
While authenticated, the game submits eligible completed-run records to Google: highest single-run score, cumulative actual bananas caught or fed, longest survival, achievement unlocks and progress toward incremental achievements. Banana-coins, currency purchases and rewarded currency grants are not treated as collected gameplay bananas. Runs using rewarded continues are excluded from competitive leaderboard records but can count toward achievements.
A separate local record book stores cumulative gameplay totals and associates them with the relevant Play Games player identifier. It supports account separation and safe retries when submissions fail. Guest records stay unassigned until you explicitly select Share Recorded Guest Runs; that action assigns the recorded guest batch to the displayed account. Records started under another player are not silently reassigned.
Google stores the submitted game-service records. Visibility to other players depends on Google's profile and leaderboard settings. Google's Play Games SDK may also process its own service usage and diagnostic information independently of the game's Firebase choices. See Google Play Games data information.
Play Games does not back up or synchronize your local game save, coins, purchases or Remove Ads entitlement. The banana leaderboard is based on this installation's recorded totals for an account; it does not add together different devices' totals.
3. Purchases
Google Play Billing handles optional banana-coin and Remove Ads purchases. The game processes product identifiers, purchase status, quantity, order information, purchase tokens and ownership results to deliver items, prevent duplicate grants, finish transactions and restore eligible ownership.
Payment-card information is handled by Google Play and its payment providers, not received by the game. Purchase tokens and the local fulfillment ledger are not sent to a Brawlpixel receipt server. They are not included in the game's Firebase event or diagnostic payloads.
Remove Ads suppresses automatic interstitial ads between runs. Optional rewarded ads may still be offered for benefits such as continuing a run or doubling earned coins. Consumed coin purchases are not a cloud backup of your coin balance. Google retains purchase records under its own policies and applicable requirements.
4. Advertising and advertising privacy
The game uses Google AdMob/Google Mobile Ads for interstitial and optional rewarded ads. Google's User Messaging Platform (UMP) manages advertising privacy choices where applicable. Advertising permission and the optional Firebase choices are separate. You can open Privacy Choices, then Manage Advertising Privacy, to access Google's options when available.
When advertising services operate, Google may process IP addresses and approximate region, advertising or other device/account identifiers, app/ad interactions, and performance or diagnostic information for advertising, measurement and fraud prevention. The game does not request GPS permission to provide precise location. Google explains these practices in its Mobile Ads data disclosure and Privacy Policy.
The available ads and personalization depend on service configuration, region and choices. Restricting personalized ads does not necessarily stop every advertising-related data transfer. Android also provides advertising identifier controls. Test releases use Google demo ads; that does not mean the SDK performs no processing. Rewarded benefits require a successful eligible ad interaction, and may be unavailable when ads cannot load.
5. Optional Gameplay Analytics
Gameplay Analytics is off until you explicitly enable it in the game's privacy choices. In builds where Analytics is enabled, Firebase Analytics helps us understand and improve gameplay through events such as run starts and endings, scores and duration, progression, feature use, ad outcomes and purchase-completion events. The SDK may also process app/device information and app-instance identifiers under Google's documentation.
The game's event payloads do not include your Play Games player identifier, gamer name, email, purchase token, payment details or raw save. Its Firebase integration does not set a custom player user ID and keeps Analytics advertising consent categories denied.
You can decline or turn off Gameplay Analytics in Privacy Choices without losing gameplay. Withdrawal disables further collection through the integration and requests a reset of local Analytics data and the app-instance identifier. It does not automatically erase data already processed by Google. Google's own service diagnostics and advertising privacy remain separate from this switch.
6. Optional Crash Diagnostics
Crash Diagnostics is independently off until you explicitly enable it. In builds where this service is enabled, Firebase Crashlytics processes crash reports, application-not-responding information, stack traces, app/device/operating-system information and installation/session identifiers to help us diagnose failures. The game may attach its current screen, game state, whether a run is active, and sanitized non-fatal JavaScript error information.
The game's diagnostic integration does not attach Play Games identity, email, advertising ID, payment information, purchase tokens, raw saves or coin balances. Native crash reports are produced by the SDK and may contain technical stack and device information.
You can withdraw Crash Diagnostics in Privacy Choices. The integration disables future reporting and asks the SDK to delete unsent reports; it cannot erase reports already received by Firebase. Google describes Crashlytics data handling and its 90-day period before removal of crash traces and associated identifiers begins in Firebase privacy information.
Declining Analytics does not enable or disable Crash Diagnostics, and the reverse is also true. Some test builds keep both services inactive even if a local preference is saved.
8. Retention, deletion and your choices
Local saves, purchase history, preferences and the Play Games record book remain in app storage until removed, replaced through normal use, or affected by your device's storage/backup controls. Clearing app storage can permanently remove progress and purchase-deduplication history. Uninstalling or clearing storage does not necessarily remove Android backups or data already held by Google or a sharing destination. Do not clear a populated installation to troubleshoot ordinary sign-in or purchase issues without understanding these effects.
Google Play Games data can be managed through Google's profile/settings tools. See Google's instructions for deleting Play Games data. Deleting Google's copy does not remove this game's local record book. If you reconnect while local records remain, the game may submit them again. Contact us for help understanding how to remove local Play Games records without deleting unrelated progress or purchases; this version has no dedicated in-game record-deletion button.
Analytics user/event retention depends on the active Google Analytics property settings; aggregated reports and separately retained provider records may follow different rules. We use Analytics for game improvement rather than retaining a complete player save. Contact us for information about the current retention settings or a privacy request. Withdrawing consent stops future collection as described above; it does not itself delete provider history.
Support correspondence is retained while needed to answer and resolve the request and meet applicable recordkeeping obligations. You can request deletion of correspondence you sent us. Records held by Google for purchases, advertising, Play Games and other services follow the relevant service settings, policies and applicable requirements. Crashlytics retention is described above.
Depending on your location and the information involved, you may have rights to request access, correction, a copy or deletion of personal information, object to processing, or withdraw consent. Send requests to brawlpixeldeveloper@gmail.com. We may need enough information to verify and locate a request. The game does not attach a player account identifier to Firebase diagnostics, so we may be unable to identify a particular report as yours. We cannot remotely erase your device or delete your Google account. We will explain the available controls and handle requests according to applicable requirements.
9. Service providers and processing locations
The game uses Google services for Play Games, purchases, advertising/privacy controls and optional Firebase services. Information is processed by Google and its relevant service providers under their applicable terms and policies. Support email is handled through our email provider. Sharing destinations receive only what you choose to share through those features.
These services may process information outside your country. Their privacy information explains the applicable processing locations and safeguards. The game does not operate a separate Brawlpixel account, cloud-save or ranking server in this version. This does not mean Google services receive no data.
If you read a hosted copy of this policy, its hosting service processes the web request needed to deliver and protect the page, which may include your IP address, browser information and request time. The policy page itself loads no advertising or analytics scripts.
10. Children and audience
The intended audience is 13+ (ages 13 and older), including teenagers and adults. The game is not directed to children under 13. Minimum ages and consent requirements can differ by region and service. If you believe a child has provided personal information to us, contact brawlpixeldeveloper@gmail.com so we can review the concern and available deletion steps.
11. Security
The Android app blocks cleartext HTTP traffic and uses Google SDK/platform networking for the services described here. App storage uses Android's app-storage protections. The game's local save checksums help detect accidental corruption; they are not encryption or proof against tampering. Do not disclose private credentials or transaction tokens in support messages.
12. Updates and contact
We may revise this policy when the game or its data practices change. The date above identifies this version. Where a change requires a new permission or consent choice, that choice is separate from merely updating this page.
Brawlpixel — Don't Wake the Gorilla!
Privacy and support: brawlpixeldeveloper@gmail.com
Further information: Google Privacy Policy, Google Play Games data information, Google Mobile Ads data disclosure, Firebase privacy information, and Google Analytics retention information.