Last updated: April 1, 2026
Fizz Bust stores game scores, gameplay settings, date of birth, age-lock timing, and ad audience settings locally on your device.
Fizz Bust itself does not send this locally stored information to our own servers.
Fizz Bust is intended for a mixed audience. We ask for a date of birth on first launch to determine the appropriate ad and privacy experience.
For eligible older users, the app may request ads from Google AdMob. When ads are requested or shown, the Google Mobile Ads SDK may automatically collect and share data such as IP address, app interactions, diagnostic information, and device or account identifiers for advertising, analytics, and fraud prevention.
For child users, or if the app cannot determine that the user is eligible for the older-user ad experience, the app uses a more limited advertising experience and does not request the standard ad flow used for older users.
Any data collected by Google AdMob is handled according to Google's policies and transmitted using encrypted connections.
Fizz Bust does not currently use a standalone third-party gameplay analytics SDK.
Fizz Bust is offered to a mixed audience. Date of birth information entered in the app is stored locally on the device and used to determine the applicable ad and privacy experience.
The app may reevaluate the stored date of birth over time so that the user's ad experience can change automatically when they age into a different audience group.
Locally stored game data remains on the device until the user clears app storage or uninstalls the app. On some Android devices, local app data may also be restored by the operating system if backup and restore features are enabled.
Ad-related data collected by Google AdMob is retained and handled by Google under Google's own policies.
For questions email: sujay123sunny@gmail.com