Privacy Policy

See also the Terms of Use.

Runehelm: Merge Defense is developed under the Batigames label and provided by:

• Batistudios s.r.o.
• Company ID (IČO): 21015066
• VAT ID (DIČ): CZ21015066
• Privacy and support contact: batistudios.com/contact

Please identify Runehelm and describe your request. Do not send passwords or full payment-card details.

This policy covers the Runehelm game. Websites you open, your app store and third-party services also have their own privacy notices.

Runehelm keeps a local profile with progress, selected heroes and chapters, upgrades, coins and gems, energy and recharge times, tutorial progress, audio/haptics/quality settings, purchase entitlements and processed transaction identifiers. It also records the versions of the Terms of Use and Privacy Policy you acknowledged and the device's acceptance timestamp.

The game uses a temporary save and a previous-save backup to recover from interrupted writes. Runehelm currently has no game account or publisher-operated cloud-save service. Device or operating-system backups may separately include app data according to your device settings.

These records let us provide gameplay, remember settings, prevent duplicate grants and record your agreement. They remain locally until replaced or removed. Losing or clearing app data can lose progress and consumable balances.

Runehelm creates a random installation identifier and session identifiers and records gameplay and diagnostic events. Events can contain the app version, platform, locale, timestamps, run seed, selected content, battle outcome, upgrades, purchases and ad outcomes. These identifiers are pseudonymous, not a guarantee of anonymity.

The current configuration has no publisher analytics delivery endpoint, remote-configuration endpoint or connected native crash-reporting provider. The game's own analytics therefore stay local. Release builds keep a bounded queue of up to 500 pending events; older events are replaced as the queue fills. Diagnostic event history and filtered error reports also exist in memory, and development builds may write diagnostic logs.

This describes Runehelm's own diagnostics, not the advertising SDK's separate data collection below. If we introduce remote analytics or crash reporting, we will update this notice with the recipient, purposes and retention and request any legally required separate choice before enabling that processing. Acknowledging this policy does not authorize future optional analytics or tracking.

An internet connection is required to verify time for energy and level access. After the entry gate, Runehelm periodically requests HTTPS time/connectivity responses, including during play and on resume. The current services are Google (www.google.com/generate_204) and Cloudflare (www.cloudflare.com/cdn-cgi/trace, used as a fallback).

Those providers receive your IP address and normal connection/request information, including a cache-busting query value. Runehelm uses the response time to validate energy and connectivity; it does not send your saved progression or payment-card details in these requests. Providers may keep their own service/security logs.

Mobile builds integrate Google AdMob and Google's User Messaging Platform (UMP). The game can offer optional rewarded ads and interstitial ads between eligible levels. Test ads can still involve network requests and SDK data processing.

Google's advertising SDK may collect and share IP addresses (which can indicate approximate location), device/account identifiers such as advertising ID and app set ID, interactions with ads and the app, and diagnostic/performance information. Uses include delivering and measuring advertising, analytics, security and fraud prevention. The exact processing depends on platform, region, SDK configuration and the choices available to you.

Where applicable, Google's consent form presents advertising purposes and providers. You can revisit available choices through Settings > Ad privacy when that entry is required by the provider. Device advertising controls may offer additional choices. Withdrawing consent affects future consent-based processing and does not undo lawful earlier processing.

Accepting the Terms or acknowledging this policy is separate from advertising consent. Refusing optional advertising consent does not itself lock Runehelm gameplay. Ads or ad rewards may be unavailable when an ad cannot be served; internet verification and normal energy rules still apply.

Google privacy information: https://policies.google.com/privacy
Google advertising partner information: https://policies.google.com/technologies/partner-sites

Where supported, the app store processes purchases and subscriptions using your store account and payment method. Runehelm receives product identifiers, purchase status and transaction/purchase identifiers needed to grant items, prevent duplicate rewards, restore eligible entitlements and check subscription status. It saves entitlement information and processed transaction identifiers locally. Runehelm does not receive your full payment-card number.

Google Play controls its account, billing, transaction retention and refund processing. Deleting Runehelm does not delete store transaction records or cancel a subscription. Manage subscriptions and store-held data in your store account.

If you contact Batistudios, we receive the contact information and message you provide, plus any diagnostic material you choose to send. We use it to answer your request, resolve faults or purchase issues, handle privacy requests and protect legal rights. Include only information needed for the issue.

We retain correspondence for as long as reasonably needed to resolve and follow up on the request, meet applicable legal duties and handle related claims; then we delete or anonymize it. Records subject to mandatory accounting or legal retention are kept for the applicable statutory period. Contact us for details about records relating to your request.

Where EU/EEA data-protection law applies, we rely on:

• Performance of our agreement for data necessary to provide requested game functions, purchases and support.
• Legitimate interests in reliable gameplay, local diagnostics, security and preventing duplicate grants or abuse, where these interests are not overridden by your rights.
• Legal obligations when handling records or requests that the law requires.
• Consent for optional advertising/tracking where required. Such consent is requested separately through the relevant controls.

Local storage necessary to operate the game is distinct from optional tracking. Agreeing to the Terms is not blanket consent to all personal-data processing.

Data may be received by the store, Google advertising/consent services, the connectivity providers described above, and providers that operate our support website when you contact us. We may disclose information where required by law or necessary to establish, exercise or defend legal claims. We do not operate a market for selling player profiles. Advertising data sharing may have a specific legal classification in your region; use the regional choices presented by the advertising provider.

Third-party providers may process information outside your country, including outside the EEA. Their notices explain locations and transfer safeguards. Where Batistudios arranges a restricted international transfer, it must use an applicable lawful mechanism, such as an adequacy decision or appropriate contractual safeguards; you can request information using our contact details.

Runehelm uses HTTPS for its configured network requests. Local saves are not end-to-end encrypted and are subject to your device's security. No system can promise absolute security.

You can read this policy and the Terms in Settings > Privacy & Terms without opening a website. Use Settings > Ad privacy for available advertising choices. On Android, clearing Runehelm's app storage removes its local saves and diagnostics; uninstalling normally removes local app data, although device backups may retain copies or restore them. Clearing data loses local progression and does not cancel subscriptions.

Depending on applicable law, you may request access, correction, erasure, restriction or portability of personal data, object to processing based on legitimate interests, and withdraw consent where processing relies on it. Contact Batistudios using section 1. We may need proportionate information to verify a request and locate the relevant records; we cannot retrieve local-only progress from our servers.

You may complain to your local data-protection authority. In the Czech Republic this is the Office for Personal Data Protection (ÚOOÚ): https://uoou.gov.cz
Store/provider-held records can also be managed through those providers. We do not use game records to make solely automated decisions with legal or similarly significant effects on you.

Follow the age rating and eligibility rules shown by your app store. Where a child cannot legally agree or provide required consent alone, a parent or guardian must be involved. Do not supply a child's personal information through support unnecessarily. If you believe a child's information has been handled improperly, contact us so we can investigate and take appropriate action. This notice does not itself verify age or parental consent.

The version and effective date identify this notice. Material changes will be communicated in the game; the entry screen asks for a new acknowledgment when the bundled policy version changes. Acknowledgment confirms that the notice has been presented and read; separate choices remain necessary for processing that requires consent.