Ggeomddakji (껌딱지) · Fennec Garden

Privacy Policy

Effective 2026-10-29 · Version 1.2

Ggeomddakji (껌딱지, “we”) processes the personal information of people who use the mobile game Fennec Garden (사막여우 퍼즐) (the “App”) in accordance with the Personal Information Protection Act of the Republic of Korea and other applicable laws. This policy applies to the iOS (App Store) and Android (Google Play) versions of the App and to the online ranking server the App uses.

Summary

Information we process and how it is collected

When the App is first launched it creates a random 64-character anonymous key (the “installation key”) and stores it on the device. The App uses this key to identify you when it talks to the server for the online ranking and cloud save. The server never stores the key itself, only its SHA-256 hash. The information below does not by itself identify a specific person, but because it could be combined with other information we protect it as personal information.

CategoryItemsHow collected · where stored
Online ranking profileSHA-256 hash of the installation key, player number assigned by the server, nickname, avatar combination (IDs of the equipped fox, accessory and eye-color cosmetics), cumulative score, next allowed nickname change time, creation and update timesSent automatically by the App (you enter the nickname yourself after completing all 5×5 stages) · server
Puzzle resultsRandom result ID, puzzle ID and stage ID, board size, score, time taken, time received by the serverSent automatically by the App after you complete a puzzle · server
Cloud save (backup)Your entire game save (progress and clear records, Sunshine, items, props and cosmetics owned and equipped, settings such as language, sound and vibration, transaction IDs (purchase tokens on Google Play) and product IDs of in-app purchases, save number, records of operator grants applied), a hash of the save, platform (iOS/Android/other), App version, save time, the 5 most recent save versions, and the hash of the recovery code with its issue and use timesSent automatically by the App while online (about 30 seconds after a change and when the App goes to the background) · server. There is no separate off switch; nothing is sent while offline
Store payment verification recordsPlatform, store transaction ID (purchase token on Google Play), product ID, player number, report and check times and verification status, plus the following looked up from the store: purchase time, price and currency (App Store), country / storefront region, order number (Google Play), original transaction ID (App Store), environment (production/test), and whether, when and why the purchase was refunded or canceledAfter a purchase the App reports the transaction ID, product ID and platform to the server during cloud sync (unreported records are sent at the next sync) → the server looks them up via the Apple App Store Server API or the Google Play Developer API and stores the result. When Apple or Google sends a payment status notification (such as a refund), the server looks the purchase up again · server
Operator grant recordsGrant ID, recipient player number, amount of Sunshine, reason, operator who registered it, times of registration, receipt and cancellationRegistered by the operator for compensation or events → the App receives it at the next sync, keeps the grant ID in the game save and applies it only once · server
Generated while using the serviceIP address, server request records such as request time, path and response statusProcessed automatically by the Cloudflare network (see sections 4 and 6)
Stored on the deviceThe game save above (backed up by cloud save), the installation key itself, the recovery code itself, and a copy of the previous save kept when you restoreApp storage on the device · the installation key, the recovery code itself and the previous-save copy are never sent to the server
InquiriesEmail address, content of the inquiry and any attachments you sendProvided by you by email

To verify scores, the App also sends the start and completion times, number of mistakes, number of hints and items used, rules version and similar data together with each result, but the server stores only the items listed in the table above and discards the rest.

The App does not collect names, email addresses, phone numbers, precise location, contacts, photos, advertising identifiers (IDFA / Android Advertising ID) or hardware device identifiers. Only development (debug) builds keep an error diagnostics log on the device; this log is never transmitted and is not created by the App distributed through the stores.

Purposes of processing

Game progress, currency and purchase and payment records are used only to provide game features, for backup and restore, payment verification and settlement, grants, and the inquiry handling and abuse checks above; they are not used for advertising or marketing.

Retention and deletion

InformationRetention period
Online ranking profile and puzzle resultsUntil we process a deletion request or end the ranking service. There is currently no automatic deletion based on inactivity.
Cloud save, save history and recovery code hashDeleted by a daily automatic cleanup if there has been no new backup for 2 years since the last one and no restore with the recovery code during that period. Only the 5 most recent save versions are kept; older ones are deleted automatically with each new save. Also deleted when we process a deletion request.
Store payment verification recordsKept for 5 years as records of payment and supply of goods under the Act on the Consumer Protection in Electronic Commerce of the Republic of Korea and other applicable laws, then destroyed. Even if your ranking and cloud save data are deleted, these records remain for that period with the link to your player number removed.
Operator grant recordsDeleted together with the player data (ranking profile) they belong to.
IP address used for rate limitingUsed only momentarily to count requests (limits on first registration and recovery code entry); not stored in the database.
Server request records (Cloudflare logs)Only a sample (about 10%) of requests is logged, and logs are deleted automatically after Cloudflare’s log retention period (a few days).
Information on the deviceUntil you delete the App or its data (we have no access to it).
Inquiry records1 year after the inquiry is resolved

When the retention period ends or the purpose has been achieved, we delete the information without delay in a way that cannot be recovered. Information that must be kept by law is stored separately for the required period. In-app purchase transaction records are kept by Apple and Google under their own policies.

Disclosure to third parties

We do not provide your personal information to third parties, except where specifically required by law or requested by investigative authorities through legal procedures. The nickname, avatar combination, cumulative score and rank you register for the ranking are visible to other users on the App’s ranking screen.

Processors and international transfers

We entrust the processing of personal information to the following service providers to operate the server. In the course of this, personal information may be transferred outside the Republic of Korea.

ProcessorTasksDestination · timing · methodItems transferredRetention
Cloudflare, Inc. (USA)Running the ranking, cloud save and payment verification server (Workers), database storage (D1), rate limiting, server logsCloudflare global network (processed at a nearby data center; the database is located in the Asia-Pacific region) · whenever the App communicates with the server · encrypted network transfer (HTTPS)Online ranking profile, puzzle results, cloud save (including save history and recovery code hash), store payment verification records, operator grant records, IP address and request records described in section 2Same as section 4
Apple Inc. (USA)App Store payment verification lookups (App Store Server API)USA · when a purchase is reported and when a payment status notification is received · encrypted API request (HTTPS)Transaction IDAccording to Apple’s policies
Google LLC (USA)Google Play payment verification lookups (Google Play Developer API)Google data centers in the USA and elsewhere · when a purchase is reported and when a payment status notification is received · encrypted API request (HTTPS)Purchase token, product IDAccording to Google’s policies
Cloudflare, Inc. (USA)Forwarding inquiry emails (Email Routing: support@ggeomddakji.com → operator mailbox)Cloudflare global network · when you send an inquiry email · email transfer (SMTP)Email address, content of the inquiryForwarded only; emails are not stored
Google LLC (USA, Gmail)Receiving and storing inquiry emailsGoogle data centers (USA and other countries) · when an inquiry email is received · email transfer (SMTP)Email address, content of the inquirySame as the inquiry record retention in section 4

If you do not want your information transferred abroad, you can play with the device offline or request deletion; in that case the global ranking and cloud save (backup and restore) will not be available to you. Apple and Google process payments directly as independent businesses, and their own privacy policies apply to payment information. For payment verification lookups we send Apple and Google only the transaction ID (purchase token) and product ID.

In-app purchases

Paid items in the App are sold only through the App Store (StoreKit) and Google Play billing. Payment methods and billing details are handled by Apple or Google and are not shared with us. So that a purchase is never granted twice and can be restored, the App records the transaction ID (the purchase token on Google Play) and product ID in the game save, and these records are also included in the cloud save backup. In addition, the App sends the transaction ID, product ID and platform to our server for payment verification, and the server looks up the transaction via the Apple App Store Server API or the Google Play Developer API and records the purchase time, price and currency (App Store), country / storefront region, order number, environment (production/test) and whether it was refunded or canceled. When Apple or Google sends a payment status notification (such as a refund), the server looks it up again. These records are used for payment verification, detecting duplicate or fraudulent payments, handling refunds, answering payment inquiries and settling sales. We never receive card numbers or other payment method details.

Your rights and how to exercise them

You (or the legal guardian of a child under 14) may at any time request access to, correction or deletion of, or suspension of processing of your personal information.

Because there are no user accounts, we may ask for additional information such as your nickname, a screenshot of the ranking screen or the recovery code from Settings → Backup to confirm that you are the user of that ranking data. We handle requests without delay after confirmation (in principle within 10 days) and inform you of the result.

Children’s information

The App does not check age and does not collect information that directly identifies a child, such as a real name or contact details. Please do not use personal information such as your real name or contact details in your nickname. A legal guardian who learns that personal information of a child under 14 has been processed may request access or deletion at support@ggeomddakji.com, and we will delete it after confirmation.

Security measures

Automatic collection tools

The App and these web pages do not use cookies, advertising identifiers, or analytics or tracking tools. The Android App does not request the Advertising ID permission.

Privacy officer

RoleDetails
Privacy officer이상훈 (owner, Ggeomddakji)
Contactsupport@ggeomddakji.com

Please send privacy questions, complaints and requests for remedies to the contact above.

Remedies for infringement

If you need advice or dispute resolution regarding a privacy infringement, you may contact the following Korean organizations.

Changes to this policy

This policy is effective from October 29, 2026. If the collected items or processing methods change, we will announce it on this page and in the version history before it takes effect, and we will also inform you of important changes through App update notes or similar means.

Version history

VersionEffectiveChanges
1.22026-10-29Added store payment verification records and operator grant records
1.12026-10-28Added cloud save and recovery code
1.02026-10-28First version