Today's Harvest Privacy Policy
- App: Today's Harvest (오늘의 수확)
- Operator account and privacy contact: creativeforoneself2
- Email: creativeforoneself2@gmail.com
- Effective date: October 24, 2026
Version scope: Advertising and update-notice provisions apply to iOS 0.1.1 and later. The earlier iOS release 0.1.0(3) contains no advertising SDK or app-tracking feature. Earlier Android 0.1.2 and the web demo contain no advertising SDK. Advertising and data processing in the Android 0.1.6 closed test and 0.1.11 production release are described separately below.
Current scope: The additional AdMob/Google consent-management section and related device-storage provisions below apply to iOS 0.1.4 and later. They do not retroactively change the behavior of iOS 0.1.3 or earlier or the historical AdFit notice, and do not apply those features to Android apps or web demos without them. On November 3, 2026, the version-scope notice was brought up to date and this English translation of the same policy was added.
1. Scope
This policy explains information processing when you use Today's Harvest, visit its official support or policy pages, or contact us by email.
Today's Harvest is a fruit-merging puzzle game that does not require registration. Files needed for basic play are bundled with the app, so you can play offline. Opening external support or policy pages, sharing to other services, or contacting us may require an internet connection.
The current version has no operator-run game, account, or cloud-save server. The app does not automatically send game progress or personal game records to the operator. On-device records, OS backups, sharing and email you choose to use, and website visits are handled separately as described below.
2. Game information stored on your device
The app stores the following information in its local app storage to resume games, show personal records, and retain settings. It does not automatically synchronize records across devices.
| Stored information | Purpose |
|---|---|
| Current board, next-fruit sequence, game mode, board size and number of fruit types | Resume a game in progress |
| Score, action/merge/harvest counts, remaining time, and progress/end state | Apply game rules and restore progress |
| Best scores by conditions, goal achievements and play records | Display personal records and achievements |
| Challenge date and values used to reproduce the fruit sequence | Reproduce a challenge under the same conditions |
| Settings such as sound on/off | Retain your chosen preferences |
This information is not sent to an online global leaderboard or an operator analytics server. The app does not ask for a name, email address, or telephone number to create a player account. Best scores and achievements may remain when you start a new game or change modes.
Additional settings in later versions: iOS versions introducing the Terms of Use store your selected language and the accepted document version and content digest on the device to retain the language and avoid repeatedly asking about the same terms. Acceptance is managed separately from advertising privacy choices and ATT permission; it is not a basis for permitting ad requests or verifying actual age. Versions introducing AdMob/Google consent management also store the app's ad-personalization preference on the device, defaulting to off when no choice has been saved. This preference is separate from Google UMP privacy choices; turning it on does not itself constitute consent to personal-data processing or tracking, or mean personalized ads are actually served. Neither these settings nor existing game records are automatically sent to an operator server. The device-storage retention and deletion provisions below apply.
3. Advertising, analytics, payments and device access
Advertising and privacy in Android 0.1.6 and 0.1.11
Scope: Added November 4, 2026, this section applies when the Android 0.1.6 update is installed. Earlier Android 0.1.2 has no advertising SDK. The iOS advertising, ATT and AdFit notices below remain unchanged and do not describe Android behavior. Android 0.1.6 and 0.1.11 use Google Mobile Ads SDK 25.5.0 and Google User Messaging Platform (UMP) 4.0.0. The Android 0.1.11 production release requests banner ads using its dedicated Android Google AdMob ad unit. Development and QA builds use Google's official test ads. The earlier Android 0.1.6 closed test uses test ads only. The ad unit is fixed in the app build, with no remote switch to change it. No Kakao AdFit or other mediation SDK is included. Both live and test ads communicate with Google and are not data-free.
Protection for every user: The app does not ask for or collect actual age or date of birth. Every ad request, including for users of unknown age, receives child-protective treatment (CHILD), a G content rating, nonpersonalized requests (npa), disabled publisher personalization and a disabled publisher first-party identifier (PFID). The app excludes Android advertising ID (AD_ID) and AdServices advertising ID, attribution and topics permissions. It does not request interest-based advertising or remarketing, or offer a switch to relax these protections. Blocking advertising ID does not eliminate every identifier or network data flow.
Google SDK processing: Google's Android disclosure describes collection and sharing of IP addresses and approximate location inferred from them, app launches, taps and ad interactions, performance diagnostics, and device or other identifiers such as app set ID, for advertising, analytics and fraud prevention. Actual fields depend on protective settings and SDK/OS restrictions. Google states that SDK transmissions use TLS encryption. The app does not request GPS location permission or directly add boards, scores or personal game records to ad requests. See Google's Android SDK disclosure.
Consent management and request limits: UMP is configured to treat every user as under the age of consent, so it does not present a personalized-ad consent request. This is neither actual age verification nor the user's consent to personal-data processing. The app initializes and requests ads only when UMP permits ad requests and confirms that neither consent nor a privacy-options screen is required. Failed checks, unknown states or required additional choices prevent requests. No other provider is used to bypass this gate. Missing ads do not remove gameplay or records. Settings explain protected-audience personalization restrictions and provide no personalization switch or privacy-options form. UMP may store status and related settings on the device.
Storage and deletion: Language and the accepted terms version/content digest are stored on the device. Terms acceptance is separate from ad consent and age verification. The operator has no game server or separate copy of Google's ad data. Local records, OS backups and correspondence follow the sections below. Clearing app data does not immediately delete information already processed by Google. For Google's retention, international processing, controls and rights procedures, see the Google Privacy Policy and retention guidance. Contact the app operator at the existing support email.
iOS advertising
Today's Harvest iOS 0.1.1 includes a top banner using Kakao AdFit iOS SDK 3.22.7. Ads occupy a dedicated area above the existing screen and do not cover the board or controls. Earlier iOS 0.1.0(3), the Android app and the web demo do not include this advertising SDK.
iOS 0.1.1–0.1.3 do not show an in-app ATT system tracking-permission prompt. Permission requests and ad conditions in later AdMob versions follow the additional notice below. Ad requests and display are not used as a switch that makes game features depend on tracking permission. iOS restricts access to the advertising identifier (IDFA) when tracking is not authorized. The app does not change or bypass OS permissions or create its own alternative advertising identifier. It does not automatically revoke permission previously granted in testing. You can check it in iOS Settings → Privacy & Security → Tracking.
Kakao's public SDK guidance and distributed privacy manifest list user/device identifiers, advertising data, product interaction, and crash, performance and other diagnostic information. The provider states that it may use this information for advertising, ad-performance measurement, usage analytics, SDK stability and service functionality. Identifiers, advertising data and product interaction include categories the provider discloses for advertising-related tracking. This notice does not treat users who have not allowed tracking as having consented to it.
Ad-network communication may transmit connection information such as IP addresses. The app does not upload boards, scores or personal game records to an operator game or analytics server. See the Kakao Privacy Policy and AdFit SDK privacy guidance.
Depending on connectivity, ad inventory or publisher review, an introductory banner or no ad may appear. All game features and stored records remain available without ads. Ad configuration is bundled with the app; remote switches are not used to change behavior between review and normal use.
Additional notice for versions introducing AdMob and Google consent management
When this applies: This section applies to iOS 0.1.4 and later introducing AdMob and Google consent management. It does not imply that iOS 0.1.3 includes these features. The tracking-permission information below was added on October 30, 2026 and applies when the relevant update is installed. The historical Kakao AdFit processing notice above remains in place.
Ad delivery: These versions prioritize Google AdMob. If AdMob supplies an ad, including a non-personalized or limited ad, the app does not switch to AdFit. In iOS 0.1.11, the app may consider the existing Kakao AdFit banner as a fallback after an explicit AdMob no-fill response or an ad-load result classified as a network, configuration, or unknown failure. Being offline is distinct from a network failure while loading an ad and is not a fallback reason. All separate AdFit eligibility conditions below must still be met in either case. Meeting the conditions to consider fallback does not mean a request was sent to AdFit or an ad was shown. The app returns to AdMob when its ads become available again and does not show both banners simultaneously. An AdFit fallback request is possible only with the app's ad-personalization preference on and iOS ATT tracking permission authorized. It is considered only when fresh signals show GDPR applicability as 0, Google UMP's privacy-options requirement as “not required,” and no active restricted-data-processing signal. In addition, either both the GPP applicable-section value and header string must be absent, or the section value must be -1 together with a nonempty header string. Missing parts, malformed values or other failures to satisfy the conditions do not permit fallback requests. Restrictions for known protected users and separate requirements such as app configuration and acceptance of the terms also remain. These SDK-signal checks do not establish a user's country, legal jurisdiction or regulatory exemption, and do not transfer Google's choice-screen status or consent to Kakao AdFit. The app preference and Google privacy choices do not automatically authorize AdFit. An ad-request restriction caused by incomplete or declined privacy choices is not a reason for fallback and is not bypassed through another provider. Other ad-load failures are not treated as explicit no-fill, and an error alone does not permit AdFit use. Ads may be unavailable because of inventory or connectivity; that does not erase progress or records or forcibly close the app for a user who has accepted the terms.
Information the Google advertising SDK may process: Google's iOS SDK disclosure lists IP addresses and approximate location inferred from them, device identifiers, ad impressions, interactions such as launches and taps, and crash, performance and other diagnostic information. Google describes uses including ad delivery, measurement and analytics, SDK stability and functionality improvements. Actual processing, including identifiers, depends on OS restrictions, user choices and the protections below. This list does not mean every item is always collected from every user. See Google Mobile Ads SDK data disclosure for categories and purposes. The app does not directly add game boards, scores, best records or shared text to ad requests.
Protective settings for Google ad requests: Before initializing the Google advertising SDK, these versions apply child-protective treatment (CHILD), a general-audience ad-content rating (G), publisher personalization restrictions (PPT), and disable the publisher first-party identifier (PFID). In this general-audience app, the app-added PPT, conservative child treatment and PFID restrictions are relaxed only if the device's saved ad-personalization preference is on, iOS ATT is authorized, fresh valid state shows that Google UMP permits ad requests, and there is no restriction such as restricted data processing. The G ad-content rating remains, as do restrictions for users known to be protected. This is not age verification or adult certification. Neither turning the preference on nor becoming eligible to request ads is treated as consent to personal-data processing or tracking, or proof that personalized ads are actually served. Actual ad requests and data processing remain subject to the SDK's privacy/consent signals and OS restrictions. The app attempts an ATT system request only when the user directly changes the ad-personalization preference from off to on in settings and iOS tracking permission has not yet been determined. Launching the app, accepting terms or a lack of ads does not itself trigger a tracking request. While permission is denied, restricted or not yet authorized, Google's additional personalization restrictions and disabled PFID remain and the app does not initiate new AdFit requests. Google non-personalized or limited ads may still be requested when required consent and SDK-supported conditions are satisfied. Declining permission does not remove game features or stored records. The app does not change or bypass iOS permissions, and acceptance of the terms is not treated as privacy or tracking consent. These settings do not eliminate all network data processing. Kakao processing remains subject to the AdFit notice and its separate conditions.
Google consent management: Google User Messaging Platform (UMP) provides privacy choices required in the relevant region, and the app checks the choice status and whether a screen is needed when it launches. UMP's privacy manifest includes approximate location, performance information and product interaction for consent-management functionality. The SDK may store and manage choice status and related settings on the device. The app does not provide UMP with an account or user identifier for synchronizing consent between apps. Google ads are requested only when UMP determines that ad requests are permitted; agreement to terms or an app switch does not replace this determination.
Changing choices: The app's ad-personalization preference defaults to off, is stored on the device and can be changed separately from Google UMP privacy choices. Turning it off reapplies Google's additional personalization restrictions and prevents newly initiated AdFit fallback requests. It does not revoke an iOS tracking permission already granted. Manage that permission separately in iOS Settings → Privacy & Security → Tracking. A previously saved on preference is not taken as iOS authorization and does not automatically request permission on launch. If permission has not yet been determined, you can turn the app preference off and back on to request it directly; if permission was already denied, change it in iOS Settings. An on preference means a preference to relax the app's additional restrictions when conditions allow, not obtained consent or actual personalized-ad delivery. In settings under Ad privacy choices, you can reopen Google's choice screen when it is required to change or withdraw choices. If a choice screen is not available, the app tells you. Turning the preference off or declining/withdrawing personalized ads may still allow non-personalized or limited ads when their requirements are met. This menu does not remove ads. Choices about other requirements, such as device storage, may restrict ad requests themselves. When the app becomes active and before requesting or displaying ads, it checks the current iOS permission again; when permission or preference changes, it clears the previous ad display and applies the new conditions. This does not retroactively cancel or delete transmitted information or requests. Changing privacy choices does not delete game records or the separately stored acceptance of the terms.
Device permissions and connection information: Requesting device location permission or reading a location sensor such as GPS is different from approximate location processing through IP addresses in advertising/consent communications. The device-access notice below does not mean there is no IP-based location estimation.
Google processing, retention and international processing: Information processed by Google services is subject to the Google Privacy Policy. Google states that it processes information on servers around the world, potentially outside your country of residence. Retention varies with the information, purposes and legal obligations; see Google's retention guidance for retention and deletion practices. Removing the app or changing privacy choices does not immediately delete everything Google has already processed. Google's policy explains its information controls and ways to exercise rights; questions for the app operator can be sent to the existing contact email. This does not replace the operator's responsibilities for correspondence and game records described below.
Optional update notices
iOS 0.1.1 and 0.1.2 cache public version-information lookups from Apple's Korean App Store for 24 hours to reduce repeated requests. iOS 0.1.3 and later attempt a lookup at a fresh launch and when returning after actually entering the background; you can also check again using Check for updates in help. The fixed Apple lookup URL in 0.1.3 and later contains the Today's Harvest app ID, store country and a number based on the lookup time to avoid reusing stale responses. Installed-version and OS-version comparisons for updates and compatibility take place on the device. The update-check code does not add boards, scores, game records or separate account/user/device identifiers to the request, but IP addresses and OS-provided connection information needed for ordinary network communication may be transmitted to Apple.
If a newer compatible version exists, an optional notice may be shown at a time that does not interrupt play. Choosing Later or losing connectivity does not prevent play or access to saved records. iOS 0.1.1 and 0.1.2 store the lookup time and postponed version/period to reduce repeated notices. In 0.1.3 and later, Later closes only the notice for the current launch/return, and a newer version may be shown again at the next launch/return. These later versions do not newly persist lookup results or postponement periods, do not use or delete the earlier versions' lookup/postponement data, and retain game records. Update opens Today's Harvest in the Apple App Store; subsequent handling is subject to Apple's policies.
There is no separate gameplay-analytics SDK, developer error-reporting SDK, in-app purchasing or payment feature. Game records are stored on the device; external visits, sharing and email you choose are described below.
The game does not access contacts, device location, photos, camera, microphone, or call/text-message contents. Score-copying and sharing are used only at your choice.
4. OS backup and device transfer
Even without an app-provided cloud-save feature, OS backup or device-transfer services may store or move app data.
The Android app is configured to permit OS backup. Depending on Android version, manufacturer, account and backup settings, records and settings may be backed up or transferred. On iPhone and iPad, app data may also be saved and restored according to your iCloud backup or device-transfer settings.
Google, Apple or the device/backup provider handles this according to your settings and its policies. The operator cannot directly access that backup storage to inspect or delete records. Recovery or cross-device synchronization is not guaranteed on every device. Check device or service settings for backup scope and deletion.
5. Optional sharing and copying
The share screen first shows the score and play conditions for you to review. The text may include the current/final score, merge count, watermelon count, mode, board size, number of fruit types and challenge date. Shared text includes scores/play conditions and an app-installation link, not account IDs or personal contact details.
Sharing to another app: When you choose Share, the score and play-condition text is passed to the OS sharing function. The service you select, such as KakaoTalk, handles sending and storage under its privacy policy. Today's Harvest does not read contacts, choose recipients or send messages automatically.
Copying score text: The copy button writes the displayed text to the device clipboard. The app does not read and analyze existing clipboard contents or send them to the operator. Retention and pasting depend on the OS and apps you choose.
Sharing and copying are optional; you can play without them. Deleting Today's Harvest data does not automatically remove messages already sent to another service. Use that service's deletion functions.
6. Email inquiries
Send game or privacy questions to creativeforoneself2@gmail.com.
An email sends the operator your sender address, display name, message and any images/files you voluntarily attach. The operator uses them as needed to answer and resolve the issue. You do not have to contact us to use the game.
Correspondence is retained until the response and necessary follow-up are complete, then deleted from operator-managed mail and separate copies when no longer needed. You may use the same email address to request access, correction, deletion or cessation of processing of your correspondence. If needed to handle a request, we check the minimum information necessary to confirm you are its sender.
Inquiries are received through Google Gmail. Google and your chosen email provider also process information for delivery, storage, security and service operation. Deletion from the operator's mailbox may occur at a different time from deletion of provider backups/system logs; provider policies apply. See the Google Privacy Policy.
For a bug report, your device model, OS/app versions and the circumstances are helpful. Hide unrelated personal information in screenshots. Passwords and payment information are not needed.
7. Websites and external services
Official support and policy pages are hosted on GitHub Pages. See the GitHub Privacy Statement.
Opening external support/policy pages may transmit IP addresses, access times, requested URLs, browser information and other connection information needed for page delivery and security to providers such as GitHub.
GitHub states that it logs and stores GitHub Pages visitors' IP addresses for security, whether or not they are signed in. See GitHub Pages privacy information. The operator does not add separate analytics or advertising-tracking code to support/policy pages. This does not mean GitHub's operational/security connection information stays only on your device; GitHub's policies and settings govern its retention and deletion.
After you move to an external service, that service's policies apply. Whether or not you visit support pages, share, or email, basic gameplay does not require connecting to an operator game server.
8. Retaining, deleting and protecting game records
Records and settings may remain on the device until you delete app/site data or the storage is removed. Low storage, browser settings or OS storage management can also cause records to be lost. The operator has no separate server copy of local records and cannot retrieve or restore them remotely.
- Android: In device Settings, use Apps → Today's Harvest → Storage → Clear data or Clear storage to delete local records. Menu names vary. Clearing cache alone may not remove all records.
- iPhone/iPad: Use Settings → General → iPhone Storage or iPad Storage → Today's Harvest → Delete App. Offloading an app while keeping documents/data is different from deleting all data.
Deleted records may be irreversible. Some information may be restored through remaining OS backups or device transfer; to remove backups too, check Google, Apple or manufacturer backup settings. There is no player account and therefore no separate account-withdrawal procedure.
Game records use OS/browser-managed storage and its protections. The operator limits mail access to what is needed for handling inquiries. Device locking and OS updates also help protect local records.
9. Policy changes and contact
If information-processing features such as advertising, account login, cloud saves or online leaderboards are added, or processing changes, we update this policy accordingly and provide notice in the app and public policy pages. In particular, before adding advertising through a future app update, we review the providers/SDKs, data processing, tracking/personalized advertising and third-party disclosures against the final implementation and revise the notice. Changes requiring separate notice or consent follow those procedures.
For privacy or game-use questions:
- Operator account and privacy contact: creativeforoneself2
- Email: creativeforoneself2@gmail.com
- Effective date: October 24, 2026