Privacy Policy

Bubbly Bakes · Crazy Games Developer · Version 2 (game version 1.2.0) · Last updated: 1 November 2026

In short: no account and no purchases. The game shows ads from Google AdMob. To show and measure them, Google may use your device's advertising ID, an approximate location worked out from your IP address, information about your device and how you interact with the ads. Where the law requires it (for example in the EEA, the UK, Switzerland and some US states), Google's consent form asks you first, and you can change your choice later in Settings → Ad privacy. Separately, if you agree on the game's privacy screen, the game sends crash reports and play statistics to Google Firebase, without your advertising ID; if you choose "No thanks", it sends none. Everything below is the detail behind that.

1. We do not ask who you are

The game has no account, no sign-in and no profile. We never ask for your name, email address, phone number, photos, contacts or location, and the game does not ask for the location permission. There is nothing to log into and nothing to fill in.

2. Your progress stays on your device

Your current level, your coins, boosters, Recipe Book tickets, cards and golden shards, the café look you chose, your daily gift progress (which day comes next, the date of your last claim and the latest time the game has seen, used so that a gift cannot be claimed twice), and your settings (sound, music, vibration and language) are written to local storage on your own device. They are not uploaded, we cannot read them, and we hold no copy. Uninstalling the game deletes them.

3. Crash reports and play statistics (only if you agree)

When the game first starts, and again whenever this policy changes what is collected (as it does with this version), it shows a privacy screen. Nothing below is sent before you answer it, and nothing at all if you choose "No thanks". If you choose "Accept", the game uses two Google Firebase services:

• Firebase Crashlytics (crash reports): when the game crashes or hits an error, a report with the error and its stack trace, the device model, the Android version, free memory and disk, screen orientation, the game version, and a random installation identifier.
• Google Analytics for Firebase (play statistics): which levels you start and finish (level number, difficulty, attempt number, win or loss, how far you got, time spent, number of taps, revives used), restarting a level, using a Hint or a Refresh, unlocking a shelf and reviving (and whether coins or an ad paid for it), which pop-up windows you close and how long they were open, the game noticing and recovering from a stuck screen, opening the Home screen, opening a Recipe Book box (with a ticket, coins or golden shards, and whether the card was new), completing a card series, claiming the daily gift, and the highest level you have reached; plus what Firebase records by itself: the first launch, sessions and their length, app updates, the device model, Android version, language, country (derived from the IP address, which is not stored), the game version and a random app instance identifier.
• Ad events in the statistics: because the game contains Google's ads software (section 4), Google Analytics for Firebase also records by itself, for players who accepted, when an ad is requested, when an ad is on screen or counted as seen, when an ad is tapped and when a rewarded ad grants its reward (events named ad_query, ad_exposure, ad_impression, ad_click and ad_reward). They are tied to the same random app instance identifier, never to your advertising ID, and we use them only to see how ads affect play.

No advertising ID in Firebase: the game tells Firebase not to collect the advertising ID and never to use this data for advertising or ad personalisation; Google signals and data sharing with other Google products are switched off, and our Firebase project is not linked to our AdMob account. We do not collect your name, email, contacts, photos or precise location. We do not use this data for advertising, we do not sell it and we do not share it with anyone: Google processes it for us as our service provider, under the Firebase data processing terms and the Google Privacy Policy. It is sent encrypted (HTTPS) and may be processed in the United States and other countries where Google operates.

How long: play statistics are kept for 14 months, crash reports for 90 days, then deleted.

Changing your mind: Settings → Privacy Policy → "Stop sharing" (or "Share data"). Stopping turns statistics off at once and crash reports off from the next start of the game. This choice does not change the ads (section 4), and your ad choices do not change it.

After you have agreed, the game also asks Google Firebase Remote Config for a few settings: when to ask you to update, and how often ads may appear (for example the level from which ads between levels start and the minimum time between them). That request carries the random installation identifier, the game version and the basic details Remote Config uses to pick settings (country, language, time zone, Android version), nothing else. If you chose "No thanks", the game uses the settings built into it.

4. Advertising (Google AdMob)

Bubbly Bakes is free to play and is paid for by ads. The ads are provided by Google AdMob, a service of Google. We do not use any other ad network in this version.

Where ads appear

• Rewarded ads, only when you choose them: a button that says what you get (a revive, a locked shelf, a free booster or a bigger win reward). If you do not tap it, no rewarded ad plays.
• Ads between levels (interstitials), from level 5: after a level ends and before the next one starts, never during play, not in the first minutes of a session, and with a minimum time between them.
• A banner at the bottom of the screen during play, from level 5, on screens tall enough to fit it without covering the game.
• A box ad (medium rectangle) on the win screen, from level 5.

No ad is requested before you have answered the game's privacy screen and, where it applies, Google's consent form. We ask Google to show only ads suitable for a teen and adult audience (content rated PG or lower). The game can be played offline; ads simply do not appear without a connection.

What Google's ads software may collect

To choose, show and measure ads, limit how often you see the same ad, and prevent fraud and abuse, the Google Mobile Ads software in the game sends Google, directly from your device:

• your device's advertising ID (a resettable identifier provided by Google Play services) and the app set ID;
• your IP address, which may be used to estimate your general location (such as your city or region, never your precise location);
• device and app information, such as the device model, Android version, language, screen size, network type, and the game's name and version;
• ad interactions and app activity: ads requested, shown, tapped or watched to the end, app launches and taps;
• diagnostic information about the performance of the game and of the ads software (for example app launch time and freezes).

Google receives this data itself and uses it under its own policies: see How Google uses information from sites or apps that use its services, How Google uses cookies and other technologies in advertising and the Google Privacy Policy. Because Google may also use it for its own purposes, this counts as sharing data with a third party, and our Google Play "Data safety" section says so. It is sent encrypted. Where Google's consent form is shown, it also lists the other ad technology providers Google works with. We do not receive your advertising ID or any of this data about you: AdMob only gives us totals (for example how many ads were shown in a country and what they earned).

Personalised and non-personalised ads

• Personalised ads may use your advertising ID and information about your activity in this and other apps and websites to choose ads that may interest you.
• Non-personalised ads are chosen from general information such as this game, the time and your approximate location. Google still uses data such as your IP address and, when available, the advertising ID to measure ads, limit how often you see them and prevent fraud.
• In the EEA, the UK and Switzerland, Google's consent form (shown after the game's privacy screen) asks whether Google and its partners may store or access information on your device and use your data for personalised ads. If you do not agree, you may see non-personalised or limited ads, or none.
• In US states with privacy laws (such as California), letting Google use your data for targeted advertising may count as "selling" or "sharing" personal information. Where Google's message applies to you, you can opt out of it in Settings → Ad privacy.
• Elsewhere, ads may be personalised unless you delete or reset your advertising ID, or opt out of ads personalisation, in your device settings (below).

Your ad choices

• In the game: Settings → Ad privacy reopens Google's form so you can review or change your choices. This option appears where Google's form applies to you.
• On your device: Android Settings → Privacy → Ads (on some devices Settings → Google → Ads, or Settings → Security & privacy → More privacy settings → Ads). There you can delete your advertising ID (apps then receive only zeros instead of an ID) or reset it to a new one; older Android versions offer "Opt out of Ads Personalization".
• With Google: My Ad Center controls the ads Google shows you when you are signed in to a Google Account.

These choices change how ads are chosen, not whether ads appear: this version has no option to remove ads. Ads and statistics are separate: declining statistics does not turn ads off, and your ad choices do not turn statistics on or off. How long Google keeps advertising data is described in How Google retains data it collects.

5. Rating the game and updates on Google Play

After you have played for a while, the game may ask Google Play to show its standard "rate this app" card. That card is displayed and handled entirely by Google Play: we do not see whether it was shown, whether you rated, or what you wrote. A rating or review you choose to post is public on Google Play and is covered by the Google Privacy Policy.

When the game starts, it asks Google Play whether a newer version of Bubbly Bakes is available, and Google Play may download and install it for you. Google Play answers this from the information it already has about your device and the installed version; the game sends nothing of its own, and we do not receive any of it. This is covered by the Google Play Terms of Service and the Google Privacy Policy.

6. Opening this page, and tapping an ad

If you tap the Privacy Policy link inside the game, your device opens this website in your browser. This site is hosted on GitHub Pages, so GitHub's servers receive that request, including your IP address, the same way any website visit works. That is a visit to a web page, not data the game sends. GitHub's handling of it is covered by the GitHub Privacy Statement. If you tap an ad, the advertiser's website or store page opens, and it has its own privacy practices.

7. No in-app purchases

There are no purchases, subscriptions or paid currency in this version. Coins, boosters, tickets and golden shards are earned by playing (some by choosing to watch a rewarded ad); Recipe Book boxes are opened only with them and cannot be bought with money. No payment data exists and none is processed.

8. Children

The game is not directed to children under 13, and the game tells Google that its ad requests are not for a child-directed audience. We do not knowingly collect data from children; if you believe a child has sent us crash reports or statistics, write to us and we will delete them. You can also delete or reset the advertising ID on the child's device as described in section 4.

9. Your rights

Laws such as the GDPR (EU/UK), the LGPD (Brazil) and US state privacy laws such as the CCPA (California) give you the right to see, correct or delete data a company holds about you, and to opt out of targeted advertising. We hold no name or contact data; the statistics and crash reports are tied only to the random identifiers above:

• To stop sharing statistics and crash reports: Settings → Privacy Policy → "Stop sharing".
• To delete what was sent to Firebase: write to the address in section 12. We delete the statistics and crash reports of your installation with Firebase's deletion tools; if we cannot find them from what you send us, we tell you.
• For advertising data: we do not hold it and cannot look it up. Use Settings → Ad privacy, delete or reset your advertising ID (section 4), or the tools described in the Google Privacy Policy.
• To delete your progress: uninstall the game, or clear its storage in your device settings.
• You may also complain to your local data protection authority.

We do not charge for any request and we do not treat you differently for making one.

10. Security

We collect as little as the purposes above need. Statistics and crash reports are sent only after your answer; ads are requested only after the game's privacy screen and, where it applies, Google's consent form; everything is sent encrypted. Access to the Firebase project and the AdMob account is limited to the developer's accounts.

11. Changes

If a future update changes what is collected, or adds purchases, this page will be updated first to describe exactly what is collected and by whom, the date and version at the top will change, the Google Play "Data safety" section will be updated to match, and the game will show its privacy screen again. The policy changes before the release does.

What changed in version 2 (game version 1.2.0): the game now shows ads from Google AdMob, which may use the advertising ID (section 4); the statistics now include ad events and the new Home, Recipe Book and daily gift events (section 3); Remote Config also sets how often ads may appear; the progress kept on your device now includes the Recipe Book and the daily gift (section 2). Version 1 was dated 27 October 2026.

12. Contact

Crazy Games Developer — contact@crazygamesdeveloper.com