WORKTIME SOFT · POLICY
Privacy Policy
Effective October 9, 2026. Applies commonly to the games provided by WorktimeSoft Inc. in the Republic of Korea.
1. Scope and controller
This policy applies to the official website of WorktimeSoft (주식회사 워크타임소프트, the “Company”) and the web and mobile services, software, games and related customer support that refer to this policy. The Company processes personal data and protects users’ rights under the Personal Information Protection Act (PIPA) and other applicable law.
Controller: 주식회사 워크타임소프트 (WorktimeSoft) / Representative: 김란 / Address: 인천광역시 서해구 솔빛로 55, 521동 3층 3호(청라동, 청라반도유보라), Republic of Korea / Privacy officer: 김란, Representative / Contact: [email protected]
| Service | Processing covered |
|---|---|
| WorktimeSoft company website | Device and connection information needed to access the site, and enquiries received by email. Visiting the company introduction page alone does not collect game accounts, login tokens, match information or payment information. |
| Covenant Rise | Data relevant to the account, sign-in, gameplay, purchase and support functions you use. The account and gameplay processing in sections 3–6 and account cookies, retention and deletion in sections 10–13 describe this game’s operating rules. |
Personal data is processed to the extent needed for the Services and features you use. Service-specific categories and purposes are explained below.
2. Purposes and legal grounds
The Company processes personal data as needed to provide the Services. Information generated during registration and use, supplied by external sign-in providers or provided by you in enquiries or transactions is used for the common and service-specific purposes below. Each purpose uses the data collected by the relevant Service and the retention and deletion rules in sections 11–13.
| Category | Purpose | Ground |
|---|---|---|
| Account and gameplay | Registration, sign-in, account connection, and progress, match and reward management | PIPA Article 15(1)(1): separate consent to collection and use of personal data obtained before registration. |
| Payments and dispute records | Purchase verification, delivery, cancellation, refunds and statutory transaction records | Performance of a contract and legal obligations, including Article 6 of the Act on the Consumer Protection in Electronic Commerce, etc. |
| Security and misuse prevention | Detecting and preventing account theft, abnormal access, automated repeated requests, fraudulent transactions and benefit abuse; investigating terms or operating-policy breaches and restricting use; investigating security incidents, recovering from harm and handling appeals | Processing necessary for contract performance. Where a separate legitimate interest is relied on, only to the extent that PIPA Article 15(1)(6) is satisfied. |
| User verification, operational notices and support | Verifying users and account ownership, recovering access, handling enquiries, reports and disputes, notifying terms or policy changes and service operations, and providing security warnings and outcomes. Comparing email addresses provided during registration or enquiries with necessary account and transaction records, and sending verification and notices by email | Measures requested by the user and processing necessary for contract performance: PIPA Article 15(1)(4). Statutory notices rely on the relevant legal ground, such as Article 15(1)(2). |
| Service quality and stability | Analysing usage, connection frequency, errors and performance; checking data accuracy and consistency; resolving and recovering from outages; improving features and environments; developing features and technology related to existing Services | Processing necessary for contract performance or legitimate interests meeting PIPA Article 15(1)(6). Analysis or development requiring separate consent is performed with that consent. |
| Legal compliance and protection of rights | Retaining transaction and dispute records, responding to statutory requests, establishing facts and managing evidence to protect users’ and the Company’s rights and resolve disputes | Legal obligations, including PIPA Article 15(1)(2). Separate processing to protect rights is limited to cases satisfying Article 15(1)(6). |
| Processing requiring separate consent | Stated purposes, such as a new optional feature | Separate consent under the applicable ground, including PIPA Article 15(1)(1). |
If required information is not provided, the relevant account or function may be unavailable. Basic service access is not restricted merely because you refuse optional processing. Agreement to the terms or acknowledgement of this policy is not treated as consent to advertising messages.
Both guest and registered accounts separately agree to the Terms of Service and to collection and use of personal data before registration. Required collection and use information presented at registration is as follows.
| Category | Details |
|---|---|
| Purpose | Confirm eligibility by age and whether guardian consent is required; register and identify members; sign in and link accounts; manage game progress, battles and rewards. Where a family connection exists, the family manager authenticated through the linked email can see the linked game names and nicknames. After a member reaches adulthood, a manager authenticated through the existing email can continue to see this information until the linked email is changed or the family connection ends. Player IDs, age, activity and battle history, currency and purchase records are not displayed in family management, and the family management screen does not provide game sign-in credentials. In the game’s “Recover with guardian email” flow, verify the linked guardian email, select an eligible linked account, and approve switching the current device to that account and signing out its previous devices. You can then return to the selected existing account (the same UID) and saved progress. Change the management email on the website; contact support to change or end an individual connection or withdraw consent, subject to identity and authority verification. |
| Data | The whole-year age selected by the player or the age band derived from a platform result; additional-verification and guardian-approval results; platform verification requests and temporary authentication/integrity evidence; necessary age restrictions, verification times and approval-revocation references. Internal account identifier (UID); optionally linked sign-in provider and provider account identifier; game nickname; registration and activity times; hash of guest credentials; faction and country selections; currency, cards, upgrades, rank, match history and rewards; required consent versions and times and guardian-consent status. Game registration does not ask for a date of birth, real name, phone number, address, US state or player email. Guardian email collection and use is explained and consented to separately. |
| Retention and use period | Information is retained until account deletion or withdrawal of consent. Ordinary guest accounts not linked to an external sign-in expire 30 days after their last activity and are deleted through subsequent scheduled cleanup. This 30-day expiry and deletion rule does not apply to a child’s game account and progress created through family registration with guardian consent. Transaction and dispute records subject to statutory retention are kept separately for the periods stated in the Privacy Policy. Original platform responses and verification tokens are not retained after the relevant check. Pending-registration verification records are deleted on registration or cancellation, or in scheduled cleanup after their validity period of up to 30 minutes. Records for checking duplicate registration requests remain valid for up to five minutes after completion and are then removed in scheduled cleanup. Account whole-year ages or age bands, verification methods, restrictions and evidence of guardian consent are retained until the relevant game account is deleted. Approval-revocation references are deleted with the account. Linked revocation records are kept while needed to enforce the restriction. Unlinked Apple revocation records are removed in scheduled cleanup after 30 days from last receipt, and unlinked Google Play revocation records after 90 days from revocation. |
| Right to refuse and consequences | You may refuse consent. This is the minimum information required to provide the account and game service. Refusal prevents guest or registered membership and use of the game. |
Processing based on grounds other than consent, such as handling support requests, fulfilling purchases and retaining statutory records, is distinguished by purpose and legal ground. Registration consent does not include consent to advertising messages or personal-data processing for a separate purpose through business tools.
Optional usage analytics in Covenant Rise relies on separate consent to measure tutorial progress and drop-off, entry into a first battle, return visits and advertising acquisition performance. Game registration or notification consent does not substitute for analytics consent.
3. Accounts and authentication
| Category | Data | Purpose |
|---|---|---|
| Ordinary guest account | Account ID, creation, last-activity and expiry times, and credential hash | Guest identification, continued sign-in, expiry and deletion |
| Registered account | Account UID, chosen sign-in provider and its account identifier, creation and activity information | Authentication, account connection and service use |
| Registration confirmation | Agreed document and notice versions, collection/use consent status and times, necessary age bands, age restrictions, verification methods and times, guardian-consent status, version and times, and references for approval revocation | Checking and recording conditions of use |
| Account-closure request | Requesting account, request and processing status and times, and deletion-status receipt hash | Identity verification, deletion processing and status information |
| Child family account | Account ID, game nickname, family-registration status, guardian connection and consent records, creation, activity and authentication-expiry information, and credential hash | Child account identification, progress retention, guardian management and account recovery |
Before creating an account, Covenant Rise uses supported Apple and Google features to check age ranges and any required additional verification or guardian approval. Sufficient results remove the need to enter an age. Where permitted, you may select your whole-year age when a result is unavailable or sharing is declined. Selecting an age cannot replace mandatory platform verification or approval; registration is restricted until it is completed. The game account is created after any required service-specific guardian consent and player consent. External sign-in may then be linked optionally. Self-declared ages are recorded in whole years, while platform information is retained as the confirmed age band. They are used to determine eligibility and protections under the applicable age thresholds. Original platform responses and verification tokens are not retained after the check. We retain the self-declared whole-year age or necessary age band, verification method, restriction results, verification time and approval-revocation references. We do not infer birthdays or dates of reaching a particular age from the selected age or age bands. When needed, we request another platform check or age selection. Revocation references are used only to handle approval withdrawal for the app. These values are protected as personal data linked to an account.
Original platform responses and verification tokens are not retained after the relevant check. Pending-registration verification records are deleted on registration or cancellation, or in scheduled cleanup after their validity period of up to 30 minutes. Records for checking duplicate registration requests remain valid for up to five minutes after completion and are then removed in scheduled cleanup. Account whole-year ages or age bands, verification methods, restrictions and evidence of guardian consent are retained until the relevant game account is deleted. Approval-revocation references are deleted with the account. Linked revocation records are kept while needed to enforce the restriction. Unlinked Apple revocation records are removed in scheduled cleanup after 30 days from last receipt, and unlinked Google Play revocation records after 90 days from revocation.
Where a family connection exists, a family manager authenticated through the linked email can see the connected game names and nicknames. Even after a player reaches adulthood, a manager using the existing email can continue to see this information until the linked email is changed or the family connection is ended. The family management screen does not show player IDs, ages, connection or battle records, currency balances or purchase history, and the family management screen does not provide game sign-in credentials. In the game’s “Recover with guardian email” flow, verify the linked guardian email, select an eligible linked account, and approve switching the current device to that account and signing out its previous devices. You can then return to the selected existing account (the same UID) and saved progress. Change the linked email through family account management on the website. Requests to change or end an individual member’s connection or withdraw consent are handled by customer support after identity and authority checks.
When an existing account rechecks age or platform approval, original platform responses and verification tokens are not retained after the check. A pending check uses references linking the account and verification request, the platform, result, verification time and expiry. Temporary check records are deleted on completion or cancellation, or in scheduled cleanup after their validity period of up to 30 minutes. Completion-retry records remain valid for up to five minutes and are then removed in scheduled cleanup. The latest check status, platform and verification time are linked to the account and retained until that game account is deleted. These records enforce current access restrictions and prevent older results from incorrectly removing them. Approval-revocation references and records follow the retention periods stated above.
New Covenant Rise game accounts can only be created in the mobile game app. On the website, existing family accounts can sign in to view linked games and nicknames and change the management email.
To verify that a request came from the app and has not been reused, we process temporary request references, verification values and expiry times. When Apple app attestation is used, we also retain the public verification key, a hash of its identifier and a request-sequence value. These records are deleted on completion or cancellation of registration or a recheck, or during scheduled cleanup after a validity period of up to 30 minutes. They do not retain original platform age responses or dates of birth.
4. Information received through external sign-in
| Provider | Information received and used | Storage and use |
|---|---|---|
| User identifier and authentication response | Only the account identifier is used for connection. Email and real name are not stored in the game account. | |
| Apple | User identifier and sign-in response, including authentication and refresh tokens | The account identifier is used. Email and real name are not stored in the game account. Tokens needed to revoke the Apple connection on account closure are stored encrypted. |
| User identifier and authentication response | Only the account identifier is used for connection. Email and real name are not stored in the game account. |
We do not access mailboxes or contact lists through external sign-in. Accounts are not automatically merged even if different providers use the same email address. Google and Facebook access tokens are used for sign-in processing and are not retained long-term in the account database.
We do not request email permission through external sign-in. Unnecessary email or name fields in a response are not saved as account information. Apple revocation tokens are deleted after use for account deletion.
Optional external account connection uses the sign-in provider and its account identifier; the player’s email and real name are neither requested nor stored as game-account data. Previously held contact information and support materials you send directly by email follow their respective retention and deletion rules. Game-account verification uses the UID and an authenticated session. Knowing a UID alone does not authorise an account change or refund.
5. Game profiles and usage records
The Company processes nicknames, selected factions and countries, currency, cards, upgrades, passes, missions, attendance, rewards, transactions, rankings, match records, battle and story results, and related times. A country displayed in a game is not used as proof of payment country or actual residence.
Opponents and ranking screens may show information needed for gameplay, such as nickname, selected country and faction, deck and match records. Emails, external sign-in identifiers and purchase evidence are not displayed in public profiles. Do not include another person’s personal data or sensitive information in a nickname.
Covenant Rise’s friends feature is optional. Players exchange friend codes, mutually accept requests and play private one-on-one matches with accepted friends. Chat, direct messages and voice communication are not provided. We process the feature-choice version and time, friend codes, requests and accepted relationships, private rooms, invitation status and related times. Other participants see nicknames, selected factions, rank points and friend codes. Turning the feature off removes friendships and pending requests and invitations while basic gameplay remains available. Blocked relationships remain until unblocked or account deletion; records limiting repeat requests to the same person are used for one minute and then become eligible for deletion. Reports contain the reporter, target, selected reason, processing status and times and are retained for up to 30 days from submission. After resolution they are deleted after the earlier of seven days or the original expiry. A friend code remains with the account for reuse when the feature is off. Room and match records follow the game-record retention periods below.
Under the company’s youth-protection policy, the friends feature requires guardian permission for players under 18 or whose 18+ status has not been established. This is not a universal legal-adulthood rule. Permission is separate from registration consent and linked to the player’s choice of the same feature notice.
Permission records contain the linked game and guardian-management account identifiers, notice version, language and verification hash, player-choice time, guardian declaration, consent response and approval time. Requests are removed in scheduled cleanup after up to 30 minutes. Permission records are deleted on withdrawal of the player’s choice or guardian permission, or deletion of the relevant account.
Do not use personal information such as a real name, phone number or email address as your nickname.
Tutorial and help progress and acknowledgement states, as well as probability-based item draw results and the applied probability-table version, are used to track progress and verify awards. Detailed state needed to recover a live match or confirm its result is processed separately from cumulative account statistics and inventory.
6. Access security and misuse prevention
Access processing involves IP addresses, connection times, request paths, authentication cookies and technical errors. Repeated-request controls temporarily use transformed identifiers derived from original IP addresses and authentication information, together with request counts, in memory. Original IP addresses are not stored long-term in game profiles.
Abnormal access may trigger additional authentication or verification using Cloudflare Turnstile. Security and incident logs are managed to avoid recording unnecessary personal data, such as authentication tokens or enquiry content.
To prevent simultaneous use of the same account, the Company manages the current login-session identifier and issue time. A new login ends game access through the previous session. Session information is used for account protection and deleted with the account.
Where abnormal sign-in or access, account theft, fraudulent transactions or breaches of terms or operating policies are suspected, the Company may compare and analyse the necessary account identifiers, email addresses and verification status, access, usage and transaction records, and reports collected by that Service. Findings are used for further verification, account protection, misuse prevention, assessment of restrictions, recovery from harm and appeals.
Where necessary, the Company may use registered contact details or an email supplied in an enquiry to verify account ownership, notify abnormal activity, request further verification or communicate outcomes. Security and operational notices are handled separately from advertising-message consent.
7. Customer support and rights requests
When an enquiry, report or appeal about the Company or a Service is received, the Company processes the reply email, content, attachments and necessary account ID, nickname, incident time and order number. If ownership of an account or transaction, or legal guardian status, needs to be checked, the required information and reasons are explained and only the minimum necessary material is requested.
Do not send passwords, sign-in verification codes, full payment-card numbers or resident registration numbers. Unnecessary information in submitted materials is deleted or masked.
Additional materials submitted to verify identity or representative authority are deleted without delay once verification is complete. Where retention is required by law, only the necessary parts are stored separately on the grounds and for the periods in section 12.
8. Purchase and refund information
When you purchase paid content or request a refund, the Company processes app-store transaction identifiers, products, purchase and verification times, status, amount and currency, delivery, cancellation and refund records, and necessary purchase evidence. Evidence required to retry purchase processing is stored encrypted.
The app store you choose handles payment methods and charging. The Company checks the purchase-account connection, receipt authenticity and cancellation or refund status; it does not directly collect full card numbers or payment passwords. A Google Play pre-purchase country check is used only to determine purchase availability, not stored in the game database or profile or reused for marketing.
9. Device and website information
Browser and device type, operating system, IP address, request path and technical errors may be processed for service provision and security when accessing a website, app or other Service.
The Company disables advertising-ID collection and personalised advertising use for optional usage analytics. Information collected by external login providers and app stores for their own services is governed by their privacy policies.
For compatibility checks, required-update notices and preventing matches between incompatible game-rule versions, we link the app platform, distribution channel, app, build and game-rule versions and observation time to the account. The latest values are updated for each account and deleted with it.
Country-level information provided by Cloudflare from the connection IP may be used temporarily to apply regional registration and age-check rules. This does not request an address or US state, infer a date of birth, or separately store that country value in age-verification records. It is distinct from the country display selected by the player in the game profile.
Game reminders in Covenant Rise are optional. If you consent to promotional reminders and allow device notifications, we process account linkage, your notification choice and notice version and time, notification tokens and installation identifiers, platform and language, and reminder occurrence and delivery status to deliver reminders and handle opt-outs. Android delivery uses Google Firebase Cloud Messaging (FCM); iOS delivery uses Apple Push Notification service (APNs). These providers may process device, app and network information for delivery and security. Declining or withdrawing notifications does not restrict account creation, sign-in, battles or other gameplay. You can turn notifications off in the game or device settings. Account, occurrence and currency-grant records used to verify rewards and prevent duplicate grants are processed separately from notification choices.
Basic SDK app events include first open, sessions, and app or operating-system updates. Supported app-store integrations may include purchase/refund events and product identifiers, amounts, currencies and quantities. The Company does not add receipt contents or purchase authentication tokens to analytics events.
Optional usage analytics · Google Analytics for Firebase: For consenting players, we process an app installation identifier, app version, operating system/device type/language, approximate region, access/session times, and events for tutorial start, steps, completion and battle entry. Campaign and acquisition-source information available through supported platforms and advertising connections may also be analysed. We do not send nicknames, email addresses, game account IDs, exact ages, currency balances or purchase receipts to the analytics service. An installation identifier distinguishes usage across an installation; this is not fully anonymous collection.
Analytics is off by default. You may consent separately or withdraw in Settings → Usage analytics, and can play after declining or withdrawing. Optional analytics is not applied to accounts under 16, with unconfirmed age, or requiring additional platform approval. Activity before consent is not uploaded retrospectively. Withdrawal stops new analytics transmission and resets local analytics data and identifiers. Previously transmitted information remains subject to the retention and deletion-request procedures in Section 11.
10. Cookies and device storage
Covenant Rise uses cookies for continued sign-in and security. Login sessions last up to seven days, guest authentication is based on 30 days of activity, and temporary registration-consent cookies last 30 minutes. Temporary cookies are also used during sign-in and reauthentication for account deletion. A temporary cookie, valid for up to 10 minutes, binds a game account recovery request to that device and prevents the request from being used on another device.
Browser storage may contain account selection, display and sound settings, device-only practice progress and request information needed for communication recovery.
You can block cookies or delete stored data through browser privacy or site-data settings. Mobile devices also provide app-data and site-storage controls. Blocking or deleting them may restrict continued sign-in, guest access or storage functions. Deleting device data alone does not close the server account.
11. Retention of account and game information
This section describes retention for Services provided in the Republic of Korea. If the Company provides Services in another region, it separately explains the processing rules applicable there.
| Information | Period | Handling |
|---|---|---|
| Registered account, game records and contact details | Until account closure or withdrawal of collection and use consent; deletion processing begins on request | Prompt deletion except for records subject to statutory retention |
| Ordinary guest account and game records without external sign-in | Expires 30 days after last activity | Deleted during periodic cleanup after expiry |
| Encrypted Apple revocation token | Account lifetime and the period needed to complete disconnection | Deleted after revoking the Apple connection on account closure |
| Deletion-status receipt | Available for up to 30 days from the request | Completed cases are deleted during periodic cleanup after expiry. Pending cases remain only as long as needed to complete deletion. |
| Child family account and game records | Until the relevant game account is closed or collection and use consent is withdrawn | Excluded from ordinary guest 30-day expiry deletion. On a deletion request, information not subject to statutory retention is promptly deleted. |
If an external-service or server failure occurs during deletion, account use is blocked first and processing is retried. Pending data is not reused for gameplay or marketing.
A family email connection is not removed merely because age changes. Expiry of authentication or ending a connection through management-account closure or similar circumstances does not itself delete the game account and progress. Family management information and members’ game-account information each follow their own retention periods.
Original platform responses and verification tokens are not retained after the relevant check. Pending-registration verification records are deleted on registration or cancellation, or in scheduled cleanup after their validity period of up to 30 minutes. Records for checking duplicate registration requests remain valid for up to five minutes after completion and are then removed in scheduled cleanup. Account whole-year ages or age bands, verification methods, restrictions and evidence of guardian consent are retained until the relevant game account is deleted. Approval-revocation references are deleted with the account. Linked revocation records are kept while needed to enforce the restriction. Unlinked Apple revocation records are removed in scheduled cleanup after 30 days from last receipt, and unlinked Google Play revocation records after 90 days from revocation.
| Data | Retention and deletion |
|---|---|
| Public app-verification keys, verification values linking keys and requests, and request-sequence values | Deleted on completion or cancellation of registration or a recheck, or during scheduled cleanup after a validity period of up to 30 minutes |
| Latest per-account app platform, distribution channel, app, build and game-rule versions, and observation time | Updated with the latest values and deleted when that game account is deleted |
| Detailed recovery state for completed real-time matches | For matches with settled results, detailed state is cleaned up after seven days from completion. On an account-deletion request, related detailed records are cleaned up through the deletion process first. Cumulative account statistics and reward records follow the separate account and game-data retention periods. |
| Information | Retention and deletion |
|---|---|
| Device registration, notification token and installation linkage | Registration is revoked and removed on opt-out, sign-out, credential replacement or account deletion. Registrations not renewed for 30 days are excluded from delivery and removed during scheduled cleanup. |
| Notification choices, consent and required guardian approval | The current choice, notice version and time are retained until account deletion. Guardian approval is removed when that choice changes or is withdrawn. |
| Reminder delivery and reward-confirmation ledger | Removed during scheduled cleanup seven days after the reminder reward window ends, or with account deletion. Ordinary records of credited currency follow the applicable game and transaction retention periods. |
| Firebase installation identifier | The app requests deletion from Google when processing an opt-out. Google states that data is removed from live and backup systems within 180 days after the deletion API call. If notifications are disabled only in device settings, the app requests revocation and deletion when it can detect and process the change on a subsequent launch. |
User-level and event-level optional analytics data is retained for two months, without restarting retention upon new activity. This period applies to analytics records that distinguish individual users. Aggregated statistics that do not distinguish individuals may follow a different retention period. Withdrawal stops new transmission; it does not immediately delete data already sent to Google servers. You may request deletion through our privacy contact, including before resetting the app identifier. After that identifier has been reset, locating records associated with the previous identifier may be difficult.
12. Support and statutory transaction records
| Category and data | Period | Ground or purpose |
|---|---|---|
| Reply email, enquiry and resolution of an ordinary support request | Up to one year after resolution | Continuity of handling and follow-up on the same matter |
| Contract and withdrawal records: order number, product, contract and withdrawal details and times | Five years | Article 6 of the Act on the Consumer Protection in Electronic Commerce, etc. and Article 6 of its Enforcement Decree |
| Payment and delivery records: transaction identifier, amount and currency, payment, grant and refund records | Five years | Article 6 of the same Act and Article 6 of its Enforcement Decree |
| Consumer complaints and disputes: requester contact details, dispute details, verification materials and outcome | Three years | Article 6 of the same Act and Article 6 of its Enforcement Decree |
| Product-description and advertising records: published product information and advertisements | Six months | Article 6 of the same Act and Article 6 of its Enforcement Decree |
Statutory transaction records remain separate from game-use information after account closure and are accessible only to staff who need them for the relevant purpose. Where a separate legal ground, such as a court order, requires longer retention, only the relevant materials are retained for the necessary period. They are promptly destroyed when retention ends.
13. Deletion of personal data
The Company promptly destroys personal data when its retention period ends or its purpose has been achieved and it is no longer needed. Electronic files are deleted using methods that make recovery difficult; paper materials are shredded or incinerated. Records retained under law are managed separately.
Request account closure and full deletion using the account-deletion function on the relevant game’s website or app. For Covenant Rise, use game settings or https://covenantrise.com/account/delete/. After identity verification, sign-in connections, contacts, profile and game records are processed for deletion. The receipt lets you check processing status.
Cloudflare D1 recovery backups may retain pre-deletion data for up to 30 days. Backup access is limited to recovery needs. Following restoration, deletion requests are reconciled so that deleted information is not reused in the Service. Device-only information can be removed through browser-storage or app-data controls.
Personal-data rights requests may be submitted through customer support or [email protected]. Players may request deletion of their own account using the website or app deletion function in section 13. Guardian requests to delete a child’s account, and rights requests from people who have difficulty accessing an account, may be submitted through customer support or [email protected]. The Company verifies the requester’s authority and communicates the outcome.
14. Processing providers and business tools
| Provider or service | Work | Information processed |
|---|---|---|
| Cloudflare, Inc. | Web hosting, game servers and databases, match processing, access protection and company-domain email forwarding. Sending guardian verification emails when family accounts are provided. | Account and game records, authentication and transaction information, access requests and other material needed for that work. Sender and recipient addresses, message content and attachments of enquiries sent to the company domain are processed for forwarding. Verification delivery processes recipient email addresses, a fixed notice containing a one-time code, and sending and delivery information. |
| Google LLC · Gmail | Sending and receiving customer-support emails and managing support records | Requester reply email, enquiry content, attachments and processing records |
| Google LLC · Firebase Cloud Messaging (FCM) / Apple Inc. · APNs | Delivery of optional mobile notifications | Notification tokens and installation identifiers, app, device and network information, and notification content and delivery information. Account passwords, game-currency balances and battle history are not included in notification content. |
Providers’ subprocessors and privacy information
- Cloudflare subprocessors and functions
- Google Privacy Policy and external processing
- Firebase subprocessors and functions
- Firebase privacy, security and data processing information
- OpenAI subprocessors and the listed product scope
- Anthropic subprocessors · Trust Center
- ChatGPT consumer services · Korea privacy and processor information
- Anthropic consumer services · external providers and privacy
- Claude consumer-service retention and deletion
- Microsoft Privacy Statement
- Microsoft Products and Services Data Protection Addendum
The Company’s processing agreements address prohibitions on use outside the stated purpose, safeguards, subprocessors, management, supervision and responsibility. The Company checks providers’ handling of the entrusted work.
AI and business-material management services
| Provider or service | Work | Data | Method |
|---|---|---|---|
| OpenAI · API (including Codex with an API key) | Classifying and summarising enquiries and drafting responses; verifying and protecting users and accounts; assisting investigations of abnormal behaviour, misuse and security incidents; reviewing reports and appeals and drafting operational and security notices; reconciling purchase, payment and refund information and documenting outcomes; developing, maintaining and improving service quality, investigating errors, and verifying data migration and recovery. | Account ID and nickname, reply email, enquiry content and attachments, order number, product, purchase date, amount, transaction status, refund request and outcome as needed for the task; where needed for security or technical investigations, the necessary portions of email-verification status collected by the relevant Service, connection times, IP addresses, request paths, usage, gameplay and transaction-processing records, reports, appeals and identifiers in error logs. | Necessary materials from code, files, logs and tool results are transmitted over a network when making business-related API requests or running development and connected tools such as Codex. |
| OpenAI · ChatGPT Pro (including Codex with a ChatGPT account) | Classifying and summarising enquiries and drafting responses; verifying and protecting users and accounts; assisting investigations of abnormal behaviour, misuse and security incidents; reviewing reports and appeals and drafting operational and security notices; reconciling purchase, payment and refund information and documenting outcomes; developing, maintaining and improving service quality, investigating errors, and verifying data migration and recovery. | Account ID and nickname, reply email, enquiry content and attachments, order number, product, purchase date, amount, transaction status, refund request and outcome as needed for the task; where needed for security or technical investigations, the necessary portions of email-verification status collected by the relevant Service, connection times, IP addresses, request paths, usage, gameplay and transaction-processing records, reports, appeals and identifiers in error logs. | Necessary materials from code, files, logs and tool results are transmitted and stored over a network when staff enter conversations, attach files or use development and connected tools such as Codex. |
| Anthropic · Claude API | Classifying and summarising enquiries and drafting responses; verifying and protecting users and accounts; assisting investigations of abnormal behaviour, misuse and security incidents; reviewing reports and appeals and drafting operational and security notices; reconciling purchase, payment and refund information and documenting outcomes; developing, maintaining and improving service quality, investigating errors, and verifying data migration and recovery. | Account ID and nickname, reply email, enquiry content and attachments, order number, product, purchase date, amount, transaction status, refund request and outcome as needed for the task; where needed for security or technical investigations, the necessary portions of email-verification status collected by the relevant Service, connection times, IP addresses, request paths, usage, gameplay and transaction-processing records, reports, appeals and identifiers in error logs. | Transmission of the materials needed for API requests |
| Anthropic · Claude Pro | Classifying and summarising enquiries and drafting responses; verifying and protecting users and accounts; assisting investigations of abnormal behaviour, misuse and security incidents; reviewing reports and appeals and drafting operational and security notices; reconciling purchase, payment and refund information and documenting outcomes; developing, maintaining and improving service quality, investigating errors, and verifying data migration and recovery. | Account ID and nickname, reply email, enquiry content and attachments, order number, product, purchase date, amount, transaction status, refund request and outcome as needed for the task; where needed for security or technical investigations, the necessary portions of email-verification status collected by the relevant Service, connection times, IP addresses, request paths, usage, gameplay and transaction-processing records, reports, appeals and identifiers in error logs. | Staff conversation input, file attachments and review of responses |
| Microsoft · Microsoft 365 (Office 365) / Excel / OneDrive | Preparing, classifying, reconciling, storing, synchronising and sharing materials among authorised staff for user and account management, support, complaints and disputes, payment, settlement and refund reconciliation, misuse and security investigations, service operation and maintenance, and statutory recordkeeping. | Account ID, nickname and reply email, enquiries, reports, appeals and attachments, order number, product, purchase date, amount, transaction status, refund request and outcome as needed for the task; where needed for security or technical investigations, the necessary portions of collected connection times, IP addresses, request paths, gameplay and transaction-processing records, and identifiers in error logs. | Creating business documents and spreadsheets in Microsoft 365 (Office 365) and Excel, and storing, synchronising and sharing them in OneDrive |
The Company uses these services for support, user management, account protection, security investigations, transactions, refunds, and service development and maintenance. It enters, attaches or connects only material needed for each request and removes or masks unnecessary identifiers and attachment content. Login passwords, verification codes, secret keys and full payment-card numbers are not included in the data processed for this work.
Originals, business files, conversations and attachments managed by the Company follow the relevant retention periods in sections 11 and 12. Temporary working copies are deleted once the task’s purpose is achieved.
AI providers may retain security records and residual data after deletion under the relevant service contract and privacy terms. Processing materials for Company work is not intended to supply data for the provider’s general model improvement.
Personal-data processing through business tools follows this policy’s purposes, categories, retention, processing-provider and overseas-transfer rules. Processing requiring separate consent takes place within the scope of that consent.
Where needed to investigate service errors or migrate or recover data, the account, gameplay, transaction and error information in the table may be processed through AI services. Only information needed for the task is used; unnecessary identifiers are removed or masked.
External providers may use affiliates or other processors to operate their services. Their functions and applicable services are described in the official information below; scope differs between consumer and organisational products.
Processing and protection conditions for Microsoft services follow the official policies and contracts applicable to the relevant service.
Processing conditions and the storage, retention and deletion of materials are managed separately for API services and consumer Pro services under each service’s contract and the relevant rules in this policy.
AI-assisted development, maintenance and error investigation include processing code, files, logs and connected-tool results through development tools such as Codex. If those materials contain personal data supplied to AI, that data may also be processed by the relevant AI service. The Company limits materials to what the business purpose requires and removes personal data or substitutes test data where possible. AI processing of business materials is distinguished from a provider’s model-training or improvement use and is managed under each service’s contract, policy and applicable data settings.
The Company uses Microsoft 365 (Office 365), Excel and OneDrive to create, store, synchronise and share materials needed for user and account management, support, transactions and refunds, security investigations and service operation. Data categories and retention follow the rules for the relevant activity in this policy.
| Processor | Service | Data |
|---|---|---|
| Google LLC · Google Analytics for Firebase | Optional usage analytics and acquisition-performance measurement | App installation identifier, app/device information, usage events and available acquisition information listed in Section 9 |
15. Overseas transfers
The Company’s AI work for support, user management, account protection, abnormal-activity and security investigations, payments, refunds, service development, maintenance and error investigation includes OpenAI API, ChatGPT Pro, Anthropic Claude API and Claude Pro. Microsoft 365 (Office 365), Excel and OneDrive are used to manage business materials. Use of these services may transmit or store the personal data below on overseas servers or allow access or processing from abroad. Excel files fall within the relevant service’s transfer scope when uploaded or synchronised to OneDrive or attached to an AI service.
| Receiving service | Data | Purpose | Timing and method |
|---|---|---|---|
| OpenAI · API (including Codex with an API key) | Account ID and nickname, reply email, enquiry content and attachments, order number, product, purchase date, amount, transaction status, refund request and outcome as needed for the task; where needed for security or technical investigations, the necessary portions of email-verification status collected by the relevant Service, connection times, IP addresses, request paths, usage, gameplay and transaction-processing records, reports, appeals and identifiers in error logs. | Classifying and summarising enquiries and drafting responses; verifying and protecting users and accounts; assisting investigations of abnormal behaviour, misuse and security incidents; reviewing reports and appeals and drafting operational and security notices; reconciling purchase, payment and refund information and documenting outcomes; developing, maintaining and improving service quality, investigating errors, and verifying data migration and recovery. | Necessary materials from code, files, logs and tool results are transmitted over a network when making business-related API requests or running development and connected tools such as Codex. |
| OpenAI · ChatGPT Pro (including Codex with a ChatGPT account) | Account ID and nickname, reply email, enquiry content and attachments, order number, product, purchase date, amount, transaction status, refund request and outcome as needed for the task; where needed for security or technical investigations, the necessary portions of email-verification status collected by the relevant Service, connection times, IP addresses, request paths, usage, gameplay and transaction-processing records, reports, appeals and identifiers in error logs. | Classifying and summarising enquiries and drafting responses; verifying and protecting users and accounts; assisting investigations of abnormal behaviour, misuse and security incidents; reviewing reports and appeals and drafting operational and security notices; reconciling purchase, payment and refund information and documenting outcomes; developing, maintaining and improving service quality, investigating errors, and verifying data migration and recovery. | Necessary materials from code, files, logs and tool results are transmitted and stored over a network when staff enter conversations, attach files or use development and connected tools such as Codex. |
| Anthropic · Claude API | Account ID and nickname, reply email, enquiry content and attachments, order number, product, purchase date, amount, transaction status, refund request and outcome as needed for the task; where needed for security or technical investigations, the necessary portions of email-verification status collected by the relevant Service, connection times, IP addresses, request paths, usage, gameplay and transaction-processing records, reports, appeals and identifiers in error logs. | Classifying and summarising enquiries and drafting responses; verifying and protecting users and accounts; assisting investigations of abnormal behaviour, misuse and security incidents; reviewing reports and appeals and drafting operational and security notices; reconciling purchase, payment and refund information and documenting outcomes; developing, maintaining and improving service quality, investigating errors, and verifying data migration and recovery. | Network transmission when making API requests or running connected tools needed for business processing or technical investigations |
| Anthropic · Claude Pro | Account ID and nickname, reply email, enquiry content and attachments, order number, product, purchase date, amount, transaction status, refund request and outcome as needed for the task; where needed for security or technical investigations, the necessary portions of email-verification status collected by the relevant Service, connection times, IP addresses, request paths, usage, gameplay and transaction-processing records, reports, appeals and identifiers in error logs. | Classifying and summarising enquiries and drafting responses; verifying and protecting users and accounts; assisting investigations of abnormal behaviour, misuse and security incidents; reviewing reports and appeals and drafting operational and security notices; reconciling purchase, payment and refund information and documenting outcomes; developing, maintaining and improving service quality, investigating errors, and verifying data migration and recovery. | Network transmission and storage when business materials are entered in conversations, attached as files or supplied through connected tools |
| Microsoft · Microsoft 365 (Office 365) / Excel / OneDrive | Account ID, nickname and reply email, enquiries, reports, appeals and attachments, order number, product, purchase date, amount, transaction status, refund request and outcome as needed for the task; where needed for security or technical investigations, the necessary portions of collected connection times, IP addresses, request paths, gameplay and transaction-processing records, and identifiers in error logs. | Preparing, classifying, reconciling, storing, synchronising and sharing materials among authorised staff for user and account management, support, complaints and disputes, payment, settlement and refund reconciliation, misuse and security investigations, service operation and maintenance, and statutory recordkeeping. | Network transmission and storage when business files are uploaded, synchronised or shared |
The Company uses Cloudflare infrastructure, Gmail, external sign-in providers and app stores, and the AI and cloud business services in section 14. Storage on their overseas servers or access by overseas providers may constitute an overseas transfer under PIPA. Overseas-transfer rules apply even when Services are offered only to users in Korea.
| Category | Transfer and processing details |
|---|---|
| Cloudflare recipient and contact | Cloudflare, Inc. / Privacy enquiries: [email protected] / Contract enquiries: [email protected] |
| Cloudflare data and purposes | Necessary account identifiers, authentication and contact information, gameplay, match and transaction records, IP addresses and access requests. Website and game provision, storage, authentication, security and incident response. Sender and recipient addresses, content and attachments of enquiries received at the company domain are processed for forwarding to staff inboxes. On a family verification request, the guardian’s recipient email and notice containing a one-time code are sent through Cloudflare email delivery services, which process sending and delivery information. |
| Cloudflare timing and method | Network transmission and storage when handling access, sign-in, gameplay and related requests; access by authorised staff where technical support is needed |
| Cloudflare processing regions | Processing may occur in multiple countries and regions where Cloudflare provides services. See the Cloudflare network locations for countries and cities. Regions may differ for request processing, storage and technical support. |
| Cloudflare retention | Company-stored account, game and transaction data follow sections 11–13. Provider security and operational records are processed for periods necessary for service provision and security or retention required by law. |
| Gmail recipient and contact | Google LLC / Google privacy contact information: policies.google.com/privacy?hl=ko |
| Gmail data, purposes and timing | Reply or registration email, enquiries, reports and attachments, minimum materials needed for account verification and security investigations, and processing records. Network transmission and storage when receiving and replying to enquiries, verifying accounts, sending operational or security notices and managing support records. |
| Gmail processing regions and retention | Processing may occur on Google servers in multiple countries. See Google data centre locations. Enquiry and transaction materials retained by the Company follow section 12 and are deleted when their period ends. Provider deletion and backup procedures and statutory retention apply separately. |
| OneDrive recipient and contact | Microsoft / See the official Microsoft privacy and data-protection information in section 14 for privacy enquiries and product-specific conditions. |
| OneDrive processing regions and retention | Microsoft states that information may be stored and processed in Korea, the United States and countries where Microsoft or its providers operate facilities. See the official Microsoft information below for details. Company business materials follow the retention and deletion rules in sections 11–13. |
| AI processing regions and storage | Input materials may be processed and stored on overseas servers of the service used. The official links below provide OpenAI and Anthropic contacts, processing regions, and storage and deletion information. |
Provider-published infrastructure locations and privacy information
- Cloudflare network countries and cities
- Cloudflare South Korea PIPA information
- Google data centre locations
- OpenAI Privacy Policy and international transfers
- OpenAI API retention and processing locations
- Anthropic Privacy Policy and overseas processing
- OpenAI ChatGPT Korea privacy addendum and overseas transfers
- Claude consumer-service retention and deletion
- Microsoft Privacy Statement, retention and deletion
- Microsoft Korea privacy supplement and overseas transfers
These links describe providers’ overall infrastructure and processing practices. They do not mean that every user’s data is stored in every listed country. Processing regions may vary with request handling, storage and support activities.
The Company gives notice of transferred data, countries, timing and methods, recipients and contacts, purposes and retention periods, and how to refuse, and transfers data on an applicable legal basis. Processing and storage necessary for contract performance rely on PIPA Article 28-8(1)(3) only when its requirements are met. Separate consent is obtained for transfers that require it.
External sign-in services and app stores process information described in sections 4, 8 and 16 during authentication and purchases you choose. Processing through OpenAI API, ChatGPT Pro, Claude API, Claude Pro, Excel and OneDrive follows the work and data scope in section 14 and the applicable processing-provider and overseas-transfer basis. Acknowledging this policy is not blanket consent to that processing.
You may send overseas-transfer enquiries or requests to stop transfers to [email protected]. The Company checks the request scope and statutory retention obligations. If stopping processing essential to account provision restricts functions, it explains those restrictions and how to close the account.
To handle verification-email bounces and prevent unwanted repeated sending, Cloudflare may process recipient emails and blocking reasons and status in a suppression list. Blocks following temporary delivery failures normally last 24 hours; some permanent bounces result in seven-day blocks. Blocks for nonexistent addresses, repeated recipient errors or spam complaints may have no automatic expiry. Expiry of a block does not mean deletion of all related records. Requests for access, deletion and other rights concerning this information may be made through the contact in section 19. After identity verification, the Company takes necessary measures within the provider’s processing scope and applicable law.
Verification-email processing information
| Item | Details |
|---|---|
| Recipients and contacts | Google LLC (FCM): https://support.google.com/policies/contact/general_privacy_form / Apple Inc. (APNs): https://www.apple.com/legal/privacy/contact/ |
| Data and purposes | Notification tokens and installation identifiers, app, device and network information, and notification content and delivery information described in section 9. Delivery of chosen notifications, operation and security of delivery services, and opt-out processing. |
| Timing and method | Encrypted network transmission during device registration, renewal, delivery and removal after notification consent. |
| Processing countries | Processing may take place in the United States and countries where Google, Apple and their processors maintain facilities. Firebase uses global Google infrastructure; the Company does not select a specific processing country for FCM. Official location and privacy resources below describe facilities and processing scope. |
| Retention | Company registration, consent and reminder records follow section 11. Google applies its live and backup deletion process of up to 180 days after a Firebase installation-ID deletion request. Other provider operational and security records follow periods necessary for service provision and statutory retention. |
| Refusal and effect | You can decline overseas processing in the notification registration notice or withdraw in game or device notification settings. Refusal restricts notification delivery to that device while account creation, sign-in, battles and other gameplay remain available. Privacy and transfer-stop requests: [email protected]. |
Notification provider processing, locations and deletion
| Item | Details |
|---|---|
| Recipient and contact | Google LLC · https://support.google.com/analytics/ |
| Purpose and data | Game improvement and acquisition-performance measurement; optional analytics data in Section 9 |
| Timing and method | Encrypted network transmission during app use after consent to optional analytics and overseas transfer |
| Processing countries | The United States and Google’s global processing facilities. See the official Google information below for processing locations and safeguards. |
| Retention and refusal | Analytics retention in Section 11. Decline or withdraw in Settings → Usage analytics without affecting game access. |
Analytics privacy information
16. Third-party disclosures and external providers
The Company processes personal data for the purposes described in this policy and discloses it to third parties only with user consent or a legal basis. Providers’ independent processing for sign-in and app-store services is distinguished from processing entrusted by the Company.
The Company exchanges information necessary for authentication and disconnection with the Google, Apple or Facebook provider you choose, and transaction information necessary for purchase verification, cancellation and refunds with the app store used for payment. Game currency and match records are not supplied to external sign-in providers.
Sections 14 and 15 describe data and overseas processing for storing customer-response materials in Microsoft OneDrive and using OpenAI ChatGPT and Anthropic Claude for programming, changes, error analysis and technical support.
For a lawful production request from a court, investigative authority or similar body, the Company checks the legal basis and scope and supplies only necessary information. If personal data is transferred through a business transfer, merger or similar event, it gives notice of the transfer, recipient and contact details and options for users who do not want the transfer, as required by PIPA.
When Apple or Google age checks and app-integrity checks are used, app and request identifiers and authentication and verification evidence are exchanged with the platform to confirm age-sharing or approval results and whether the request came from the legitimate app. Required checks also take place before account creation. This process is distinct from social sign-in linking and app-store purchase verification, and the platform’s privacy policy also applies.
17. Security safeguards
The Company limits staff access and permissions to what is necessary and applies safeguards such as hashing or encrypting authentication and contact information, encrypted communications, access controls and separate secret-key management. Personal data is managed to avoid unnecessary disclosure in logs or public screens.
If a personal-data breach or similar incident is confirmed, the Company takes necessary response measures and notifies authorities and users where statutory requirements apply.
18. Automated processing and review
Matchmaking, reward verification, request-rate limits and abnormal-transaction checks use automated processing based on server rules. You may request an explanation and review of restrictions or transaction errors at [email protected].
Where processing meets the conditions for an automated decision under PIPA Article 37-2, you may exercise rights such as refusal and requesting an explanation within the scope of the law. The Company checks the applicable conditions and exceptions and provides the necessary explanation or reprocessing with human involvement.
For statutory requests to refuse, explain or review automated decisions, the Company provides the outcome within 30 days of receipt. If a justified reason requires an extension, it explains the reason and schedule and extends only within the legally permitted scope. Reasons for refusing a request are provided without delay.
When AI is used to review business materials, staff verify the facts and evidence. Sanctions, refunds and account deletion are not decided solely on AI output.
Age checks apply the player’s selected whole-year age or the platform’s age band and required-verification and approval results. In the Korean service, registration is restricted below age 13, and ages 13–15 must complete the required guardian consent. Incomplete or withdrawn mandatory platform approval, unsupported app versions or repeated requests may restrict registration, access or particular features. Users may ask support to correct inaccurate data, explain a decision or arrange a staff review. We review the verified information and applicable criteria and explain the result.
19. Rights of users and legal guardians
You may request access to, correction or deletion of your personal data, suspension of processing and withdrawal of consent. You may also act through a legal guardian or authorised representative. The Company may request the minimum information needed to verify identity or representative authority.
Personal-data rights requests may be submitted through customer support or [email protected]. Players may request deletion of their own account using the website or app deletion function in section 13. Guardian requests to delete a child’s account, and rights requests from people who have difficulty accessing an account, may be submitted through customer support or [email protected]. The Company verifies the requester’s authority and communicates the outcome.
The Company enables access within 10 days of receiving an access request. If access is restricted, delayed or refused on statutory grounds, it explains the reason and how to object within that period. For suspension requests, it provides the outcome or refusal reason and objection method within 10 days of receipt. Correction, deletion and consent-withdrawal requests are also handled without delay, with any statutory exceptions explained. Within 10 days of receiving a correction or deletion request, the Company notifies the requester of the action taken or the statutory grounds restricting deletion and how to object.
Deletion or suspension may be restricted to the extent prescribed by law, including for information another law requires to be collected or retained. Withdrawal does not affect lawful processing before withdrawal. If stopping processing necessary for a Service prevents use of a feature, the Company explains the impact.
Parents or legal guardians may request access to, correction or deletion of their child’s personal data, suspension of processing, withdrawal of consent or deletion of the child’s account through in-game support or [email protected]. In the initial request, provide the game name, the child’s game nickname and the requested action. The Company checks the relevant account, the requester’s authority and applicable law before handling the request, and asks only for additional information needed for those checks. Do not attach passwords, verification codes or identity-document copies to the initial request.
As a rule, the Company handles personal-data rights requests and communicates the outcome within 10 days of receipt. Any shorter deadline or separate procedure required by applicable law takes priority. If additional steps are needed, such as verifying the player or guardian or checking legal retention duties, the period may be extended only to the extent permitted by applicable law. The Company explains the reason and expected completion date within the required deadline.
A request may be restricted in whole or in part on grounds provided by applicable law, including legal retention duties. In that case, the Company explains the grounds and how to object. A guardian’s authority and the required verification steps are assessed under the applicable national or regional law.
20. Children and young players
The ages 13, 14 and 16 in this section concern Covenant Rise registration and guardian procedures in the Republic of Korea. Other Services’ age and personal-data rules are described in their service information.
Covenant Rise in Korea does not permit new registration or guest access for children under 13. Ages 13–15 require a legal guardian’s consent and verification for registration and gameplay before account creation and play. For the 13–15 age band, the guardian is informed of the purposes, data categories, retention, right to refuse and consequences of personal-data collection and use, and their consent is obtained. The player must also complete the required consent steps presented to them. Ages 16 or older follow the ordinary registration process.
Higher binding age restrictions under local law or a distribution platform apply where relevant. Advisory ratings are distinguished from legal prohibitions. A content rating alone does not determine capacity to consent to data processing or enter a contract. Guardian requests such as cancelling a minor’s purchase are handled after necessary relationship checks.
Registration and gameplay for ages 13–15 are restricted while guardian consent and verification services are unavailable. When guardian consent is requested through family accounts, a guardian-managed email is collected to send verification instructions and a one-time code. Registration and data consent are not blanket consent to all paid-content purchases. Requests for consent withdrawal, account deletion or assistance may be made through the game account menu or [email protected].
Family accounts process the guardian’s management email separately from the child’s game profile. The child’s own email and real name are not required for family linking. Even when a guardian’s email is used, the child’s account ID, nickname, age group, progress and family connection information remain protected under this policy.
| Category and data | Purpose | Retention |
|---|---|---|
| Guardian management email, guardian account identifier, email-verification status and time | Authenticating and recovering guardian management accounts, preventing duplicates, connecting children and sending necessary security and service notices | Until guardian account closure. Deleted after explaining procedures needed for linked child accounts; statutory records remain separate under section 12. |
| Guardian-child connection identifiers, legal-guardian confirmation responses, agreed document and notice versions, consent and withdrawal times and status | Child linking, consent verification and management, rights requests and disputes | Management connection records remain until the connection ends; evidence of a child game account’s registration and use consent remains until that game account closes. Only records qualifying for statutory contract or consumer-dispute retention are stored separately for the purposes and periods in section 12. |
| Unused child-approval identifier, guardian identifier, age band and verification method, consent responses, document versions and time | Confirming guardian approval and the relevant child’s registration or connection request | Approval is valid for up to 10 minutes; unused records are promptly deleted after expiry. Records used for registration or linking follow the child connection and consent retention rules above. |
| Email-verification request identifier, encrypted recipient email, code verification value, request, expiry and verification times, and attempt count | Sending and verifying authentication emails; preventing code reuse and brute-force attempts | Promptly deleted after the request’s 10-minute validity ends. The code verification value is discarded after successful verification or the attempt limit is reached. |
| Irreversible keyed verification value of the email, rate-limit time window and request count | Preventing verification-email abuse | Promptly deleted one hour after the rate-limit record is created. |
| Guardian management session hash, guardian account identifier, creation and expiry times | Maintaining management sign-in and verifying access authority | Valid for up to 30 minutes after creation and promptly deleted after expiry. Signing out or signing in again invalidates the previous session. |
| Game account recovery request identifiers and verification values; management-session and temporary-device verification values; identifiers of the selected game account and family link; account and session identifiers needed to check the current device and previous access; request, expiry and completion times | Restore the selected linked account on the requesting device, prevent use for a different account or device and replay of requests, end previous access and confirm the result | Recovery requests remain valid for up to 10 minutes after creation and are deleted after expiry through the existing temporary-authentication cleanup process. Completed requests are also retained within that validity period to check retries of the same request and confirm its result. |
Guardians may refuse collection and use consent needed for family verification and linking. Refusal restricts those functions and registration or use by children who require guardian consent. The Company separately explains and confirms consent to processing the guardian’s own information, consent to the child’s registration and use, and consent to collection and use of personal data for a child in the 13–15 age band. Emails for authentication, security and consent verification serve those purposes and are not treated as consent to advertising messages.
Parents or legal guardians may request access to, correction or deletion of their child’s personal data, suspension of processing, withdrawal of consent or deletion of the child’s account through in-game support or [email protected]. In the initial request, provide the game name, the child’s game nickname and the requested action. The Company checks the relevant account, the requester’s authority and applicable law before handling the request, and asks only for additional information needed for those checks. Do not attach passwords, verification codes or identity-document copies to the initial request. A request may be restricted in whole or in part on grounds provided by applicable law, including legal retention duties. In that case, the Company explains the grounds and how to object. A guardian’s authority and the required verification steps are assessed under the applicable national or regional law.
On guardian management account closure, the management email and sign-in information are deleted. If a child still requires guardian management or is undergoing deletion, the necessary account-handling or support steps are explained first. A child’s game account and progress that have moved to ordinary-user status in the Korean Service are not deleted merely because the guardian management account closes. Evidence of that game account’s registration and use consent follows the retention rules above.
The 10-minute request validity and deletion rules above apply to temporary requests in the Company’s authentication database. They do not mean remotely deleting an email already delivered to the recipient’s inbox. Provider delivery and security records are handled separately under the processing-provider and overseas-transfer information in sections 14 and 15. Email retained by a recipient follows that email service’s retention and deletion settings.
For a player in the 13–15 age band, separate guardian consent is required for the personal-data processing described above for this feature.
Email verification confirms access to the email address. Entering a code does not by itself verify adulthood or parental or other legal representative authority. Required consent information is presented separately for explicit agreement. Any additional verification or approval required by applicable law or the platform must be completed separately.
Covenant Rise requires separate parent or guardian approval to register promotional reminders for players under 18. Approval for gameplay, registration or friends does not replace notification approval. Without notification approval, players can continue using gameplay features otherwise permitted to them.
Optional usage analytics is not used for accounts under 16 or whose age has not been confirmed. Existing guardian consent for registration, friends or notifications is not extended to this new analytics purpose.
21. Privacy contact and remedies
Privacy officer: 김란, Representative / Requests and replies: [email protected]. This contact handles rights requests, including access, and privacy enquiries and complaints. Do not send passwords or sign-in verification codes.
In addition to contacting the Company, you may seek advice or dispute mediation from the Personal Information Infringement Report Center (privacy.kisa.or.kr, 118 without an area code in Korea) or the Personal Information Dispute Mediation Committee (kopico.go.kr, 1833-6972).
22. Changes and effective date
If this policy changes, the Company announces the changes and effective date on the website or in the game. Matters requiring separate notice or consent, such as new processing purposes, third-party disclosures or overseas transfers, are applied after the procedures required by law.
Previous policies are available in the legal-document history. Providing an English policy does not itself expand service territories, features or the scope of personal-data processing.
See the legal document board for document history. Family-account provisions apply when the relevant feature is provided. Required separate notice and consent procedures are completed before new processing begins.