Yukinon Lab
JA
Back to Home

IfZen Privacy Policy

Last Updated: October 10, 2026 (Established: September 23, 2026)

Yukinon Lab ("we") establishes this Privacy Policy regarding the handling of user information in the game "IfZen" (formerly Ifinite Zenario; the Android and PC versions; the "App"). Ads exist only in the Android version.

1. Overview of Information We Collect

The App does not require account registration and does not collect information that directly identifies you, such as your name, email address, phone number or precise location. The App has no free-text input and does not hold permissions to use location, camera, microphone or contacts.

The App handles information through Google services for two purposes:

  • Improving the game and fixing bugs: the App collects gameplay statistics (such as how far you progressed through the screens and at which depth you won or lost) and crash information (Section 2). This information is linked to an identifier randomly generated for each user and is not tied to your name or similar information. This analytics does not use the Advertising ID
  • Delivering ads (Android version): Google AdMob collects information such as the Advertising ID to deliver ads (Section 3)

2. Usage Analytics and Crash Reporting

2.1 Services used

  • Android version: Google's Firebase Analytics (Google Analytics) and Firebase Crashlytics
  • PC version: Google Analytics 4 (sent via the Measurement Protocol)

2.2 Information sent

  • In-game events: launching and quitting, moving between screens, milestones reached for the first time (such as your first battle and your first win or loss), how far you viewed the how-to-play guide, starting, restarting and ending a run (the leader chosen, depth reached, win or loss, and time taken), the start and result of battles (depth, opponent, win or loss), the types of conditions, skills and modifiers used in battle, items bought in the shop, items received after battles, and total play time
  • Ad events (Android version): where and what kind of ad was shown, and whether a rewarded-ad reward was received
  • Device and app information: app version, OS type and version, device model, screen size, and language setting
  • An identifier randomly generated for each app installation (app instance ID / client ID)
  • Approximate region (country or region level, estimated by Google from the IP address of the connection. The IP address itself is not stored in Google Analytics)
  • Crash information (Android version only): the time of the crash, the program's call history (stack trace), and device state such as device type, OS version and free memory

2.3 Information not sent for analytics

  • The Advertising ID (Advertising ID collection in Firebase is disabled; the Advertising ID is used only for ad delivery in Section 3)
  • Your name, email address, precise location, contacts, photos, etc.
  • Text you enter (the App has no free-text input)

2.4 How to turn it off

If you turn off Settings → Analytics → "Send data for analytics" in the App, usage analytics and crash reports will no longer be sent from that point on. You can still use all features of the game with it turned off. This does not affect ads (for ads, see Sections 3 and 4).

2.5 Handling by region

  • If you use the App from the European Economic Area (EEA), the United Kingdom or Switzerland, nothing is sent until you give consent (Section 4)
  • In other regions, data is sent by default. The PC version lets you know about this at first launch. You can turn it off at any time as described in 2.4

2.6 Retention and management

Information that is sent is stored on Google's servers, and we view it in aggregated form in the Google Analytics and Firebase consoles. Events are retained for 14 months. Crash information in Crashlytics is retained for the period set by Google (90 days). We do not operate servers of our own and never send this information to our servers.

For how Google handles information, see the Google Privacy Policy, How Google uses information from sites or apps that use our services and Privacy and Security in Firebase.

3. Ads (Android version; third party: Google AdMob)

3.1 When ads are shown

  • Full-screen (interstitial) ads: shown only at the boundaries between dungeon zones, that is, when you defeat the boss at depth 5, 10 or 15, close the battle result screen and move on. At most 3 times per run. Not shown during the first 10 minutes after launch. Not shown when you lose, suspend a run or return to the title. If an ad has not finished loading, the App moves on without waiting
  • Rewarded ads (optional): shown only when you press a button (such as "Watch an ad to reroll") to reroll the rewards on the battle result screen once, or to restock the shop once for free. The reroll or restock happens only if you watch the ad to the end. You can play the whole game without watching them

You are never blocked from continuing because of an ad.

3.2 Information collected by Google

When delivering ads, Google may automatically collect the following information:

  • Advertising ID
  • IP address and approximate location
  • Device information (model, OS version, etc.)
  • Information about ad impressions and interactions

Google uses this information for ad delivery, fraud prevention and measuring ad performance. We never directly obtain or store it. For details, see the Google Privacy Policy and Advertising by Google. You can delete or reset your Advertising ID, or opt out of personalized ads, in your device settings (Settings → Google → Ads, or Settings → Privacy → Ads).

4. Consent and Opt-Out (EEA, UK, Switzerland and Certain US States)

  • Android version: at launch, the App checks your consent status through Google's User Messaging Platform (UMP), and shows a consent screen for usage analytics and for personalized ads and related data processing only when required. Analytics and ads both follow your answer on that screen
  • PC version: if your device's region settings suggest the EEA, the UK or Switzerland, the App shows its own consent screen for analytics at first launch (the PC version has no ads)
  • If you do not consent, usage analytics and crash reports are not sent. Ads are either shown as non-personalized ads or not shown, depending on your choices. In every case you can still use every feature of the game, and your progress is never blocked
  • In regions where consent is required, the App does not initialize the Google Mobile Ads SDK or request ads until the consent check is complete
  • Your consent record is stored on your device by Google's UMP (by the App on PC). We do not obtain this record
  • If you live in certain US states (where state privacy laws require it), the Android version may show a screen through Google's UMP where you can opt out of the sale or sharing of personal information for advertising. If you opt out, Google restricts how it uses information for ads (restricted data processing). You can still use every feature of the game after opting out
  • You can change your choice at any time: on Android from Settings → Analytics → "Consent settings" (shown only in regions where a consent or opt-out screen is required), and on PC from Settings → Analytics → "Send data for analytics"
  • In any region, you can opt out of personalized ads or reset your Advertising ID at any time in your device settings (3.2)

5. In-App Purchases

The App currently has no in-app purchases. If we introduce them in the future, we will revise this Policy to describe how purchase information is handled.

6. Information Stored on Your Device

The App stores the following information only on your device (in the App's private storage area):

  • Settings (BGM and sound effect volume, BGM type, text size, battle speed, display, whether analytics data is sent, etc.)
  • Records (deepest depth reached, number of runs played and completed, a list of past run results, unlocked leaders and parts, and the codex)
  • A suspended run you can continue later (party, logic setup, parts in hand, etc.)
  • The identifier for analytics and your consent status (Sections 2 and 4)

Apart from the information listed in Section 2, none of this is sent to us or to any third party.

7. Device Permissions (Android version)

7.1 Permissions for analytics and networking

  • Access the internet and check the network state (INTERNET, ACCESS_NETWORK_STATE): for sending the data described in Section 2 and for ads in Section 3
  • Keep the device awake (WAKE_LOCK): used by Google's libraries while sending data
  • Read install referrer information (BIND_GET_INSTALL_REFERRER_SERVICE): declared by Firebase Analytics to measure where on Google Play the App was installed from
  • Protect the App's internal broadcast receivers (com.yukinonlab.ifzen.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION): added automatically by an Android library so that other apps cannot call them
  • Vibration (VIBRATE): for short vibrations when attacks hit or enemies are defeated, while the "Vibration" setting is on (you can turn it off in Settings; no information is collected)

7.2 Permissions for ads (Google AdMob)

  • Advertising ID (AD_ID): for ad delivery in Section 3. Not used for analytics in Section 2
  • Android Privacy Sandbox related (ACCESS_ADSERVICES_AD_ID, ACCESS_ADSERVICES_ATTRIBUTION, ACCESS_ADSERVICES_TOPICS): declared by Google's ad SDK; we do not use them directly

All of these are permissions that do not show a permission prompt at runtime. The App does not use any permissions that show a permission prompt (such as location, camera, microphone, contacts, or photos and videos).

8. Google Play and Distribution Platforms

Downloads and updates of the Android version are handled by Google Play, and information involved in that process is handled under Google's Privacy Policy. We may view statistics that do not identify you (such as install counts and the number and details of crashes) in the Google Play Console.

Information handled by the platforms that distribute the PC version (such as Steam) is subject to each platform's privacy policy.

9. How Information Is Used

We use the information we collect (Section 2) only for the following purposes:

  • Tuning the game's difficulty and clarity (such as where players stop playing and at which depths they tend to lose)
  • Investigating and fixing the causes of bugs and crashes
  • Understanding overall trends among users (such as which leaders and setups are used most, and how often ads are shown and used)

We never sell the information we collect or use it for advertising. Information collected by Google AdMob (Section 3) is used by Google for ad delivery, fraud prevention and measuring ad performance. Information stored on your device (Section 6) is used only to carry it over to the next launch.

10. Data Deletion

  • Data on your device is deleted by uninstalling the App, or by using "Clear storage" in Android
  • Analytics data sent to Google is linked only to a random per-user identifier, so as a rule we are unable to locate the data belonging to a specific user. If you turn off sending in Settings and then clear the App's data (or reinstall the App), a new identifier is created and is no longer linked to the earlier data. For any other requests, please contact us using the details in Section 13
  • You can delete or reset your Advertising ID, or opt out of personalized ads, in your device settings (3.2). For changing your consent or opt-out choices, see Section 4
  • If you have enabled backup to Google in your device settings, Android's Auto Backup feature may save the data on your device to your Google Account and restore it when you reinstall the App or switch devices. These backups are managed by Google, and we cannot see their contents. To delete them, use the backup management for your Google Account (such as Google One)

11. Children's Privacy

The App is intended for users aged 13 and over. We do not intentionally collect personal information from children under 13 (we ourselves do not directly collect personal information from any user).

12. Changes to This Policy

This Policy may be revised in response to legal changes or new App features. When its content changes, we will update this page and revise the Last Updated date at the top. Significant changes will be announced on this page.

13. Contact