Privacy Policy

Summary

Черемша: Завод без суеты (Cheremsha: No Rush Factory) is an Android casual game that can be played without an account.

Game progress is stored locally on your device. The developer does not operate accounts, cloud saves, or public social profiles.

The app may offer optional one-time creature and wardrobe cosmetic unlock purchases through Google Play Billing. Google Play processes the payment flow; the developer does not receive payment card details.

The app uses a limited developer-operated referral promo-code endpoint to register and redeem optional friend codes. The referral service is not an account system and does not store your local save file.

The current release includes optional rewarded ads through Google Mobile Ads SDK and Yandex Mobile Ads SDK. The active ad provider may vary by build or rollout configuration. Rewarded ads are shown only when you choose an ad reward action, such as doubling tickets after a shift or after an idle reward.

The current release uses Firebase Analytics for limited gameplay analytics and Firebase Crashlytics for crash diagnostics when Analytics and diagnostics are enabled in Settings.

The developer does not receive your name, email address, precise location, contacts, photos, microphone, camera, or local save file.

Local save data

The app stores game progress locally on your device, including tickets, cosmetics, settings, tutorial state, canteen progress, room progress, mini-game progress, purchased one-time product identifiers, and shift statistics.

Most local save data is not sent to the developer or to a developer-operated server.

Referral promo-code state is stored locally too, including your generated referral code, pending code entry, and reward receipts. When you use the referral feature, the app sends the promo code and a locally generated referral install identifier to the developer-operated referral endpoint so the code can be registered, limited to five uses, and redeemed once per install.

The in-app progress reset removes gameplay progress but keeps one-time purchase entitlement identifiers so purchased creatures and wardrobe cosmetics remain available. Clearing app data in Android settings or uninstalling the app removes the local entitlement cache from the device.

The app may show one local on-device reminder per day in the evening to invite you back to the game. Reminders can be disabled in the app Settings or in the Android notification settings.

Optional purchases

One-time creature and wardrobe cosmetic unlocks are optional. The game remains playable without buying them.

When you start a purchase, Google Play displays the final local price and handles the transaction. The app receives a Google Play purchase result so it can unlock the purchased creature or cosmetic and stores the product identifier locally as a non-consumable entitlement cache.

The Settings screen includes a restore purchases action, and the in-app progress reset keeps one-time purchase entitlements so purchased creatures and cosmetics stay unlocked.

The current client-only integration does not send Google Play purchase tokens to a developer-operated server. If server-side receipt verification is added later, this policy and the Play Console Data safety form must be updated before rollout.

Refunds, payment methods, receipts, and purchase management are handled by Google Play according to Google's terms and policies.

Referral promo codes

Referral promo codes are optional. You can play the game without opening or redeeming a referral code.

The referral endpoint stores HMAC hashes of the local referral install identifier and promo code, use counters, reward counters, timestamps, and app version. It does not store your name, email address, account, advertising ID, local save file, or precise location.

The readable promo code is processed in the request so the service can validate and redeem it, but the database is designed to store hashes rather than raw codes.

Cloudflare delivers the referral endpoint and may process technical request information such as IP address, user agent, request URL, request time, and security logs to deliver and protect the service.

Ads and third-party processing

The app uses Google Mobile Ads SDK and Yandex Mobile Ads SDK for optional rewarded ads. The active provider may vary by build or rollout configuration.

According to Google's SDK disclosure, Google Mobile Ads SDK may automatically collect and share IP address, user product interactions such as app launches, taps and video views, diagnostic information, and device or account identifiers such as the Android advertising ID and app set ID.

According to Yandex Mobile Ads SDK disclosure, the SDK transmits user data off-device, shares it with a third party for ad delivery, encrypts SDK data in transit over HTTPS/TLS, and may process device or other IDs such as the advertising ID when the permission is granted.

The app disables Yandex location tracking in SDK startup and does not request device location for Yandex ad targeting.

Google says its ad SDK data is used for advertising, analytics, and fraud prevention, and is encrypted in transit.

Google's privacy policy is available at https://policies.google.com/privacy.

Yandex's privacy policy is available at https://yandex.com/legal/confidential/.

Analytics and diagnostics

When Analytics and diagnostics are enabled in Settings, the app sends limited gameplay analytics events to Firebase Analytics, such as app opens, shift starts and completions, reward claims, settings changes, cosmetic actions, and coarse progress counters.

The app also uses Firebase Crashlytics for crash reports, non-fatal diagnostics, ANR diagnostics where available, app version, package name, build type, Firebase installation identifiers, and related technical diagnostics so stability issues can be fixed.

Analytics and diagnostics can be turned off in Settings. When turned off, the app disables Firebase Analytics and Crashlytics collection, resets local Firebase Analytics data, and deletes unsent Crashlytics reports.

The app does not send the player's name, account ID, advertising ID, precise location, local save file, or a custom persistent user ID to Firebase.

Data collected or shared

• Personal information such as name, email address, phone number, or user IDs created by the developer: not collected by the developer.
• Referral promo backend: HMAC-hashed local referral install identifiers and promo codes, use counters, reward counters, timestamps, and app version are processed by the developer-operated Cloudflare Worker when you use referral codes.
• Precise location: not collected by the developer.
• Approximate location: Google Mobile Ads SDK may derive approximate location from IP address.
• Contacts: not collected.
• Photos, audio, camera, and microphone: not collected.
• Local game progress and settings: processed locally on device.
• Purchase history: Google Play processes one-time purchases. The app stores purchased one-time product identifiers locally to keep creature and cosmetic entitlements available.
• Location data through Yandex Mobile Ads SDK: not enabled by the app.
• App interactions related to ads: may be collected and shared by Google Mobile Ads SDK.
• App interactions related to gameplay analytics: limited low-cardinality gameplay events may be sent to Firebase Analytics when enabled.
• Diagnostics related to the app and SDK: may be collected by Google Mobile Ads SDK and Firebase Crashlytics when enabled.
• Advertising ID, app set ID, and device identifiers: may be collected and shared by Google Mobile Ads SDK unless limited by device settings or platform controls. Yandex Mobile Ads SDK may process device or other IDs when the advertising ID permission is granted. Firebase may process app instance, installation, and crash reporting identifiers for analytics and diagnostics.

Advertising choices

Rewarded ads are optional gameplay choices. If you do not tap a rewarded ad button, you can continue playing without that ad reward.

Android and Google settings may let you reset or delete the advertising ID, limit ad personalization, or manage Google ad preferences.

For regions where consent is legally required for ads personalization or related storage, ad serving must follow the applicable ad provider consent requirements before broad rollout in those regions.

Third-party services

The public legal website and referral promo-code endpoint use Cloudflare. Cloudflare may process technical request information, such as IP address, user agent, request URL, request time, and security logs, to deliver and protect the website and endpoint.

Firebase Analytics is used for optional gameplay analytics. Firebase Crashlytics is used for optional crash diagnostics.

If the app is installed through Google Play, Google may process store, device, crash, and installation information according to Google's own policies.

If you buy an optional one-time product, Google Play processes the purchase according to Google's own policies.

If you view or complete a rewarded ad, Google, Yandex, and their ad partners may process ad-related information according to their policies and applicable law.

Children

The app is not directed to children. It is intended for teens and adults as a light casual game.

If the declared target audience or distribution strategy changes to include children, ad serving and data handling must be reconfigured before that launch to meet Google Play Families and applicable children's privacy requirements.

Data deletion

Because the app does not operate accounts, there is no remote account data for the developer to delete.

The in-app progress reset removes gameplay progress but keeps one-time purchase entitlements so purchased creatures and cosmetics remain available.

Clearing app data in Android settings or uninstalling the app removes the local entitlement cache from the device. Google Play purchase history and refunds are managed by Google Play, and the app can restore active non-consumable purchases from Google Play where supported.

Referral records are not account records and are stored as hashes for fraud prevention and reward accounting. Contact support if you have questions about referral records.

Firebase Analytics data collection can be disabled and reset by turning off Analytics and diagnostics in Settings.

Privacy questions can be sent to help@userstoday.net.

Contact

Privacy questions can be sent to help@userstoday.net.