This policy applies to every game Loha Studio publishes on Google Play and the App Store. The games it covers today are listed below; it is amended whenever a new game ships or the processing changes.
The following is written to on-device storage only — a per-game SQLite database — and is never transmitted to us:
Uninstalling the app deletes all of it from the device, subject to section 4.
| Service | What is sent | Purpose |
|---|---|---|
| Firebase Analytics | App instance ID; device information (model, OS version, language, screen); app version; a coarse region inferred from your IP address; automatically collected events such as first open, session start and screen views; and one custom event per completed game, carrying the game mode, the difficulty and whether it was a daily challenge. On Android an advertising identifier (AAID) may also be collected, depending on your device settings. On iOS no advertising identifier (IDFA) is collected and the app shows no App Tracking Transparency prompt — Firebase uses only app- and vendor-level identifiers. We use none of them for advertising. | Understanding how the game is used; deciding what to improve |
| Firebase Crashlytics | On an error or crash: stack trace, exception message, device model, OS version, app version and timestamp. Internal failures such as a storage error are reported the same way. | Finding and fixing errors |
These events carry none of your game records themselves — no statistics values, no points, no nickname. We do not set a user identifier (setUserId is not used anywhere in the app) and we send no contact details to Firebase. Google acts as our processor and under its own terms: Google Privacy Policy, Firebase Privacy and Security. Analytics retention follows our Firebase console setting, currently 2 months for event data and 14 months for user data. Crashlytics reports follow Google's own policy, currently 90 days.
On Android the operating system's Auto Backup is enabled for this app, so if you have device backup switched on, your records (the game's local database and its settings) may be included in your own Google account backup. The same applies to iCloud backup on iOS. This happens between your account and your devices; we cannot reach it. You control it in your device settings, and a backup may be restored when you reinstall the app or set up a new phone.
No camera, microphone, location, contacts, photo or file permission is requested.
If you are in the European Economic Area, the United Kingdom or Switzerland, we rely on the following bases under the GDPR and UK GDPR:
| Processing | Basis |
|---|---|
| Analytics events and identifiers (section 3) | Our legitimate interest in keeping the app working and diagnosing crashes (GDPR Art. 6(1)(f)). The app ships no consent prompt today, so if you would rather not be measured at all, uninstalling stops collection. An in-app consent prompt for the EEA and the UK is under review. |
| Crash reports (section 3) | Our legitimate interest in keeping the app working and secure |
| Records stored on your device (section 2) | Performance of the game you asked us to provide |
We do not sell personal information, we do not share it for advertising, and we disclose it to no one beyond what section 3 describes. The data in section 3 is processed by Google LLC and its affiliates to provide Firebase, which involves transfer to servers outside your country, including the United States. Google relies on the EU Standard Contractual Clauses and its certification under the EU–US Data Privacy Framework for those transfers.
The app ships no in-app switch for analytics collection. You can limit collection by deleting or resetting your advertising ID under Settings → Privacy → Ads on Android. On iOS there is no advertising identifier to reset, because the app collects none. Collection stops entirely once the app is uninstalled.
Our games are intended for users aged 14 and over. They are not directed at children, and we do not knowingly collect personal information from them. If you believe a child's information has been collected, contact us and we will verify and delete it.
You may ask what data relating to you we hold, and ask us to correct or delete it, or to stop processing it. Because the app creates no account we hold nothing that identifies you individually, so we may need extra detail (your device model, roughly when you played) to locate the relevant data — and in some cases we may be unable to link any data to you at all.
You additionally have the rights of access, rectification, erasure, restriction, data portability and objection, the right to withdraw consent at any time, and the right to lodge a complaint with your local supervisory authority.
We collect the categories "identifiers" and "internet or other electronic network activity information" described in section 3. We do not sell or share personal information, we do not process it for cross-context behavioural advertising, and we offer no financial incentives. You may exercise the rights to know, delete and correct through the contact in section 14, and we will not discriminate against you for doing so.
Korean residents' rights, the mandatory disclosures under the Personal Information Protection Act, and the local complaint channels are set out in the Korean version of this policy, which follows the Personal Information Protection Commission's drafting guidelines.
If this policy changes we will update the effective date above and keep the current version published here. For material changes — a new category of data or a new purpose — we will give notice in the app or on the store listing before the change takes effect, and keep earlier versions available for reference.
Privacy enquiries: ymseok.studio@gmail.com
Publisher: Loha Studio, Republic of Korea
This policy is published in two languages, each at its own address:
The Korean version is not a translation of this page. It follows the drafting guidelines of the Korean Personal Information Protection Commission and carries the disclosures the Personal Information Protection Act requires, so Korean residents should read that version. Both versions describe the same processing and share the same effective date. If the two ever differ, the Korean version governs, except where local law requires otherwise.