Legal information

Privacy Policy

This policy explains how the MIHENKAYNAK mobile game handles local saves, Google AdMob advertising data, and Firebase Analytics.

Last updated: October 4, 2026 · Developer: Lumoza Studio (Oğuzhan Alper Tosun)

In short: Your game progress stays on your device and is not sent to a developer-owned server. Optional rewarded ads and limited interstitials at completed trade or day-report breaks are provided by Google AdMob. The iOS app also uses Firebase Analytics for general usage statistics.

1. Local game data

Your shop name, selected character, progress, cash, stock, and preferences are stored only in local storage on your device. MIHENKAYNAK has no account or developer-operated cloud-save server. Deleting the app or clearing its data may erase this save.

The app's own code does not access your camera, microphone, contacts, or precise location. Your game save is not sent to Firebase; no separate crash-reporting service is installed.

You may optionally create a save-backup file in Settings and restore a file you select. It contains your shop name, character, game progress, and preferences, but not payment details, purchase entitlements, or authentication material. You choose where to save or share it; any cloud or sharing service you select applies its own privacy terms. The developer does not automatically receive the file. The temporary app file used for sharing is removed when the share sheet closes.

2. Google AdMob advertising

iOS Premium purchases are verified using Apple StoreKit. Apple processes payment details; the developer does not receive card information. The app checks ownership on-device through Apple without sending it to a developer server. Premium players claim rewards without ads; existing daily limits and cooldowns still apply. No ad requests are made while Premium is active.

The app has no banner ads. It may show:

Rewarded ads after non-Premium players deliberately choose a clearly labelled in-game advertising benefit. Their reward is granted only after completion.
Interstitial ads at saved trade or day-report breaks after sufficient active play and completed trades, at most twice per session. They grant no reward and are skipped for Premium, unsuitable consent or unavailable creatives.

The Google Mobile Ads SDK may process IP address and approximate location derived from it, device or advertising identifiers, ad impressions and interactions, app interactions, performance data, and non-identifying crash or diagnostic data. Processing may support ad delivery and measurement, fraud prevention, security, analytics, and performance. This data is sent to Google's systems.

See Google's Mobile Ads SDK data disclosure and Privacy Policy for details.

Reminder notifications

If you choose, the game shows a "time to open the shop" reminder when you skip a day. The notification is scheduled locally on your device; no data is sent to a server for it. At most one notification a day, and it can be turned off in Settings.

3. Firebase Analytics

In the iOS app, Google Firebase Analytics may process usage events such as app opens and sessions, along with technical data such as app version, device and operating system information, approximate region, and an app instance identifier. This data is sent to Google to understand usage trends and improve the game. From 2.1.0 the game also sends its own events: tutorial step, a trade's profit/loss sign (+/−, not the amount), the day number with a coarse cash and stock range at day close (e.g. "100k–1M"), and ad-break and reminder outcomes. Shop names, exact amounts, and save files are not sent. This integration uses Firebase Analytics Core, which does not include IDFA collection capability, and does not include Crashlytics. See Firebase's privacy information.

4. ATT and consent choices

On iOS, App Tracking Transparency (ATT) permission is requested before an advertising identifier can be used to track activity across companies' apps and websites. If you decline, the app remains usable and ads may be non-personalised or limited.

In the European Economic Area, the United Kingdom, and other consent-required regions, Google User Messaging Platform (UMP) may show a consent form when required. Declining consent does not block the game's core features. When Google requires a privacy-options entry point, it is available in Settings.

5. Sharing and retention

The developer cannot access or sell your local save. Retention and sharing of AdMob and Firebase Analytics data are governed by Google's policies and your regional advertising and consent choices.

6. Children's privacy

This general-audience simulation game does not ask for age, legal name, email, or account details. A parent or guardian may contact us with any privacy concern.

7. Changes and contact

If cloud save, accounts, another ad provider, or new data processing are added, this policy and the store privacy disclosures will be updated. For privacy questions or requests, email oguzhaanttnn@gmail.com.