K-Tile — Privacy Policy (English)
There are sixteen things that leave your device. We list them all.
① Ads — Google AdMob processes the advertising ID and other data in order to show ads (§5).
② Purchase verification — When you buy a paid item, and when the app restores or re-checks the purchases you already have at start-up, receipt information is sent to our server to check that the purchase is genuine (§7).
③ Invites — Each time you start the app, your device's random 12-character ID is used to ask our server whether an invite gift has arrived. If the app was installed through an invite link, the inviter's 12-character ID and the new device's 12-character ID are sent together (§8).
④ Rankings — Each time you clear a level, one number — that level's score — is sent so we can show you "top X% in your country". No identifier goes with it (§8-1).
⑤ Word error reports — Only when you report one: the word ID, language, reason and app version are sent (§8-3).
⑥ New pack downloads · notice check — The app asks whether there are new word packs or map packs, and whether there is a notice that the Terms or this Policy are changing, and downloads them. Nothing is sent (§8-4).
⑦ Returning-player gift — Only when an earlier purchase comes back, the purchase token is sent to check whether a gift applies (§8-5).
⑧ Refund check — Only when you restore purchases, the same purchase token is used to ask whether it was refunded (§8-6).
⑨ Visit statistics — Once a day the random 12-character ID is sent, and the server records it with the date and the two-letter country code of the internet request (§8-7).
⑩ Versus — When you enter the arena, seven word-pack skill numbers and the level number are sent (§8-8 · §10-1).
⑪ Coupons — When you enter a coupon code, the code and the random 12-character ID are sent; after that, the random 12-character ID is sent when you start the app (§8-10).
⑫ Google sign-in — Only if you choose it, Google's verification token and an "aged 14 or over" confirmation are sent; while you are signed in, the sign-in session is sent when you start the app (§8-11).
⑬ App error reports — Only when an unhandled error occurs in the game code, the error details and the app version, device model, OS version and the like are sent. Nothing is sent if you are under 14 or your age is not yet known, and you can switch it off in Settings (§8-12).
⑭ Coin restore · Taking back refunded coins — When you enter an order ID: that order ID, a random code and a list of hashes of the purchases whose coins were received on this device are sent. Also, on a device that has such purchases, only that list of hashes is sent when the app starts, to check whether any coin bundle was refunded, and when coins bought with real money go down, the number of unspent coins for each order is sent (§8-13).
⑮ Account progress saving — Only if you sign in with Google and choose "Save": a copy of your game progress is saved to your account and moved to another device (§8-15).
⑯ Asking friends for hearts — Only if you use "Ask friends for a heart": a random ask number and key are registered, and hearts your friends sent are collected. When a friend sends a heart from the link, the ask number and a hash of a random token from the sender's browser are recorded on our server. If you are under 14 or your age is not yet known, this button does not appear (§8).
These sixteen are what our app sends. Separately, when the app starts, Google Play on your device checks whether a new version exists — this is handled by the Google Play Store app on your device rather than sent by our app, and nothing comes to our servers (§8-14).
1. Operator
| App name | K-Tile / 케이타일 Store listing: K-Tile: Space Journey |
|---|---|
| Package name | com.softback.layerpuzzle |
| Business name | Softback (소프트백) |
| Representative | 백영존 |
| Business registration number | 416-31-65901 |
| Mail-order business report number | 2026-화성동탄-2967 (filed with Dongtan-gu, Hwaseong-si, Gyeonggi-do) |
| Phone | 010-2697-5218 |
| Address | 99 Dongtan-jungang-ro, Dongtan-gu, Hwaseong-si, Gyeonggi-do, Republic of Korea (경기도 화성시 동탄구 동탄중앙로 99) |
| Hosting service provider | Cloudflare, Inc. |
| Chief Privacy Officer | 백영존 · [email protected] |
2. What we do not collect · App permissions
| Item | Collected? | Details |
|---|---|---|
| Name · gender | Not collected | There is no screen that asks for it |
| Phone number | Not collected | There is no screen that asks for it |
| Year and month of birth | Not collected | We ask on first launch, but on your device we only turn it into an age band; it is neither stored nor sent (§4-1). We do not ask for the day |
| Only if you sign in | If you choose Google sign-in, we store on our server the one email address that Google has verified (§8-11). If you do not sign in, it is never exchanged | |
| Location | Precise location not collected | We do not request the location permission. For rankings, visit statistics and versus, our server uses only the two-letter country code it reads from the internet request (§8-1 · §8-7 · §8-8) |
| Contacts · call logs · text messages | Not collected | The app has no such permission |
| Photos · camera · microphone · device files | Not collected | The app has no such permission |
| List of installed apps | Not collected | We do not look it up |
| Behavioral analytics · usage statistics | No third-party analytics tools | We do not use third-party analytics tools. The only things our server counts directly are visits (§8-7), versus records (§8-8), and totals that do not point to anyone: the ranking distribution (§8-1), the number of times each pack was sent out (per pack, version and day) and the number of times each app error occurred (per error, day and app version · §8-12) |
Permissions the app uses
The only permission we ask you for separately is notifications (Android 13 and later), and we ask not at installation but after you finish the tutorial or when you turn notifications on in the settings. You can still play the game if you refuse it. All other permissions are normal permissions that Android grants automatically; what each one is used for is shown below.
| Permission | Used for |
|---|---|
| Internet · network state | The sixteen kinds of communication listed above, such as ads, purchase verification and new pack downloads |
| Notifications · re-scheduling after reboot · wake · foreground service | Showing notifications scheduled on your device at the right time (§8-2) |
| Google Play billing | Buying paid items (§7) |
| Advertising ID · ad-related services · install referrer | Google AdMob ads (§5) |
| Account credentials | The Google sign-in window (§8-11). The same library also adds biometric-related permissions, but the app does not use biometrics |
The app has no location, contacts, camera, microphone or storage permission. You can check this yourself in the app info on the Play Store (§16).
3. Information exchanged — all of it
| What | Where to | Why · when | Do we receive it? |
|---|---|---|---|
| Advertising ID (AAID) · device and app information · IP address · diagnostic and performance information | Google AdMob | To choose and show ads and to prevent invalid clicks | No. We see only totals such as impression counts |
| The letters of a single word (e.g. 강아지) | Your device's speech engine | To read it aloud | No (§6) |
| Device metadata · app version · list of installed modules and asset packs (this app's own) | Google Play on your device → Google | To check whether a new version exists and its expected size — when the app starts | No. Of Google Play's answer, only whether a new version exists and its version number and name are used on the device (§8-14) |
| Product ID · purchase type · purchase token · (for coin bundles) a grant-confirmation flag and a 16-character random code created by the device | Our server (Cloudflare) | To check with Google that the purchase is genuine — when you buy a paid item · when the app restores or re-checks the purchases you already have at start-up | Yes (§7) |
| The random 12-character ID (invite check) · invite marker (the inviter's and the new device's 12-character IDs) | Our server (Cloudflare) | Invite gifts — when you start the app · when the app was installed through an invite | Yes (§8) |
| A random ask number (12 characters) · a key (our server keeps only its hash) · records of hearts friends sent (ask number · time · a hash of a random token from the sender's browser, mixed with the ask number) | Our server (Cloudflare) | Hearts from friends — when you tap "Ask friends for a heart" · when a friend sends a heart from the link · when you start or return to the app after asking | Yes (§8) |
| That level's score — a single number | Our server (Cloudflare) | "Top X%" — each time you clear a level | Yes. Only the number, with no identifier (§8-1) |
| Word ID · language · reason · app version | Our server (Cloudflare) | To fix wrong translations — only when you report one | Yes. No identifier (§8-3) |
| — (nothing is sent; download only) | Our server · image server | Downloading new packs and word pictures · checking for notices that the Terms or this Policy are changing | — (§8-4) |
| Purchase token | Our server (Cloudflare) | Returning-player gift · refund check — when an earlier purchase comes back · when you restore purchases | Yes (§8-5 · §8-6) |
| The random 12-character ID (the server sets the date and reads the two-letter country code from the request) | Our server (Cloudflare) | Visit statistics — once a day | Yes (§8-7) |
| Seven skill numbers · level number · time rule · layout number · progress curve · (when finding an opponent in real time) board size · difficulty · board layout name · the previous temporary number when you re-join the queue — the server reads the two-letter country code from the request | Our server (Cloudflare) | Finding a versus opponent — when you enter the arena | Yes. No identifier (§8-8 · §10-1) |
| Coupon code · the random 12-character ID | Our server (Cloudflare) | Granting coupon benefits — when you enter a code · when you start the app after that | Yes (§8-10) |
| Google verification token (ID token) · a one-time check value · the sign-in method · a single true/false for "aged 14 or over" · the random 12-character ID / after that, the sign-in session | Our server (Cloudflare) | Creating an account — only if you choose to sign in · checking the sign-in when you start the app while signed in | Yes (§8-11) |
| Error type · error message · stack (where in the code the error occurred) · names of recent screens (up to 6) · app version · whether it is a development build · OS version · device model · native language · how many seconds after start-up it occurred | Our server (Cloudflare) | To find and fix the causes of app errors — only when an unhandled error occurs in the game code (aged 14 or over only · can be switched off in Settings) | Yes. No identifier (§8-12) |
| Order ID · a 16-character random code for that attempt · a list of purchase-token hashes (first 16 characters of SHA-256) of the purchases whose coins were received on this device | Our server (Cloudflare) | Recovering coin bundles bought with real money — only when you enter an order ID | Yes (§8-13) |
| A list of purchase-token hashes (first 16 characters of SHA-256) of the purchases whose coins were received on this device | Our server (Cloudflare) | Taking back refunded coin bundles — when the app starts (only if this device has received coins from a purchase) | No. Used only for matching and not stored (§8-13) |
| For each coin-bundle order bought with real money: the purchase-token hash (first 16 characters of SHA-256) and the number of unspent coins | Our server (Cloudflare) | So that order-ID restore gives back "only unspent coins" — when coins bought with real money go down | Yes. Only the remaining number (§8-13) |
| Sign-in session · one copy of your game progress and a summary (total stars · number of coins) · the key of the device that holds the progress | Our server (Cloudflare) | Account progress saving and device transfer — only if you sign in and choose "Save" (the request asking whether saving is switched on is sent right after signing in and when you open the account window · it carries no progress) | Yes (§8-15) |
Your game progress records (cleared levels · stars · word collection · coins · items) do not leave your device except as listed in the table above — a copy is saved to your account only if you sign in and choose "Save" (§8-15). Your phone number and precise location are not included in any request. Your name may be contained in Google's verification token if you choose Google sign-in, but we neither use nor store it (§8-11).
4. Stored on your device
To continue a game, your progress has to be kept somewhere. That place is inside your device (the app's storage area). If you sign in with Google and choose "Save", a copy of the same progress is also saved to your account (§8-15).
| What | Examples |
|---|---|
| Progress | Cleared levels, stars, best scores |
| Game currency | Coins, hearts, heart refill time, item counts |
| Purchase status | Packs and patterns you own · the time you bought the Full Edition (the basis on which the Full Edition opens “the packs released up to then”) |
| Notice record | The numbers of the notices about the Terms or this Policy that you confirmed (§8-4) |
| Learning records | Words you got right on your own, word collection, memory stars |
| Settings | Native language, language you are learning, sound, low-stimulation mode, notifications |
| Customization | Outfits, poses, tile patterns, badges |
| Random identifier | A random 12-character string created by the device (§8) |
| Age band | One of "18 or over · 14–17 · under 14", and the month in which it changes to the next band (§4-1) |
| Sign-in information (only if you signed in) | The sign-in session · account ID · email · expiry time kept by the app, and the Google verification token · Google access token (if one was issued) · granted scopes kept by the Google sign-in module (§8-11) |
| Records for processing purchases | The ledger of purchases not yet completed and which purchase each enabled item came from (purchase tokens) · the 16-character random code used while a coin grant is being completed, with its purchase token (§7) · the list of purchase tokens first confirmed on this installation (for deciding the returning-player gift · §8-5) |
| Coin-restore records | Hashes of the purchase tokens (first 16 characters of SHA-256, up to 200, from the app version that added coin restore) of the purchases whose coins were received on this device · order IDs you asked to restore, with the 16-character random code of each attempt (up to the latest 32; the one for an order is deleted once its coins are received) · hashes of refunded orders already taken back (up to 200, so the same order is not taken back twice) · for each coin-bundle order bought with real money, the number of unspent coins and the number last reported (up to 50 orders) (§8-13) |
| Account progress link (only if you signed in) | Which account this device's progress belongs to (account ID · the key of the device that holds the progress · revision number) · your answer to "Save progress?" right after signing in and "Don't show again" · a temporary copy used while received progress is being installed (deleted once installed) (§8-15) |
| Unsent error reports | Up to 10 app error reports that could not be sent — sent and deleted the next time you start the app (§8-12) |
| New version notice record | The number of the new version for which you tapped "Later", and the time until which we will not ask about it again (one day later) (§8-14) |
If you delete the app, these records are deleted with it. If you sign in with Google and choose "Save", your game progress (stars · coins · collection, etc.) is saved to your account, and it moves to another device when you sign in there with the same account (§8-15). If you did not sign in or chose "Don't save", our server has no backup of your game records, so we cannot restore them. Items you bought directly with real money can be recovered separately — those other than coin bundles are remembered by Google Play and come back on the same Google account, and for coin bundles the unspent coins can be recovered once per order with the order ID (table below · §8-13).
4-1. On first launch we ask for your year and month of birth
When you first open the app — or once after an update if you were already using it — a screen appears asking for your year and month of birth. It appears once for everyone, whether or not you sign in.
- Why we ask — What we must observe differs by age. Google does not allow personalized ads for users under 18, and Google Play requires that users whose age is unknown be treated like children. In Korea, processing the personal information of a child under 14 requires the consent of their legal representative.
- What we keep — On your device we keep only one of "18 or over · 14–17 · under 14" and the month in which it changes to the next band. Your year and month of birth themselves are not stored.
- It never leaves your device — If you are under 18, your birth month could be counted back from "the month it changes". So we send this value neither to our server nor to Google. When you sign in, the only thing sent to the server is a single true/false: "aged 14 or over?".
- How age is calculated — During your birth month we treat your birthday as not yet passed, and add one year from the following month.
- It cannot be entered again — Once you enter it, this screen does not appear again. If you entered it wrongly, clear the app's data in your device settings and we will ask again (your game records will be deleted as well).
| Age band | Ads | Sign-in |
|---|---|---|
| 18 or over | Personalized ads may be shown (§5). In Europe · the UK · Switzerland, only if you have consented | You can sign in |
| 14–17 | Only non-personalized ads are shown | You can sign in |
| Under 14 | No ads are shown — the ads module itself is not started, and there are no buttons for watching ads | The sign-in button does not appear |
If you change device: what comes back and what does not
The rule is "what you paid with". Only things you bought directly with real money are attached to your account and remembered by Google Play.
| What | How it is bought | If you change device |
|---|---|---|
| Remove Ads · Time Spirit · Defense Tower (Carrier station) | Real money | Comes back — if you reinstall with the same Google account, the app restores it automatically |
| Unlimited hearts (subscription) | Real money · monthly or 1-week subscription | Comes back — Google Play holds the remaining period |
| Full Edition (whole-app purchase) | Real money | If you reinstall with the same Google account, the app restores it automatically, and the packs released up to the time you bought the Full Edition are unlocked as well (after those packs have been downloaded) |
| Language pack | Real money | Comes back — if you reinstall with the same Google account, the app restores it automatically |
| Packs bought individually with real money (always-on-sale word packs · map packs · tile skins) | Real money | Comes back — if you reinstall with the same Google account, the app restores it automatically (map packs and skins open after the pack has been downloaded) |
| Coin bundles | Real money | Do not come back on their own — they are consumable items that are used up, so Google Play does not restore them. Instead, if you enter the Google Play order ID (GPA.…) in the app's Settings → Restore coins, we give you that order's unspent coins again, once per order. Coins you have already spent cannot be recovered, nor can refunded orders or purchases recorded on this device as having already received their coins (§8-13). If you signed in and chose "Save", your remaining coins move together with your game progress below |
| Things bought with coins (word packs · map packs · items · outfits · tile patterns, etc.) | In-game coins | If you signed in and chose "Save", they move with your account (§8-15) · otherwise they do not come back — what you spent coins on is recorded only on your device |
| Game progress (levels · stars · word collection · hearts) | — | If you signed in and chose "Save", it moves with your account (§8-15) · otherwise it does not come back |
| Unlimited-hearts period received with a coupon | Coupon | Enter the coupon code again and the remaining period moves over (§8-10) |
Purchase restoration is attempted automatically when you start the app. If the internet is briefly unavailable, it may fail to restore, but anything already switched on is not taken away — it tries again the next time you start the app. If you switch to a different Google account, earlier purchases cannot be found.
5. Ads (Google AdMob)
You can get this app for free; it is run on ads and optional purchases. You can play every level to the end without paying.
Which ads appear and when
| Type | When | Reward |
|---|---|---|
| Interstitial ad | Once every time 3 levels have ended. It appears only after a level ends and never interrupts play | None |
| Rewarded ad | Only when you tap a button (get hearts · reward ×2 · one more spin) | Granted only if you watch to the end |
If you are under 14, neither type of ad appears — the ads module itself is not started (§4-1).
Information processed for ads — automatic collection
To show you ads, Google collects and uses, through the ads module (SDK) in the app, the advertising ID (AAID), device and app information, IP address and diagnostic and performance information (whether an ad loaded properly, errors, response times, etc.). This processing follows the Google Privacy Policy and How Google uses information from partner apps. This information does not come to our server. We see only totals such as impression counts. This app does not use cookies.
Personalized ads
Personalized ads may be shown only to those who told us they are "18 or over" (§4-1). If you are under 18 or your age is unknown, every ad request is sent with a non-personalized ads flag. If you are 18 or over, that flag is not added; whether Google then shows personalized ads based on your app usage information (behavioral information) depends on your region and your choices.
- European Economic Area · UK · Switzerland — only if you consent in the consent dialog below.
- Some US states — Google shows an opt-out dialog under that state's law.
- Other regions — if you choose "Delete advertising ID" or "Opt out of Ads Personalization" in your device settings, personalized ads are not shown (see below).
Even for non-personalized ads, Google may process the information above to prevent ad fraud, cap ad frequency, estimate approximate location (IP-based) and so on.
In Europe and the UK, we ask for consent first
When you first open the app in the European Economic Area (EEA) or the UK, a consent dialog about ads appears. It is shown by Google's User Messaging Platform (UMP). This dialog appears after the age check, and only to users aged 14 or over.
- You can still play the game without consenting. Ads then appear in a non-personalized (or limited) form.
- We do not request ads before the consent result is confirmed. If we could not ask you (for example, when there is no internet), the ads module is not started.
- Even non-personalized ads use the advertising ID for frequency capping and aggregation, so we ask for consent. If you are 18 or over, your answer in this dialog also decides whether ads are personalized.
- You can change it at any time — open it again from "Ad consent settings" in the app's settings (shown only in regions where consent is required). If you withdraw consent, the consent used for personalized ads is withdrawn from that point on. Ads themselves may continue to appear in non-personalized form.
How to delete the advertising ID or turn off personalized ads
In Android Settings → Privacy (or Google) → Ads, you can choose "Delete advertising ID" or "Opt out of Ads Personalization". It is a device setting, so you can change it at any time.
Remove Ads
If you buy "Remove Ads" in the shop, the interstitial ads that appear every 3 levels no longer appear. Rewarded ads that you tap yourself (get hearts, etc.) remain.
6. Read aloud (TTS)
When a word you got right is read aloud, the letters of that single word (e.g. 강아지, dog) are passed to the speech engine installed on your device. They do not pass through our server. Only words included in the game are passed; nothing you typed is passed. Your device's speech engine (e.g. Google Speech Services) may use the network on its own, and that processing follows the policy of the engine's provider. If you turn off read-aloud in the app settings, nothing is passed.
7. Payments
This app offers optional purchases. You can play every level to the end without buying anything.
| Paid with | What |
|---|---|
| Real money (Google Play Billing) | Coin bundles · Remove Ads · Time Spirit · unlimited hearts (monthly subscription · 1-week subscription) · Defense Tower (Carrier station) · Full Edition · language pack |
| In-game coins | Word packs · map packs · items · outfits · poses · tile patterns |
Language pack
This product lets you choose the language shown on the answer side of word cards. Currently we sell only one: German. Korean, English, Romanian and Japanese, which come with the app, are free. All 13 menu languages (native language) are free. The German words are already inside the app and the purchase unlocks them, so the only new information exchanged for this purchase is the purchase verification below.
Payment method information
All purchases are made through Google Play Billing. We do not receive, see or store your card number, bank account or billing address. Payments and refunds are handled through Google Play.
Purchase verification — what goes to our server
We can give you the item only after checking that the purchase is genuine. So right after payment, and when the app restores or re-checks the purchases you already have at start-up, we send the following to our server.
| What is sent | Example |
|---|---|
| Product ID | coins_800 |
| Purchase type | inapp / subs |
| Purchase token (receipt string) | A string Google issued for that single payment |
| Grant-confirmation flag · 16-character random code (coin bundles only) | A random string the device created for that purchase — if the app closes during the grant and checks again later, it makes sure the same purchase is not granted twice. It is deleted from the device once the grant is finished |
The server asks the Google Play Developer API about the received token and grants the item only if it is genuine; the server also decides the amount granted. So that the same payment is not granted twice, we record the purchase token · product ID · purchase type · amount granted · verification time and, from Google's response, the order ID · payment time · payment state · region code (country) · purchase kind (whether test or promotion) · test purchase flag. For coin bundles, we separately record the purchase token · time the first grant was decided · the 16-character random code above. These records contain no name, email or account and are not linked to a Google sign-in account. However, if you sign in and choose "Save", the progress copy saved to your account contains the hashes of the purchases whose coins were received on this device (§8-15), so by matching those hashes against these records we could link those purchases to the account. We do not do such matching. They are kept for 5 years (§10). The order ID in these records is also used to find your purchase when you ask for a coin restore (§8-13).
8. Invites · Random identifier
On first launch the app creates one random 12-character ID and keeps it on your device. It is a random value with no relation to your name, device number or account. However, because it keeps pointing to the same device, we regard it as pseudonymized personal information under the European (GDPR) standard and treat it that way. This value is used for invites (this section), visit statistics (§8-7), coupons (§8-10) and Google sign-in (§8-11).
- When you tap "Invite a friend" in the shop, your device's share window opens with an invite link containing this 12-character ID. Where it goes is decided by the app you choose, and it does not come to us.
- When you tap "Ask friends for a heart", your device creates a random ask number (12 characters) and a key, separate from this 12-character ID, and registers them on our server (each tap re-confirms the same number). We do not keep the key itself — only its hash. If you are under 14 or your age is not yet known, the "Ask friends for a heart" button does not appear and nothing is sent to our server (§4-1). Your device's share window then opens with a link containing the ask number. Where it goes is decided by the app you choose, and the message does not come to us.
- When the person who received the link taps "Send a heart" on the page on our website, the ask number, the time and a hash of a random token created by that browser, mixed with the ask number, are recorded on our server. That random token stays in the sender's browser storage so that they can send to the same person only once a day; it disappears when they clear the site data in their browser. The sender needs neither the app nor a sign-in, and we do not record their name, account, contact details or IP address (we only count requests for a short time to prevent abuse). One person can send to the same friend once a day, up to 30 hearts a day can newly arrive for a person (a day starts at 9:00 a.m. Korea time), and the sender's hearts do not go down.
- If you have tapped "Ask friends for a heart" at least once, each time you start or return to the app your device uses the ask number and key to ask our server whether hearts have arrived and collects them. Heart gift records are deleted automatically after 30 days; an ask number that has received no gifts and has not been used for 30 days, and any ask number not used for 1 year, are deleted.
- When a friend installs the app through an invite link and opens it for the first time, "the inviter's 12-character ID" and "the new device's 12-character ID" are sent to our server. This is so we can give the inviter a gift. Only the two random values are exchanged — no name, contact details or advertising ID.
- Each time you start the app, this 12-character ID is sent to our server as a query to check whether there is a gift to receive. It is sent even if you have never tapped the invite button. The reply is only a number: "how many gifts to receive".
- Invite records are deleted automatically 30 days after the gift is granted, and uncollected ones after 1 year.
- If you clear this app's stored data in your device settings, the 12-character ID disappears and a new value is created, and we cannot link the old value to the new one. If you want stored invite records deleted, send that 12-character ID to [email protected].
8-1. Rankings — "top X%"
When you clear a level, a single score for that level goes to our server. This is to compare it with the score distribution of people in the same country and show you "top X% in your country".
- Nothing goes with it — no random 12-character ID, no advertising ID, no account.
- The only thing left on the server is a total: "how many people in which score band of which country". We do not store who submitted it.
- The country is the two-letter country code automatically attached to the internet request, as read by the server. We do not store the IP address and do not use the location permission.
- Because it is a total not linked to any individual, there is no separate "my record" to delete.
8-2. Notifications — shown by your device itself
Notifications such as "Your hearts are full" or "Today's missions are still waiting" are scheduled by the app inside your device with a time and a text, and your device shows them on its own at that time (local notifications). Our server is not involved, and no push token is created or received. Notifications still appear in airplane mode.
- They are shown only between 9 a.m. and 9 p.m., no more than once a day. Even if you stay away for a long time, we remind you only twice, at 3 days and at 7 days.
- Turning off "Reminders" in the game settings also deletes the ones already scheduled. You can also turn them off in your device's app notification settings.
- We do not use the permission for alarms at exact times (SCHEDULE_EXACT_ALARM).
8-3. Word error reports — you only choose
If a word's meaning looks wrong, you can tell us by long-pressing that word in the collection.
| What is sent | Example |
|---|---|
| Word ID | n_volleyball |
| Language | en · ro · ja |
| Reason | One of: wrong meaning · spelling error · awkward · picture does not match |
| App version | 1.0.0 |
| Selected option number (second step only) | The number of an option we created |
- There is no free text. We did not even create a field to type in.
- We do not send a device number, advertising ID, account, device model, location or progress.
- When reports pile up for the same word, we create alternative options, and the app downloads only the text of those options.
- Report records are deleted automatically after 1 year.
8-4. New pack downloads — download only
- When you start the app — the app only asks for the list of what is new (word packs · map packs · tile patterns) and lets you know if there is something new.
- Notices about changes to the Terms or this Policy — when you start the app, it downloads the notice file from our site (
k-tile.pages.dev) and, if there is a notice you have not confirmed yet, shows it in a window. Nothing is sent; only the numbers of the notices you confirmed are written on your device. - When you have no downloaded packs at all (usually right after installing), it downloads the contents on the spot as well. Otherwise, packs are downloaded when you tap them in the shop.
- If the prices or bundle sizes of items bought with coins have changed, the app downloads that price list without a notice when it starts and uses it from your next purchase. Items you have already bought stay as they are.
- Word card pictures for word packs you bought are downloaded from our image server (
k-tile.pages.dev). The pictures for the free animal pack are included in the app. - Nothing is sent. No word ID, progress or identifier is attached. What is downloaded is stored only on your device.
- To deliver files, your IP address reaches the server. We do not read or store it; Cloudflare, our infrastructure provider, processes it during transmission (§9).
- Without internet, nothing is downloaded, but the game keeps running as usual.
8-5. Returning-player gift — only the purchase token is sent
If you reinstall the app or change device and your earlier purchases come back but your game progress starts from the beginning, we let you skip the tutorial and give you 500 coins. At that time we send the purchase token to check "has this purchase already received the gift?". We do not send a name, account or identifier. Because a purchase token keeps pointing to the same purchase, we treat it as pseudonymized personal information under the European (GDPR) standard. The records are kept for 5 years (§10).
8-6. Refund check
A refunded item should be switched off along with the refund. Our server asks Google for the list of refunds once a day and keeps it, and the app only asks "has this purchase token been refunded?" when restoring purchases. The reply contains only those of the tokens you sent that have been refunded. Refund records contain the purchase token · order ID · refund time · the reason code given by Google · Google's value indicating which side initiated the refund · the time we first received it, and are kept for 5 years (§10). If the check cannot be made, nothing is switched off. If a coin bundle was refunded, coins are taken back from your remaining coins as described in §8-13.
8-7. Visit statistics — counting how many people come
To keep improving the game, the app tells our server once a day that "this app was opened today". Even if you open it ten times a day, it counts once.
- What is sent: the random 12-character ID (§8) only. The server records the day's date and the two-letter country code of the internet request with it. The time, what you did and how long you played are not sent.
- What we can learn: things like "how many devices came yesterday", "the share of first-time visitors who came back" and "how many devices from which country". We count installations, not people.
- Records are deleted entirely, together with that identifier, 400 days after the last day you visited (§10).
- If you clear the app's data, you are counted as a different installation.
We do not use third-party analytics tools (such as Google Analytics). The app build contains a Facebook login SDK for another sign-in option, but it does not start on its own and none of our code calls it, so no information goes out through that SDK. If we turn on an analytics or sign-in tool, we will state it in this policy and in Google Play "Data safety" before turning it on.
8-8. Versus matches (VS) — sent when you enter the arena
This feature lets you solve a level side by side with an opponent of similar skill. Entering an arena level next to the Star Route means using this feature, and the last step of the tutorial is also playing one level in the arena. If you do not start an arena level, nothing in this section is sent.
- Seven skill numbers — one for each of the seven word packs: "the number of words you got right on your own without hints" (e.g. 3·0·12·0·5·1·0). Which words they are is not sent.
- Level number · time rule (whether the clock runs in that level) · layout number (0–7) — to compare people who solved the same puzzle.
- Two-letter country code — to find you someone from the same country first; the server reads it from the internet request. We do not store the IP address.
- Only when finding an opponent in real time: board size · difficulty · board layout name, and the previous temporary number when you re-join the queue (§10-1).
- Only when you clear the level: that level's progress curve — at which second, which pair number, and which two cells (cell numbers) you matched. This curve becomes the opponent for the next player. It contains no words and no screen coordinates.
- We do not send the random 12-character ID, name, email, account, advertising ID, stars or coins. So even if the same person plays versus many times, we cannot link the matches together.
If there is no opponent, you play against the device instead of a person, and the screen says "Device" so it does not pretend to be a person. The curves kept on the server are limited to the latest 30 per level · rule · country, and separately they are deleted after 90 days (§10). The temporary records used when finding an opponent in real time are described in §10-1.
8-9. Public word-review page — a web page outside the app
This is a public web page (ktile-api.softbackdev.workers.dev/words) for people who check, in many languages, whether word meanings are correct.
Using the app alone has nothing to do with this section; it applies only when you open this address yourself.
- What you send: word ID · language code · corrected meaning (up to 40 characters) or a "correct" mark · reason (optional, up to 200 characters).
- There are no name, email or account fields, and no cookies are used. The language you chose and the picture size are stored only in your browser.
- Because anyone can submit, we have to prevent spamming, so we keep the request's IP address only after converting it into an irreversible value (the first 16 characters of a SHA-256 hash). The original address is not stored. Its only use is counting "how many times were submissions sent in an hour", and it is deleted after one day (§10).
- Your suggestions contain no value pointing to you, so we cannot find and delete "what I sent".
8-10. Entering coupons — the code and the device's random ID are sent
You can receive an unlimited-hearts period with a coupon code.
- When you enter a coupon code — the coupon code and the device's random 12-character ID (the random 12-character ID of §8) are sent.
- After that, when you start the app — only the random 12-character ID is sent, to recheck the remaining period. The server decides the period, to prevent the period from being extended by changing the device clock.
- If you have never entered a coupon, this request is not sent.
- The server does not store the coupon code as it is; it keeps only a value scrambled so that it cannot be reversed. The only other things kept are which device used it and when (the random 12-character ID · time) and until when it is valid.
- If you change device, you can enter the same code again to move the remaining period. Only one device holds it at a time; once moved, it ends on the previous device. A code whose period has ended is not accepted.
- Retention: used coupons are deleted after 1 year, and coupons that expired unused after 90 days (§10).
8-11. Google sign-in — optional
You do not have to sign in. You can enjoy the whole game without signing in. At present, only a Google account can be linked. If you choose "Save" after signing in, your game progress is saved to your account and moved when you change device (§8-15). The sign-in window tells you so first.
What is sent when you sign in
- The verification token issued by Google (ID token) — a value signed by Google stating "this person is the owner of this Google account". It contains the Google account identifier and the email, and Google may also include the name and profile picture. After checking that the token was genuinely issued by Google, the server uses the identifier and the email, stores the email only if Google says it is a verified email, and does not store the token itself or the rest.
- A single true/false for "aged 14 or over?" — derived from the age band set on first launch (§4-1). Your year and month of birth are not sent.
- The device's random 12-character ID (§8), a one-time check value the app creates for each sign-in window (so the same token cannot be reused), and the sign-in method (
google). - Your password never comes to us — you enter it only on Google's screen. We do not request access to contacts, Google Photos, Calendar or Drive. The Google sign-in module also requests the basic profile (name · profile picture), and the app uses only the email from it.
- While you are signed in — when you start the app, the sign-in session is sent to check that the sign-in is still valid. The server then updates the last-used time.
What the server keeps
- The link between the account ID (random) and the Google account identifier · the time it was linked.
- Email — stored only if Google reports it as a verified address; otherwise left empty.
- Account status (active · suspended) · sign-up time · time of the "aged 14 or over" confirmation · last sign-in time · re-join marker (if you deleted your account and signed up again, the time of that — §11-1).
- Sign-in session — not the original but an irreversibly scrambled value, the random 12-character ID (§8) of the device that opened that sign-in, and the times it was created, expires and was last used — 7 days.
- Sign-in log — the time and type of each sign-in · new sign-up · rejection · sign-out · deletion · re-join · restore · emptying the vault, the account ID, the sign-in method and the rejection reason code — 90 days. The email · Google identifier · IP address · the device's random 12-character ID are not recorded.
Your name · profile picture · contacts · year of birth are not stored on the server. The list above (kept in the deletion vault for 30 days if you choose "Keep 30 days, then delete" when deleting your account) and the single hash line that remains after account deletion (§11-1) are everything.
Under 14
The sign-in button does not appear (§4-1). The server also does not create an account without the "aged 14 or over" confirmation.
Deleting your account
You can delete it inside the app (Settings → Account → Delete account) or outside the app at k-tile.pages.dev/en/account/delete.
Before deleting, you verify yourself with Google once more and choose "Keep 30 days, then delete" or "Delete permanently now". What is deleted and what remains is described in §11-1.
8-12. App error reports — sent only when an error occurs
To find and fix the causes of the game freezing or the screen behaving strangely, when an unhandled error occurs in the game code (JavaScript) of the Android app, a record of that error is sent to our server. If no error occurs, nothing is sent.
| What is sent | Example |
|---|---|
| Error type | One of: unhandled error · unhandled asynchronous error |
| Error message | The error sentence produced by the app's code (up to 300 characters) |
| Stack | Where in the code the error occurred — function names · file names · line and column numbers (up to 12 lines and 1,500 characters) |
| Names of recent screens | Up to 6 names of the screens passed through just before the error (e.g. map · stage:3 · shop) |
| App version · development build or not | In the form 1.0.0+3 · whether it is a development build for testing |
| OS version · device model | In the form Android 10 · SM-N960N |
| Native language | The menu language code you chose in the app (ko · en, etc.) |
| Time since start-up | How many seconds after you started the app the error occurred |
- What is not sent — No device number, random 12-character ID (§8), account, advertising ID, email or game progress is sent.
- Nothing is sent if you are under 14 or your age is not yet known (§4-1). The age band at the moment the error occurs is checked, and when nothing is sent, nothing is kept on the device to send later either.
- What the server does — It discards everything except the fields above and, in the text, removes addresses (URLs), anything in the form of an email address, anything in the form of a Google Play order number, runs of 7 or more digits (including ones split by hyphens or spaces) and unbroken strings of more than 40 letters and digits before recording it. It then groups "the same error · the same day (UTC) · the same app version" into one row and only counts how many times it occurred. Whether two errors are the same is decided by a hash the server makes from the error type, the message and the first line of the stack; the row keeps only the first record received that day, together with the times it was first and last received that day.
- IP address — Used only for rate limiting, to stop floods of requests, and not stored (§13).
- How much is sent — The same error is sent once per run of the app, and at most 8 reports per run. Reports that could not be sent (for example, without internet) are kept on the device, up to 10, and are sent and deleted the next time you start the app.
- Retention — Deleted automatically after 90 days (§10). Because there is no field pointing to you, we cannot find and delete "my error reports".
- How to switch it off — You can switch it off in the app's Settings → Send error reports (it is on at first). Once you switch it off, nothing is sent from then on, and reports waiting on the device because they could not be sent are deleted too. You can still use the game as usual.
- App versions — Versions of the app without this feature (those before the next update) send nothing.
Crashes that stop the whole app (native crashes) and "app not responding" (ANR) cannot be caught by this feature. We check those through the statistics (Android vitals) that Google collects from devices whose users have allowed usage and diagnostics data to be shared with Google automatically, and provides to developers together with details such as the device model, Android version and app version. That collection and processing follows Google's policy, and our app sends nothing additional for this.
8-13. Coin restore · Taking back refunded coins
Coins are stored on your device, so they disappear if you delete the app or change device or account (if you signed in and chose "Save", they move with your game progress · §8-15). Separately, coin bundles bought with real money can be recovered with the Google Play order ID.
If you enter the order ID (starting with GPA.) in the app's Settings → Restore coins, our server finds that order in the purchase verification records (§7) and gives you that order's unspent coins again, once. You do not need to sign in.
- Once per order · unspent coins only — Coins you have already spent cannot be recovered. Each time your coins go down, the app reports the number of unspent coins for each order to our server ("What is sent" below), and a restore gives you the number last reported. Coins you received for free are counted as spent first. Our server cannot know about coins spent without internet after the last report. Orders bought with app versions before this counting was added still give back all of that order's coins. You cannot receive them twice with the same order ID.
- If someone else seems to have received them first — If the app says the order "has already been restored" but you never restored it, please email us (§15) the order ID and the receipt email Google sent to your purchasing account, forwarded (you may hide the card digits, name and address). If it matches our purchase verification record (§7), we delete that order's restore record so that you can receive it once more; a new record is kept when you restore again. This is not an exception to "once per order" but a correction for a buyer who has not yet received them. The order ID works like a key to the coins, so please do not show it to others.
- When coins cannot be recovered — When you have spent all of that order's coins; refunded orders; purchases recorded on this device as having already received their coins (so that the same purchase is not received twice on a device where the app was not deleted · recorded from the app version that added coin restore); items other than coin bundles; and orders that are not in our server's purchase verification records (those records are kept for 5 years · §10). Paid items other than coin bundles are restored separately through Google Play, as in the "If you change device" table above.
- Things you bought with coins (word packs · map packs · items · outfits · tile patterns, etc.) do not come back. Please open them again with the recovered coins.
- What is sent — The order ID you entered · a 16-character random code the device created for that attempt (so that if you did not get the reply, asking again with the same code gets the same answer) · a list of irreversibly converted values (the first 16 characters of SHA-256 hashes, up to 200) of the purchase tokens of the purchases whose coins were received on this device. The random 12-character ID (§8), account, advertising ID and email are not sent. And when your coins go down — for each coin-bundle order bought with real money, the number of unspent coins and an irreversibly converted value of its purchase token (the first 16 characters of the SHA-256 hash, up to 50 orders). Our server records that number in a per-order ledger only in the decreasing direction (it never increases it) and keeps it for 5 years from its creation (orders with unspent coins are kept until they are closed · §10). This report carries no random 12-character ID, advertising ID or email. If the order is linked to an account (for example, bought while signed in), the app also sends your sign-in token so we can confirm it is that account's order; it is used only for that check and not stored (§8-16).
- What the server keeps — The order ID · that order's purchase token · the number of coins given back · the random code of that attempt · the time. The hash list you send is used only for the check and is not kept. The per-order ledger keeps the purchase-token hash · the number of coins first given · the number of unspent coins · the time it was created · whether the order has been restored (once an order has been restored, its ledger no longer accepts reports). These records contain no name, email, account number or device number. However, orders you bought or restored while signed in can be linked to your account through a separate link record (§8-16). Restore records are kept for 5 years from the restore and the ledger for 5 years from its creation (the ledger is kept until the order is closed if it still has unspent coins · §10).
- What stays on the device — The hash of the recovered purchase is added to the list of "purchases whose coins were received on this device", and the attempt code for that order is deleted (§4).
- The IP address is used only for rate limiting and is not stored. If you do not use coin restore, this request is not sent. Versions of the app without these features (coin restore · taking back refunded coins), i.e. those before the next update, do not send these requests.
- Taking back refunded coins — If this device has received coins from a purchase, when the app starts it sends only the same list of hashes to our server to check whether any of them is a refunded coin-bundle order. If so, that order's number of coins (or, if you recovered that order with its order ID, the number you recovered) is taken back from your remaining coins. If you have fewer coins left, we take back only down to 0 and do not recover coins you have already spent. You are told in an in-app notice when this happens. The server does not store this check, and the device records the hash of each order taken back so that it is not taken back twice (§4). If the check cannot be made (for example, without internet), nothing is taken back and it is checked again the next time you start the app.
8-14. New version notice — checked by Google Play on your device
So that you can get urgent fixes quickly, every time the app starts it checks whether a new version exists using Google Play's "in-app updates" feature. This check is not something our app sends over the internet: it asks the Google Play Store app on your device, and nothing comes to our servers.
- What Google processes — Google states that it processes device metadata · the app version · the list of installed modules and asset packs (this app's own) to determine whether an update is available and its expected size. Google processes this directly under the Google Play Terms of Service; it is not something we have entrusted to Google. Google states that this data is encrypted, is not transferred to third parties and is deleted after a fixed retention period; the retention period follows Google's policy.
- What our app uses — of Google Play's answer, only whether a new version exists and its version number and name. This is used on the device only to show a notice and is not sent anywhere.
- If a new version exists — we tell you in a notice. If you choose "Update", you get it on a Google Play screen; if you back out of that screen, you simply continue with your current version. If you choose "Later", we do not ask about that version again for one day (only the version number and a time are kept on the device · §4).
- How to turn it off — there is no setting to turn this check off. It runs as soon as the app starts, so it comes before the age check, and it runs the same way on the devices of people under 14. It does not run outside Android or on devices without Google Play services.
- App version — app versions without this feature (versions before the next update) do not make this check.
8-15. Account progress saving and device transfer — only if you sign in and choose "Save"
When you sign in with Google (§8-11), right after signing in we ask in a window: "Save progress to your account?" The window explains why we save it and what happens when you move to another device. However, if this device has no progress and your account has saved progress, we ask "Bring your progress here?" instead — if you bring it, saving is switched on as well; if you do not, the sign-in ends. If you choose "Don't save", the progress copy described below is never sent, and your progress stays only on this device, just as when you are not signed in. If you turn on "Don't show again" before choosing, we will not ask again for that account; you can turn saving on later with "Save progress to account" in the account window.
- What is sent before we ask — Right after signing in and when you open the account window, one request is sent asking whether saving is switched on and whether your account already has saved progress (if you are signed in it carries only the sign-in session; before signing in it carries nothing; it never carries your progress). If saving is switched off, the server receives and keeps nothing, and the window does not appear.
- What is sent — One copy of this device's game progress: stars · level records · best scores · the memory state of each word (which words you know and how well) · badges · collection · items · hearts · daily missions · attendance · the wheel · the tutorial · milestone gifts · the daily call · coins and the packs opened with coins · outfits · poses · the chosen tile pattern · whether the Defense Tower is switched on · the per-order ledger of "unspent coins" for coins bought with real money, and the lists of hashes of the purchases whose coins were received on this device and of refunded orders already taken back (§8-13 — so the same order is not recovered twice or taken back twice on a new device) · learning-habit settings (showing word cards · reading aloud, etc.), the language you are learning and whether the time limit is on. Also a summary shown in the choice window (total stars · number of coins). The sign-in session (§8-11) tells us whose it is.
- What is not sent — Device settings such as sound · volume · notifications · native language · entitlements to items bought with real money (Google Play restores those) · the random 12-character ID (§8) · the age band · ad consent.
- When — Right after you choose "Save" · at most once a minute if your progress has changed · when you send the app to the background · when your coins go up · when you sign out. In addition, a device linked to the account sends, when the app starts, a request asking whether the progress has moved to another device (only the sign-in session and this device's key).
- What the server keeps — For each account, one copy of the progress and one "copy before it was overwritten" · the summary (total stars · number of coins) · the hash of the key pointing to the device that currently holds the progress (the key itself stays on the device) · a revision number · times. They are deleted when you delete your account — if you choose "Keep 30 days, then delete", they are kept with the account in the deletion vault for 30 days and then deleted (§11-1).
- If you move to another device — When you bring the progress to a new device, the next time the previous device connects to our server (when the app starts or uploads progress) it first tells you in a window and is then signed out, and the achievements and all game data on that device are deleted (the progress remains in your account). What is deleted is the progress and learning-habit settings listed under "What is sent" above; device settings · the age band · the random 12-character ID · entitlements to items bought with real money remain. If both your account and the new device have progress, you choose one (they are not merged).
- If you sign out — Your latest progress is uploaded to your account and then this device's progress is deleted. If your latest progress cannot be uploaded (no internet, or our server cannot be reached, etc.), you are not signed out (so that progress that could not be uploaded is not deleted). On a device where you chose "Don't save", signing out does not delete your progress.
- If you delete your account — The progress copies on the server are deleted (Delete permanently now) or kept with the account in the deletion vault for 30 days and then deleted (Keep 30 days, then delete — they come back if you restore within that time), and this device's progress stays as that of a "user who is not signed in" (§11-1).
- Limits that cannot be removed — Play done on the previous device without internet is discarded the moment that device connects to the internet. If the previous device never connects to the internet, the progress remains on it (internet features cannot be used). If the Google account you signed in with differs from your Google Play payment account, items bought with real money do not follow.
- The IP address is used only for rate limiting and is not stored. App versions without this feature (versions before the next update) do not send these requests.
8-16. Coin ledger · account links · duel results — records kept on our server
Below, one by one, are the records kept on our server such as the coin ledger, account links and live duel results (added 2026-11-15). None of these records contains your name, email or advertising ID.
Coin balance notices — while coin-spending records are off
Even while coin-spending records are off on our server, the app tells our server how coins you bought with money are used. What it sends: a purchase identifier hash showing which purchase the coins came from, the number of coins used, a random transaction number so the same record is never counted twice and, where no transaction number could be made (an earlier app version or a storage error on the device), the number of coins remaining your device knows for that purchase. We do not send item codes, your name, email or advertising ID. Our server keeps the items above and the time we received it. We do not store records for purchases that are not in our ledger.
Why: so the same coins are never deducted or restored twice and so we can count the unspent coins of each order exactly. If the number of coins remaining your device reports is lower than our ledger, we do not deduct coins straight away; our support team checks it first.
These records are sent and stored even while coin-spending records are switched off, whether or not you sign in (records for a purchase linked to an account are stored only when you are signed in to that account, and the sign-in information used for that check is not stored). They contain no account number, but if you sign in and the purchase is linked to your account, the purchase hash can have them linked to that account, so we treat them as pseudonymised personal information. If you delete your account, that link is deleted but these records stay with the purchase hash.
Retention: deleted at the once-a-day cleanup 5 years after we received it. Records for an order that still has unspent coins, or that support has not finished checking, are not deleted until the coins are used up or the order is closed by restore or refund and the check is finished. Basis: Article 6 of the Enforcement Decree of the Korean Act on Consumer Protection in Electronic Commerce (records of payment and supply, 5 years).
Coin spending key — so nobody else can use coins you paid for
When you buy coins with money, the app creates a random key for that purchase on your device and registers it with our server. What is sent: a purchase identifier hash showing which purchase it is, the random key, and right after payment the purchase token that confirms the purchase is yours (used only for that check and not kept in this record). Our server keeps the purchase identifier hash, a hash of the key, how it was registered and the time we received it. We do not keep the key itself. The key is also sent with your coin-use records, only to check it, and is not kept. If you sign in and save your progress, the key is included in your account save so you can keep using those coins on another device.
Why: so someone who only has the purchase identifier hash cannot deduct that purchase's coins or block its restore. Restoring by order number does not need this key.
This registration happens even while coin-spending records are switched off, whether or not you sign in. The record holds no account number, but if you signed in and the purchase is connected to your account it can be linked to that account through the purchase hash, so we treat it as pseudonymised personal information.
Retention: deleted together with that purchase's coin ledger (§8-13) — the ledger is deleted at the once-a-day cleanup once 5 years have passed since it was created and that order's coins are used up or it is closed by restore, and this key record is deleted at the same time.
Link between a coin order and an account
If you buy coins while signed in, or a purchase is linked to your account through progress saving or support, our server keeps that order's purchase identifier hash, your account number and the time, so someone else cannot restore that order.
When you delete your account, we delete the link between your account number and the purchase identifier hash. At that time, we move the order's purchase identifier hash to a separate table (coin_lot_gone) to prevent it from being restored to someone else (see "Coin orders of a deleted account"). This does not retain the link to your account number.
Retention: while the account exists, deleted at the once-a-day cleanup 5 years after the link was made. If that order still has unspent coins, it is kept until the coins are used up or the order is closed by restore or refund. When you delete your account it is deleted at once.
Coin orders of a deleted account
When you delete your account, we move and keep only the purchase identifier hash of coin orders linked to it and the time of deletion, so those orders are not restored again with just an order number. The account number is not kept. Orders with this mark can be reopened only through support.
Retention: deleted at the once-a-day cleanup 5 years after the account was deleted. If that order still has unspent coins, it is kept until the coins are used up or the order is closed by restore or refund.
Account and purchase account tag
If you buy or restore coins while signed in, our server keeps the purchase account tag that is also kept in the Google purchase record (an irreversible 32-character value made from your account number), your account number and the time first recorded. This tells whether the purchase belongs to an account that still exists, and through it the purchase record can be linked to your account.
It is deleted when you delete your account. Retention: kept until you delete your account (at deletion only the tag is moved to the record of deleted accounts' purchase account tags below).
Purchase account tag of a deleted account
When you delete your account, we move and keep only that account's purchase account tag and the time of deletion, so purchases of the deleted account are not wrongly restored to someone else. The account number is not kept.
Retention: deleted at the once-a-day cleanup 5 years after the account was deleted. We matched the period during which a deleted account's purchase must not be granted again to the 5 years of the purchase verification records (§10).
Minimal proof of remaining coins
This happens only if the record clean-up feature is switched on. When a purchase record past its retention period is deleted and the order still has coins, we keep only the order number hash, the purchase identifier hash and the time created, so the right to restore is not lost. The original purchase token and order number are not kept.
Retention: deleted at the once-a-day cleanup once that order's coins are used up or the order is closed by restore or refund.
Complete Edition deduction records
When we deduct what you already paid from a Complete Edition purchase, our server keeps the purchase token of the purchase used for the deduction and its product, the purchase token of the Complete Edition and its product, the time, the amount deducted and, if the original product is later refunded, that time, so the same receipt is not used for another Complete Edition. Names, email addresses and account numbers are not included.
Retention: not deleted after a fixed period — deleting it would let the same receipt be used for a discount again, so we keep it for as long as that reuse must be prevented. If we become able to store less (for example an irreversible value instead of the purchase token), we will update this section.
Complete Edition refund queue records
For a Complete Edition purchase that was paid but finally rejected by the price check, our server keeps the purchase token, product, Google order number, reason for the rejection, processing state, attempts, last error, the deduction evidence in the request and times, in order to process the refund. Automatic refund requests go to Google only if that feature is switched on. Names, email addresses and account numbers are not included.
Retention: records still being processed (waiting or on hold) are kept until processing ends; finished records (refund requested, cancelled or failed) are deleted at the once-a-day cleanup 5 years after they were last processed. Basis: Article 6 of the Enforcement Decree of the Korean Act on Consumer Protection in Electronic Commerce (records of payment and supply, 5 years).
Returning-player gift request number
So that the same installation can receive the returning-player gift (§8-5) again if the app closes midway, our server stores the purchase token, a gift request number made by your device (a 16-character random value), and the time the record was created. The purchase token is used to verify the Google Play purchase. This table does not contain your name, email address or account number.
Retention: deleted at the once-a-day cleanup 5 years after it was recorded (the same period as the returning-player gift records, §10).
Real-time match result records
So both screens show the same result, the server keeps one row per match: the match number, the hashes of the temporary numbers of both players (with marks for who won and who left), the reason for the result, the time decided and whether each side has received it. Names, email addresses and account numbers are not included.
Cleanup rule: a match record becomes eligible for cleanup 60 seconds after the decision if both players received the result, or 600 seconds (10 minutes) after the decision if either player did not. It is not deleted exactly when it becomes eligible; it is deleted when a scheduled cleanup or match request runs the deletion. The 60- and 600-second thresholds therefore do not guarantee when deletion will finish.
Retention: deleted at the first cleanup after the criteria above have passed. The periodic cleanup runs once a day, so at the latest it is deleted within about a day of the decision.
9. Outsourced processing · Overseas transfer
We do not sell or provide personal information to third parties. To run the service, we use the facilities and services of the companies below, and these companies' servers are located overseas. Information is transmitted over the internet (HTTPS) when the app is used.
| Recipient | Items | Country | Purpose | Retention period |
|---|---|---|---|---|
| Cloudflare, Inc. (our server · database · website hosting) |
Purchase verification records · coin grant records · returning-player gift records · refund check records · invite markers · visit records · versus records · real-time waiting-queue records · word error reports · coupon records · public review suggestions · account and sign-in records (§8-11) · app error reports (§8-12) · coin-restore records (§8-13) · IP addresses when requests are exchanged (used only for transmission, rate limiting and determining the two-letter country code; not stored) | The United States and other countries where Cloudflare operates | Server operation · data storage · file delivery (outsourced processing) | The periods in §10. Cloudflare does not use this information for its own purposes |
| Google LLC (AdMob) | Advertising ID · device and app information · IP address · diagnostic and performance information | The United States and other countries where Google operates | Ad serving · measurement · fraud prevention (collected directly by Google through the ads module in the app) | According to Google's policy |
| Google LLC (Play Billing · Google sign-in) | Payment method information, Google account sign-in — you do these directly on Google's screens, and they do not pass through us | The United States, etc. | Processing payments · refunds, identity verification | According to Google's policy |
| Google LLC (Google Play in-app updates) | Device metadata · app version · list of installed modules and asset packs — processed directly by Google Play on your device, without passing through us | The United States and other countries where Google operates | Checking whether a new version exists and its expected size (processed directly by Google · not entrusted by us · §8-14) | According to Google's policy |
| Google LLC (Gmail · our support mailbox) | The email address of anyone who emails us · what you send (order ID · a forwarded receipt email, etc.) | The United States and other countries where Google operates | Receiving and answering inquiries (outsourced processing) — created only when you email us | The periods in §10 |
Recipients' contact addresses — Cloudflare, Inc.: 101 Townsend St, San Francisco, CA 94107, USA · Google LLC: 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA. Inquiry emails are transferred to Gmail when you send them.
If you wish to refuse — if you do not buy paid items, no purchase verification records are created; if you do not sign in with Google, no account information is created; and if you do not enter the arena, no versus records are created; and if you do not use coin restore, no restore records are created. The invite check at app start and the once-a-day visit record are made only with the random 12-character ID, and if you clear the app's data they are no longer linked. The statistics on crashes and "app not responding" (Android vitals) are collected directly by Google according to device settings and provided to developers; they do not pass through our app or server (§8-12). App error reports can be switched off in Settings → Send error reports, and they have no field pointing to you (§8-12). If you do not email us, nothing is stored in the support mailbox (but matters handled only by email, such as an order shown as "already restored", cannot then be handled). Even in these cases, you can still use the game as usual.
10. Retention and destruction
| What | Where | How long |
|---|---|---|
| Purchase verification records (the items in §7) | Our server | 5 years |
| Coin grant records (purchase token · time the first grant was decided · 16-character random code) | Our server | 5 years |
| Returning-player gift records (purchase token · time · number of coins) · their gift request numbers (§8-16) | Our server | 5 years |
| Refund check records (the items in §8-6) | Our server | 5 years |
| Coin-restore records (order ID · purchase token · number of coins given back · attempt code · time · §8-13) | Our server | 5 years from the restore |
| Per-order ledger of purchased coins (purchase-token hash · number of coins first given · number of unspent coins · time created · whether restored · §8-13) | Our server | 5 years from its creation — orders with unspent coins are kept until the coins are used up or the order is closed by restore or refund |
| Coin usage records (purchase identifier hash · number of coins used · random transaction number · number of remaining coins · time received · §8-16) | Our server | 5 years from receipt — kept until closed and checked if coins remain or support is still checking |
| Coin spending keys (purchase identifier hash · hash of the key · time received · §8-16) | Our server | Deleted together with that purchase's ledger |
| Links between coin orders and accounts (purchase identifier hash · account number · time · §8-16) | Our server | 5 years from the link (orders with unspent coins until closed) · at once when you delete your account |
| Account-to-purchase-account-tag mapping (tag · account number · time · §8-16) | Our server | Until you delete your account |
| Order marks and purchase account tags of deleted accounts (no account number · §8-16 · §11-1) | Our server | 5 years from the account deletion — order marks for orders with unspent coins until closed |
| Minimal proof of remaining coins (order ID hash · purchase identifier hash · time · §8-16) | Our server | Until that order's coins are used up or the order is closed by restore or refund |
| Complete Edition deduction records (purchase tokens and items of the deducted purchase and of the Complete Edition · time · amount deducted · §8-16) | Our server | Not deleted after a fixed period — kept while reuse of the same receipt must be prevented |
| Complete Edition refund-queue records (purchase token · order ID · reason for the rejection · processing state · §8-16) | Our server | In progress: until finished · finished: 5 years from the last processing |
| Live duel result records (match number · hashes of the temporary numbers · reason for the result · time · §8-16) | Our server | At the first cleanup after the criteria pass following the decision — within about a day at the latest |
| Inquiry emails (email address · what you sent · §15) | Our support mailbox (Google Gmail · §9) | 3 years after we finish answering — for complaints and disputes about transactions such as purchases, refunds and coin restore (Korea's Act on the Consumer Protection in Electronic Commerce) · 1 year after we finish answering for other inquiries |
| Invite markers (two random 12-character IDs) | Our server | 30 days after the gift is granted · 1 year if never collected |
| Word error reports | Our server | 1 year |
| Visit records (random 12-character ID · date · two-letter country code) | Our server | 400 days from the last day you visited |
| Versus curves (level · rule · skill numbers · country · progress curve · time taken) | Our server | The latest 30 per level · rule · country, and 90 days |
| Coupon records | Our server | Used: 1 year · expired unused: 90 days |
| App error reports (the items in §8-12 · one row per error, day and app version, with its count) | Our server | 90 days |
| Account (the items in §8-11) | Our server | Until you delete your account (30 more days in the deletion vault if you choose "Keep 30 days, then delete" · §11-1) |
| Account progress copies (progress copy · copy before overwriting · summary · key hash · revision number · times · §8-15) | Our server | Until you delete your account (30 more days in the deletion vault if you choose "Keep 30 days, then delete" · §11-1) |
| Sign-in sessions (including the random 12-character ID of the device that opened the sign-in) | Our server | 7 days |
| Sign-in log | Our server | 90 days |
| The single hash line that remains after account deletion | Our server | 1 year |
| Deletion vault (only accounts for which you chose "Keep 30 days, then delete" — account ID · Google account identifier · email · sign-up and confirmation times · account progress copies · §11-1) | Our server | 30 days from the day you delete — then deleted automatically |
| Point-in-time recovery records of the server database (past-point copies of the server data above · created automatically and cannot be switched off) | Our server (Cloudflare D1 · §9) | Up to 30 days — older ones disappear automatically · used only for disaster recovery |
| Public review suggestions (word ID · language · corrected meaning · reason) | Our server | Kept on an ongoing basis — this is data about words, not about people |
| └ The IP hash of that suggestion (first 16 characters of SHA-256) | Our server | 1 day |
| Game progress · settings · age band · sign-in information · records for processing purchases · coin-restore records · account progress link · unsent error reports (§4) | Your device | Until you delete the app (on a device that saves progress to the account, game progress is also deleted when you sign out or when the progress moves to another device · §8-15). The sign-in information kept by the app and what the Google sign-in module keeps are deleted together on sign-out or account deletion, and also when a sign-in does not go through or the server no longer has that sign-in. The coin-grant code is deleted once the grant is finished, a coin-restore attempt code once that order's coins are received, and unsent error reports once they are sent |
- Why 5 years — The Act on Consumer Protection in Electronic Commerce (전자상거래 등에서의 소비자보호에 관한 법률) requires records on payment and on the supply of goods to be kept for 5 years, and we need evidence to check in refund or double-payment disputes. Coin-restore records are kept so that coins are not given twice for the same order, for 5 years from the restore. The per-order ledger of purchased coins is kept so that a restore gives back only unspent coins, for 5 years like the purchase verification records.
- How we delete — Once a day, the server automatically deletes records whose period has passed, in a way that cannot be recovered. An account is deleted immediately if you choose "Delete permanently now", or at the first clean-up after 30 days if you choose "Keep 30 days, then delete" (§11-1). Deleted data can remain in the point-in-time recovery records for up to 30 more days from the day you delete and then disappears automatically.
- Inquiry emails — The mailbox is not deleted automatically; the operator deletes emails whose retention period has passed by hand every 3 months. Complaint and dispute inquiries about transactions (purchases · refunds · coin restore) are kept for 3 years because the Enforcement Decree of Korea's Act on the Consumer Protection in Electronic Commerce requires records of consumer complaints and dispute handling to be kept for 3 years.
- Records on your device — They are deleted when you delete the app or go to Android Settings → Apps → K-Tile → Storage → Clear data. In that case, your progress cannot be restored.
10-1. Temporary records when finding an opponent in real time
When people who are in the arena at the same time play each other right away, the server needs to know briefly "who is waiting right now". So the server issues a temporary number used only for that one match. This number is not linked to your device or to any other value, so the server cannot tell whether the same person has come again.
| What | How long |
|---|---|
Waiting-queue record (vs_queue) — temporary number · level number · level size and difficulty · time rule · layout number · skill numbers · two-letter country code · time you joined the queue;
after you are paired, the opponent's temporary number and the match number · time you started together · progress during the match (which pair number was matched with which two cells and when · whether finished · time taken · time of the last update).
The board layout name and the status (waiting · paired · done) are kept as well. No name, email, device number or IP is included |
Deleted immediately when both of you have finished the board or you stop searching. Otherwise, once 3 minutes have passed if you were waiting, or 30 minutes after the last update if you were in a match, the server deletes it when it handles the next arena request or at its once-a-day clean-up |
| Leave record — a single hash of the temporary number. Kept only when you leave on your own, to slow down repeatedly getting paired and then leaving right away | Used for 10 seconds, then deleted when the server handles the next arena request or at its once-a-day clean-up |
These records are also handled only within our server (Cloudflare), and no additional party is entrusted with them (§9). There is no chat feature.
11. Your rights
Under the Personal Information Protection Act (개인정보 보호법), you can request access to, correction or deletion of, or suspension of processing of your personal information, and you can withdraw your consent. Your legal representative can exercise the same rights. In this app, you can do so as follows.
| Right | How |
|---|---|
| Access | You can see the records on your device in the game screens at any time. If you signed in, you can see the linked email in the app's account window. For purchase verification records and coin-restore records, tell us the order ID on your Google Play receipt and we will check them |
| Correction · deletion | You can delete the records on your device immediately by clearing the app's data. You can delete your account yourself (§11-1). For invite records, tell us the random 12-character ID; for other server records, give us information we can verify; and we will delete them. You can also ask at any time to delete an account in the deletion vault permanently right away (§11-1). However, purchase verification records must by law be kept for 5 years, and inquiry emails about transaction complaints or disputes for 3 years, so they cannot be deleted during those periods |
| Suspension of processing · withdrawal of consent | You can turn off personalized ads with the ad consent settings or your device's ad settings (§5). You can turn off notifications in settings. For versus, coupons, sign-in, purchases and coin restore, the related processing does not happen if you do not use them. Account progress saving does not happen if you choose "Don't save" right after signing in; to stop saving, sign out (§8-15). App error reports can be switched off in Settings → Send error reports (they have no field pointing to you · §8-12) |
We do not hold names or phone numbers, so if you have not signed in we cannot find you by email. If you send a request to the contact in §15, we will reply within 10 days.
11-1. What remains when you delete your account
This applies only if you signed in with Google. If you did not sign in, there is no account at all.
- Where — In the app: Settings → Account → Delete account. Outside the app:
k-tile.pages.dev/en/account/delete. In the app (1.0.3 or later) and on the deletion page outside the app, you verify yourself once more by signing in with Google before deleting. You can also request it at [email protected]; an email request is deleted permanently right away and processed within 10 days. You can delete your account even after deleting the app. - You choose (nothing is pre-selected) — ① Keep 30 days, then delete: in case you deleted by mistake, your account details (account ID · Google account identifier · email · sign-up and confirmation times) and the account progress copies (§8-15) are kept separately in a "deletion vault" for 30 days from the day you delete. ② Delete permanently now: nothing goes to the vault and it cannot be restored. If you delete from an app version lower than 1.0.3, it is deleted permanently right away without the choice.
- As soon as you press it, you are signed out and the account can no longer be used. The Google account link · email · sign-in sessions · account · both account progress copies and the summary (§8-15) are removed from the account.
- Restoring — If you chose ①, when you sign in again with the same Google account in the app within 30 days, we ask "Restore / Start fresh". Restoring brings back your progress as it was when you deleted it; later progress is not included. If you created a new account with the same Google account in the meantime, that new account is deleted when you restore and only one remains (they are not merged). Choosing "Start fresh" empties the vault right away. Identity is verified only by signing in with Google — if you ask by email to restore, we will explain this method.
- Deletion vault — Its only purpose is restoring your account; it is not used for ads · statistics · analytics · re-signup checks. It is kept apart from other data, and at the first once-a-day clean-up after 30 days from the day you delete, the server deletes it automatically so that it cannot be recovered (anything past the deadline is not restored even before the clean-up). While it is kept, you can ask at any time to delete it permanently right away — verify yourself with Google on the account deletion page and press "Delete the kept account permanently now", or request it via §15 and we will delete it within 10 days.
- Point-in-time recovery records — Our server database (Cloudflare D1) automatically keeps records that can roll it back to any point in the past 30 days for disaster recovery, and this cannot be switched off. So whichever you choose, deleted data can remain in these records for up to 30 more days from the day you delete and then disappears automatically. These records are used only for recovering the server from failures, never for individual restores or other purposes, and if we ever roll back for disaster recovery, we delete again any account you had already deleted, using the deletion records in the sign-in log, so that it does not come back. Data disappears from all records at most about 60 days after you delete for ①, and at most about 30 days for ②.
- What remains (the same whichever you choose) — ① A single irreversible hash line made by mixing the Google identifier with a server secret (1 year) — to recognize people who deleted their account and signed up again. It does not stop you from signing up again. ② The sign-in log (90 days) — the account ID, the time and type of events, the sign-in method and a reason code (for a deletion, the number of links removed and whether it was kept) remain; no email or Google identifier is recorded in it. ③ For coin orders that were linked to the account, the order's purchase identifier hash and the account's purchase account tag (no account number · 5 years from deletion · order marks for orders with unspent coins until closed) — so that a deleted account's purchase is not granted again to someone else (§8-16). The link between the order and your account number itself is deleted at once.
- This device's game progress (stars · coins · collection) stays on the device as that of a "user who is not signed in". To delete it as well, clear the app's data.
12. About children
This app is intended for users aged 14 and over. Anyone who is interested in foreign languages and enjoys puzzle games is welcome. Google Play's age groups have no "14 and over" group, so we also selected the 13–15 group, and that is why we ask your age on first launch (§4-1).
If you are under 14, we show no ads, do not start the ads module, do not show the sign-in button or the "Ask friends for a heart" button, and do not send app error reports (§8-12 · for the statistics Google collects separately according to device settings, see the last paragraph of that section). So no personal information such as email is exchanged. Your year and month of birth are only turned into an age band on your device and are not sent. We do not knowingly collect personal information of children under 14. If you have concerns about your child's use of the app, please contact us via §15.
13. Safeguards
- Minimal collection — We do not take information we do not need in the first place. Information we do not have cannot leak.
- Encrypted transmission — All communication with our server is encrypted with HTTPS (TLS).
- Irreversible storage — Sign-in sessions, coupon codes, traces of deleted accounts and IP addresses on the public review page are kept as irreversibly scrambled values instead of the originals.
- Cleaning error reports — App error reports accept only fixed fields, and addresses (URLs), anything in the form of an email address, anything in the form of a Google Play order number, runs of 7 or more digits (including ones split by hyphens or spaces) and unbroken strings of more than 40 letters and digits are removed before they are stored (§8-12).
- Device isolation — Game records stored on your device are isolated per app by Android, so other apps cannot read them.
- Access restriction — The server's operator management screen can be used only by operators who know the key, and the key is accepted only in a request header, never in the address bar. It is not indexed by search engines.
- Request rate limiting — To stop machines from flooding us with requests, for some requests we use the IP address to count "how many requests came from the same place within a short time". That count disappears shortly afterwards, and the IP address itself is not stored (for the public review page hash, see §8-9).
- Automatic destruction — Every day, the server automatically deletes records whose retention period has passed (§10). Inquiry emails are deleted by hand by the operator every 3 months (§10).
- Access to the deletion vault — The server reads the deletion vault only to restore an account (signing in with the same Google account) and to clean up anything past its deadline. There is no screen for the operator to look into the vault. Only when you ask by email to delete your account do we check whether that email has a row in the vault and delete it, to carry out the request (§11-1).
- Distribution channel — The app is distributed only through Google Play.
14. When this policy changes
If laws or the app's features change, this policy changes too. When it changes, we post the new content and its effective date on this page. If you need a previous version, please request it via §15.
| Version | Effective date |
|---|---|
| v2.4 | 2026-11-15 |
| v2.3.1 | 2026-10-20 ~ 2026-11-14 |
| v2.3 | 2026-10-15 |
| v2.2 | 2026-10-11 |
| v2.1 | 2026-10-07 |
| v2.0 | 2026-10-06 |
| v1.0 – v1.9 | 2026-08-12 – 2026-10-05 |
15. Contact · Remedies for infringement of rights
| Chief Privacy Officer | 백영존 |
|---|---|
| [email protected] | |
| Response time | Within 10 days |
If you email us, we use your email address and what you send (order ID · a forwarded receipt email, etc.) only to answer and handle that inquiry; we do not use it for any other purpose or copy it elsewhere (keeping it for periods required by law is covered in §10). Retention periods are in §10; the mailbox is Google Gmail (§9).
If you need to report or get advice about an infringement of personal information, you can also contact the organizations below.
- Personal Information Infringement Report Center (개인정보침해신고센터) — privacy.kisa.or.kr / 118 (no area code)
- Personal Information Dispute Mediation Committee (개인정보 분쟁조정위원회) — www.kopico.go.kr / 1833-6972
- Supreme Prosecutors' Office Cyber Investigation Division (대검찰청 사이버수사과) — 1301 · Korean National Police Agency Cyber Investigation Bureau (경찰청 사이버수사국) — 182
16. How to check for yourself that this policy is true
- Look at the permissions — Play Store app details → App info → Permissions. There is no location, contacts, camera, microphone or storage permission (§2).
- Try airplane mode — Levels you have already downloaded run to the end without any connection. Only ads, purchases, rankings and new pack downloads do not work.
- Check the server status — Enter
https://ktile-api.softbackdev.workers.dev/v1/healthin your browser, and the server tells you what is switched on. - Look at the Data safety section — "Data safety" on the Play Store must say the same thing as this policy. If it differs, please let us know.
The Korean text is the original and prevails if the two differ. Full Korean document: here. Contact: [email protected] · [email protected] · Tel 010-2697-5218