Privacy Policy for It's Driller
Effective date: August 13, 2026
YGJeong Games ("we," "us," or "our") provides the Android mobile game It's Driller. This Privacy Policy explains how information is handled when you use the game.
Information stored on your device
It's Driller uses Unity PlayerPrefs to store game progress and preferences locally. This includes coins; owned and equipped Worlds, Drills, and Skins; drill upgrade levels; best distance; audio, vibration, handedness, screen-shake, and graphics settings; and a completed-run counter used to manage gameplay flow.
The game also stores an age-treatment state (Unknown, Child, Teen, or Adult) and age-treatment schema version 2. It does not store your answer as a date of birth and does not ask for or collect your exact date of birth.
YGJeong Games does not operate an account server or cloud-save service for this local progress and cannot view it directly.
In addition to local progress and option values, the current save format stores technical metadata used to validate save integrity, recognize incomplete writes or damaged save candidates, select a valid save candidate, and manage recovery when saved states diverge. This metadata is part of the local save and is not described as encryption.
To support restart recovery and reduce duplicate Game Over rewards, the local save may store SHA-256 digests derived from run identifiers, a pending verified result that includes earned coins, verified distance, and reward eligibility, and a bounded history of completed-result digests. The original run identifier is not persisted in these lifecycle fields. These records are used for local save recovery and duplicate-result checks; the game does not use them for advertising profiling or behavioral tracking.
The Google User Messaging Platform (UMP) SDK may store consent information and privacy choices on the device as part of Google's consent-management process. The game does not add these consent choices to its PlayerPrefs progress save and does not operate a separate server for them.
First-launch age handling
On first launch, the game asks: “Are you 13 or older?”Selecting No assigns the Child treatment. SelectingYes asks Google Play for available age signals.
If Google Play does not share an age signal, the request fails, or the response is missing or invalid, the game assigns the Unknown treatment. The game stores only the resulting treatment state and schema version; it does not ask for or store an exact date of birth.
The age question and Google Play Age Signals are not used to allow or block Google Play Games sign-in, leaderboard access, advertising consent, advertising personalization, marketing, user profiling, or analytics. Google Play Games authentication follows the same attempt and fallback rules for Child, Teen, Adult, and Unknown treatments. Advertising uses the separate protective configuration and consent process described below.
The Play Age Signals client library reports that it does not collect data about use of the API. The Google Play Store performs its own processes under Google's terms when the runtime request is made. Learn more in the Play Age Signals overview.
Google Play Games sign-in and leaderboards
Google Play Games authentication follows the same rules for Child, Teen, Adult, and Unknown treatments. When the player presses PRESS TO START, the game may make at most one authentication request for that input. Authentication success, failure, cancellation, offline status, or an unavailable provider does not prevent the game from entering the Main screen.
If the player is not authenticated, the Main Ranking screen shows a local Best fallback and provides a SIGN IN action for another user-initiated authentication attempt. After successful authentication, a positive local Best Distance may be submitted at most once for the active ranking request before the game loads server leaderboard results. A score of zero, or a score that is the same as or lower than the score already submitted by the app, is not unnecessarily resubmitted. A failed server request does not create a fabricated rank.
The Game Over Ranking screen automatically submits a positive new Best Distance and loads server ranking data only when Google Play Games is already authenticated. It does not start an authentication popup when the player is unauthenticated and instead keeps the local fallback.
When the leaderboard is used, Google Play Games may process a Play Games player identifier, display name, profile avatar, leaderboard scores, and rank information to authenticate access and display leaderboard results. The Google Play Games SDK also automatically processes analytics and diagnostics information to support SDK stability and product improvement. The game does not receive your Google Account password. YGJeong Games does not operate a separate server that stores your Play Games profile.
Google handles Play Games information under the Google Privacy Policy and its Play Games profile privacy and settings.
Unity Engine diagnostics
The current production project enables Unity Engine Diagnostics and is linked to a Unity Cloud project. When a published game runs on a supported device, Unity may process essential technical data such as crash logs, application diagnostics, performance information, telemetry, configuration metadata, and device or other identifiers for stability, reliability, and troubleshooting.
Unity Analytics, legacy Cloud Diagnostics reporting, Unity Ads, and Unity Purchasing are disabled in the examined project settings. We do not use Unity diagnostics for advertising or marketing.
See Unity's Game Player and App User Privacy Policy and Diagnostics data information.
Advertising
The production version uses Google Mobile Ads and may display banner ads on the Main and Game screens. The Shop does not request ads. The app uses its approved production AdMob configuration; it does not use Google's test ad units in the production release.
Before Google Mobile Ads is initialized, the app applies Google's child age-restricted advertising treatment to every user, limits ad content to a maximum rating of G, disables publisher privacy personalization, and disables the publisher first-party identifier. The app does not use remarketing or behavioral targeting and does not include a third-party mediation adapter. The game's age question, stored age-treatment state, Google Play Age Signals, Google Play Games, and leaderboard results are not used to decide advertising consent or personalization.
The app uses Google's User Messaging Platform (UMP) SDK for regional privacy messaging. On each app launch, the app asks the UMP SDK to update consent information at most once. If the SDK reports that a consent form is required, the app asks the SDK to load and show that form. Google Mobile Ads is initialized and an ad is requested only after the update and any required form have completed and ConsentInformation.CanRequestAds() is true.
If the consent update or form fails, is unavailable, remains unresolved, or does not permit ad requests, the app does not initialize Google Mobile Ads or request a banner. This fail-closed advertising result does not block gameplay, local saves, Main-screen entry, Google Play Games sign-in, or leaderboard use.
Where the UMP SDK reports that privacy options are required, the Main Options screen provides a Privacy Optionsentry. This opens the Google-managed privacy form so the user can review or change an applicable advertising privacy choice. The entry is not shown when the SDK reports that it is not required.
The app removes Android advertising-ID and Privacy Sandbox advertising permissions. The Google Mobile Ads SDK can nevertheless process information such as an IP address, app interactions, diagnostic information, and device or account identifiers such as an app set ID for ad delivery, measurement, diagnostics, and fraud prevention. See Google's Google Play data disclosure for the Mobile Ads Unity Plugin.
Regional consent messages may identify Google and applicable ad technology providers. The exact provider list must match the provider list disclosed in the applicable Google consent message. This policy does not claim that every provider in Google's public commonly-used list is active for this app.
How information is used
- Local data saves progress, equipment, items and upgrades acquired with in-game coins, best distance, and preferences.
- The stored age-treatment state records the result of the first-launch age flow. It does not determine access to Google Play Games or advertising consent.
- Google Play Games data authenticates permitted users and displays leaderboard results.
- Unity diagnostic data supports game and engine stability, reliability, and troubleshooting.
- Google Mobile Ads information supports production banner delivery, measurement, diagnostics, and fraud prevention under the protective advertising settings described above. Google UMP information supports regional consent and privacy-choice management.
Service providers and sharing
We do not sell personal information. Google provides Play Age Signals, Google Play Games, Android backup, Google Mobile Ads, Google User Messaging Platform, and related platform services. Unity provides the game engine and Engine Diagnostics. These providers process information under their own terms and privacy policies for the services described above.
Regional Google consent messages disclose the ad technology providers applicable to those messages. Because Google's public commonly-used provider set and an account's selected provider list can change, this policy does not state that all publicly listed providers are active for this app. Any final provider disclosure must remain consistent with the provider list shown in the applicable consent message.
Data retention, backup, restore, and deletion
Local PlayerPrefs data remains in the app's local storage until it is overwritten, cleared through Android app controls, or removed from the device. Uninstalling normally removes the app's local copy from that device.
The current Android manifest does not opt out of Android backup and does not exclude PlayerPrefs from backup. Because Android may back up SharedPreferences, some local progress, preferences, and the stored age-treatment state may be included in Android cloud backup or device-to-device transfer and later restored after reinstalling the game or setting up another device. Whether backup or restore occurs depends on Android version, device manufacturer, Google Account, and the user's backup settings. YGJeong Games does not operate or directly access those Android backups.
Google retains and deletes Play Games information under its own policies and account controls. You can delete Play Games data or a Play Games profile.
Google controls retention for information processed by Google Mobile Ads and UMP. Where the UMP SDK reports that privacy options are required, the Main Options screen provides a Privacy Options entry through which the user can reopen the applicable Google-managed privacy form and review or change an advertising privacy choice. Other requests concerning Google-managed information may need to be completed through Google's privacy controls.
Unity controls retention for information it processes as a service provider. Contact us for a privacy request concerning information handled on our behalf. We may need enough technical information to locate the relevant record, and some requests may need to be completed through Google or Unity controls.
Children's privacy
The game is intended for players in the following age groups: 9–12, 13–15, 16–17, and 18 and over. Ages 5 and under and ages 6–8 are not target audiences for the game.
Child, Teen, Adult, and Unknown treatments follow the same Google Play Games authentication and fallback rules. The local core game remains available when authentication fails, is canceled, is offline, or is unavailable.
The age question and Google Play Age Signals are not used to make advertising-consent or personalization decisions, for marketing, or for profiling, and the game does not ask for an exact date of birth. Before initializing Google Mobile Ads, the app applies Google's child age-restricted advertising treatment and a maximum G content rating to every user, disables publisher privacy personalization, and disables the publisher first-party identifier. Regional advertising consent is handled separately through Google UMP.
Security
We use the platform and service-provider safeguards available for the features described above. No method of storage or transmission can be guaranteed to be completely secure.
Your choices and rights
The local core game remains playable without Google Play Games. Google Play Games authentication follows the same rules for every stored age treatment. An unsuccessful, canceled, offline, or unavailable authentication attempt does not block entry to the Main screen. An unauthenticated player can use the SIGN IN action in Main Ranking to try again.
Where required by the UMP SDK, the Main Options screen provides aPrivacy Options entry for reviewing or changing an applicable advertising privacy choice. Google also provides account and privacy controls for information managed through Google Play Games, Google Mobile Ads, and other Google services.
You can clear local app data through Android settings and manage Play Games information through Google's controls. Depending on where you live, you may have legal rights concerning personal information. Contact us to make a privacy request. Because we do not maintain a first-party account or server-side player profile, we may direct requests concerning provider-managed information to Google or Unity.
Changes to this policy
We may update this Privacy Policy when the game, service providers, or legal requirements change. A revised policy will be posted on this page with an updated effective date. Advertising integration is a mandatory policy and Data Safety re-review gate.
Contact
YGJeong Games
Email: ygjeong.games@gmail.com
For game support, visit the It's Driller Support page.