ARROW BUBBLE POP PRIVACY POLICY
Effective date: 2026-09-11
Last updated: 2026-09-11
This Privacy Policy explains how Gikeon ("we", "our", "us") handles information when you use Arrow Bubble Pop ("Game") on Android.
NOTE: What changed in this version (2026-09-11). This version clarifies the identifiers, approximate location inferred from an IP address, Google Play Games account processing, the complete set of mediation adapters shipped in the Android build, and the difference between a compiled adapter and an active ad source. It also clarifies consent, withdrawal, deletion requests, and provider retention. Sections 3 to 15 and 18 describe this.
1) Scope
This Policy applies to Arrow Bubble Pop on Android and related support requests sent to us.
2) Age and Audience
Arrow Bubble Pop is intended for users 16 years or older. We do not knowingly collect personal data from children under the applicable age in their region.
3) Information We Collect
A) Information stored locally on your device
The Game stores data locally on your device so progress and settings can be restored. Examples include:
• level progress and unlock state;
• coins and power-up inventory (hints, bombs, wand, rainbow);
• sound, vibration, and reduced-motion preferences;
• tutorial and intro flags;
• whether you accepted the legal notice;
• cached ad-removal purchase status;
• an app install identifier - a random value generated by the Game on first launch (see Section 3C);
• the time of first launch, and a time reference used to keep in-game timers accurate;
• your assigned configuration group for feature testing (see Section 5B);
• a record of which reminder notifications have been scheduled.
This data stays on your device unless you clear app data or uninstall the Game. We do not operate a user account system of our own. Some of this data is also saved to your Google account through Google Play Games Services - see Section 7.
B) Information collected by third-party services
The Game uses third-party SDKs for advertising, consent management, purchases, analytics, and remote configuration. These providers may process data such as:
• device and app identifiers (for example, Android Advertising ID, app set ID, Firebase's app instance identifier, and provider-specific identifiers);
• IP address and approximate region (typically country-level, inferred from IP). Under Google Play's Data safety definitions, an approximate location inferred from an IP address is still approximate location;
• device and app information - model, operating system version, language, region, app version, and coarse hardware characteristics such as available memory and processor core count;
• ad load, display, and interaction events, and ad revenue values reported by the ad network;
• gameplay events described in Section 3C;
• purchase and entitlement status from Google Play;
• crash and diagnostic information.
Third-party services used:
• Google AdMob / Google Mobile Ads SDK - banner, interstitial, and rewarded ads;
• AdMob mediation adapters - AppLovin, Chartboost, InMobi, Mintegral, Moloco, Pangle, Unity Ads, and Vungle/Liftoff are included in the Android build as possible demand sources. An adapter being included in the build does not by itself send it an ad request: a network processes data only when it is enabled and configured as an active ad source in the relevant AdMob mediation group;
• AppLovin MAX - an optional alternative mediation SDK is included in the build. It is inactive unless its SDK key and ad units are configured and Remote Config selects the MAX provider; if that configuration is missing, the Game falls back to AdMob;
• Google User Messaging Platform (UMP) - ad consent and privacy choices where required;
• Google Play Billing - in-app purchase processing and restoration;
• Google Play In-App Review and In-App Update - the rating prompt and update prompt (see Section 6);
• Google Play Games Services - saving your game progress to your Google account. Google may also process Play Games account data such as a gamer identity and service diagnostics as part of the SDK (see Section 7);
• Google Firebase Analytics - gameplay, ad and purchase analytics;
• Google Firebase Remote Config - delivering configuration values to the Game;
• Google Firebase Crashlytics - crash and stability diagnostics (see Section 3D);
• GameAnalytics (GameAnalytics ApS, Denmark) - gameplay, economy and advertising analytics. GameAnalytics creates and controls its own installation identifier.
The mediation adapters named above are a disclosure of the SDKs shipped in the current Android build, not a promise that every network is live. The active ad partners can change in the AdMob or AppLovin dashboard without an app update. When that happens, the partner's own policy applies to the information it receives and the partner must be included in the consent configuration where required by law.
C) Analytics events and the install identifier
To understand how the Game is played and whether it is balanced fairly, the Game reports events to Firebase Analytics. These include:
• app opens and session starts;
• level starts, completions, failures and restarts, including time taken, shots fired and hearts remaining;
• use of in-game items (hint, bomb, wand, rainbow);
• coins earned and spent, and the resulting balance;
• ad requests, outcomes, rewards granted, clicks and reported ad revenue;
• purchase, restore and purchase-failure events for the Remove Ads product;
• notification permission results and which reminder (if any) was tapped to open the Game;
• coarse device class (a "low", "mid" or "high" bucket derived from memory and processor cores), used to identify performance problems affecting particular devices.
These events describe gameplay and app behaviour. We do not collect your name, email address, contacts, precise location, photos, or the content of anything you type.
The install identifier is a random value the Game generates on first launch. It is not your Advertising ID and not a hardware or device identifier. It is an app-assigned identifier, so it is treated as a user or device identifier by the analytics and crash-reporting services that receive it. It exists so that events from the same installation can be linked together, and it is deleted when you clear the Game's data or uninstall the Game. A reinstall produces a new, unrelated identifier.
Analytics events are sent to Firebase Analytics and to GameAnalytics only after the legal notice has been accepted. GameAnalytics receives the same categories of gameplay, economy and advertising events, restructured to fit its own reporting format, and generates its own separate installation identifier which we do not control or link to the identifier above. Firebase Analytics receives the app-assigned install identifier as its user ID; Crashlytics receives the same value as the crash report user ID. We do not use either identifier to identify you by name.
D) Crash and stability diagnostics
If the Game crashes or stops responding, Firebase Crashlytics collects a diagnostic report. This may include:
• the error and the technical stack trace;
• device model, operating system version, available memory, and orientation;
• the app version and how long the app had been running;
• the install identifier described above;
• a small amount of context we attach so the report is actionable - the level being played, the coarse device class, whether ads were removed, and a short trail of recent in-game actions (for example, "level_start 47").
This context describes app state, not you. We do not attach your name, contacts, message content, or anything you type.
Crash reporting follows the same consent gate as analytics: it stays off until you accept the legal notice on first launch. If you withdraw that consent through a supported in-game control, the Game stops new Firebase Analytics, Crashlytics, and cloud-save uploads; information already received by the providers is handled under their policies and retention settings.
4) Ads and Rewarded Content
The Game may show:
• Banner ads during gameplay;
• Interstitial ads at certain points (for example, after some levels);
• Rewarded video ads that you may choose to watch in exchange for in-game benefits (for example, extra power-ups or continue options).
Rewarded ads are optional. If you purchase Remove Ads, banner and interstitial ads are disabled; rewarded ads remain available so that the benefits they unlock are not lost, and where you choose to use one the reward is granted without showing an ad.
When and how often ads appear is controlled by configuration values that we can adjust remotely (see Section 5A).
Ad mediation. Ads are served through Google AdMob, which runs an auction or mediation waterfall among the ad sources enabled for the relevant ad unit and shows an eligible winning ad. The current Android build contains adapters for AppLovin, Chartboost, InMobi, Mintegral, Moloco, Pangle, Unity Ads, and Vungle/Liftoff. An active source that wins an impression receives the data it needs to serve and measure that ad - typically your Advertising ID (where available), IP address, approximate region, and device and app information - and processes it under its own privacy policy, linked in Section 18. AppLovin can also be selected as the separate MAX mediator only when the required MAX configuration is present; the Game falls back to AdMob otherwise.
Ad personalization and consent choices may be managed through prompts shown by Google UMP and through Ad privacy choices in Settings (where available). Your choice is passed through the consent mechanism to participating ad partners where the SDK supports it. Google requires each active partner to be included in the applicable consent configuration; the list in this Policy cannot replace the partner selection in the AdMob or AppLovin dashboard.
5) Remote Configuration and Feature Testing
A) Remote configuration
The Game retrieves configuration values from Firebase Remote Config at startup - for example, how frequently ads are shown, reward amounts, the selected mediator, and reminder timing. Retrieving these values involves a network request to Google, which processes it as described in Section 3B. The most recently retrieved values are cached on your device so the Game works offline. Remote configuration can change ad partners and pacing without an app update, subject to the controls and review required by the applicable platform and privacy rules.
B) Feature testing
The Game supports assigning installations to different configuration groups so that changes can be compared (for example, different ad frequencies). Where this is active, your assigned group is stored on your device, included with analytics events, and remains stable for that installation. Group assignment is random or server-directed; it is not based on any personal characteristic.
6) Rating and Update Prompts
The Game uses two standard Google Play features:
• In-App Review - after you finish a level, the Game may ask Google Play to show its rating dialog. Google Play decides whether the dialog actually appears and limits how often it can be shown. We are not told whether you left a review, or what you rated. Nothing in the Game is unlocked or withheld based on this.
• In-App Update - the Game asks Google Play whether a newer version exists and may offer to install it. This is handled entirely by Google Play.
Neither feature sends us any personal data.
7) Cloud Save (Google Play Games Services)
So that your progress survives reinstalling the Game or changing phone, the Game saves it to your own Google account using Google Play Games Services. Play Games may process your Play Games gamer identity, account and service diagnostics as part of authentication and operation, even though the Game does not request or display your name, email address, contacts or profile content. The Game uses the Saved Games/Snapshots feature and does not run its own account system.
What is saved: level progress, coins, power-up inventory, whether tutorials have been seen, and whether you purchased Remove Ads.
What is not saved: your sound, vibration and reduced-motion settings, and your acceptance of this notice. These describe a particular device and install, so they stay on the device.
Where it goes: the save is stored by Google under your Google Play Games account (the Saved
Games service uses Google's account storage), not on any server of ours. We cannot read it. We have no backend, no account system, and no ability to view, export, or delete an individual player's save.
Sign-in: Play Games signs in silently, with no prompt. If it is unavailable - you have no Play Games account, you opted out, or you are offline - the Game keeps working normally using the save on your device, and nothing is uploaded.
Managing or deleting it: because the save belongs to your Google account, you control it. Use
the Play Games app or Google's account controls to manage or delete Play Games data for this Game. The exact menu names can change as Google updates Play Games; Google's current help is linked in Section 18. You can also turn off Play Games sign-in for this Game in those controls. Deleting the save there does not delete local save data until you clear the Game's app data.
Cloud save has no effect on the Remove Ads purchase itself, which is tied to your Google Play account independently and is restored by Google Play.
8) Notifications
With your permission, the Game may send local reminder notifications - for example, an occasional prompt to return to a level you have not finished.
• These are scheduled and shown by your device. Their content is generated on your device and is not sent from our servers.
• Permission is requested inside the Game after you have played for a while, not on first launch. You may decline.
• On Android 13 and later, notifications require your explicit permission. You can revoke it at any time in Android Settings → Apps → Arrow Bubble Pop → Notifications.
• When you open the Game by tapping a reminder, the Game records which reminder it was in
analytics, so we can tell which messages are useful and stop scheduling ones that are not.
• Reminder timing can be adjusted remotely, and notifications can be switched off entirely from our side.
• We do not operate a push messaging service for this Game and cannot send you messages directly.
9) How We Use Information
We use information to:
• provide gameplay and restore local progress;
• show, measure, pace, and limit ads;
• process and restore the Remove Ads purchase;
• understand how levels are played, where players get stuck, and whether difficulty is fair;
• measure whether changes to the Game improve or harm the experience;
• identify crashes and performance problems, including problems specific to certain device classes;
• send optional reminder notifications where you have permitted them;
• save and restore your game progress through your Google account (see Section 7);
• improve stability, security, and compatibility.
We do not use this information to build advertising profiles ourselves, and we do not sell it.
10) Device Permissions
The Android app may request permissions needed to run the Game, such as:
• Internet and network state - ads, billing, consent, analytics, crash reporting, remote configuration, cloud save, and the Play rating and update prompts;
• Vibrate - optional haptic feedback when enabled in settings;
• Post notifications (Android 13+) - optional reminder notifications, requested only when you are asked;
• Receive boot completed - so that reminders you have already permitted survive a device restart;
• Advertising ID and related ad-permission declarations required by Google Play and ad SDKs, including Android Privacy Sandbox permissions (Topics and Attribution) used by advertising libraries;
• Network type - a limited phone-state permission (READ_BASIC_PHONE_STATE) declared by the Google Mobile Ads library to tell Wi-Fi from mobile data. It does not grant access to your phone number, IMEI, SIM details, or call information;
• Wake lock and foreground service - declared by Google's analytics and background-work libraries so queued events finish uploading; the Game itself schedules no foreground service.
The Game does not access your camera, microphone, contacts, or precise location. An ad SDK may infer approximate location from the device IP address; this does not require a location permission.
The Game does not request the "exact alarm" permission; reminders are scheduled approximately and may be delivered later than the stated time.
11) Legal Bases (where applicable)
Depending on your region, processing may be based on:
• your consent (for example, ad-consent choices and notification permission);
• performance of contract (providing features you request);
• legitimate interests (measuring and improving the Game, security, fraud prevention, service reliability);
• legal obligations (billing or compliance requirements).
Analytics, crash reporting, and cloud-save uploads do not begin until you accept the legal notice shown on first launch. The Game is designed to stop new analytics, crash-reporting, and cloud-save uploads when the relevant consent is withdrawn; provider-held data is not erased merely by withdrawing consent. Ad-personalization consent is handled separately through the prompt described in Section 4. Notification permission is a separate Android permission and is never required for gameplay.
12) Sharing and Disclosure
We do not sell your personal data.
Data may be shared with service providers strictly to operate and measure the Game - including Google services for ads, consent, billing, analytics, remote configuration, crash reporting and Play Games cloud save; GameAnalytics for gameplay, economy and ad analytics; and an active ad source that wins an AdMob or MAX auction or mediation decision. The possible mediation sources in the current build are AppLovin, Chartboost, InMobi, Mintegral, Moloco, Pangle, Unity Ads, and Vungle/Liftoff. A compiled adapter is inactive until configured as an ad source. Data may also be disclosed to authorities where required by law.
Google, GameAnalytics and each advertising network act as a data processor or as an independent controller depending on the service and your region; see the policies linked in Section 18.
13) Data Retention
• Local save data, the install identifier, and configuration group assignments remain on your device until you remove them (for example, by clearing app data or uninstalling).
• Your cloud save is held by Google under your own Google Play Games account and is retained until you delete it there. We cannot read or delete it for you - see Section 7 for how to manage it.
• Firebase Analytics data is retained according to the retention period configured for our Firebase project and Google's published controls and policies.
• Firebase Crashlytics retains crash reports according to Google's current Crashlytics retention practices and the configuration of our Firebase project.
• GameAnalytics retains event data according to its current policy and the retention settings of our GameAnalytics account. GameAnalytics' current documentation says detailed event and filter availability is reduced over time; historical retention and export options can vary by product and plan.
• Other third-party providers, including advertising networks, retain data according to their own policies.
14) International Transfers
The third-party services above are operated by Google (United States), GameAnalytics ApS (Denmark, an EU/EEA country), and the advertising networks participating in ad mediation. They may process and store data on servers outside your country, including in the United States. Where required, such transfers rely on legal transfer mechanisms provided by those services.
15) Your Choices and Rights
Depending on your location, you may have rights to access, correct, delete, restrict, object to, or request portability of personal data processed about you.
You can:
• stop using the Game at any time;
• uninstall the Game, or clear its app data, to remove local data and the install identifier;
• delete or manage your cloud save through the Play Games app (Section 7), and turn off Play Games sign-in for this Game;
• change ad consent through in-app prompts or Ad privacy choices in Settings (where available);
• turn Gameplay analytics off in Settings. This also stops new Firebase Crashlytics reports and cloud-save uploads for this installation;
• turn reminder notifications off in Android Settings at any time;
• reset or delete your Advertising ID in Android Settings;
• contact us using the details below to make a request about analytics or crash data associated with your installation. Because we have no account system, please include the install identifier if you are able to provide it. We will assess the request and coordinate with the relevant provider where its controls permit deletion; clearing app data or uninstalling removes the local identifier but cannot by itself erase provider-held records.
16) Security
We use reasonable measures to protect data handled through the Game and its integrations. No method of transmission or storage is completely secure.
17) External Links, Store Pages, and Policy Updates
The Game may open external links (for example, the Play Store listing, Privacy Policy, or Terms of Service). We are not responsible for third-party websites' privacy practices.
We may update this Policy from time to time. Material changes will be reflected by updating the "Last updated" date and, where appropriate, by notice in the Game.
18) Contact and Third-Party Policy Links
For privacy questions or requests, contact:
• Developer/Publisher: Gikeon
• Email: gikeon.support@gmail.com
• Country/Region: India
Third-party policies:
• Google Privacy Policy: https://policies.google.com/privacy
• Google Play terms: https://play.google.com/about/play-terms/
• Google Play Games Services data disclosure: https://developer.android.com/games/pgs/data-collection
• Google Play Games Saved Games: https://developer.android.com/games/pgs/savedgames
• Google Play Billing: https://developer.android.com/google/play/billing
• Google Play In-App Review: https://developer.android.com/guide/playcore/in-app-review
• Google Play In-App Update: https://developer.android.com/guide/playcore/in-app-updates
• Google AdMob data disclosure: https://developers.google.com/admob/android/privacy/play-data-disclosure
• Google AdMob mediation and partner controls: https://support.google.com/admob/answer/9012903
• Google advertising technologies: https://policies.google.com/technologies/ads
• Firebase privacy and security: https://firebase.google.com/support/privacy
• Firebase Android Play data disclosure: https://firebase.google.com/docs/android/play-data-disclosure
• Firebase Crashlytics data collection: https://firebase.google.com/docs/crashlytics/data-collection
• How Google uses data from apps that use its services: https://policies.google.com/technologies/partner-sites
• GameAnalytics privacy policy: https://gameanalytics.com/privacy
• GameAnalytics data retention practices: https://docs.gameanalytics.com/event-tracking-and-integrations/data-retention-and-limits/data-retention-practices/
• AppLovin privacy policy (including MAX): https://legal.applovin.com/privacy/
• Chartboost / LoopMe privacy notice: https://docs.chartboost.com/en/legal/privacy-policy/
• InMobi privacy policy: https://advertising.inmobi.com/privacy-policy
• Mintegral privacy policy: https://www.mintegral.com/en/privacy
• Moloco Ads Services privacy notice: https://www.moloco.com/terms-and-policies/advertising-policy
• Pangle end-user data privacy policy: https://www.pangleglobal.com/en/privacy/enduser-en
• Unity game player and app user privacy policy: https://unity.com/legal/game-player-and-app-user-privacy-policy
• Liftoff Monetize / Vungle privacy policy: https://liftoff.io/privacy-policy/
The links above are the current public policy pages checked on 2026-09-11. Provider policies can change without an app update; the AdMob and MAX dashboards determine which active partners receive requests. Before publishing, the publisher must reconcile those dashboard partner lists with this Policy and the consent message shown to users.