Wood Tower: Balance Blocks is an offline, local party game intended for users aged 16 and older. It does not require an account and the developer does not receive player names. Before Google Mobile Ads or Firebase Analytics can collect data, the app asks for a date of birth and derives only a protected-or-adult category on the device. The date of birth itself is not stored or transmitted.
1. Information handled by the app
The app handles a limited amount of information needed to run the game and remember settings.
- Whether the first-run guide has been completed.
- Your sound and selected haptic settings.
- Only the derived age category: protected (under 18 or date not provided) or adult (18 or older).
- An advertising consent profile containing the derived age category and advertising privacy settings, used to check whether cached Google consent applies.
- Player display names and order entered for a local game or immediate rematch.
The date of birth is used only on the device to derive the category above and is then discarded. It is not saved in app storage, included in analytics, or sent to Google. This app does not require registration and does not ask for an email address, phone number, contacts, calendar, precise location, photos, microphone access, payment information, health information, or government identification.
2. Advertising and third-party data
The app uses the Google Mobile Ads SDK (AdMob). A fixed banner is placed in a dedicated area outside the game viewport, controls, and touch region. For completed party games, an interstitial may be requested after the 3.5-second collapse presentation and before the result is shown. Google and its advertising partners may automatically collect or share:
- IP address, which may be used to estimate a general location.
- App interactions, such as app launches, taps, and ad or video views.
- Diagnostic information, such as launch time, hang rate, and energy usage.
- Device or account identifiers, including the advertising ID, app set ID, and other applicable identifiers.
This information may be used for advertising or marketing, analytics, and fraud prevention, security, and compliance. The developer does not receive information that identifies a user account because the app has no account system.
For more information, see Google's Privacy Policy and Google Mobile Ads data disclosure.
3. Intended age range and advertising privacy settings
The app is intended for users aged 16 and older, including teenagers aged 16 or 17 and adults. It is not intended for users under 16. This intended audience does not mean every user is an adult. Before advertising or analytics collection is allowed, the app presents a neutral screen with empty year, month, and day fields. The screen does not prefill a date or suggest that an adult age is required. The app uses the date entered by the user to select privacy settings; it does not independently verify identity or age. The complete date is processed only on the device and immediately discarded; only the derived protected-or-adult category is stored and can be changed later.
- Users whose entered date indicates they are under 18, including those aged 16 or 17, and users who choose not to provide a date are treated as protected. Child-directed advertising treatment is enabled, the publisher disables personalization, and Firebase Analytics collection remains off.
- If no age category has been established, or the saved category is missing or invalid, advertising is not initialized and Firebase Analytics collection remains off until an age category is set.
- For adults, advertising and analytics privacy choices are evaluated through Google's User Messaging Platform and Consent Mode according to the applicable region.
- The maximum ad content rating is set to G for every age range.
These settings limit advertising treatment, but Google Mobile Ads may still process the data described above for permitted advertising, measurement, security, and compliance purposes.
4. Anonymous usage statistics
Firebase Analytics collection is off before the age category and applicable Google privacy choices have been evaluated. It remains off for protected users. For adults, collection is enabled only when Google's Consent Mode result permits analytics storage under the applicable regional message or configured default consent state. Changing from adult to protected disables collection and clears queued in-memory analytics events and local analytics state.
When collection is permitted, the app records a limited set of screens and game-flow events, such as game start and end, result actions, and whether an interstitial was attempted or dismissed. The app does not put the entered date of birth, derived age category, player names, a custom user ID, touch coordinates, or continuous physics values in analytics events. Google Mobile Ads may separately record its own automatic advertising events.
For more information, see Privacy and Security in Firebase and Google's Privacy Policy.
5. How information is used and shared
Local game and privacy settings are used only to operate the app and remain on the device. The developer does not sell personal information and does not share locally stored settings or session player names with third parties.
Data processed by Google Mobile Ads is shared with Google and applicable advertising service providers as described in their policies. Tapping an ad may open a third-party service governed by that service's own privacy policy.
For an adult whose applicable Consent Mode result permits analytics storage, the limited analytics data described above is processed by Google Firebase for product analytics.
6. Security
Local settings are stored within the app's private storage managed by Android. Data processed by Google SDKs is encrypted in transit according to Google's disclosures. No method of storage or transmission is completely secure.
7. Retention and deletion
- Player display names are kept only in memory for the current game or immediate rematch and are cleared when that session ends or the app process closes.
- Guide completion, sound, haptic, the derived protected-or-adult category, and the advertising consent profile remain on the device until they are changed or cleared by the app, you clear the app's storage, or you uninstall the app. The complete date of birth is never retained.
- The developer does not maintain a server-side account or gameplay database, so there is no developer-held account record to delete.
- Google and its service providers control retention and deletion of advertising data and analytics data collected when permitted under their own policies. Android advertising ID controls may be used to reset or delete the advertising ID.
8. Changes to this policy
This policy may be updated when the app's features, SDKs, advertising, or data practices change. The current version will remain available at the public URL shown above.
9. Contact
weimaraner.logan.choi@gmail.com