Privacy Policy
This page is an English translation of the Korean original. If the versions differ, the Korean original is the reference, except where the mandatory laws of your place of habitual residence require that the version provided to you, or the interpretation most favourable to you, applies. For users residing in France or the Province of Quebec, the French version governs.
BOOMUK GAMES (Representative: HAN CHEOLHEE; the “Operator”) complies with the Personal Information Protection Act (Korea) and other applicable laws and regulations, and establishes and discloses this Privacy Policy as follows in order to process securely the personal information of users of the mobile game Rise of the Archer and the official website (collectively, the “Service”) and to handle related grievances promptly and smoothly.
The game’s age rating and the age standards for personal information protection are different from each other. The actual age rating of the game and the target age shown in the stores are displayed according to each store and the results of the rating classification, and separate protection standards under the Personal Information Protection Act may apply to the processing of personal information of children under the age of 14.
Article 1. Purposes of Processing Personal Information and Legal Bases
The Operator processes personal information only to the minimum extent necessary to provide the Service. The main purposes of processing and their legal bases are as follows.
| Purpose of processing | Main details | Primary legal basis |
|---|---|---|
| Account creation, login and linking | Guest, Google and Apple login; identification of users; linking of Google and Apple logins to a single game account; maintenance of accounts; management of records of consent to the Terms of Service and the Privacy Policy | Article 15(1)4 of the Personal Information Protection Act (conclusion and performance of a contract) |
| Support for recovering Guest accounts | Customer support where a user, while on a Guest account, logged in with a Google or Apple account already linked to another game account and can no longer access the original Guest account: verifying the user’s identity by comparing the account-switch record remaining on the server with the email address of the linked account, and moving that login link to the original game account | Article 15(1)4, and Article 15(1)6 to the extent that a legitimate interest in protecting rights and accounts is recognized |
| Provision of game services | Storage, synchronization and recovery of game progress information and of currency, item, equipment, skill, settings, mail and ranking data | Article 15(1)4 |
| 1:1 Duels | Displaying the lobby list and Accept challenges, matching opponents, running duels, deciding results and granting rewards, managing monthly duel records, and preventing fraudulent use of duels such as failed-match abuse, match fixing and automated play | Article 15(1)4; fraud prevention under Article 15(1)6 to the extent of a legitimate interest |
| Delivery of coupon rewards | Delivery of coupon rewards through in-game coupon entry and through the coupon redemption page of the official website (entry of a Nickname and coupon code without logging in); display of the recipient account for confirmation; verification of one use per account; checking of Member Codes for first-come, first-served coupons; prevention of abuse such as repeated entries | Article 15(1)4; for prevention of abuse, Article 15(1)6 to the extent that a legitimate interest is recognized |
| Management of character names | Prevention of duplicate character names (Nicknames) and of the use of inappropriate names, such as names impersonating the operations staff | Article 15(1)6, to the extent that a legitimate interest in operating the Service is recognized |
| Payment and refund processing | Verification of in-app purchases, delivery, restoration of purchases, prevention of duplicate delivery, confirmation of cancellations and refunds and any necessary clawback, and verification and delivery of Google Play pre-registration and App Store pre-order rewards (once per store account and once per game account) | Article 15(1)4; Article 15(1)2 where there is an obligation under applicable laws |
| Advertising and rewarded ads | Provision of rewarded ads, verification of rewards, management of ad consent, prevention of ad fraud, measurement of ad performance | Article 15(1)4 to the extent necessary to provide the Service, or Article 15(1)6 to the extent that a legitimate interest is recognized. Personalized advertising that requires separate consent is based on consent |
| Sending of promotional push notifications (optional) | Sending push notifications to users who have consented to receive them, informing them that their idle rewards are full; management of records of consent and withdrawal of consent; prevention of duplicate sending | Sending notifications and storing scheduled-notification information: the user’s consent (Article 15(1)1) and consent to receive under Article 50 of the Act on Promotion of Information and Communications Network Utilization and Information Protection (Korea). Registration and management of notification registration tokens of Android devices before consent: Article 15(1)6 to the extent that a legitimate interest is recognized |
| Clean-up of abandoned Guest accounts | Where a different game account is started on a device that was using a Guest account (where, from the Guest account, the user logged in with a Google or Apple account already linked to another game account, or deleted the Android app or cleared its app data and started again), releasing the Nickname of the previous Guest account, which can no longer be accessed, and excluding it from the rankings, to prevent Nickname squatting and distortion of the rankings | Article 15(1)6, to the extent that a legitimate interest in operating the Service is recognized |
| Security and prevention of fraudulent use | Detection of cheating, abuse, abnormal payments and ad rewards, and ranking manipulation; verification of app integrity; detection of app tampering and abnormal execution environments; restrictions on use based on the server’s fraud detection results (detection results of the app protection SDK are used only for record-keeping); protection of servers and accounts | Article 15(1)6 (legitimate interest), and Article 15(1)4 to the extent necessary to perform the Service |
| Backup and recovery in case of failures | Keeping backup copies in case of service failures or data corruption, recovery, and testing of recovery procedures | Article 15(1)4, and Article 15(1)6 to the extent that a legitimate interest is recognized |
| Customer support and dispute handling | Receiving inquiries, verifying accounts, resolving service failures and payment problems, handling disputes | Article 15(1)4, or Article 15(1)6 for the protection of rights |
| Compliance with legal obligations | Retention of transaction records relating to electronic commerce; responding to lawful requests from relevant authorities | Article 15(1)2 (legal obligation) |
If a purpose of processing changes, the Operator will take the measures required by applicable laws and update this Policy.
Article 2. Personal Information Processed and Methods of Collection
Depending on the actual features of the Service, the following information may be processed.
| Category | Information that may be processed | Method of collection or generation |
|---|---|---|
| Account and authentication | Firebase user identifier (UID); login method; account identifiers provided by Google/Apple; for Google login, the email address, name and profile photo address (URL) of the Google account; for Apple login, the email address the user has allowed to be shared (Apple’s relay address if “Hide My Email” is selected) and name; account creation and last login times; identification information of anonymous Guest accounts; Member Code (an 8-character value calculated from the UID; shown in the game under Settings → Account and not stored on the server or the device). For accounts linked to Apple login, the authentication information needed to revoke Apple authorization upon account deletion (Apple refresh token) and the Apple user identifier are processed in encrypted form | Generated when the user chooses to start as a Guest; received from the relevant provider during Google or Apple login or account linking. For Apple login on Android, the Operator’s server function relays to the app the result obtained through the Apple authentication screen, and the authentication result is not stored during this relay |
| Records of consent to terms and to receive notifications | Version and time of consent to the mandatory terms (Terms of Service and Privacy Policy); whether the user has consented to receive promotional push notifications and the times of consent and withdrawal (based on server time); records of the confirmation, every 2 years, of consent to receive promotional push notifications (time of confirmation, and time and cycle of the consent being confirmed) | Consent window shown at first launch for each account; “Push Notifications” in the in-game Settings |
| Account-switch records | Where, from a Guest account, the user selects a Google or Apple account already linked to another game account: the UIDs of the two game accounts, an irreversibly transformed value of that login account’s identifier, and the times of first and last confirmation and the number of confirmations (the email address and the original login account identifier are not stored) | Generated automatically when the server confirms that the login account is linked to another game account |
| Guest account recovery requests | The UIDs and Nicknames of the two game accounts; the email address of the linked account compared for identity verification (only a partially masked value is kept after the comparison); the staff member handling the request, the inquiry number and the outcome | When the user asks customer support to recover the original Guest account |
| Coupon redemption | Coupon redemption records (a transformed value representing the coupon used, the time of use, and the identifier of the mail delivered); records of the number of in-game coupon entries. On the coupon redemption page of the official website: the Nickname, coupon code and Member Code (first-come, first-served coupons only) entered, and the IP address of the connection | Entered directly by the user. The server finds the recipient account by Nickname; the Member Code is only checked against a value calculated from that account’s UID and is not stored; the IP address of the connection is held only temporarily in the memory of the server function to limit repeated requests and is not stored |
| Game use | Nickname; progress information on stages, growth, enhancement, summoning and content; in-game currencies such as Gold, Ruby, Diamonds, Emeralds and Stars; items, equipment and skills; check-in, mail, coupon and event records; settings; information used to calculate rankings; save and synchronization information; usage logs such as changes in in-game currencies | Generated in the course of game use and server saving |
| 1:1 Duels | Lobby registration information (Nickname, archery Title level, character appearance, duel power and its rounded public value, registration and liveness-check times, the reason for leaving the list); matchmaking and match progress information (both users’ Nicknames, Titles and appearances, the score and misses of each arrow, the number of the speech bubble chosen, results and rewards); monthly duel counts and wins/losses; a value irreversibly converted from the opponent’s UID to check repeated wins/losses against the same opponent; a record of duels you caused to fall through before the match was confirmed (the time of the first canceled match and the number of canceled matches within 1 hour of it, and the end time of the 60-minute duel restriction applied at the 3rd); and recent shot records for fraud observation | Generated and stored by the server in the course of using 1:1 Duels |
| Payments and refunds | App store (Google Play or App Store); product ID; order and transaction identification information (for the App Store, the transaction ID and original transaction ID); an irreversibly transformed value of the purchase token; an identifier linking the purchase to the game account (a transformed value of the game account identifier); purchase environment; times of purchase and delivery; purchase, cancellation and refund status; delivery and clawback records; delivery records of pre-registration rewards; app transaction information for verifying App Store pre-orders (app transaction ID, pre-order date and time, environment). The original purchase tokens and signed transaction information are used only for verification and are not stored | Google Play or Apple App Store payment, verification and refund notification processes. For App Store pre-order rewards, the iOS app sends to the server the signed app transaction information it receives from Apple |
| Ads and reward verification | IP address (which may be used to estimate approximate location); app and ad interactions; usage information such as ad impressions and video views; diagnostic information; device and account identifiers such as the advertising ID and App Set ID; a verification value based on the game account identifier and the ad placement name, sent to Google for server-side verification of rewarded ads; verification results sent by Google (transaction ID, ad unit, reward time, etc.) | Processed automatically by the Google Mobile Ads (AdMob) SDK and in the rewarded-ad verification process |
| Push notifications | Push notification registration token (FCM token); device platform (Android/iOS); game language; the device’s time zone offset; reference, scheduled and sending times of idle-reward notifications | After login, the Android app registers this device’s notification registration token and platform with the server regardless of whether the user has consented to receive promotional notifications; the iOS app registers them only after consent to receive and permission for notifications on the device have been confirmed. The game language and time zone offset are sent together when the game is saved, and the reference, scheduled and sending times of notifications are stored only if the user has consented to receive them. No notifications are sent without consent to receive them |
| Technical and security information | IP address; user agent; Firebase app and installation identification information; app and OS versions; diagnostic information related to the device and network; app integrity verification information (Firebase App Check: Google Play Integrity on Android, Apple DeviceCheck on iOS); detection results of the app protection SDK (NHN AppGuard) (types and codes of device and execution environment detections, such as rooting or jailbreaking, emulators or virtual environments, app tampering, debuggers, speed manipulation, macro or cheating tools, and VPN use) and the game account identifier (UID) registered for this purpose; connection and request times; server request and error logs; signs of abnormal use and verification results; startup-stage diagnostic records when app startup is delayed (build number, elapsed time per stage, error type; sent at the next connection); and automated-play (macro) observation values calculated from archery shot timing | Generated automatically in the course of using Firebase, the servers, the app protection SDK and security features |
| Device identifier values | An irreversibly transformed value of the Android device identifier (ANDROID_ID) or the iOS Identifier for Vendor (IDFV), and the UID of the Guest account that sent that value (the original identifier is not stored, and values from accounts linked to Google or Apple are used only to identify a previous Guest account and are not stored) | When each game account first completes a connection on the device where the app is installed, the app sends the original device identifier to the server over encrypted communication, and the server stores only an irreversibly transformed value immediately upon receipt |
| Engine and payment SDK diagnostic information | Unity installation identifier; payment progress stages (purchase start, payment, failure, delivery) and product and transaction IDs; device model, operating system version, language, region and currency; iOS Identifier for Vendor (IDFV); the engine’s hardware statistics (device model, operating system, graphics device, etc.) | Processed automatically by the game engine (Unity) and the in-app purchase SDK (Unity IAP) when the app runs and during payment |
| Storage on the device | Login state; saved copies of game data for each account; device settings such as language, graphics, sound and vibration; the game account UIDs and device identifier values this device has reported to the server (a record kept so that the same information is not sent again) | Stored by the app in the device’s app-specific storage. Deleted together with the app when the app is deleted; on iOS, however, the login state remains in the device keychain and may persist after reinstallation |
| Customer support | The inquirer’s email address; Nickname; platform and login method used; content of the inquiry; materials attached by the user (such as order numbers for payment inquiries); handling records | Provided directly by the user by email or other means |
| Official website | Web request information such as IP address, user agent, request time and URL, and technical information necessary for security. On the coupon redemption page, the information entered as described under “Coupon redemption” above, and the Nickname of the account to which a coupon was last sent (stored only in the storage of the user’s browser) | Access to the site through Google Firebase Hosting (including the Fastly delivery network); entries on the coupon redemption page |
The Operator does not directly collect Google or Apple account passwords or the original details of app store payment methods, such as users’ full credit card numbers or bank account numbers. Because the game does not display the UID to users, customer support identifies accounts by Nickname.
The Service is currently not designed on the premise of phone number verification, contacts, precise GPS location, photo or video uploads, microphone input, or user-generated content features such as free-text chat or posts (the speech bubbles in 1:1 Duels can only be chosen from sentences predefined by the game). If such features are added in the future and the scope of personal information processing changes, this Policy will be updated before those features are provided.
Article 3. Information That May Be Made Visible to Other Users, Such as Rankings
To provide rankings and competitive content (all-time highest stage, all-time best archery score, and this week’s and last week’s standings in the weekly Archery Challenge), the Nickname, score and rank, together with the character’s appearance (outfit, shoes, hair and eyes; Bow and Bow Costume; Bowstring), Inner Power realm, Bow amplification level, enhancement level of the Bow shown in the portrait, equipped Bow and archery Title level may be made visible to other users. Email addresses, login provider identifiers, payment identification information and the like are not made public in the rankings.
In 1:1 Duels, the following information may be shown to other users. (1) To other users in the same lobby while you are on the lobby list with ‘Accept challenges’ turned on: Nickname, archery Title level, character appearance, a rounded value of your duel power (shown on screen as the opponent strength category and the winner chest probability), and the time you joined the list. You are removed from the list when you use other content, the Mailbox, summons or purchase windows, leave the app, or lose your connection. (2) To your duel opponent: Nickname, archery Title, character appearance, the score and result of each arrow, and the speech bubbles you choose (sentences predefined by the game). If account deletion is completed while a duel record still exists, the Nickname and appearance in that record are erased and you are shown to the opponent as ‘Deleted user’.
Last week’s archery rankings, once settled, are displayed with the Nicknames in use at the time of settlement. When account deletion is completed, that account’s records are deleted from the rankings; in last week’s rankings that have already been settled, only the Nickname and account identifier are erased and the rank and score entry is kept so that other users’ ranks do not change. If deletion was requested through the Android app or by other means, the account may continue to appear in the rankings during the 7-day deletion waiting period.
If a different game account is started on a device that was using a Guest account (where, from the Guest account, the user logged in with a Google or Apple account already linked to another game account, or deleted the Android app or cleared its app data and started again), the previous Guest account can no longer be accessed; its Nickname is therefore released and becomes available to other users, and the account is excluded from the rankings (in last week’s settled rankings, as with account deletion, only the Nickname and account identifier are erased and the rank and score entry is kept). The game progress data of that account is not deleted. This does not apply where the app is reinstalled on iOS (iPhone or iPad) and the same Guest account is accessed.
When a Nickname and coupon code are entered on the coupon redemption page of the official website, the person who entered them is shown the official spelling of the Nickname of the account using that Nickname, that account’s highest stage, and whether that account has already used the coupon entered, so that rewards are not sent to the wrong account by mistake. Because the recipient account is determined by Nickname without login, coupon rewards sent by another person who entered the Nickname are also delivered to that account’s Mailbox. UIDs, email addresses and Member Codes are not displayed, and accounts pending deletion or restricted from receiving rewards are shown with the same message as a Nickname that does not exist.
Article 4. Processing and Retention Periods of Personal Information
The Operator retains personal information for the period necessary for the purposes of processing and, once the purpose has been achieved or the account has been deleted, destroys without delay any information that applicable laws do not require to be retained. All times below are in Korea Standard Time (KST, UTC+9).
| Information | Retention period |
|---|---|
| Account and authentication information and game data linked to the account (including records of consent to terms and to receive notifications) | Until the account is deleted. If deletion is requested in the iOS (iPhone or iPad) app, the data is destroyed immediately; if any part remains due to a temporary failure, it is destroyed at the next scheduled processing time, 4:40 a.m. daily. Where deletion is requested through the Android app or by email, and where deletion has been scheduled under Article 10 (an account linked only to Apple login for which use of Apple login has been stopped, or an account locked when its login was moved through customer support), the data is destroyed at the first daily 4:40 a.m. run after the 7-day deletion waiting period has passed; during the waiting period, the deletion request can be canceled by accessing the account again (except for locked accounts that have no means of login) |
| Game usage logs, fraud detection records and audit records | While the account exists, deleted progressively once 30 days have passed since creation. Destroyed together with the account upon account deletion, regardless of this period |
| 1:1 Duel information | Lobby registration information: deleted when you leave the list (the record of the reason for leaving is deleted after 10 minutes, and list entries whose liveness check has lapsed for more than 90 seconds are deleted by the cleanup function). Matchmaking information: deleted by the cleanup function 10 minutes after the matchmaking ends; match records (both users’ Nicknames, Titles, appearances, scores and speech bubbles): 72 hours after settlement. Monthly duel counts and wins/losses: kept while the account exists. The canceled-match record is replaced at the next canceled match and kept while the account exists. Fraud observation records: only the most recent 50 shots and today’s and yesterday’s wins/losses against the same opponent are kept. All destroyed upon account deletion, and the account’s Nickname and appearance are erased from match and matchmaking records not yet cleaned up |
| Use restriction (sanction) status and history | Restriction status: until lifted; history of changes to restrictions: 1 year. Destroyed together with the account upon account deletion |
| Rewarded-ad verification records | Individual verification records: 24 hours; daily totals: 60 days; cumulative totals: until the account is deleted |
| Transformed values of device identifiers | While the Guest account exists (replaced by the value of another device when the same account first connects on that device). Deleted when the account is cleaned up as a previous Guest account, or when a different account connects on the same device after Google or Apple has been linked; destroyed upon account deletion |
| Push notification registration information and scheduled-notification information | The registration for the device is deleted upon logout, confirmation that the registration token is invalid, or switching to another account. Destroyed upon account deletion |
| Server Mailbox | Claimed mail: 180 days from the date claimed; mail whose claim deadline has passed without being claimed: cleaned up daily once 7 days have passed after the deadline (however, mail whose delivery processing has not been completed is kept until processing is completed). Mail delivered for real-money purchases and pre-registration rewards has no claim deadline and is kept, even after being claimed, for as long as the account exists. Mail delivered through the coupon redemption page of the official website, Frost Dragon interruption reward mail and Welcome-Back Reward mail also have no claim deadline and are kept until claimed, and for 180 days from the date claimed thereafter. 1:1 Duel reward mail is claimed automatically by the app and kept for 180 days from the date claimed. All destroyed upon account deletion |
| Coupon redemption records | Until the account is deleted (to prevent duplicate use of the same coupon) |
| Connection IP addresses and entered information on the coupon redemption page | Not stored (held temporarily in the memory of the server function to limit requests, and deleted when the server function restarts). Server request logs of error responses (Nickname not found, already used, etc.) are kept for the period stated for “Server request and error logs” below |
| Nickname stored in the browser by the coupon redemption page | Until the user clears the site data in the browser (not stored on the Operator’s servers) |
| Authentication information for revoking Apple authorization | Kept in encrypted form while Apple login is linked. Upon account deletion, deleted after a request to revoke authorization has been sent to Apple; if revocation fails due to a temporary error, used only to retry revocation for 14 days and then destroyed at the next scheduled processing time (4:40 a.m. daily) (up to approximately 15 days). Deleted if the Apple link is removed because use of Apple login for this game has been stopped in Apple settings |
| Account-switch records | Destroyed in the daily 5:25 a.m. run once 3 years have passed from the date of last confirmation or the date of handling by customer support. Destroyed together with the game account to which the relevant Google or Apple account was linked, when that game account is deleted |
| Guest account recovery handling records | Destroyed in the daily 5:25 a.m. run once 3 years have passed from the date of last handling (records of consumer complaints and dispute handling under Article 6 of the Enforcement Decree of the Act on the Consumer Protection in Electronic Commerce (Korea)). Kept for this period even if the account is deleted. However, records needed to reverse a moved login link are destroyed once deletion of the related game accounts has been completed |
| Records of customer inquiries, complaints and dispute handling | Up to 3 years after handling is completed. Where a shorter or longer period applies under law, that period |
| Records of payment, supply of goods, and withdrawal (cancellation) of purchases (refunds), including refund notification records sent by the app stores | Kept while the account exists (needed to confirm ownership of one-time products and to prevent refunded payments from being delivered again). After both the account data and the login information have been deleted, destroyed in the daily 5:10 a.m. run once 5 years and 1 month have passed from the payment date (or the refund date, if there was a refund) (5 years under the Act on the Consumer Protection in Electronic Commerce, plus a 1-month processing margin). Refund notification records with no matching payment record are destroyed in the same run once 5 years and 1 month have passed from the date the notification was received. These records do not include names, contact details or payment method information |
| Destruction confirmation records | Only the UID of the destroyed account and the time of destruction, for 45 days (used to prevent destroyed accounts from being revived when the Service is restored from a backup) |
| Backup copies for failure recovery | Maximum periods from the time the account’s destruction is completed: daily full data backups, 38 days; copies of server change records (progress saves, payments, mail claims, etc.) and of the login account list (UID; identifiers, email addresses and display names of linked Google and Apple accounts), 22 days; encrypted full data copies made immediately before server updates (stored on the developer’s PC), 31 days (copies needed to investigate a security incident are kept until the investigation ends). Monthly copies of payment records: up to 5 years and 2 months from the date made. Each period is a maximum that includes delays in deletion processing and a recovery waiting period (7 days) for restoring backups deleted by mistake |
| Server request and error logs | Kept for the default retention period of Google Cloud Logging (30 days) and then deleted automatically. Request logs may be kept only for requests to which the server returned an error response (HTTP 4xx or 5xx), including the server warm-up requests the app sends without login information, for example when it starts, to reduce response delays (the server rejects them without processing them). Request logs of server requests that were processed normally are not collected |
The retention periods of information processed independently by external service providers may be governed by each provider’s applicable policies and laws.
Article 5. Provision of Personal Information to Third Parties
The Operator does not sell users’ personal information. As a rule, the Operator processes personal information within the scope of the purposes of processing set out in Article 1 and does not arbitrarily provide personal information to third parties, except where the user has given separate consent or where there is a basis in law.
The relationships for processing personal information when external businesses such as Google and Apple provide authentication, app store payments, advertising, cloud, push notification, app protection and other functions are explained below under “Outsourcing of Processing and External Services” and “Overseas Transfer”.
Article 6. Outsourcing of Personal Information Processing and Use of External Services
The Operator uses the following external services to operate the Service. Some of these businesses may process personal information as processors (outsourcees) acting on the Operator’s instructions, and others as businesses that independently provide app store, login or advertising services.
| Provider | Service used | Main tasks and purposes |
|---|---|---|
| Google LLC | Firebase Authentication | Authentication of Guest, Google and Apple accounts and identification of users |
| Google LLC | Firebase Realtime Database | Storage and synchronization of server data such as game progress information, currencies, items, settings, mail and rankings |
| Google LLC | Cloud Functions for Firebase | Server processing such as verification of game saves, payment verification, delivery and refund processing, ranking calculation, account deletion, coupons and sending of push notifications |
| Google LLC | Firebase Cloud Messaging | Sending notifications to users who have consented to receive promotional push notifications |
| Google LLC | Firebase App Check, Google Play Integrity API | Verifying that requests were sent from a genuine app and device; prevention of fraudulent use |
| Google LLC | Google Cloud (BigQuery, Cloud Storage, Cloud Logging) | Keeping server change records and backup copies for failure recovery; recording server error logs |
| Google LLC | Google Mobile Ads (AdMob), User Messaging Platform | Provision of rewarded ads, verification of rewards, management of ad consent, measurement of ad performance and prevention of fraudulent use |
| Google LLC | Google measurement component included in the Firebase SDK (Google Analytics for Firebase) | As an SDK component, may send technical information such as the app instance identifier and app launches and sessions to Google. The Operator does not use this to analyze user behavior |
| Google LLC | Google Play | App distribution, in-app purchases, order and purchase verification, and checking of refund status |
| Google LLC | Google Workspace (Gmail) | Receiving and storing customer support and privacy inquiry emails |
| Google LLC | Firebase Hosting (including its delivery network sub-processor Fastly, Inc.) | Delivery of the entire official website (pages, images, fonts, etc.), prevention of abuse, forwarding of coupon redemption page requests to the server function (Cloud Functions) |
| Apple Inc. | Sign in with Apple, App Store, In-App Purchase, Apple Push Notification service (APNs), DeviceCheck | Apple login and revocation of authorization upon account deletion, app distribution, in-app purchases, transaction verification, purchase restoration and refund checks, delivery of iOS notifications, iOS app integrity verification |
| NHN Cloud Corp. | NHN AppGuard | App protection, such as detection of app tampering, cheating and macro tools, and abnormal execution environments |
| Unity Technologies | Unity engine, Unity IAP (in-app purchase SDK) | Provision of the game engine and in-app purchase functionality; processing of diagnostic and statistical information on the payment process and of engine hardware statistics |
Name resolution (DNS) for the official website domain (boomukgames.com) is provided by Cloudflare, Inc. Since October 13, 2026, all delivery of the website’s pages and files and all handling of connections have been performed by Google Firebase Hosting, and Cloudflare does not relay or analyze visitors’ web requests.
The “Community” button in the in-game Settings opens the official Naver Cafe (cafe.naver.com/archergirl) operated by NAVER Corporation (the “Notice” button opens a notice window within the game). The app does not pass game account information to Naver in this process, and the processing of personal information in connection with joining and using the Cafe is governed by Naver’s privacy policy and the Cafe’s operating policy.
The Operator does not use separate error reporting services such as Crashlytics and does not connect Google Analytics to analyze usage behavior. If external services are added or the items processed change, the Operator will check the items actually processed by the relevant service and then update this Article together with the privacy disclosures submitted to the stores.
Article 7. Overseas Transfer of Personal Information
The Operator uses global service providers for login, server storage and processing, backups for failure recovery, advertising, app store payments, push notifications, app integrity verification, customer support email and the provision of the website, and in this process personal information may be transferred to and processed outside the Republic of Korea. Where an overseas transfer takes place on a basis permitted by applicable laws, such as outsourcing of processing or storage necessary to perform a contract, the Operator discloses the details of the transfer in this Policy.
| Recipient | Country | Items transferred | Timing and method | Purpose | Retention and use period |
|---|---|---|---|---|---|
| Google LLC Firebase Authentication | United States | Information necessary for authentication, such as UID, login method, Google and Apple account identifiers, email address, display name, profile photo address, account creation and last login times, IP address and user agent | Transmitted over an encrypted network (TLS) at login and authentication | Login, authentication and prevention of fraudulent sign-ups | Until the account is deleted; however, periods under the provider’s applicable retention policies and laws apply |
| Google LLC Firebase Realtime Database, Cloud Functions, BigQuery, Cloud Storage | Singapore (asia-southeast1) | UID; information stored on the server such as Nickname, game progress, currencies, items, settings, mail and rankings; records of consent to terms and to receive notifications; payment and ad verification records; push notification registration and scheduling information; transformed values of device identifiers; encrypted authentication information for revoking Apple authorization; account-switch and Guest account recovery handling records; coupon redemption records and coupon redemption page request information (Nickname, coupon code, Member Code, connection IP; the IP is processed only in memory to limit requests); copies of server change records and of the login account list (UID, email address, display name, login provider information) | Transmitted via TLS during game use and server processing; backup copies are created at set intervals (daily and monthly) | Storage, synchronization and server processing of game data; backups for failure recovery | The periods set out in Article 4 |
| Google LLC Firebase Realtime Database automatic backups | Singapore (asia-southeast1) | Full copy of the database (the server-stored information above) | Created automatically once a day | Backup and recovery in case of failures | Kept for 30 days from the date created and then deleted (up to 38 days including delays in deletion processing and the recovery waiting period) |
| Google LLC Firebase Cloud Messaging | United States and other overseas processing locations where Google provides the service | Push notification registration token, device platform, notification title and body | Transmitted via TLS when notifications are registered and sent | Sending push notifications | Periods according to the purpose of providing each service and the provider’s applicable retention policies and laws |
| Google LLC Firebase App Check, Play Integrity, Firebase SDK measurement component | United States and other overseas processing locations where Google provides the service | App and device integrity verification requests and verdicts; Firebase app and installation identification information; app instance identifier; technical information such as app launches and sessions | Transmitted via TLS when the app is launched and when the verification token expires (12 hours); transmitted automatically while the SDK is running | Verifying requests from the genuine app, prevention of fraudulent use, operation of SDK functions | Periods according to the purpose of providing each service and the provider’s applicable retention policies and laws |
| Google LLC Cloud Logging | United States and other overseas processing locations where Google provides the service | IP address, user agent and request information of server requests that received an error response (including the app’s server warm-up requests); server processing logs (some include the UID) | Recorded automatically during server processing | Identifying server failures and responding to security issues | 30 days (default retention period of Google Cloud Logging) |
| Google LLC AdMob / User Messaging Platform / Google Play | United States and other overseas processing locations where Google provides the service | Of the following, the information necessary to provide the relevant service: advertising and device identifiers, IP, interaction and diagnostic information, ad consent choices, rewarded-ad verification values (including the game account identifier) and ad placement names, purchase and verification information, and identifiers linking purchases to game accounts | Transmitted via TLS for ad requests, reward verification and payment verification | Advertising, prevention of fraudulent use, in-app purchases and purchase verification | Periods according to the purpose of providing each service and the provider’s applicable retention policies and laws |
| Google LLC Google Workspace | United States and other overseas processing locations where Google provides the service | The inquirer’s email address, content of the inquiry and attachments, reply records | Transmitted when the user sends an email and when a reply is sent | Handling customer support and privacy inquiries | Up to 3 years after handling is completed |
| Google LLC Firebase Hosting (Fastly delivery network) | United States and other overseas processing locations where Google and Fastly provide the service | Request information such as the IP address of visits to the official website, user agent, request URL and time; Nickname, coupon code and Member Code entered on the coupon redemption page (forwarded to the server function) | Processed automatically over an encrypted network (TLS) when the website is accessed | Delivery of the official website, security and prevention of abuse | The period necessary for providing the service and for security purposes, or the period under the provider’s applicable retention policy |
| Apple Inc. | United States and other overseas processing locations where Apple provides the service | Apple login identification information; email address and name the user has allowed to be shared; authentication information and authorization revocation requests; purchase and transaction verification information; identifiers linking purchases to game accounts; app transaction information for verifying pre-orders; iOS notification tokens and notification content; app integrity verification (DeviceCheck) information | Transmitted over an encrypted network for Apple login, account deletion, payment verification, notification delivery and integrity verification | Login, authentication and revocation of authorization; App Store payments, purchase restoration and refund checks; delivery of iOS notifications; prevention of fraudulent use | Periods according to the purpose of providing each service and the provider’s applicable retention policies and laws |
| Unity Technologies | United States and other overseas processing locations where Unity provides the service | Unity installation identifier, payment progress stages and product and transaction IDs, device model, operating system version, language, region and currency, iOS Identifier for Vendor (IDFV), engine hardware statistics | Transmitted automatically via TLS when the app runs and during payment | Diagnostics and statistics for the game engine and the in-app purchase SDK | Periods under the provider’s applicable retention policies and laws |
If a user refuses the overseas transfer for essential authentication, server and app store functions, it may be difficult to use some or all of the Service, such as the relevant login method, server saving and payments. Users can end their use of the Service and request deletion of the related personal information through account deletion or customer support. Promotional push notifications, which are optional, are no longer sent once consent to receive them is withdrawn.
Privacy contacts of the recipients: Google LLC (Firebase, Google Cloud, AdMob, Google Play, Google Workspace and Firebase Hosting, including the sub-processor Fastly, Inc.) — Google privacy contact form · Apple Inc. — Apple privacy contact page · Unity Technologies — DPO@unity3d.com
Because the global processing locations and sub-processors of external businesses may change in the course of operating their services, the Operator regularly checks the providers’ current privacy and data processing documents and the actual configuration of the services, and keeps this Policy up to date.
Article 8. Automatically Collected Information, Advertising Identifiers and Behavioral Information
- The game uses only rewarded ads that users choose to watch, and does not use banner or interstitial ads. The Google Mobile Ads SDK and similar components may automatically process IP addresses, app and ad interactions, diagnostic information, and device and account identifiers such as the Android advertising ID and App Set ID, in order to provide and measure ads and prevent fraudulent use.
- Android users can reset or delete their advertising ID through the device’s ads privacy settings. The iOS app does not request App Tracking Transparency (ATT) permission and therefore does not access the advertising identifier (IDFA).
- In regions where consent for advertising is required by applicable laws, such as the European Economic Area and the United Kingdom, the app asks whether the user consents through Google’s consent management tool (User Messaging Platform) when the app is launched, and loads ads only if ad requests are permitted. In the iOS app, users in regions where this consent is required are shown an “Ad privacy choices” button at the bottom of More → Settings, which they can use to review and change their choices at any time. The Android app does not currently have this menu. Where any other processing requires separate consent under applicable laws or platform policies, the Operator provides the necessary means to give or refuse consent.
- The Firebase SDK included in the app contains Google’s measurement component, so technical information such as the app instance identifier and app launches and sessions may be sent to Google, and the in-app purchase SDK (Unity IAP) and the Unity engine may send diagnostic information on the payment process and hardware statistics to Unity. The Operator does not use this information to analyze user behavior.
- The app protection SDK (NHN AppGuard) and Firebase App Check automatically check for app tampering, abnormal execution environments and app integrity while the app is running. Detection results of the app protection SDK are used only for record-keeping purposes, and use is not restricted on the basis of these results alone.
- The BOOMUK GAMES official website has no advertising or visitor behavior analytics scripts or cookies installed by the Operator. However, Google (Firebase Hosting) may process technical information such as the IP address of the connection to deliver and secure the site. To make the next entry easier, the coupon redemption page stores the Nickname of the account to which a coupon was last sent only in the user’s browser storage (localStorage). This value is used only as an input value the next time a coupon is sent and can be removed by deleting the site data in the browser; coupon codes and Member Codes are not stored.
Article 9. Processing of Personal Information of Children Under 14
- The game’s age rating and the age standards for personal information protection are separate. Under the Personal Information Protection Act, the consent of a legal guardian is required in order to process the personal information of a child under the age of 14 on the basis of consent. The Service’s essential processing is based not on consent but on the performance of a contract and similar grounds (Article 1), and the only processing based on consent is the optional receipt of promotional push notifications and the ad consent requested in regions where consent is required by applicable laws (Article 8). The app currently has no procedure for obtaining or verifying the consent of a legal guardian.
- The Service is not primarily intended for children under the age of 14 (Google Play target age: 13 and over), and the app has no separate age verification procedure. The optional consent to receive promotional push notifications shown at first launch is displayed regardless of age, so users under the age of 14 should not consent to this optional item without the consent of their legal guardian.
- If the Operator becomes aware that a child under the age of 14 has consented to an optional item without the consent of their legal guardian, the Operator will take the necessary measures, such as stopping the sending of notifications based on that consent. Legal guardians may make requests through the contact points in Article 13.
- If features requiring separate consent are introduced in the future for users under the age of 14, the Operator will first put in place explanations that are easy for children to understand and procedures for obtaining and verifying the consent of legal guardians, and will update this Policy.
Article 10. Rights of Users and Legal Guardians and How to Exercise Them
- To the extent provided by applicable laws, users may request access to, transmission of, correction or deletion of, and suspension of processing of their personal information, as well as withdraw consent, among other things. Legal guardians of children under the age of 14 may also exercise rights regarding the child’s personal information in accordance with applicable laws.
- Up to one Google account and one Apple account can be linked to a single game account (More → Settings → Account). There is no function to unlink a login account that has already been linked or to replace it with another external account, or to merge or transfer different game accounts. A Google or Apple account already linked to another game account cannot be linked; if a user selects such an account from a Guest account, the user can log in to that game account after a confirmation window. In this case, the original Guest account can no longer be accessed from the app.
- A user who has lost a Guest account as described above may request its recovery through customer support. If an account-switch record remains on the server and the user’s identity is verified by the email address of the relevant Google or Apple account, the Operator moves that login link to the original Guest account. Game data is not copied or merged; if the login being moved is the only login of the current game account, the Operator, with the user’s consent, locks that game account instead of deleting it. When the game account that received the moved login is deleted, deletion of the locked game account is scheduled at the same time, and the locked account is deleted after the 7-day deletion waiting period has passed (where logins were moved to several game accounts, when the last of those accounts is deleted). Support may be limited where there is no switch record or 3 years have passed, or where sufficient identity verification is difficult.
- Account deletion can be requested in the app under More → Settings → Account → Delete Account; on the deletion screen, the request is confirmed by entering the current character name exactly and going through a 5-second countdown. Guest, Google and Apple accounts can all request deletion in the same way. If the app cannot be accessed, the email request method described on the Account and Data Deletion page can be used.
- Deletion requested in the iOS (iPhone or iPad) app proceeds immediately without a deletion waiting period and cannot be canceled. Deletion requested through the Android app or by email goes through a 7-day deletion waiting period. If the user accesses the account during the waiting period, the time remaining until deletion is shown, and selecting [Continue] cancels the deletion request and restores normal use. Once 7 days have passed, at the first daily 4:40 a.m. (Korea Standard Time) run thereafter, the account and game data, except information that must be retained under applicable laws, are deleted so that they cannot be recovered; once deletion processing has started, it cannot be canceled.
- When deletion is completed, the character name is released and becomes available to other users (during the deletion waiting period, the account continues to hold it). If the user logs in with the same Google or Apple account after deletion is completed, the user starts with a new game account without the previous data. Merely deleting the app or logging out does not delete the account and game data on the server, and the data of a Guest account that can no longer be accessed because of a switch to another game account also remains until deletion is requested.
- Under Google Play and Apple policies, account deletion is distinct from mere account suspension; in-app account deletion deletes the entire game account, including the linked Google and Apple logins, together with account-linked data that is not required to be retained under applicable laws.
- When an account using Sign in with Apple is deleted, the Operator requests Apple to revoke authorization using the Apple authentication information it holds. If revocation fails due to a temporary error, the encrypted authentication information and Apple user identifier are used only to retry revocation for 14 days and are then destroyed at the next scheduled processing (up to approximately 15 days); if, in the meantime, the same Apple account has been linked to and is being used with another game account, authorization is not revoked so that the login of that account is not cut off. Regardless of the outcome of revocation, the Operator still fulfills its obligation to delete the account and game data it holds.
- If the user stops using “Sign in with Apple” for this game in the Apple Account settings or deletes the Apple Account, a game account linked only to Apple login has its existing login invalidated and enters a 7-day deletion waiting state (canceled by logging in again during the waiting period and selecting [Continue]); for a game account also linked to Google login, only the Apple link and the Apple authentication information are deleted, and the game account and data are kept.
- Logging out does not delete the account or game data; upon logout, the device’s push notification registration is removed (on Android, the game closes after logout; on iOS, it returns to the title screen). Guest accounts have no logout function, and a Guest account not linked to Google or Apple may become inaccessible if the app is deleted or the device is changed.
- Users may choose not to consent to receive promotional push notifications in the consent window shown on first entry, and even after consenting may withdraw consent at any time in the game under More → Settings → Option → Push Notifications; withdrawal takes effect immediately. The Operator records the times of consent and withdrawal, does not send promotional notifications without consent and, even with consent, sends them only when both Korea Standard Time and the device’s local time are between 8:10 a.m. and 8:50 p.m. In addition, in accordance with Article 50(8) of the Act on Promotion of Information and Communications Network Utilization and Information Protection, the Operator reconfirms on the game’s start screen, every 2 years from the date of consent, whether the user consents to receive them (with notice starting 30 days before the confirmation deadline), and informs the user of the result of the choice (sender, date of processing, result of processing). If the user does not confirm by the confirmation deadline, the consent remains in effect, but promotional notifications are not sent until the user confirms again. The device’s notification permission can be turned off separately in the device settings.
- To prevent fraudulent use, the Operator’s server automatically detects and evaluates signs of abnormal activity. Accounts for which different types of abnormal signs have been confirmed above a certain threshold may, without human review, be excluded from public display in the rankings and from weekly Archery Challenge rewards, and claiming of weekly challenge reward mail already issued is also put on hold (mail whose claim deadline passes before the measure is lifted cannot be claimed). In addition, until the measure is lifted, in 1:1 Duels such accounts are shown on the lobby list to, and matched with, only accounts subject to the same measure. This measure is not lifted automatically; it is lifted after review by the operations staff. Heavier use restrictions, such as restrictions on claiming mail or coupons or blocking the saving of an account’s game data, are imposed only after direct review by the operations staff. Separately, the server may automatically reject, or adjust to the permitted range, save or reward requests that are impossible under the game rules. Users may request an explanation of, or object to, such automated decisions through the contact points in Article 13, and the Operator will have a person review the matter again and inform the user of the result.
- To prevent erroneous deletion or unauthorized deletion of another person’s account, the Operator may verify, to the minimum extent necessary, whether the requester is the user or a legitimate representative.
- Separately from the account deletion procedure, if a user exercises rights such as correction or deletion of personal information under the Personal Information Protection Act, the Operator will investigate the request without delay in accordance with applicable laws, take the necessary measures and inform the user of the result. Information that must be retained under other laws may be stored separately for the relevant statutory period.
Article 11. Procedures and Methods for Destroying Personal Information
- The Operator destroys personal information without delay when a reason for destruction arises, such as expiry of the retention period, achievement of the purpose of processing or account deletion. If an automatic destruction job scheduled for a set time cannot be completed due to a temporary failure, it is performed again in the next run.
- Information that must continue to be retained under other laws is kept separately from other information or with restricted access for the statutory retention period, and is then destroyed.
- Electronic files are deleted in a way that makes recovery or reproduction difficult. Destroyed information may remain in backup copies for failure recovery for the periods set out in Article 4, and is deleted automatically once those periods have passed. Backup copies are used only for failure recovery and for testing recovery procedures, and if the Service is restored from a backup, accounts that have already been destroyed are destroyed again using the destruction confirmation records. Separately stored backup copies are protected by a lock that prevents modification or deletion, so no one can delete them before the periods in Article 4 have passed.
- Where paper documents are processed, they are destroyed by methods that make recovery difficult, such as shredding or incineration.
Article 12. Measures to Ensure the Security of Personal Information
The Operator implements measures appropriate to the scale and risks of the Service to prevent the loss, theft, leakage, forgery, alteration or damage of personal information.
- Use of encrypted communications such as HTTPS/TLS
- Access control for account and server data through Firebase authentication, database security rules and similar means (account data is saved only through server functions)
- Verification of requests from the genuine app using Firebase App Check, and detection of app tampering and abnormal execution environments using the app protection SDK
- Encrypted storage (AES-256-GCM) of Apple authentication information; storage of purchase tokens and the like as irreversibly transformed values instead of the originals; encryption of backup copies made immediately before server updates
- Minimization of administrator privileges and secure management of credentials and secret keys
- Verification of in-app purchases and rewarded ads; detection of abnormal use, cheating and abuse
- Review of error and security logs and remediation of vulnerabilities as needed
- Minimization of personal information processing that is unnecessary for providing the Service
Article 13. Chief Privacy Officer and Contact Information
Users may send inquiries, complaints and requests for remedies relating to personal information protection to the contacts above, and the Operator will endeavor to review and handle them without delay in accordance with applicable laws.
Article 14. Remedies for Infringement of Rights
If consultation, dispute mediation or a report regarding an infringement of personal information is needed, the following organizations are available.
- Personal Information Dispute Mediation Committee: 1833-6972 / www.kopico.go.kr
- Privacy Incident Reporting Center (KISA): 118 (no area code) / privacy.kisa.or.kr
- Korean National Police Agency: 182 (no area code) / ecrm.police.go.kr
Article 15. Changes to the Privacy Policy
This Policy may be revised to reflect changes in the Service, the status of personal information processing, applicable laws or platform policies. If there is a change that significantly affects users’ rights, users will be notified before it applies by a method they can easily check, such as an in-game notice, the official website or the official Cafe.
Date of announcement: November 7, 2026
Effective date: November 7, 2026
When this Policy is revised, previous versions are kept, and the current Policy provides a way to view previous versions.
Changes (November 7, 2026):
- Described, in line with actual operation, the canceled 1:1 Duel match record (Articles 2 and 4), the retention of Welcome-Back Reward mail (Article 4), the app store refund notification records included in payment records and their destruction (Article 4), request logs of error responses and of server warm-up requests (Articles 4 and 7), and the in-game button that opens the official community (Article 6).
Changes (November 4, 2026):
- Added the purposes and items of processing for real-time 1:1 Duels, the information shown to other users, the retention periods of duel information, and the separation in duels of accounts under use restrictions (Articles 1, 2, 3, 4 and 10).
- Described, in line with actual operation, startup-delay diagnostic records and archery automated-play observation values (Article 2), the retention of Frost Dragon interruption reward mail and 1:1 Duel reward mail (Article 4), and the deletion-prevention lock on separately stored backup copies (Article 11).
Changes (October 23, 2026):
- Added the coupon redemption page of the official website (entry of a Nickname, coupon code and, for first-come, first-served coupons, Member Code; display of the recipient account for confirmation; storage of the Nickname in the browser), coupon redemption records and Member Codes (Articles 1, 2, 3, 4, 6, 7 and 8).
- Added the verification and delivery of Google Play pre-registration and App Store pre-order rewards, and the processing of App Store app transaction information for this purpose (Articles 1, 2 and 7).
- Updated the descriptions of the official Naver Cafe, the confirmation every 2 years of consent to receive promotional push notifications, the “Ad privacy choices” menu on iOS, the Bow enhancement level shown in the rankings, and the method of transmitting device identifier values and the records kept on the device, to match actual operations (Articles 2, 3, 6, 8, 10 and 15).
Changes (October 22, 2026):
- Added the processing that, where a different game account is started on a device that was using a Guest account (where the user logged in with a Google or Apple account already linked to another game account, or deleted the Android app and started again), releases the Nickname of the previous Guest account, which can no longer be accessed, and excludes it from the rankings, as well as the processing of device identifier values (irreversibly transformed values) for this purpose (Articles 1, 2, 3, 4 and 7).
Previous versions: Version effective November 4, 2026 (Korean) · Version effective October 23, 2026 (Korean) · Version effective October 22, 2026 (Korean) · Version effective October 13, 2026 (Korean) · Version effective October 12, 2026 (Korean) · Version effective September 23, 2026 (Korean)