Last updated: August 17, 2026
Anvil Bastion is developed and published by BurningArktis.
Privacy and support contact: burningarktis@proton.me
Anvil Bastion is designed as an offline-first game. Gameplay progress and settings are stored locally on the user's device. Local data may include currencies, equipment, research levels, stage progress, optional advertising reward counters, settings, and timestamps used for offline or time-based gameplay systems.
The game does not require users to create an account for core gameplay.
Builds of Anvil Bastion that enable advertising may use Google AdMob / Google Mobile Ads to provide optional rewarded advertisements. A rewarded advertisement is initiated by the user. The game grants the associated gameplay reward only when the advertising SDK reports that the reward was earned. Closing or skipping an advertisement, a load failure, or a show failure does not by itself grant the gameplay reward.
When advertising is enabled, Google Mobile Ads may automatically collect and share information for advertising, analytics, and fraud-prevention purposes. According to Google's current Mobile Ads data-disclosure documentation, this may include:
Google states that data handled by the Mobile Ads SDK is encrypted in transit. Users may be able to reset or delete the Android advertising ID through Android settings, and advertising-ID transmission can also be limited by applicable SDK configuration and privacy controls.
Where required, Anvil Bastion uses Google's User Messaging Platform (UMP) to obtain or refresh consent information before requesting network advertisements. The app is designed to refresh the current consent status on app launch rather than treating a locally cached consent choice as the sole source of truth.
When UMP indicates that privacy options must be available, the app provides an in-app entry point that lets the user revisit applicable advertising privacy choices.
Advertising-related information may be processed by Google and advertising partners configured through Google AdMob. Their processing is governed by their own applicable terms and privacy policies. Google's privacy policy is available at policies.google.com/privacy.
The initial release does not require a separate user-account service, contact-list access, photo-library access, or precise-location feature for core gameplay. If future versions add new services or data practices, this policy will be updated before or together with the corresponding release.
Local game data remains on the device until it is deleted by the user, for example by clearing the app's storage or uninstalling the app. Because the initial release does not require a BurningArktis account for core gameplay, BurningArktis does not maintain a separate server-side gameplay account database to delete.
Information processed independently by Google or its advertising services is subject to Google's applicable retention, deletion, and privacy controls.
Local gameplay data is stored using the platform and application storage mechanisms available on the device. Advertising data transmitted by Google Mobile Ads is documented by Google as encrypted in transit using TLS. BurningArktis limits production advertising requests until the applicable privacy/consent state permits them.
BurningArktis maintains the app's target-audience declaration and advertising configuration through Google Play and Google AdMob. If a released version includes children in its declared target audience, the app and advertising configuration will be reviewed and configured to comply with the additional Google Play Families requirements applicable to that audience.
This policy may be updated when the game's online services, advertising configuration, SDK versions, data practices, or applicable legal requirements change. The updated page will show a revised “Last updated” date.
Questions about this Privacy Policy can be sent to burningarktis@proton.me.