Timber Pin

Huawei Android — release candidate and test builds

The Huawei Android release candidate 0.8.7 (26) uses com.pantevia.games.timberpin.huawei. It is not yet a confirmed public AppGallery release. The separate consent test app uses com.pantevia.games.timberpin.huawei.consentpreview. Both are separate from the Google Play edition. This section describes the configuration updated on 4 October 2026. A HarmonyOS NEXT edition has not been implemented.

The Huawei edition uses Huawei Ads Kit 13.4.91.301 and Huawei Ads Consent SDK 3.4.91.301, not Google Mobile Ads or Google UMP. The release candidate contains production banner and rewarded advertising identifiers; test builds retain Huawei test identifiers. Production identifiers do not guarantee ad availability or platform approval. Completing the rewarded ad can provide one continuation after a collision; it does not promise a period of ad-free play. Both test and live advertising involve provider network communication.

Advertising is restricted to a current local adult age selection (18 or older). No advertising requests are made for children, teenagers, or an unknown age group. On the age screen, adults can choose an optional advertising-permission checkbox. Details and provider privacy links are available before choosing. This single permission covers contacting Huawei for current provider information and non-personalised advertising processing; there is no second advertising-permission screen after Continue. Leaving the checkbox unchecked allows play without advertising.

After permission, the Consent SDK queries Huawei. The returned provider names and privacy-policy links must match the complete provider disclosure bundled with the app before ads can load. A mismatch, error, invalid response or timeout keeps advertising off without preventing play. Provider responses can vary by region, so advertising may remain unavailable where the list differs; this does not silently extend permission to new providers. The choice is remembered locally for up to 90 days. A remembered allowance includes querying provider information on later launches, with the same matching check. Expiry, changed disclosure text or language, changed providers, or a new age selection can require another choice. Old session-only test permissions are not reused.

The configuration requests non-personalised advertising, sets Huawei content classification W, and disables SDK location requests. These settings do not mean that advertising is anonymous or that no technical information is processed. Review the provider information and privacy links shown before consenting. The Google-specific SDK, UMP and advertising age-treatment descriptions below apply to the Google edition, not the Huawei edition.

Starting with build 26, the app explicitly disables optional Wi-Fi and Bluetooth information collection through Huawei’s InformationController before initialising Ads Kit. The APK also excludes Wi-Fi-state, nearby-Wi-Fi, Bluetooth-access and location permissions. Earlier builds, including build 25, did not apply these explicit Wi-Fi/Bluetooth controls. This restriction concerns the app’s SDK configuration; it does not disable the device’s network connection or independently govern Huawei services used outside this app.

When advertising is allowed, Huawei and applicable advertising providers may still process advertising/device identifiers such as OAID and ODID, IP address and IP-derived approximate city or country, device model, operating system, display resolution, language, storage/device status, network type and carrier, basic app information, app settings and usage, and ad impressions, clicks and touch positions. These data support ad delivery, performance measurement and attribution, fraud prevention, and service operation. We do not claim that disabling personalisation or optional radio collection disables these processing activities.

Advertising data are processed by providers, not just stored locally by the game. Huawei’s advertising statement describes disclosure of identifiers, app/device/network information and ad events to advertisers for measurement and attribution, and international processing that depends on the user’s region and service arrangements. See Huawei’s advertising privacy statement and the provider-specific links in the app’s Details screen. Local game progress and local consent audit records are distinct from this provider processing. Regional provider terms, diagnostic processing and store declarations remain subject to release review.

Huawei AppGallery store processing is separate from in-app advertising and local game progress. Clearing this app’s storage or uninstalling it removes its local data, but does not delete information already processed by Huawei or other providers. Use the relevant provider’s privacy controls for those requests. See the data deletion page for requests concerning correspondence held by Pantevia Games.

The Huawei release candidate also keeps local records of advertising choices: the time, a random consent-session reference, app version, language, whether the age selection is currently adult, displayed permission text, provider privacy links, and the requested advertising settings. These records do not contain a date of birth, account identifier or advertising identifier. They are stored in private application storage excluded from backup and are not automatically sent to Pantevia Games. They are evidence of a past choice, not permission to enable advertising on a later launch. A sudden process termination may prevent a session-end record from being written.

Record-management builds provide a Delete consent records action in Settings → Privacy Options. This stops new ad requests and removes local consent records without deleting game progress; deleting records does not grant fresh consent. Earlier test builds can remove them by clearing application storage or uninstalling the app, which also removes other local app data. The 90-day retention update deletes local consent records aged 90 days or more when the app opens or resumes and before a new consent event is saved, using the device clock and record file timestamp. It does not run while the app is closed; clock changes or deletion errors may delay cleanup, which is retried on the next opening or event. Earlier builds do not expire records automatically. This is our chosen technical retention period, not a claim about a legally mandated duration. Any mechanism for providing evidence in response to a provider request remains under review before production; local-only records do not by themselves establish that all provider evidence requirements are met.

The release candidate enables the production advertising configuration, subject to the age and consent gates above. Opening Settings → Privacy Options stops advertising and records a refusal; changing the choice requires a new permission flow. Delete consent records also clears the remembered choice without deleting game progress. The remembered choice is stored separately in private, non-backed-up storage with its original decision time and disclosure/provider fingerprints; ordinary launches do not extend its 90-day lifetime. Store declarations, final device testing and provider evidence handling remain release checks. This description is not a claim of store approval or legal compliance.

Android and iOS — current scope

This policy also covers Timber Pin for iPhone and iPad, including the iPad compatibility version on supported Apple Silicon Macs. The iOS Bundle ID is com.pantevia.games.timberpin. Version 1.0, build 14 is uploaded to App Store Connect for TestFlight; it is not yet a public App Store release. The current local Android release configuration is version 0.8.1, version code 11; this does not independently confirm its store rollout.

The Android-specific details below do not describe Apple permissions. The shared descriptions of local progress, age groups, no player account, no cloud save, and optional banner/rewarded advertising also apply to iOS. The iOS details in this section supplement the Android disclosure.

The iOS build uses Google Mobile Ads 13.10.0 and Google UMP 3.1.0. Release build 14 contains production iOS advertising identifiers; Debug builds retain Google demo identifiers. Production identifiers do not guarantee ad availability or AdMob approval. Personalisation and the publisher first-party ID are disabled in the iOS request configuration, and the maximum ad content rating is G for all age groups. Adult consent choices are requested through UMP where required; Settings provides privacy options when UMP requires them.

Google’s iOS SDK may process IP-derived approximate location, device identifiers, ad interactions, crash diagnostics and performance data. Some performance data can be associated with a user; disabling personalised ads does not make all SDK data anonymous. The iOS app does not request precise-location permission or call Apple’s tracking-authorisation prompt. Android AD_ID permission removal is not an iOS control. UMP choices are separate from Apple’s tracking permission.

Google iOS SDK data disclosure · Google iOS UMP documentation

Apple independently processes App Store and TestFlight account, installation, diagnostic and voluntarily submitted feedback information under its policies. This is separate from the game’s local save data and Google advertising processing. TestFlight feedback submitted to the developer may include screenshots, comments and diagnostic information.

Apple privacy information

1. What does this disclosure cover?

This page supplements the main Pantevia Games privacy policy for Timber Pin. If there is a conflict, this application-specific disclosure takes precedence for Timber Pin’s data practices. It describes the documented Android and iOS configurations and separates data kept on the device from information processed by Google and Apple services.

2. Application and core purpose

Timber Pin is a timing and reflex game. Its Android package name and iOS Bundle ID are com.pantevia.games.timberpin. Platform-specific release information is listed above.

The game does not include a Pantevia Games account, Google Play Games sign-in, an online profile, cloud save, Firebase Analytics, Firebase Crashlytics, notifications, in-app purchases, or virtual currency. The Terms of Use and Privacy Policy are available in Settings. The game does not require or retain a separate mandatory legal-acceptance record.

3. On-device game and age data

Game progress, high scores, settings, selected language, and accessibility preferences are stored locally on the device. Pantevia Games does not receive these data from the game.

The game does not retain the exact age or date of birth entered on the neutral age screen. It stores only the resulting age_group and the local verification time age_verified_at. Age is requested again after approximately 365 days. These local values are used to apply the advertising safeguards described below and are not sent to Pantevia Games.

4. Advertising and privacy choices

The documented Android build uses Google Mobile Ads SDK 25.4.0 and Google User Messaging Platform (UMP) SDK 4.0.0. The available advertising formats are an adaptive banner and a completely optional rewarded ad. This build does not include interstitial, App Open, or rewarded interstitial ads.

According to Google’s disclosure, Google Mobile Ads may process IP address and approximate location, application and advertising interactions, diagnostic and performance information, and—depending on permissions and device settings—device or other identifiers. The application manifest removes the Android AD_ID and Privacy Sandbox advertising-ID permissions. Actual data availability still depends on Google’s SDK behaviour, the device, permissions, and configuration. Non-personalised advertising does not mean that no technical data is processed. See Google’s Android SDK data disclosure and Google Privacy Policy.

Age selection is completed before advertising services start. UMP advertising choices are handled separately after age selection and only in the eligible adult flow where they are required for the user’s region. Android’s advertising controls and Google’s privacy controls are separate from the game’s local age selection. See Google’s UMP guidance.

The debug build and the current Google Play closed-test release use Google’s official demo banner and rewarded-ad unit identifiers. The AdMob application identifier is the real application identifier. A future public production release will use Pantevia Games production ad-unit identifiers after the final advertising configuration is completed.

5. Age groups and advertising safety

Timber Pin is a mixed/general-audience game suitable for children, teenagers, and adults. It is not primarily directed to children; however, because children are part of the intended audience, the game applies a neutral age screen and Google Play Families safeguards.

The local age-treatment groups are CHILD for ages 1–12, YOUNG_TEEN for ages 13–15, OLDER_TEEN for ages 16–17, and ADULT for ages 18–100. Missing or invalid age information results in the safe UNKNOWN state. Mobile Ads and UMP are not started while the age state remains UNKNOWN. As an additional defensive safeguard, any UNKNOWN state that reaches the advertising policy layer is assigned the same child-safe configuration as CHILD: child-directed treatment, G-rated content, and disabled personalisation.

All valid age groups use a G content rating and a non-personalised advertising approach. CHILD receives child-safe treatment. Both teen groups receive teen-safe treatment. The adult flow uses UMP only in regions where it is required. The UMP choice is not treated as age verification, and the age screen is not treated as advertising consent.

6. Sharing, support, and distribution

Pantevia Games does not receive or share the player’s locally stored game progress, scores, settings, language, accessibility preferences, age_group, or age_verified_at through the game. Google may process the advertising and consent-related technical information described above to deliver and measure advertising, prevent fraud, diagnose performance, and provide applicable regional privacy choices. This processing is governed separately by Google’s policies and may occur outside Türkiye.

Google Play independently processes store account, download, security, and diagnostic information under Google’s policies. The game does not provide a separate player account or support-ticket database. If you contact support or privacy by email, the message and any attachments you choose to send are separate from the device-local game data and Google advertising data; the main Pantevia Games Privacy Policy explains how correspondence is handled.

7. Deletion and contact

On iPhone or iPad, use Delete App to remove the app and its local data; Offload App retains documents and data. Device backups are controlled separately by the operating system and may restore local data. Deleting the app does not delete your Apple account, TestFlight feedback or information already processed by advertising providers.

Device-local game and age data can be removed by clearing the application’s storage or uninstalling Timber Pin. This does not delete advertising data that Google may already have processed; Google-held data and choices remain subject to Google’s own controls, retention practices, and request channels.

For information about deleting data or correspondence held by Pantevia Games, visit the data deletion page. Support: support@panteviagames.com. Privacy contact: privacy@panteviagames.com.

8. Technical disclosure review

The Android disclosure was reviewed on 26 September 2026; the iOS configuration and platform-specific additions were reviewed on 1 October 2026. This description must be reviewed again before changes to SDKs, advertising, accounts, cloud services, analytics, purchases, age handling or data practices. It describes the documented configuration and does not independently establish legal compliance.