Privacy Policy
Apprentice Witch Idle (견습 마녀 키우기) · Effective date: 2026-10-28
This is an English translation of the Korean original (privacy-ko.html). If the two differ, the Korean original prevails. The pages marked "(Korean)" are available in Korean only.
- What we collect: account and progress information, payment records, the country you connect from, the result of the genuine-app check, your age range (only for accounts where it was entered in version 0.1.3 and earlier), and (if you agreed) usage statistics and notification registration data, and (if you send one) the text you write in the feedback box. We do not collect your device's location, contacts, photos or microphone (section 3).
- Age to use: you must be 14 or older to use the Service. From version 0.1.4 the app does not ask your age and the start screen shows only a one-line notice (section 9).
- Retention: once account deletion is confirmed, we keep only a minimum set of items for 30 days and then delete or anonymize them. Payment records are kept for 5 years, dispute-handling records for 3 years, and login and access records for 3 months. Review and suspension marks and operator audit records are also kept for 3 years as dispute-handling records (section 4).
- Provision to third parties: we do not sell your information, and we do not provide information held on our server for advertising. However, information that the rewarded-ad SDK sends directly from your device to Google (advertising ID and the like) is processed by Google for advertising purposes (section 6, section 11-2).
- Transfer abroad: our servers are in AWS Japan (Tokyo), app update files come from Cloudflare (United States and others), and we use Google services (United States and others), including a Google Form that keeps a copy of the text you send in the feedback box (section 7).
- Consent and choice: we process usage statistics analysis and advertising notifications only if you agree, and you can use the game without agreeing (section 11-3, section 11-5).
- Feedback box: we process only what you agree to and choose to send on the feedback screen. Please do not write personal information (name, contact details and the like) in your feedback. When you delete your account, we erase the text on our server and delete its copy in the Google Form (section 11-13).
- Contact: promptrun.studio@gmail.com (section 12)
1. General
PROMPT RUN (PromptRun, "we") provides the mobile game "Apprentice Witch Idle" (package com.lunamethod.lanternmage, the "Service"). We set this policy to comply with applicable laws, including the Korean Personal Information Protection Act, and to protect your personal information. The Service shows rewarded ads (Google AdMob) only when you press the button yourself. For usage statistics analysis we use Google Analytics for Firebase. Ads are described in section 11-2, usage statistics in section 11-3, and push notifications that you turn on yourself (Android app, using Google Firebase Cloud Messaging) in section 11-5. The country determined from your connection location is described in section 11-6, the genuine-app check (Google Play Integrity) in section 11-7, automated decisions in section 11-8, the payment ledger in section 11-9, app permissions in section 11-10, and the age signal in section 11-11. The Service may be used only by people aged 14 or older, and from version 0.1.4 the app does not ask your age (section 9). The feedback box, which you use only when you send something yourself, is described in section 11-13.
2. Purposes of processing
- Providing the game: saving and syncing progress, checking connection times, running rankings, the Arena and the World Boss
- Account management: creating guest accounts, linking a Google account and switching devices, processing account deletion
- Payments: verifying purchases, granting items, revoking items on refund or cancellation, calculating and refunding unused paid diamonds on withdrawal, and managing take-backs and refund debt when Google or a card company returns the payment (section 11-9)
- Abuse prevention and security: server-side recalculation and verification, review flags, rate limits on account creation and sign-in, the genuine-app check (section 11-7), checks for abnormal increases
- Applying country-specific rules: deciding, by the country determined from your connection location, which items are sold and whether paid draws and payment features are provided, and preventing abuse that evades the restrictions by faking the country (section 11-6)
- Applying a stored age range: according to the age range (under 14 / 14-15 / 16-18 / 19 or older) calculated on the device from the date of birth entered the first time the app was started in version 0.1.3 and earlier, applying the purchase restrictions and the monthly Package payment limit to accounts whose range is under 19 (section 9). From version 0.1.4 the app does not ask your age and does not collect a new age range. For accounts in some countries, we check and record the age signal from Google Play, and for those accounts we do not offer paid draws and top-ups whatever the signal result is (section 11-11)
- Usage statistics to improve the Service (by analytics pseudonym): checking the tutorial, progress, currency flow, purchases, ad watching, errors, performance, abuse and refunds, plus daily counts of visits, new users and returning users (section 11-3)
- Event package conversion analysis: linking, per account, when an event package was first seen with the first purchase made afterwards (test payments excluded) to produce purchase-conversion statistics by country and language (section 11-3).
- Customer support: answering inquiries and handling deletion requests
- Legal obligations: keeping login and access records under the Korean Protection of Communications Secrets Act (section 4)
- Ad rewards: confirming the result of watching a rewarded ad, granting the reward, enforcing daily limits (section 11-2)
- Push notifications: delivering notices about maintenance, outages and changes to the terms, announcing events and benefits to users who agreed (advertising), and managing records of consent and withdrawal (section 11-5)
- Feedback box: using the feedback you choose to send to improve the game and fix bugs, enforcing the daily limit, and granting the first-feedback reward (diamonds by in-game mail) (section 11-13)
- App updates: delivering signed app update files (Cloudflare, section 7)
3. Information we process
| Category | Items | How collected |
|---|---|---|
| Account and credentials | Account number created by the server, device credential (only a hash of the secret is stored), creation time, account status, language (ko/en/ja/zh-TW), nickname shown on rankings (a combination of fixed words) | Created automatically as a guest account (on the start screen you choose Google sign-in or start as a guest) |
| Google sign-in (optional) | We receive only the unique ID of your Google account (the sub value in the ID token), and the server keeps only a SHA-256 hash of that value. The Google ID token is used only to verify signature, issuer and audience; we do not store the token, email, name or photo. We do not request your birthday, email, name, photo or any other Google account information, and any email or name contained in the token is processed only in memory during verification and is not stored. | Only if you choose to link Google (on the start screen or in the in-game settings) |
| Game progress | Full save data, command log, revision history, time-correction results, review flags, coupon codes entered and their use, mail claims, Arena and World Boss actions | Sent automatically while playing |
| Public display | The only information other players see in rankings, the Arena and the World Boss is a nickname made of two fixed words and a 4-digit number, a title, and a summary of witch rank, limit break and costume. There is no chat, friend list or free-text input. | Generated automatically |
| Payments | A SHA-256 hash of the purchase token (the token itself is not stored or logged), product ID, order ID, country code reported by Google Play, purchase time, price and currency reported by the app (reference only), grant ledger, diamonds granted per purchase (base amount and bonus amount), the usage record showing how spent diamonds were allocated to purchases, withdrawal and refund handling records, and the refund debt amount (section 11-9). Card numbers and other payment details are handled by Google Play and are not passed to us. | Sent automatically on purchase |
| Connection data | IP address: used briefly to rate-limit account creation and Google sign-in and to determine the country you connect from (section 11-6). When it is stored for this purpose, only an HMAC of the IP made with a server secret (IPv6 at /64) is stored, and the original IP is not stored. The login and access records we keep by law are separate (next row). The country you connect from (a two-letter country code) is stored as a property of the account. App version (to force updates). | Collected automatically per request |
| Login and access records (kept by law) | Login and access times, account number, and the IP address of the connection. Kept separately from the server operations logs, for 3 months (section 4). | Recorded automatically at login and access |
| Server operations records | Server logs (account number, revision, result, country code, part of a purchase-token hash, etc.), operator action audit records, account events (creation, deletion requests, etc.) | Generated automatically |
| Genuine-app check | The genuine-app attestation (token) issued by Google Play services, which our server sends to Google, and the result it gets back: whether the app is the genuine one distributed by Google Play, its package name, signing certificate fingerprint and version, and whether it was installed through Google Play. We do not store the raw attestation token. We keep the check result (pass or failure code, and time) with the account number as an abuse-check record. The record row of a check that did not pass (failure, limit, Google response error, exemption, etc.) also keeps the purpose, reason, platform, version code and the list of device verdicts that Google reported (section 11-7). | Automatically at sign-in and session renewal |
| Age range | The age range calculated on the device from the date of birth entered the first time the app was started in version 0.1.3 and earlier (under 14 / 14-15 / 16-18 / 19 or older). The date of birth is neither sent to nor stored on the server; only the age range is sent. From version 0.1.4 the app does not ask your age, so we do not collect it anew. | Entered by you in version 0.1.3 and earlier |
| Age signal (some countries) | The age signal result that Google Play reports: access status (shared, not shared, verification required, unavailable, unspecified), lower and upper age bounds, range source (A to D), significant-change status (pending, approved, declined), and the time our server received it. The age bounds, range source and change status are present only when the access status is "shared". Checked only for accounts in countries that use this signal, such as Brazil (section 11-11). | Checked automatically for accounts in those countries |
| Advertising (AdMob SDK) | Advertising ID, approximate location derived from the IP address, device and OS information, ad interaction, SDK diagnostics. Google's ad SDK sends these straight from your device to Google; our server does not receive them (section 11-2). Our server keeps only an ad reward record (ticket ID, placement, status, times, hash of the transaction ID). | In regions where consent is required (the European Economic Area, the UK, Switzerland and others), collected automatically only after you consent; in other regions, including Korea, collected automatically after the ad SDK has started |
| Push notifications (optional) | (1) Device registration: the notification registration token (FCM; an identifier for this app on this device), platform (Android), app version, language, time zone (offset from UTC, in minutes), account country, the times of registration, last check and status change, and the registration status (active, deregistered, replaced, reported invalid by Google, erased). (2) Consent: on/off and the time of change for informational notices, event and benefit notifications (advertising), night advertising and Idle Chest (advertising); the time of the last confirmation; the consent wording version; and a history row for every change (kind, value before and after, how it was changed, consent wording version, app version, country, language, time). (3) Send records: campaign number, receiving device, result (sent, failed, deferred), time, FCM message ID, and the number of messages sent per day. The Firebase installation ID is exchanged between the notification SDK on your device and Google; our server does not receive it. See section 11-5. | Sent automatically by the app after you turn notifications on (on Android 13 and later this includes allowing notifications on the device), and recorded automatically by the server when consent changes and when a notification is sent. No token is created before you turn notifications on |
| Usage statistics | Firebase app instance ID, the analytics pseudonym, and the contents of three kinds of records. (1) App usage statistics (sent directly to Google): screens, tutorial, progress, currency spending, summon and purchase flow (shop and limited-offer views, product ID and step), ad-watching flow, idle claims and time spent (connect and play time); sign-in, account-linking and notification-permission results; settings changes; error fingerprints and performance values; the automatic record of Google Play purchases (product ID, price, currency); account-state bands (account type guest/Google, purchase history none/1/2 or more, ads removed or not, rank and stage bands, whether the server is connected); device type, OS, WebView version, device tier, app version and language; the install source; and an approximate region derived from the IP address (we do not use the raw IP). (2) In-game activity records (our server): currency changes and a once-a-day snapshot of the currencies held; progress, summon, gear, dungeon, Arena, World Boss, mail, coupon and event reward results; purchase verification results (product ID, price and currency, the country Google Play reports, whether it was a first purchase or a test purchase), refusal reasons and refund take-backs; ad reward status; connect, idle and play time; notification consent state (informational, marketing, night); account events (creation, sign-in, linking, deletion request); abuse-review records (suspension or hold and review flags with reason codes, server recalculation mismatches, sync refusal codes); and, on every record, the app version, build number, content version, platform, language, account country and the time the server confirmed it. The advertising ID is used only for ads (section 11-2), never for analytics. See section 11-3. (3) Event package conversion record (our server): event and product IDs, the time the package was first seen and the account's country and language at that time, the event's end time, and the time the first later purchase (test payments excluded) was seen. Unlike the analytics pseudonym, this record is kept under the account number. | The app sends app usage statistics directly to Google only after you choose "Allow and continue" on the analytics consent card, and the server records the server activity records automatically as service operation records. You can use the game without agreeing, and you can turn it off at any time in Settings (section 11-3) |
| App update check | IP address, request time, the address of the requested file, and normal HTTP headers (such as User-Agent, which includes the device model and OS version). The app sends these directly to Cloudflare (section 7) to download signed update files; our server does not receive them. No account number, game data or advertising ID is sent, and we do not use or set cookies for these requests. | Sent automatically when the app checks for and downloads updates |
| Feedback box (optional) | The feedback text (1 to 1,000 characters), app language, app version, time received, a feedback ID (a randomly generated value), and the account number (used to enforce the daily limit and the first-feedback reward). The copy in the Google Form holds everything except the account number. Please do not write personal information in your feedback. Details in section 11-13. | When you agree to the collection and the transfer abroad on the feedback screen and send feedback yourself |
Kept only on your device and not sent to the server: sound, power-saving and language settings, tutorial records, presets, and the local copy of save data (in-app storage). Apart from the Google ad SDK described in section 11-2, the Service does not collect your device's location (section 11-6 explains how the country you connect from is determined), contacts, photos, microphone, advertising identifier or hardware identifiers (the registration token of push notifications that you turn on is described separately in section 11-5). Because of the ad SDK, the app includes the advertising ID permission (com.google.android.gms.permission.AD_ID) in addition to internet access. Push notifications are provided only in the Android app, and a notification registration token is created and sent to the server only after you turn notifications on (section 11-5). The advertising ID is not used for usage statistics analysis (section 11-3).
4. Retention
- Account and game progress: kept while the account exists. If you request deletion, after a 7-day grace period (you may cancel during it) personal fields (country, language, ranking nickname) are erased and the credential is revoked.
- Payment and grant records: under the Korean Act on Consumer Protection in Electronic Commerce, etc., records on contracts and withdrawal and records of payment and supply of goods are kept for 5 years, and records of consumer complaints and dispute handling for 3 years. The records allocating spent diamonds to purchases and the refund debt records are kept together with the payment records.
- Game history kept to prevent abuse and handle disputes (save and revision history, ad reward records, account events, archive logs, IP hash counters): when account deletion is confirmed, the link to the account is cut, and only the minimum items that are essential for abuse checks are kept for 30 days under a pseudonymous account number and then deleted or anonymized. Records whose retention period is set by law (such as the payment and grant records above) follow that period.
- Review, suspension and hold marks and operator audit records (target account number, values before and after a correction, reason): kept for 3 years as dispute-handling records and then deleted or anonymized. They may remain for this period even after account deletion is confirmed.
- Age range (accounts where it was entered in version 0.1.3 and earlier) and age signal results: kept while the account exists and erased with it when account deletion is confirmed. Genuine-app check results and the connecting country are kept as abuse-check records for the same period as the game history above.
- Server operations logs (CloudWatch): 14 days.
- Login and access records (Korean Protection of Communications Secrets Act): login and access times, account number and the IP address of the connection are kept for 3 months in a store separate from the server operations logs above, then expire automatically and are deleted. They are not used or provided except as the law provides.
- Analytics records (app usage statistics and in-game activity statistics): kept only under a pseudonymous number that differs from the account number; when an account is deleted, the link between the pseudonym and the account is destroyed at once and the records remain only as statistics that do not identify anyone. Google Analytics event-level records are deleted by Google after 14 months.
- Event package conversion records: kept until 7 days after the event ends, and their contents are erased the next day. They are erased as soon as the server learns that you turned off "Send analytics data" or that account deletion was confirmed (if your device is offline, the next time it connects). What stays under the account number afterwards is only a marker that the records were erased (its state and the time of the erasure); it holds nothing about whether or when the account saw or bought an event package. Statistics keep only totals by country and language, which are not linked to an account. (Unlike the analytics records above, these records are kept under the account number.)
- Push notifications (section 11-5): when you turn notifications off, that device stops being a send target at once, but its device registration record stays on the server until account deletion is confirmed (after the 7-day grace period following a deletion request), when the notification registration token value is erased. The consent and withdrawal history and the send records are proof that consent was obtained, so they are kept under a pseudonymous account number that is not linked to a name or email for as long as the consent remains in force and for 3 years (for dispute handling) from the day the consent is withdrawn or the account is deleted, and are then deleted or anonymized. Information held by Google (FCM) follows the periods Google sets.
- Feedback box records (section 11-13): kept until account deletion is confirmed or the Service ends. When account deletion is confirmed (after the 7-day grace period following the request), we erase the feedback text and its link to your account number on our server, and we delete the copy in the Google Form responses within 3 days of that confirmation.
Records past these periods are deleted or irreversibly anonymized.
5. Destruction
Personal information whose retention period has ended or whose purpose has been achieved is promptly deleted or irreversibly anonymized. A job that our server runs automatically every day erases the contents of records whose retention period has ended, and electronic files are processed so that they cannot be recovered. Information we must keep by law is kept separately from other information and only for the required period. Server backups for disaster recovery (point-in-time recovery copies) may hold erased contents for up to 35 days; when we restore from a backup, we apply again the analytics opt-outs and account deletions made after the restore point.
6. Provision to third parties
We do not sell your personal information and do not provide the personal information held on our server to third parties for advertising. What the ad SDK sends from your device directly to Google is governed by section 11-2. Exceptions are only where a law provides a basis or an investigative authority requests it by lawful procedure. Google Play billing and Google sign-in are parts that Google processes as its own services.
7. Processors and international transfers
| Recipient (country) | Items transferred | Purpose | When and how | Retention | Recipient contact | Basis for transfer |
|---|---|---|---|---|---|---|
| Amazon Web Services, Inc. (stored in Japan, Tokyo region) - Lambda, DynamoDB, S3, CloudWatch, Amazon Data Firehose, Athena (analytics records), etc. for server operations (outsourced processing) | All server-processed items in section 3 | Operating the game server, storing data | Sent over HTTPS, encrypted, when you use the Service | As in section 4. Deleted promptly when the processing agreement ends | Contact guidance at aws.amazon.com/privacy | Article 28-8(1) item 3 (a) of the Personal Information Protection Act (outsourced processing and storage for performing the service contract) |
| Google LLC and affiliates (United States and others) - Google Play distribution and payments, Google sign-in, refund notices (Pub/Sub) | Purchase information (purchase token, product and order IDs); ID token verification request at Google sign-in | Payment verification, sign-in authentication, refund notices | Sent encrypted at purchase and sign-in | Periods set by Google (Google Privacy Policy). Information kept on our server follows section 4 | Google privacy contact form | Article 28-8(1) item 3 (a) (performing the service contract, such as payment verification and sign-in) |
| Google LLC (United States) Google Play Integrity API - genuine-app check | The genuine-app attestation token (our server sends it to Google for decoding and receives whether the app is the genuine one distributed by Google Play, its package name, signing certificate fingerprint and version, and whether it was installed through Google Play) | Preventing abuse by modified apps and automation | Sent encrypted at sign-in and session renewal | Periods set by Google (Google Play Integrity terms). Results kept on our server follow section 4 | Google privacy contact form | Article 28-8(1) item 3 (a) (abuse prevention for performing the service contract) |
| Google LLC (United States) Google AdMob (Google Mobile Ads SDK, User Messaging Platform) - serving and measuring rewarded ads | Advertising ID, approximate location (IP), device and OS information, ad interaction, diagnostics. Sent from your device directly to Google, not through our server | Serving and measuring ads, preventing invalid traffic, managing consent | Sent encrypted after the ad SDK has started (when the server's ad setting is on, it starts right after the app has connected to the server; in regions where consent is required, after consent). To find out whether to show a consent form, UMP may send a consent-status request (including some device information) to Google before consent, and this is the same even when the server's ad setting is off | Periods set by Google (Google Privacy Policy) | Google privacy contact form | Article 28-8(1) item 3 (a) (outsourced processing and storage by which Google is entrusted with serving and measuring rewarded ads). In regions without a consent form, including Korea, the transfer is made on this basis and not on consent, and may happen after the ad SDK has started. In regions where a consent form is shown (the European Economic Area, the UK, Switzerland and others), the SDK is started and the transfer is made only after you consent in that form. The part in which Google independently processes, under its own privacy policy, the information it receives directly through the ad SDK may be a provision to a third party (Google) and not outsourced processing |
| Google LLC (United States) Firebase Hosting - hosting of this information website | Access records such as IP address when a page is visited | Serving web pages | When a page is visited | Firebase service policies | Google privacy contact form | Article 28-8(1) item 3 (a) (serving web pages) |
| Cloudflare, Inc. (United States; requests are handled at a nearby Cloudflare location) Cloudflare Pages - delivering app update files | IP address, request time, the address of the requested file, normal HTTP headers (such as User-Agent, which includes the device model and OS version). No account number, game data or advertising ID is sent | Providing signed app update files (web bundle) | Sent directly from the device over HTTPS when the app checks for and downloads updates | The period Cloudflare sets (Cloudflare privacy policy). We do not receive or separately keep Cloudflare's access records | Contact details at cloudflare.com/privacypolicy | Article 28-8(1) item 3 (a) (outsourced processing and storage to provide app update files) |
| Google LLC (United States) Google Analytics for Firebase - analyzing app usage statistics | Firebase app instance ID, the analytics pseudonym, in-app behaviour records (screens, tutorial, progress, summon and purchase flow, ad-watching flow, sign-in, settings changes, error fingerprints, performance values), the automatic record of Google Play purchases (product ID, price, currency), account-state bands (account type, purchase history band, ads removed or not, rank and stage bands), the install source, device type, OS, WebView version, app version, language, an approximate region derived from the IP address. Sent from your device directly to Google, not through our server | Analyzing usage statistics to improve the Service | Sent encrypted while you use the app (only after you agree on the analytics consent card; stops when you turn it off in Settings) | Event-level records for 14 months, then deleted by Google | Google privacy contact form | Article 28-8(1) item 1 (consent). Transferred only if you chose "Allow and continue" on the analytics consent card (or the regional consent form) |
| Google LLC (United States) Firebase Cloud Messaging (FCM) - delivering push notifications | The notification registration token, the notification title and body, the name of the game screen to open when tapped and a campaign number (no account number, nickname or email is sent). To issue the token, the notification SDK on your device sends the Firebase installation ID and device information directly to Google (our server does not receive them) | Delivering push notifications (notices about maintenance, outages and changes to the terms; event and benefit news to users who agreed) | Sent encrypted when you turn notifications on (token issue) and when a notification is sent. Nothing is sent before you turn notifications on | Periods set by Google (Google Privacy Policy). Information kept on our server follows section 4 | Google privacy contact form | Article 28-8(1) item 1 (consent). Transferred only if you turned notifications on |
| Google LLC (United States and others) Google Forms - keeping a copy of feedback | Feedback ID, time received (UTC), language, app version, feedback text (the account number is not sent) | Keeping the feedback together so it can be used to improve the game and fix bugs | Our server collects the feedback and sends it over an encrypted connection (HTTPS) | Until account deletion is confirmed or the Service ends (section 4). When account deletion is confirmed, we delete the entry from the Form responses within 3 days. Information remaining in Google's systems follows the period Google sets | Google privacy contact form | Article 28-8(1) item 1 (consent). Transferred only if you separately agree to the transfer abroad when sending feedback (keeping the feedback is entrusted to Google) |
If you do not want an international transfer, you can stop using the Service and request account deletion. This transfer is needed to provide the Service, so refusing it makes the Service difficult to use. However, the transfer of usage statistics (Google Analytics) is not required to use the Service, and nothing is sent if you do not agree on the analytics consent card or if you turn it off under Settings > Send analytics data (section 11-3). In regions without an ad consent form (including Korea), there is no separate screen to refuse the international transfer by the ad SDK. You can delete or reset the advertising ID or turn off ads personalization in your device settings (section 11-2), and you can keep playing without watching ads. In the "Basis for transfer" column, "item 1" means the user's consent and "item 3 (a)" means outsourced processing and storage for performing the service contract. The transfer for push notifications is not required to use the Service either, and nothing more is sent once you do not turn notifications on or turn them off (section 11-5). The transfer abroad for the feedback box (the Google Form copy and storage on our server in Japan) relies on a separate consent you give when sending feedback; if you do not agree, only the feedback box is unavailable and the rest of the game is unaffected (section 11-13).
7-2. Items processed without consent and the legal basis
We process the following items without obtaining consent. The legal basis for the processing is given as the item number of Article 15(1) of the Personal Information Protection Act, and the Company bears the burden of proving that processing without consent is allowed.
| Items | Purpose | Legal basis |
|---|---|---|
| Account number, device credential hash, Google identifier hash, game progress and save data, age range (accounts where it was entered in version 0.1.3 and earlier) | Providing the game, syncing, applying purchase restrictions according to the stored age range | Item 4 (performing a contract) |
| Age signal results | Restricting paid draws and top-ups by minors as the law of that country requires | Item 6 (the Company's legitimate interest); item 2 for the part that the law of that country requires |
| Purchase token hash, product and order IDs, payment country code, grant ledger, allocation of spent diamonds to purchases, refund debt | Payment verification, granting items, take-back on refund, calculating the refund on withdrawal | Item 4, and item 2 under the laws that require transaction records to be kept |
| IP hash (rate limiting), connecting country, genuine-app check result, abuse-check records | Abuse prevention, applying country-specific rules | Item 6 (the Company's legitimate interest). Country-specific sales restrictions: items 4 and 2 |
| Ad reward records | Confirming ad rewards, enforcing daily limits | Item 4 |
| Information the ad SDK (advertising ID, approximate location, device information, ad interaction) sends directly to Google - in regions without a consent form, such as Korea | Serving and measuring rewarded ads, preventing invalid impressions | Item 6 (the Company's legitimate interest: operating the feature that gives free goods through rewarded ads). You can delete or reset the advertising ID or turn off ads personalization in your device's ad settings |
| Login and access records | Retention required by the Protection of Communications Secrets Act | Item 2 (a legal obligation) |
| Server activity records (analytics pseudonym) | Producing statistics to improve the Service | Article 28-2 of the Personal Information Protection Act (statistical purposes for pseudonymized information) |
| Push notification registration and consent records | Delivering notifications, proving consent | Turning notifications on is consent (item 1); notices are item 4 |
| IP address and HTTP headers (such as User-Agent, which includes the device model and OS version) the device sends to Cloudflare when checking for app updates | Delivering signed app update files | Item 4 (performing the contract) |
What we process with consent is advertising notifications (events and benefits, night, Idle Chest), app usage statistics (the analytics consent card, in all countries including Korea), and the ad SDK processing in regions where Google says consent is required (the European Economic Area, the UK, Switzerland and others) (the consent form), as well as the feedback box (the consent to collection and use and the consent to the transfer abroad given when sending feedback, section 11-13). There is no ad consent screen in Korea, and the ad SDK processing for Korean users follows the basis in the table above (item 6).
8. Your rights and how to exercise them
- You may request access to, correction of, deletion of, or suspension of processing of your personal information at any time.
- Delete in the app: Settings > Request account deletion.
- Delete on the web: if a Google account is linked, use the account deletion page. If you only used a guest account without Google, email promptrun.studio@gmail.com with your account number.
- For 7 days after a deletion request you can cancel it; afterwards personal fields are erased and the credential is revoked. Rankings show "Erased Witch", and scores and match records remain only as summaries with the name removed.
- Requests may also be made through an agent, including a legal guardian. We act within 10 days of receiving the request and tell you the result. If we are late, we tell you the reason and the schedule.
- If you think a decision we made automatically, without human involvement (section 11-8), significantly affects your rights or obligations, you may ask for an explanation or a review. On request, a person will check it again or explain it, and we will tell you within 30 days of receiving your request.
- Requests for withdrawal and for cancellation of a minor's purchase are also accepted at the same contact (Articles 11 and 13 of the Terms of Service).
- You can stop usage statistics at any time by turning off Settings > "Send analytics data" in the app (section 11-3).
- To see the event package conversion records we keep about you, email promptrun.studio@gmail.com with your account number. After verifying the request we will tell you what is held.
- You can turn off push notifications, or withdraw your consent, at any time and free of charge under Settings > Notifications in the app, separately for notices, events and benefits, night and Idle Chest; a withdrawal applies from the next send. You can also turn them off in the device settings (section 11-5).
- Until you agree on the analytics consent card (all countries, including Korea), no usage statistics are sent, and you can change your choice at any time under Settings > Send analytics data. In regions where an ad consent form is shown (the European Economic Area, the UK, Switzerland and others), you can change your ad consent again under Settings > Privacy options (ads).
- When you delete your account, the link between the analytics pseudonym and the account is destroyed, and deletion of the data held in Google Analytics for that pseudonym is requested automatically (section 11-3).
- The text you send in the feedback box is erased when you delete your account (section 11-13). To erase only your feedback, or to withdraw your feedback-box consent, without deleting your account, email the contact with your account number; we act within 10 days as above. Please do not write personal information in your feedback.
9. Age of use and children's personal information
The Service may be used only by people aged 14 or older and is not directed at children under 14. From app version 0.1.4, in every country the app no longer asks for your age the first time you start it, and the start screen shows only one line saying that only users aged 14 and over may use the game. If we learn that personal information of a child under 14 was collected without a legal guardian's consent, we delete it without delay. A legal guardian can ask to access, correct, delete or stop the processing of a child's personal information at promptrun.studio@gmail.com. Version 0.1.3 and earlier asked for your date of birth (year, month and day) with a date input the first time you started the app, calculated only an age range (under 14 / 14-15 / 16-18 / 19 or older) on the device, and sent only the age range to the server. The date of birth was neither sent to nor stored on the server. That age range stays on accounts made in those versions for as long as the account exists (section 4), and the server keeps applying it. If version 0.1.3 or earlier confirmed that the user was below the minimum age, it left a refusal mark on the device that held only the minimum age (14, or 16) and not the date of birth you entered. Version 0.1.4 and later keep honoring only a mark that says 14, and do not apply a mark that says 16 (the former European Economic Area rule). Ad requests are not marked as child-directed (the Service is for users aged 14 and over), and the ad content rating is capped at G (all ages). We do not turn on Firebase's child-directed setting for usage statistics. The purchase restrictions (no diamond top-up sales, monthly Package payment limit) for accounts that were entered in 0.1.3 or earlier and have a stored age range under 19, and the notice before purchase for accounts stored as 14-15, are in the Guide for Teens and Guardians (Korean), where a guardian can see the same information. Purchases by accounts with no stored age range (such as accounts created in 0.1.4 or later) go through Google Play, and a guardian can require approval of a child's purchases with the purchase approval feature of Google Family Link. For accounts in countries that have laws restricting paid draws and payments by minors, such as Brazil, we check and record the age signal from Google Play, and currently we do not offer paid draws and top-ups whatever the signal result is (section 11-11).
10. Security measures
- Encryption in transit (HTTPS); only hashes of the device credential secret, Google identifier and purchase token are stored
- Server-side recalculation and rate limits on account creation and sign-in
- Least privilege: operator actions are audit-logged
- Limited retention of server operations logs (14 days); login and access records are deleted after 3 months and access to them is restricted
11. Automatic collection tools
The Service uses no cookies. The app keeps settings and save data in on-device storage (localStorage and Android storage), which is removed when you uninstall the app. If device auto-backup is on, the operating system may back up this storage. The analytics SDK (Firebase) in the app keeps the app instance ID and usage statistics not yet sent in on-device storage. If you turn off Settings > Send analytics data it stops collecting and sending, and uninstalling the app removes this storage too. If you turn on push notifications, the notification SDK (Firebase Cloud Messaging) also keeps the Firebase installation ID and the notification registration token in on-device storage, and turning notifications off deletes the token from the device.
11-2. Advertising (Google AdMob)
This section covers the rewarded ads and the ad removal product in the Service.
| Item | Details |
|---|---|
| Ad format | Rewarded ads only. An ad appears only after you press the "Watch an ad for a reward" button; there are no banners, interstitials or auto-playing ads. If you close it before the end, you get no reward. Ads appear only in the Android app while connected to the server, and daily limits apply. An ad appears only when you press the button, but when the server's ad setting is on, the ad SDK starts as soon as the app has connected to the server, before you watch an ad (where consent is required, after the consent step). In regions without a consent form, including Korea, it starts without separate consent. |
| Ad provider | Google AdMob of Google LLC (Google Mobile Ads SDK), and the User Messaging Platform (UMP) SDK for the consent form. |
| Data the SDK processes | Advertising ID (Android advertising identifier), approximate location derived from the IP address, device and OS information (model, OS version, language, screen), ad interaction (impression, completion, click), SDK diagnostics (errors, performance), consent status. |
| Purposes | Serving and measuring ads, limiting how often ads appear, preventing invalid impressions and clicks, analytics. |
| Consent (UMP) | In the European Economic Area (EEA), the UK, Switzerland and other regions where Google says consent is required, a consent form is shown after the app has connected to the server and before the ad SDK starts, and the ad SDK is not started and no ad is requested before you consent. However, to find out whether to show the consent form, UMP may send a consent-status request (including some device information) to Google before consent, and this is the same even when the server's ad setting is off. There is no consent form in other regions, including Korea. You can change your consent at any time in the app under Settings > Privacy options (shown only where required). |
| Personalized ads | In regions where consent is required, personalized ads are shown only if you consent. In other regions, including Korea, there is no separate consent screen, and unless you have turned off ads personalization in your device's ad settings or deleted the advertising ID, ads based on the advertising ID may be shown. |
| Opting out | (1) In your device ad settings (Android Settings > Privacy or Google > Ads; names differ by device), delete the advertising ID or turn off ads personalization. (2) Change your consent in the app under Settings > Privacy options (ads) (shown only in regions that have a consent form). (3) Buy the ad removal product (no ads are shown; the starting of the ad SDK itself is separate from the purchase). (4) You can keep playing without watching ads; they are optional. |
| Data shared with Google | The data listed under "Data the SDK processes" may be sent from your device directly to Google once the ad SDK has started, and Google processes it independently under its own privacy policy. We do not receive it and do not sell it. Google's explanations: policies.google.com/privacy, policies.google.com/technologies/partner-sites. |
| What our server receives | It does not receive the advertising ID. To confirm a reward we give Google a SHA-256 hash of the account number (not the advertising ID) and a one-time ad ticket ID, and receive Google's signed server-to-server confirmation (ad unit, time, transaction ID). The server stores only the ticket ID, account number, placement, status, times and a hash of the transaction ID; it does not store the raw transaction ID, advertising ID or IP. |
| Retention of ad reward records | Same as game history in section 4: when account deletion is confirmed, the link to the account is cut, and only the minimum items are kept for 30 days and then deleted or anonymized. |
| International transfer | The ad SDK's data may go to Google LLC (United States and others) once the SDK has started (table in section 7). If the server's ad setting is off, or where consent is required and you do not consent, the ad SDK is not started (however, UMP's consent-status request may go to Google before that). Watching ads is not required to use the Service, but while the server's ad setting is on, in regions without a consent form, including Korea, you cannot choose whether the ad SDK starts. |
| US state residents' rights | We do not sell personal information. Using the ad SDK may count as "sharing" or "targeted advertising" under some US state laws; you can opt out through your device ad settings and the in-app privacy options (in the regions where they are shown), or by emailing promptrun.studio@gmail.com. |
| Ad removal product | The product is a permanent purchase that lets you claim the same free rewards without watching ads. The daily limits are the same as with ads. If it is refunded or canceled, ad removal is turned off and rewards already received are not taken back. The ad SDK and the consent form may still start on your device whether or not you buy the product. |
| Children | The Service is not directed at children under 14 (section 9); ad requests are not marked as child-directed and the ad content rating is capped at G (all ages). See also section 9. |
11-3. Usage statistics (Google Analytics for Firebase and server activity records)
This section covers usage statistics used to improve the Service. Ads are covered in section 11-2.
| Item | Details |
|---|---|
| Purpose | Analyzing usage statistics to improve the Service: where players get stuck in the tutorial, progress and currency flow, summons, purchase and ad-watching flow, errors and performance, and checks on abuse and refunds. We do not use it to evaluate or track individuals or to personalize ads. Abuse checks follow the abuse-prevention purpose in section 2. |
| Two kinds of records | (1) App usage statistics: Google Analytics for Firebase inside the app sends them from your device directly to Google. (2) In-game activity records: from the checks our server already performs, our server (AWS) keeps currency, progress, summon, purchase-verification, ad-watching, Arena, World Boss, mail, coupon, account and abuse-review results as service operation records. |
| (1) App usage statistics: items | Firebase app instance ID (a random value Firebase creates per installation), the analytics pseudonym, screens, tutorial and first-open guides, progress, currency spending, summon and purchase flow (shop and limited-offer views, product ID and step), ad-watching flow, idle claims, time spent (connect and play time), sign-in, account-linking and notification-permission results, settings changes (sound, power saving, language, guides), error fingerprints and performance values, the automatic record of Google Play purchases (product ID, price, currency), ad revenue values (recorded automatically by Google when AdMob is linked to Firebase), the SDK's automatic records (app install, first open, sessions, updates, removal) and the install source, account-state bands (account type guest/Google, purchase history none/1/2 or more, ads removed or not, big-rank band, stage band in tens, whether the server is connected), device type, OS, WebView version, app version, language and device tier (low/mid/high), and an approximate region that Google derives from the IP address. In the EEA and the UK, detailed location and device data collection is turned off. |
| (2) In-game activity records: items | The analytics pseudonym, currency changes and a once-a-day snapshot of the currencies held, stage, rank, level, unlock and spell progress, summon, gear, dungeon, tower, quest and idle-claim results, Arena and World Boss results (season, band, win/lose), mail, coupon and event reward claims (campaign number and amount granted), purchase verification results (product ID, price and currency, the country Google Play reports, whether it was a first purchase or a test purchase), purchase refusal reasons and refund take-backs, ad reward status and ad removal grants, connect, idle and play time, notification consent state (informational, marketing, night, on/off), account events (creation, sign-in, linking, unlinking, deletion request), abuse-review records (suspension or hold and review flags with reason codes, server recalculation mismatches, sync refusal codes) and the kind of operations action (no operator identity). Every record also carries the app version, build number, content version, save format, platform, language, account country and the time the server confirmed it. IP addresses are not used in these records. |
| What we leave out | Name, nickname, email, phone number, Google user identifier, advertising ID, Android device identifier (SSAID), order number, purchase token (including hashes), raw coupon codes, raw error messages, free-text input. |
| The analytics pseudonym | A random value the server creates for each account; it is different from the account number and is not linked to your name or email. It is attached to app usage statistics after the app has connected to the server, and the same value is used in the in-game activity records. The daily summary statistics do not contain it at all. |
| Where it is kept and for how long | App usage statistics: stored event by event in Google Analytics (Google) for 14 months, after which Google deletes them; the aggregate figures in reports remain as statistics that do not identify anyone. In-game activity records: stored write-once, without deletion, in AWS storage (Japan, Tokyo) on our server; when an account is deleted, the link between the pseudonym and the account is destroyed and the records remain only as statistics that do not identify anyone. Daily summary statistics are kept as well (they contain no personal information). |
| International transfer | App usage statistics go to Google LLC (United States and others) (table in section 7). In-game activity records are stored at AWS (Japan) (table in section 7). We keep Google's data-sharing settings to the minimum and turn off Google signals and ads personalization so that usage statistics are not used for ad personalization. |
| Consent and regional handling | All countries, including Korea: app usage statistics are sent to Google only if you choose "Allow and continue" on the analytics consent card. If you choose "Decline" or do not answer, nothing is sent, and you can use the game as usual even if you do not agree. The card appears while you play, and you can change your choice at any time under Settings > Send analytics data. In the EEA, the UK and Switzerland you also choose on the same analytics consent card. The Google consent form (UMP) that appears in these regions is for the ad SDK, and you can change your ad consent again at any time under Settings > Privacy options (ads). United States: we do not sell usage statistics, and Google processes them as a service provider for us. The Service is not directed at children under 14, and if we learn that personal information of a child under 14 was collected without a legal guardian's consent, we delete it without delay (section 9). In-game activity records are service operation records and accumulate regardless of consent, but only under the analytics pseudonym; accounts that objected or turned analytics off are counted in totals without the pseudonym. (3) Event package conversion records are made only while sending app usage statistics is allowed, and are erased at once if you withdraw consent or turn analytics off in Settings, as soon as the server receives that. |
| How to turn it off | Turn off Settings > "Send analytics data". App usage statistics collection and sending stop, and the off marker is passed to the server, which clears that account's pseudonym in the in-game activity records (it stays only in totals). You can keep playing and can turn it back on. Event package conversion records are erased as soon as the server receives the off marker too. |
| Deletion and the analytics link | After you request account deletion and the 7-day grace period passes, (1) our server automatically asks Google Analytics to delete the user data for that pseudonym (the result is kept only in the audit log, without the pseudonym), and (2) afterwards the link between the account and the pseudonym is destroyed. In-game activity records are not erased but can no longer be linked to anyone. See section 8 and the account deletion page for how to request deletion. Exception: app usage statistics from before the app first connected to the server exist only under the app instance ID, which we cannot link to an account, so we cannot ask for their deletion; Google deletes them after 14 months. |
| Children | We do not turn on Firebase's child-directed setting for usage statistics, and the Service is not directed at children under 14 (same as sections 9 and 11-2). |
11-4. Pseudonymized information
- Purpose: producing usage statistics to improve the Service
- Items: the analytics pseudonym and the app usage statistics and in-game activity records attached to it (section 11-3)
- Retention: as in section 4. When an account is deleted, the link between the pseudonym and the account is destroyed.
- Additional information kept separately: the information that links a pseudonym to an account is kept apart from the pseudonymized data, access to it is restricted, and processing is logged.
- No re-identification: we do not process pseudonymized information to identify a specific person, and we do not provide it to third parties other than the processors listed in section 7.
11-5. Push notifications (Firebase Cloud Messaging)
This section covers push notifications that you turn on yourself. Rewarded ads are covered in section 11-2 and usage statistics in section 11-3. The kinds of notification and the consent wording are also in the Notification Guide (Korean).
| Item | Details |
|---|---|
| Scope and how it is turned on | Provided only in the Android app (none on Windows or the web). Only after you turn notifications on, in the in-app card or under Settings > Notifications while connected to the server, is a notification registration token created and registered on the server (Android 13 and later also need you to allow notifications on the device). The app does not ask when it first starts, and no token is created unless you turn notifications on. You can use the game as usual even if you do not allow notifications. |
| Kinds of notification | (1) Notices (informational): news needed to use the Service, such as maintenance, outages, changes to the terms and this policy, and forced updates. Turned on together with notifications and can be turned off in Settings. Unless a notice is marked urgent, it is held until after 08:00 during the night hours (see (3)). (2) Events and benefits (advertising): announcements of event starts and ends, benefits and new content. Needs your separate consent and is off by default. (3) Night advertising: your separate consent to also receive (2) from 21:00 to 08:00 the next day (possible only while (2) is on; off by default). (4) Idle Chest (advertising): a notice that your device itself shows when the Idle Chest is full (below). Needs your separate consent and is off by default. Notifications carry no third-party ads and no links to external web addresses; tapping one opens only a fixed screen inside the game. |
| Rules for advertising notifications | (1) We do not send them without your consent. The server checks the device's consent record and the account status again just before sending, so nothing advertising is sent right after you withdraw. Allowing notifications in the device settings is not treated as consent to advertising. (2) The mark "(Ad)" before the title, and a last line in the body with the sender "PromptRun" and how to opt out (Settings > Notifications), are added automatically. For users whose account country is Korea or unknown, "(광고)" is added whatever the app language; for everyone else the mark of the app language ((Ad), (広告) or (廣告)) is added. (3) From 21:00 to 08:00 the next day (by the device's local time; for Korean accounts Korean time is checked as well) they are sent or shown only if you have given the night advertising consent. Without it they wait until after 08:00, and are not sent if the event period ends before then. (4) The server sends at most 1 advertising notification and 3 notifications of all kinds per account per day (an operating setting that may change). (5) Your consent to advertising is confirmed again in the app every 2 years (we remind you from 30 days before the deadline); if it is not confirmed by the deadline, no advertising notification is sent until you confirm. (6) Every time you consent, decline or withdraw, the app shows you the date of processing, the sender and the content. |
| Idle Chest notification | The notice that tells you when the Idle Chest will be full is scheduled inside your device, not by the server. It is set once when you leave the app and canceled when you return; the only information it sends to the server separately is the on/off consent record. It is treated as advertising: the title carries the ad mark, the body ends with the sender and how to opt out, and during the night hours it waits until 08:00 unless you gave the night consent. |
| Items collected and where they are kept | The items are those in the "Push notifications" row of section 3. They are stored in the database on our server (AWS, Tokyo, Japan) as device registrations, the current consent state, the history of consent changes, and send records. The notification registration token identifies this app on this device, so we treat it as personal information and do not write the raw token to logs. Our server does not receive the Firebase installation ID. Changes to your notification consent (informational, marketing, night) are also kept in the server activity records under the analytics pseudonym (section 11-3), and the result of your notification permission choice is sent to Google as app usage statistics. |
| International transfer | The notification registration token and the notification content go to Firebase Cloud Messaging of Google LLC (United States and others) (table in section 7). When our server sends a notification it does not send your account number or nickname with it. Push notifications are not required to use the Service, and nothing more is sent once you do not turn them on or turn them off. |
| Retention | When you turn notifications off, that device stops being a send target at once, and so does a token that Google reports as no longer usable. The device registration record stays on the server until account deletion is confirmed (after the 7-day grace period following a deletion request), when the token value is erased; language, country, time zone, app version and times remain with the pseudonymous account number. The consent and withdrawal history and the send records are proof that consent was obtained, so they are kept under a pseudonymous account number that is not linked to a name or email for as long as the consent remains in force and for 3 years (for dispute handling) from the day the consent is withdrawn or the account is deleted, and are then deleted or anonymized. Information held by Google (FCM) follows the periods Google sets. |
| How to turn off and withdraw | Under Settings > Notifications in the app, you can turn each switch (notices, events and benefits, night, Idle Chest) off separately, free of charge. It reaches the server at once and applies from the next send decision. If you turn off both notices and events and benefits, this device's notification registration is released. You can also turn notifications off in the device settings (Android Settings > Apps > Notifications), but then notifications are only not shown and the consent record on the server stays as it was, so to withdraw please also turn them off in the app's Settings. |
| Deletion and the link | We do not send notifications to an account that has requested deletion. When deletion is confirmed after the 7-day grace period, the token values of all of the account's device registrations are erased, all consents are set to off, and that change is kept in the history. See section 8 and the account deletion page for how to request deletion. |
11-6. The country determined from your connection location
When the app connects to our server, the server determines the country you connect from (a two-letter country code) from the IP address of the connection path. This determination uses a value that AWS (Amazon CloudFront) works out from the IP address and passes on. We do not store the raw IP address used for the determination, and only the country code stays on the account (the IP used for rate limiting is stored only as the hash value described in section 3). The exception is the login and access records we keep by law (section 4). We use the billing country code that Google Play reports as a supplement, and if the two values differ, the stricter country restriction applies.
- Purposes: (1) deciding, in line with the laws and policies that differ by country, which items are sold and whether paid draws and payment features are provided; (2) selecting the target country for maintenance notices, mail and announcements; (3) preventing abuse that evades the restrictions by faking the country
- Legal basis: see the table in section 7-2.
- It may not be accurate. If you think it was determined wrongly, tell us at the contact. A person will review it again and reply within 15 days of receipt.
11-7. Genuine-app check (Google Play Integrity)
To prevent abuse by modified apps or automation, at sign-in and session renewal the app obtains a genuine-app attestation from Google Play services and sends it to our server. Our server asks Google to decode it and receives the result (whether the app is the genuine one distributed by Google Play, its package name, signing certificate and version, and whether it was installed through Google Play). Google processes app information and device attestation information in this process. We do not store the raw attestation token. We keep the check result (pass or failure code, and time) with the account number as an abuse-check record. The record row of a check that did not pass (failure, limit, Google response error, exemption, etc.) also keeps the purpose, reason, platform, version code and the list of device verdicts that Google reported. We do not use it to track individuals or to identify devices. The retention period is the same as for the abuse-check records in section 4. Information held by Google follows the periods Google sets.
11-8. Automated decisions
In the following cases we make decisions automatically, without human involvement.
- Whether items are sold and whether paid draws and payment features are provided, based on the connecting country determination
- A ranking and reward hold (a hold on paying out Arena and World Boss ranking rewards) based on a failed genuine-app check or a check for abnormal increases
- Restriction of diamond summons and Cauldron (lamp) purchases while refund debt remains after a refund or payment cancellation
- Payment restrictions and ranking and reward holds based on the number of refunds that created refund debt (counted over 180 days)
- Suspension or holds of use based on abuse checks
- The restriction on diamond top-up purchases and the monthly Package payment limit for accounts whose stored age range (entered in version 0.1.3 and earlier) is under 19
- The restriction on paid draws and diamond top-ups for accounts in countries where the age signal is checked (such as Brazil) (applied whatever the age signal result is)
These decisions use the connecting country code, the genuine-app check result, the stored age range, the age signal result, the account's purchase and refund records, and the server recalculation result. The criteria and procedures for the decisions are in Articles 6, 12, 13 and 15 of the Terms of Service and in the Operating Policy (Korean). If you think a decision significantly affects your rights or obligations, you may ask for an explanation or a review (section 8). The Service is not directed at children under 14, and these decisions do not use sensitive information.
11-9. Payment ledger and refund debt
For each purchase we keep on the server, with the account number, the diamonds granted (base and bonus), the record of how spent diamonds were allocated to purchases, withdrawal and refund handling records, and the refund debt amount. The purposes are calculating and refunding unused paid diamonds on withdrawal, managing take-backs and refund debt when Google or a card company returns the payment, and preventing abuse. The legal basis is the same as in the table in section 7-2, and the retention period is the same as for the payment and grant records in section 4. Refund debt is reduced only by subtracting it from the paid diamonds granted by later paid purchases; it is not repaid automatically from free diamonds.
11-10. App permissions
| Kind | Permission | Reason | If you do not allow it |
|---|---|---|---|
| Required permissions | None | The app does not ask for any required permission to access your device's information or functions. | - |
| Optional permissions | Notifications (a permission prompt appears on Android 13 and later) | To show maintenance and notice notifications and, if you agreed, event and benefit notifications | You can use the game as usual without allowing it. You can change it at any time under Settings > Notifications in the app or in the device settings (Settings > Apps > Notifications). |
| Normal permissions granted automatically at installation | Internet, Google Play billing, vibration, advertising ID (ad SDK), and other permissions used by the notification, ad and analytics SDKs to work | Server communication, payments, manual spell casting and boss-defeat effects (can be turned off in Settings), serving ads | These are permissions for which no prompt is shown to the user. You can delete or reset the advertising ID in your device's ad settings (section 11-2). |
We do not request access to the camera, microphone, location, contacts, or photos and storage. The notification permission prompt is shown only after you press "Yes, notify me" on the in-app card.
11-11. Age signal (Google Play Age Signals)
For accounts in countries that have laws restricting paid draws and payments by minors, such as Brazil, we check and record the age signal reported by the Google Play Age Signals API. Currently, regardless of what the signal says, our server refuses paid draws and new diamond top-up payments for accounts in those countries, and the app shows a notice that these are unavailable at the moment.
- Purpose: protecting minors as that country's law requires
- Items processed: the age signal result (access status, lower and upper age bounds, range source, significant-change status) and the time our server received it
- No other use: under Google's API terms, this signal is not used for advertising or usage statistics.
- Retention: the same as the age range in section 4. For the legal basis, see the table in section 7-2.
- It may not be accurate. If you think it is wrong, tell us at the contact. A person will review it and reply within 15 days of receipt.
11-13. Feedback box
This section describes the feedback box in the game. It is used only when you write and send something yourself, and you can use the game without sending anything.
| Item | Details |
|---|---|
| What we process | The feedback text (1 to 1,000 characters after trimming leading and trailing spaces), the app language (ko/en/ja/zh-TW), the app version, the time received, and a randomly generated feedback ID. Our server also keeps your account number with it. The account number is used only to enforce the daily limit and the first-feedback reward. |
| Purposes | Improving the game and fixing bugs, enforcing the daily limit, and granting the first-feedback reward (once per account, diamonds sent by in-game mail). |
| Please do not write personal information | Please do not write personal information such as your name, contact details or account information in your feedback. What you write is stored as it is and is also copied to the Google Form. |
| Copy in a Google Form | Our server collects the feedback it has received and sends it to the company's Google Form, which keeps it in the form's responses. The form is not linked to a spreadsheet (Google Sheets). The items sent are only the feedback ID, the time received (UTC), the language, the app version and the text; the account number is not sent. The form does not collect email addresses. We entrust Google with keeping this copy (entrustment and transfer abroad, section 7). |
| Server operation logs | The feedback text is not written to server operation logs; only its length and ID are. |
| Storage location and transfer abroad | The server record is in AWS Japan (Tokyo), and the Google Form copy is with Google LLC (United States and others) (table in section 7). |
| Retention | Kept until account deletion is confirmed or the Service ends. The purposes are improving the game, fixing bugs and granting the first-feedback reward. |
| Deletion | When account deletion is confirmed (after the 7-day grace period following the request), we erase that account's feedback text on our server and remove the link between the feedback records and the account number. What remains is only the feedback ID, time received, language, app version and a mark that it was erased, which cannot be traced to anyone. Within 3 days of that confirmation we delete the entries from the Google Form responses. To erase only your feedback while keeping your account, contact us as described in section 8. Erased text may remain for up to 35 days in server backups for disaster recovery (section 5), and in Google's systems for the period Google sets. How to request deletion is in section 8 and on the account deletion page. |
| Consent and legal basis | When you send feedback, the feedback screen asks for two separate consents: (1) to the collection and use of the personal information, and (2) to the transfer abroad (the Google Form, and our server in Japan) (Personal Information Protection Act, Article 15(1) item 1 and Article 28-8(1) item 1). If you do not agree, only the feedback box is unavailable and the rest of the game is unaffected. You can withdraw your consent as described in section 8. |
12. Controller and contact
- Controller: PROMPT RUN (Korean trade name 프롬프트런)
- Privacy officer: BAE HYEONSEONG (Representative)
- Business registration number (Korea): 232-64-00778
- Contact email: promptrun.studio@gmail.com
Korean users may also report or seek advice on a personal information infringement at the Personal Information Infringement Report Center (privacy.kisa.or.kr, dial 118) or the Personal Information Dispute Mediation Committee (kopico.go.kr, 1833-6972).
13. Changes to this policy
When we change this policy we will notify you in the app or on this page 7 days before it takes effect (30 days for changes unfavorable to you). If new features add data items, we will update this policy before introducing them. Changes that increase the information we process, such as usage statistics collection, will be announced 30 days before they take effect.
14. Effective date
This policy applies from 2026-10-28.
Revision history: 2026-10-28 published and effective; added the feedback box and app update delivery (Cloudflare), added a start screen (start with Google sign-in or as a guest), removed the age-check screen and added a 14+ notice on the start screen (0.1.4), and stated the 3-year retention of review, suspension and audit records (At a glance, sections 1 to 4, section 7, section 7-2, section 8, section 9, section 11-2, section 11-3, section 11-8, section 11-13 and section 15). The previous effective date was 2026-10-27.
15. Notices for specific regions
This section applies where the law of the region applies to you.
- Legal bases (EEA, UK): performing the contract with you (creating your account, saving your progress, delivering purchases); your consent (usage statistics analysis, advertising notifications, the feedback box, and the ad SDK in regions where a consent form is shown, which you can withdraw at any time as described in sections 8, 11-2, 11-3, 11-5 and 11-13); our legitimate interest in preventing abuse and keeping the Service secure (rate limits, server-side checks, review flags); and legal obligations (payment records).
- Your rights: access, correction, deletion, restriction and objection, and data portability where the law gives them to you. Use the contact in section 12. You may also complain to your local data protection authority.
- United States: we do not sell personal information. Our use of Google's ad SDK may count as "sharing" or "targeted advertising" under some state laws; see section 11-2 for how to opt out. The Service is not for children under 13 (the minimum age is 14, section 9), and if we learn that we have collected personal information from a child under 13 without verifiable parental consent, we delete it.
- Deletion: you can delete your account in the app or on the account deletion page. See section 8 for how to request deletion, and section 4 for what remains and for how long.
PROMPT RUN (PromptRun) · promptrun.studio@gmail.com