BeltFactory Back to website

Legal

Privacy Policy

Effective date: September 29, 2026

This Privacy Policy explains how BeltFactory ("BeltFactory", "we", "us", or "our") handles information when you use the BeltFactory mobile game (the "Game"), visit belt-factory.web.app (the "Website"), make a purchase, or contact support.

The developer responsible for the Game and Website, and the controller of the personal information described in this policy, is Daniel Roke, established in Belarus, operating under the BeltFactory name. Contact: beltfactory.support@gmail.com.

1. Summary

  • The Game does not require an account and does not contain advertising.
  • Game progress, blueprints, settings, and a local copy of purchase entitlement information are stored on your device. Our server also keeps purchase verification records.
  • We use Google Firebase services for analytics, crash diagnostics, purchase verification, and small read-only catalog downloads.
  • We do not sell personal information or use Game data for cross-app advertising.
  • The Website does not use analytics SDKs, advertising cookies, contact forms, or tracking pixels.

2. Information handled by the Game

Gameplay and analytics data. Google Analytics for Firebase receives automatically collected app-use and device information as well as events that we send to understand progression, retention, feature use, menus, settings, paywalls, and purchases. These events can include level starts and completions, tutorial actions, restarts, second app openings, menu and feature selections, setting changes, paywall views, checkout attempts, purchases, restores, refunds, purchase errors, app version, build number, platform, selected language, current level, premium status, completion time, and incorrect deliveries.

Analytics assigns an app-instance identifier to distinguish installations and calculate usage metrics. It also derives approximate location, such as country or city, from the device's IP address. This is not GPS or precise location. Firebase services use installation and session identifiers for their operation and diagnostic metrics. These identifiers are not linked by us to a player account or email address. Collection of the Android advertising ID and advertising personalization signals is disabled in the Android Game.

We do not send factory blueprints, saved factory state, text entered by the player, contacts, precise location, or store transaction identifiers to Analytics.

Crash and diagnostic data. Firebase Crashlytics receives crash traces, non-fatal error reports, installation identifiers, app and operating-system versions, device model and architecture, available memory and storage information, and technical details needed to diagnose a failure. Firebase states that Crashlytics keeps crash traces and associated identifiers for 90 days before beginning removal from live and backup systems.

Purchase verification. The Game sends the store-signed transaction or purchase token, product identifier, app identifier, version, build, and platform to a Firebase callable function. The function verifies the entitlement with Apple or Google before the Game unlocks paid levels. Store transaction data is not sent to Analytics.

Our server stores purchase verification and store notification records in Cloud Firestore. These include a hashed purchase identifier, platform, product and app identifiers, store environment, entitlement and acknowledgement status, verification timestamps, and notification event types and timestamps. Purchase and notification identifiers are hashed before being written to these records; the raw transaction identifier or purchase token is not stored in the purchase ledger. Hashing does not make these records anonymous. We use them to maintain and restore the full-game entitlement, process refunds and revocations, avoid duplicate notifications, prevent fraud, and resolve purchase problems. Requests to our supporting services also expose technical connection information, including the caller's IP address, to Google infrastructure.

Storage downloads. The Game can download small, read-only JSON files from Cloud Storage for App Store price information. The Game does not upload your save, blueprints, or personal content to Cloud Storage.

3. Website information

The Website is hosted on Firebase Hosting. Firebase may process IP addresses, request timestamps, user-agent information, requested URLs, and related technical data to deliver the Website, prevent abuse, and provide hosting usage metrics. Firebase states that Hosting retains IP data for a few months.

The Website does not set cookies. If you choose a language, the preference is stored only in your browser's local storage so the Website can use that language on your next visit.

4. Purchases

Purchases are offered as a one-time, non-consumable full-game unlock and are processed by Apple App Store or Google Play. Apple or Google handles your payment method, billing details, receipts, refunds, and store account. We receive the signed transaction or purchase token and entitlement status required to securely unlock, restore, or revoke the purchase. Their respective privacy policies govern information they process.

5. Support communications

If you email us, we receive your email address, message, and any information or attachments you choose to provide. We use this information to answer your request, diagnose problems, protect the service, and comply with legal obligations. Support correspondence is retained only as long as reasonably necessary for those purposes.

6. How we use information

  • Operate, maintain, and improve the Game and Website.
  • Understand progression, balance, stability, and feature usage.
  • Diagnose crashes and technical errors.
  • Provide price information.
  • Process and restore purchase entitlements.
  • Respond to support and legal requests.

Legal grounds. Where the GDPR applies, we rely on performance of a contract, or steps you request before a contract, for providing purchased access, verifying and restoring purchases, and handling related support. We rely on legitimate interests in operating a secure service, preventing fraud, diagnosing technical failures, and understanding and improving Game usage, where applicable law permits this and those interests are not overridden by your rights and interests. Where we must keep or disclose information to meet a legal obligation, that obligation is the basis for the processing. You may object to processing based on legitimate interests as explained in section 11. This policy provides information about processing and does not itself obtain your consent or override any consent requirement under applicable law.

7. Service providers and international processing

We use Google LLC and its Firebase, Google Analytics, Cloud Storage, Hosting, and related infrastructure services. Apple and Google act as independent store providers for purchases and distribution. These providers may process information in countries other than your own and use safeguards described in their terms and privacy documentation.

More information is available in Firebase Privacy and Security, the Google Privacy Policy, and the Apple Privacy Policy.

8. Retention and deletion

  • Local data. Progress, blueprints, settings, and cached entitlements remain on your device until you remove the relevant data. Restarting the Game resets gameplay progress; clearing application data or uninstalling removes the app's local data, subject to any device or store backups. These actions do not automatically delete records already held by Firebase or our server, or cancel a store purchase.
  • Analytics. Our Google Analytics property is configured to retain event-level data for 2 months and user-level data for 14 months. Reset on new user activity is enabled: a new event from an installation restarts the retention period for its user identifier. Google automatically deletes expired data during its monthly deletion process. Standard aggregated reports are not subject to the same user-level and event-level retention controls. See Google Analytics data retention.
  • Crash reports. Firebase Crashlytics retains crash traces and associated identifiers for 90 days before beginning removal from live and backup systems.
  • Firebase installations. Installation identifiers are managed by Firebase. Deleting an installation starts removal from the Firebase services that use it, according to each service's retention rules. Google documents that deletion can take up to 180 days for applicable services and may generate a new identifier if the app continues using those services. See Firebase installation management.
  • Purchase records. Our purchase ledger currently has no automatic expiry. We retain entitlement and verification records while needed to provide and restore a valid full-game purchase, handle refunds or revocations, prevent fraud, and resolve disputes or meet applicable legal obligations. Removing local Game data does not remove this ledger. When a record is no longer needed for these purposes, it can be deleted following a verified request unless retention is legally required.
  • Website and support. Firebase Hosting retains IP data for a few months under Google's service policies. Support correspondence is kept while needed to handle the request and any related dispute or legal obligation.

The Game has no player account to delete. We do not attach your email address to analytics or crash identifiers, so an email address alone may not let us locate a specific Firebase record. We explain any identification or retention limits when responding to a request. See section 11 for how to contact us about data rights.

9. Children

BeltFactory is intended for a general audience and is not directed to children under 13. We do not knowingly collect personal information directly from children under 13. If you believe a child has provided personal information through support email, contact us so we can investigate and delete it where appropriate.

10. Security

We use reasonable technical and organizational measures appropriate to the information handled. Firebase encrypts supported service data in transit and encrypts many service datasets at rest. No storage or transmission method can be guaranteed completely secure.

11. Your choices and rights

Depending on where you live, you may have rights to request access, correction, deletion, portability, restriction, or objection regarding personal information, or to complain to a data-protection authority. These rights apply even though the Game has no player accounts.

To make a privacy or data-rights request, email beltfactory.support@gmail.com, explain what you are requesting, and identify the information concerned. For purchase records, tell us which store you used and the relevant order reference if you have it. Never send a store password, payment-card details, or an authentication code. We may ask for only the additional information reasonably needed to locate the record and verify your request.

Where deletion applies, we delete identifiable support or server records that we can locate and ask the relevant service provider to act where applicable. We may retain information necessary for a valid purchase entitlement, fraud prevention, disputes, or legal requirements where the law permits or requires this, and we explain any applicable limitation. We respond within the time required by the law applicable to your request; where the GDPR applies, this is normally within one month, with any lawful extension explained to you. The current Game collects analytics and crash diagnostics automatically and has no in-game collection switch; contacting support does not itself disable collection by an installed copy of the Game.

12. Changes to this policy

We may update this Privacy Policy when the Game, Website, providers, or legal requirements change. The effective date at the top will be updated when material changes are published.

13. Contact

Controller: Daniel Roke, Belarus, operating under the BeltFactory name. Privacy questions and requests can be sent to beltfactory.support@gmail.com.