@mpgd/cli 0.57.0 → 0.58.0

package/templates/phaser-game/README.md

@@ -507,3 +507,75 @@ credentials: Game Services reports `missing_authoritative_backend` or
 backends require both a non-production authority mode and an explicit
 `allowLocalBackend` opt-in, so they cannot manufacture successful production
 purchase, rewarded-ad, or leaderboard ledger results.
+
+### Guest identity
+
+Store purchases on Android and iOS are bound to the player of a server
+session: Google Play's `obfuscatedAccountId` and StoreKit's `appAccountToken`
+are derived from that player's id (`src/platform/commerceAccountBinding.ts`),
+and the backend checks them before it grants. The native shell's local player
+(`android-local-player` / `ios-local-player`) is the same on every install, so
+it binds nothing: Play refuses with `ACCOUNT_BINDING_REQUIRED` and StoreKit
+throws an error naming the missing session.
+
+Point the game at the kit's reference guest identity Worker
+(`apps/game-identity-worker` in mpgd-kit, deployed per
+`docs/CLOUDFLARE_WORKER_DEPLOY.md`):
+
+```sh
+VITE_MPGD_IDENTITY_URL=https://identity.example.com
+```
+
+`src/platform/guestIdentity.ts` then signs the player in during bootstrap: a
+server-issued guest on the first launch, kept with a rotating refresh token in
+the device's Keychain or Keystore, and the same guest on later launches. The
+server player becomes the game services' `playerId` and the purchases'
+binding, and `setStarterServerSession` sends its access token to the
+game-services Worker, which resolves it through the identity Worker's
+bindings. A session the identity service ended (logout, a replayed refresh
+token, or 180 days without play by default) is replaced by a new guest; without a linked
+account that player's purchases stay with the old one.
+
+Offline at launch, the game starts anyway and keeps trying in the background
+(after 5 s, 15 s, 1 min, then every 5 min, and at once when the device reports
+it is online). A purchase or a Restore Purchases tap signs in first; if that
+still fails, the purchase is refused before any store sheet opens (it
+answers `failed` with the retryable diagnostic `STARTER_SESSION_REQUIRED`,
+which the game action coordinator treats as a plain failure; retry with a
+new idempotency key, as for any failed purchase) and the restore control says it could not
+reach the game server and stays tappable as a retry. The purchase, restore,
+and notification services (`src/platform/sessionGatedServices.ts`) come up
+for the server player as soon as a sign-in succeeds, and run the startup
+purchase recovery then; they are never bound to the platform's local
+placeholder, so no purchase or journal record changes owner. Rewarded ads
+stay off for such a run: an ad watched before the session exists could not
+be claimed. The scenes' `player` and `identitySession` are the boot values
+for the whole run (the platform's player when the boot sign-in failed) and
+the server player from the next launch on: key game-owned save data by
+something that does not change, such as the platform storage itself, not by
+`player.playerId`. A native shell only reaches `https:` origins, so test on a
+device or emulator through an https tunnel to a local Worker. Account linking (Sign in with Apple or Google) is not
+part of the reference Worker yet.
+
+### Restore Purchases
+
+The lobby (Phaser) or a corner button (lite) shows **Restore purchases** on
+targets that sell through a store and have a Game Services client. It calls
+`monetizationRecovery.restorePurchases()` (`src/platform/restorePurchases.ts`):
+the store resynchronizes (StoreKit `AppStore.sync()`; Google Play re-reads owned
+items) and every purchase is verified through the backend ledger before anything
+is granted. App Review expects this control while the catalog sells a
+non-consumable such as `REMOVE_ADS`. On the App Store and Google Play a purchase
+is bound to the server player, so without a server session (see Guest identity)
+the button says to connect to the game server instead of restoring; keep it reachable from the game's own
+store or settings screen when you replace the lobby.
+
+A reinstall on Android, a new device, a second device, a logout, or (by
+default) 180 days away make a new guest, and the store then returns the
+purchase's non-consumables bound to the guest that bought them. The kit's
+reference Worker grants a verified restore of such a non-consumable to the new
+guest as well (restore sharing; earlier devices keep it, up to five guests per
+purchase by default), and the control then says **Restored to this device**;
+past the limit it says the purchase is already in use on the maximum number of
+devices. Consumables are never shared. See "Reinstalls and new devices" in the
+kit's `docs/CLOUDFLARE_WORKER_DEPLOY.md` before selling non-consumables.

package/templates/phaser-game/agent/acceptance.md

@@ -67,7 +67,10 @@ the snapshot bounds for persistent controls.
 ## Server session
 
 Verify the game sets its real server-backed session with `setStarterServerSession`
-before `bootstrap()` (a guest backend through `createGuestServerSession`) and does
+before the game services are created (the starter's `guestIdentity.ts` does it
+with `VITE_MPGD_IDENTITY_URL`, a guest backend through `createGuestServerSession`),
+that a store purchase on Android and iOS carries the server player's binding
+(not `android-local-player` / `ios-local-player`), and that the game does
 not rely on the development fallback, which only a game created with
 `--providers notifications` reads. `VITE_MPGD_DEV_NOTIFICATION_SESSION` is local-only evidence:
 a `pnpm build` never signs in with it (its `mpgd-dev` header needs the Vite dev

package/templates/phaser-game/agent/brief.md

@@ -51,10 +51,20 @@ and reconcile existing operations on startup and resume without opening SDK UI.
 
 ## Server session
 
-Set the game's server-backed session with `setStarterServerSession`
-(`src/platform/serverSession.ts`) before `bootstrap()`; with a guest backend use
-`createGuestServerSession(coordinator)`, whose `sessionId` is the stable
-session-family id. For local notifications work only (a game created with
+With `VITE_MPGD_IDENTITY_URL` set (the kit's reference guest identity Worker,
+`apps/game-identity-worker`), `src/platform/guestIdentity.ts` signs the player
+in as a server-issued guest during bootstrap, before the game services read
+the session: it keeps the refresh token in the device's Keychain or Keystore,
+calls `setStarterServerSession` with `createGuestServerSession(coordinator)`
+(whose `sessionId` is the stable session-family id), and binds StoreKit and
+Google Play purchases to the server player. A failed boot sign-in is retried
+in the background and before each purchase or restore; the purchase,
+restore, and notification services come up when it succeeds
+(`src/platform/sessionGatedServices.ts`). Without it the native shell's
+local player binds no purchase, and StoreKit and Play refuse with the reason.
+A game with its own identity service sets its session with
+`setStarterServerSession` (`src/platform/serverSession.ts`) before the game
+services are created instead. For local notifications work only (a game created with
 `--providers notifications`), `VITE_MPGD_DEV_NOTIFICATION_SESSION` on the Vite
 dev server in the `development` mode signs in with an unauthenticated
 development session (`src/platform/developmentServerSession.ts`)

package/templates/phaser-game/gitignore

@@ -18,3 +18,14 @@ apps/*/.env
 .DS_Store
 *.log
 *.ait
+# Signing and store credentials stay out of Git (use mise or CI secrets).
+# google-services.json and GoogleService-Info.plist are committed on
+# purpose: Firebase documents them as non-secret, and release builds run from
+# a pinned Git checkout that needs them.
+*.p12
+*.p8
+*.mobileprovision
+*.provisionprofile
+*.keystore
+*.jks
+*.pepk

package/templates/phaser-game/legal/delete-account.html

@@ -0,0 +1,133 @@
+<!doctype html>
+<html lang="en">
+  <head>
+    <meta charset="utf-8" />
+    <meta name="viewport" content="width=device-width, initial-scale=1" />
+    <title>Delete Your __GAME_TITLE__ Account</title>
+    <style>
+      :root {
+        color-scheme: light dark;
+        font-family:
+          Inter, ui-sans-serif, system-ui, -apple-system, BlinkMacSystemFont, "Segoe UI", sans-serif;
+        line-height: 1.6;
+      }
+
+      body {
+        margin: 0;
+        background: Canvas;
+        color: CanvasText;
+      }
+
+      main {
+        box-sizing: border-box;
+        margin: 0 auto;
+        max-width: 760px;
+        padding: 48px 24px;
+      }
+
+      h1,
+      h2 {
+        line-height: 1.2;
+      }
+
+      a {
+        color: LinkText;
+      }
+
+      nav {
+        display: flex;
+        flex-wrap: wrap;
+        gap: 16px;
+        margin: 0 0 32px;
+      }
+    </style>
+  </head>
+  <body>
+    <main>
+      <nav aria-label="Legal pages">
+        <a href="/privacy/">Privacy</a>
+        <a href="/support/">Support</a>
+        <a href="/terms/">Terms</a>
+        <a href="/delete-account/" aria-current="page">Delete account</a>
+      </nav>
+      <!--
+        Google Play: enter this page's URL (https://<your legal site>/delete-account/)
+        in Play Console > App content > Data safety > "Delete account URL".
+        The page must name the app as the store listing does, let players
+        request deletion without reinstalling the game, and say what is
+        deleted and what is kept and for how long. Starting point, not legal
+        advice: replace every REPLACE marker in square brackets (mpgd legal
+        build and check warn while any remain).
+      -->
+      <h1>Delete Your __GAME_TITLE__ Account</h1>
+      <p>
+        This page explains how to delete your __GAME_TITLE__ account and the
+        data linked to it. __GAME_TITLE__ is published by [REPLACE: developer
+        name exactly as shown on the store listing].
+      </p>
+      <h2>In the Game</h2>
+      <ol>
+        <li>Open __GAME_TITLE__ and go to [REPLACE: menu path, for example the lobby's Delete account button].</li>
+        <li>Tap <strong>Delete account</strong>, read what is deleted, and tap <strong>Delete permanently</strong>.</li>
+        <li>
+          The game deletes your account and signs you out. Anything our server
+          cannot finish at once is completed automatically within
+          [REPLACE: period, for example 24 hours].
+        </li>
+      </ol>
+      <h2>Without the Game</h2>
+      <p>
+        If you no longer have the game installed, you do not need to reinstall
+        it. Send a deletion request to
+        [REPLACE: support email address or request form URL] with the subject
+        "Delete my account" and [REPLACE: what lets you find the account,
+        for example the player ID shown in the game's settings, or the store
+        order number of a purchase made with it]. We delete the account within
+        [REPLACE: period, for example 30 days] and confirm by reply.
+        [REPLACE: what happens to a guest account that has neither, for
+        example "If you cannot give either, we cannot find your account; its
+        data is deleted after N months without play."]
+      </p>
+      <h2>What Is Deleted</h2>
+      <ul>
+        <li>Your player account and every sign-in session on every device.</li>
+        <li>Scores and leaderboard entries.</li>
+        <li>[REPLACE: game progress, if our server stores it; otherwise delete this item.]</li>
+        <li>Rewarded-ad records.</li>
+        <li>Notification tokens, notification settings, and your consent records for advertising messages.</li>
+      </ul>
+      <h2>What We Keep, and for How Long</h2>
+      <ul>
+        <li>
+          <strong>Purchase records</strong> (the product, the store's order or
+          transaction number, and the date) for 5 years from the purchase or its
+          last refund, whichever is later, for payment and supply record
+          obligations [REPLACE: confirm with counsel which apply to you, for
+          example Korea's Act on Consumer Protection in Electronic Commerce].
+          They are kept separately and no longer contain your player ID (the
+          store's own order number still identifies the purchase), and they
+          also stop the same store purchase from being used twice. They are
+          deleted after that period.
+        </li>
+        <li>[REPLACE: anything else the game keeps, such as support messages, with the period.]</li>
+      </ul>
+      <h2>Purchases</h2>
+      <p>
+        Deleting your account does not refund purchases. Items you buy once
+        (such as removing ads) stay owned by your Google Play or Apple
+        account: if you play again, Restore purchases gives them to your new
+        game account as a new record, and the deleted account is never
+        restored. Consumable items (such as coins) are not restored. To ask
+        for a refund, contact Google Play or Apple. A purchase still pending when
+        the account is deleted (waiting for a payment or a parent's approval)
+        is never delivered: Google Play refunds it automatically, but an App
+        Store purchase is not refunded automatically; ask Apple for the
+        refund. [REPLACE: subscriptions, if the
+        game sells any: cancel them in the store first, because billing
+        continues through the store.]
+      </p>
+      <h2>Contact</h2>
+      <p>[REPLACE: support email or form, and the data protection contact if required.]</p>
+    </main>
+  </body>
+</html>

package/templates/phaser-game/legal/privacy.html

@@ -48,30 +48,129 @@
         <a href="/privacy/" aria-current="page">Privacy</a>
         <a href="/support/">Support</a>
         <a href="/terms/">Terms</a>
+        <a href="/delete-account/">Delete account</a>
       </nav>
       <h1>__GAME_TITLE__ Privacy Policy</h1>
       <p>Last updated: __LEGAL_LAST_UPDATED__</p>
       <p>
-        __GAME_TITLE__ collects only the information needed to run the game,
-        keep player progress, operate platform features, and respond to support
-        requests.
+        This policy explains what __GAME_TITLE__ (the "game") and its operator,
+        [REPLACE: legal name of the developer or company] ("we"), collect, why,
+        how long we keep it, and how to have it deleted.
       </p>
+      <!--
+        Starting point, not legal advice. Before publishing, replace every
+        REPLACE marker in square brackets (mpgd legal build warns while any remain) and
+        delete what the game does not do or use.
+      -->
       <h2>Information We Process</h2>
+      <ul>
+        <li>
+          <strong>Player identifiers.</strong> A random guest player ID issued by
+          our game server, a random ID for this installation of the game, and,
+          when you sign in, the account ID of the sign-in provider. Store purchases are bound to a one-way hash of your signed-in player ID.
+        </li>
+        <li>
+          <strong>Game progress.</strong> Saves, settings, scores, and the
+          leaderboard entries you submit.
+        </li>
+        <li>
+          <strong>Purchases.</strong> The products you buy and the store's
+          transaction records (Google Play order IDs and a one-way hash of the
+          purchase token, which our server sends to Google to verify the
+          purchase; App Store transaction and original transaction IDs), kept in
+          our purchase ledger so a purchase is granted once and can be
+          restored. We never receive your payment card details.
+        </li>
+        <li>
+          <strong>Rewarded ads.</strong> Records of ads you chose to watch for a
+          reward, so the reward is granted once.
+        </li>
+        <li>
+          <strong>Notifications.</strong> If you allow notifications, a push
+          token for your device and your notification choices, including any
+          consent to advertising messages and when you gave it.
+        </li>
+        <li>
+          <strong>Technical data.</strong> App version, platform, coarse device
+          type, and error details needed to operate and fix the game.
+        </li>
+        <li><strong>Support.</strong> Messages you send us.</li>
+      </ul>
+      <h2>How We Use Information</h2>
       <p>
-        The game may process platform player identifiers, gameplay progress,
-        leaderboard scores, purchase or reward validation records, coarse
-        device/runtime information, and support messages you choose to send.
+        To run the game and its online features, keep your progress and
+        purchases, grant purchases and rewards exactly once, prevent fraud and
+        cheating, send the notifications you asked for, answer support requests,
+        and meet store and legal requirements. We do not sell your personal
+        information. [REPLACE: keep "We do not track you across other
+        companies' apps or websites." only if the game shows no personalized
+        ads and uses no other tracking; otherwise describe the tracking and how
+        to refuse it.]
       </p>
-      <h2>How We Use Information</h2>
+      <h2>Third-Party Services</h2>
+      <!-- Keep only the services the game uses. -->
+      <p>
+        These third-party services are involved in running the game; some act on
+        our behalf and some under their own privacy policies.
+      </p>
+      <ul>
+        <li>
+          Google Play Billing and the Google Play Developer API (Google) or Apple
+          StoreKit and the App Store Server API (Apple): purchases and their
+          verification.
+        </li>
+        <li>
+          Firebase Cloud Messaging (Google): delivering push notifications.
+        </li>
+        <li>
+          Google AdMob and the User Messaging Platform (Google): showing ads and
+          asking for consent where required. AdMob may use the device
+          advertising identifier where the platform and your choices allow it.
+        </li>
+        <li>
+          Cloudflare: hosting our game server, database, and these pages.
+        </li>
+        <li>[REPLACE: any other analytics, crash-reporting, or sign-in service.]</li>
+      </ul>
+      <h2>Retention</h2>
+      <p>
+        We keep account, progress, and notification data while your account is
+        active and delete it when you delete your account [REPLACE: and/or
+        after N months of inactivity]. We keep purchase records (product,
+        store order or transaction number, and date) for 5 years from the
+        purchase or its last refund, whichever is later, for payment and supply
+        record obligations
+        [REPLACE: the laws that apply to you, for example Korea's Act on
+        Consumer Protection in Electronic Commerce], also after the rest of
+        your data is deleted, stored separately and without your player ID. Server logs are kept for
+        [REPLACE: period].
+      </p>
+      <h2 id="delete-account">Deleting Your Account and Data</h2>
+      <p>
+        You can delete your account and the data linked to it in the game
+        ([REPLACE: menu path, for example the lobby's Delete account button])
+        or, without reinstalling the game, by following the steps on our
+        <a href="/delete-account/">account deletion page</a>. The deletion
+        page lists what is deleted and what we must keep (see Retention).
+      </p>
+      <h2>Your Choices</h2>
+      <p>
+        You can turn notifications off in the device settings [REPLACE: and in
+        the game's settings, if it has a notification settings screen], change
+        your ad privacy choices [REPLACE: from the game's privacy options, if it
+        shows ads with a consent form], and ask us for a copy or correction of
+        your data. [REPLACE: rights and contact points required where you
+        operate, for example GDPR, UK GDPR, CCPA, or Korea's PIPA.]
+      </p>
+      <h2>Children</h2>
       <p>
-        We use this information to provide gameplay features, prevent duplicate
-        grants, maintain leaderboards, troubleshoot issues, and satisfy platform
-        review or safety requirements.
+        [REPLACE: who the game is for. If it is directed at children, describe
+        the stricter handling the store programs require.]
       </p>
       <h2>Contact</h2>
       <p>
-        Replace this template before release with the game owner's support
-        contact and jurisdiction-specific privacy disclosures.
+        [REPLACE: support email or form, postal address, and data protection
+        contact if required.]
       </p>
     </main>
   </body>

package/templates/phaser-game/legal/support.html

@@ -48,6 +48,7 @@
         <a href="/privacy/">Privacy</a>
         <a href="/support/" aria-current="page">Support</a>
         <a href="/terms/">Terms</a>
+        <a href="/delete-account/">Delete account</a>
       </nav>
       <h1>__GAME_TITLE__ Support</h1>
       <p>

package/templates/phaser-game/legal/terms.html

@@ -48,6 +48,7 @@
         <a href="/privacy/">Privacy</a>
         <a href="/support/">Support</a>
         <a href="/terms/" aria-current="page">Terms</a>
+        <a href="/delete-account/">Delete account</a>
       </nav>
       <h1>__GAME_TITLE__ Terms</h1>
       <p>Last updated: __LEGAL_LAST_UPDATED__</p>

package/templates/phaser-game/mpgd.game.json

@@ -8,6 +8,9 @@
   "ui": {
     "textSelection": "disabled"
   },
+  "native": {
+    "orientation": "landscape"
+  },
   "acceptance": {
     "gameplay": {
       "schemaVersion": 1,

package/templates/phaser-game/src/env.d.ts

@@ -19,6 +19,12 @@ interface ImportMetaEnv {
   readonly VITE_MPGD_GAME_SERVICES_URL?: string;
   readonly VITE_MPGD_GAME_SERVICES_TARGET?: string;
   readonly VITE_MPGD_GAME_SERVICES_TRANSPORT?: string;
+  /**
+   * The guest identity service (the kit's reference Worker,
+   * `apps/game-identity-worker`): an https URL, or http on a local
+   * development host. See `src/platform/guestIdentity.ts`.
+   */
+  readonly VITE_MPGD_IDENTITY_URL?: string;
   /**
    * Local development only: `<playerId>` or `<playerId>.<installationId>`
    * for an unauthenticated notifications session (see `serverSession.ts`).

package/templates/phaser-game/src/i18n/messages.ts

@@ -16,7 +16,32 @@ export type GameMessageKey =
   | 'rewardPending'
   | 'rewardUnavailable'
   | 'analytics'
-  | 'bootError';
+  | 'bootError'
+  | 'restorePurchases'
+  | 'restoreWorking'
+  | 'restoreDone'
+  | 'restoreToDevice'
+  | 'restoreHolderLimit'
+  | 'restoreNothing'
+  | 'restoreIncomplete'
+  | 'restorePartial'
+  | 'restoreNeedsSession'
+  | 'restoreNeedsConnection'
+  | 'restoreFailed'
+  | 'deleteAccount'
+  | 'deleteAccountConfirm'
+  | 'deleteAccountPendingPurchase'
+  | 'deleteAccountConfirmButton'
+  | 'deleteAccountCancel'
+  | 'deleteAccountClose'
+  | 'deleteAccountWorking'
+  | 'deleteAccountDone'
+  | 'deleteAccountDoneLocalFailed'
+  | 'deleteAccountSessionEnded'
+  | 'deleteAccountNeedsSession'
+  | 'deleteAccountUnavailable'
+  | 'deleteAccountFailed'
+  | 'deleteAccountRejected';
 
 const messages = {
   en: {
@@ -36,6 +61,36 @@ const messages = {
     rewardUnavailable: 'Rewarded ads unavailable on this target',
     analytics: 'Analytics events: {count}',
     bootError: 'Failed to start game',
+    restorePurchases: 'Restore purchases',
+    restoreWorking: 'Restoring purchases...',
+    restoreDone: 'Purchases restored ({count} confirmed)',
+    restoreToDevice: 'Restored to this device ({count} confirmed)',
+    restoreHolderLimit: 'This purchase is already in use on the maximum number of devices',
+    restoreNothing: 'No new purchases to restore',
+    restoreIncomplete: 'Some purchases are not confirmed yet. Try again later.',
+    restorePartial: 'Purchases restored ({count}); others are not confirmed yet. Try again later.',
+    restoreNeedsSession: 'Restoring purchases needs a game server session',
+    restoreNeedsConnection: 'Could not reach the game server. Tap to try again.',
+    restoreFailed: 'Could not restore purchases. Try again later.',
+    deleteAccount: 'Delete account',
+    deleteAccountConfirm:
+      'Delete your account? Your progress, scores, and notification settings are erased and you are signed out. '
+      + 'Purchases are not refunded; ask the store you bought from for a refund. Items you bought once (such as Remove ads) can be restored to a new account with Restore purchases while the store account still owns them. '
+      + 'Purchase records are kept for 5 years from the purchase or its last refund, for payment and supply record obligations, without your player ID.',
+    deleteAccountPendingPurchase:
+      'A purchase is still being processed. Deleting now loses it: Google Play refunds it, but for an App Store purchase ask Apple for the refund.',
+    deleteAccountConfirmButton: 'Delete permanently',
+    deleteAccountCancel: 'Cancel',
+    deleteAccountClose: 'Close',
+    deleteAccountWorking: 'Deleting your account...',
+    deleteAccountDone: 'Your account was deleted and you are signed out.',
+    deleteAccountDoneLocalFailed:
+      'Your account was deleted, but this device could not forget its sign-in. Clear the app data or reinstall the app.',
+    deleteAccountSessionEnded: 'Your session has ended: your account deletion most likely completed.',
+    deleteAccountNeedsSession: 'Sign in to delete your account.',
+    deleteAccountUnavailable: 'Account deletion is not available here. Use the deletion page linked from the privacy policy.',
+    deleteAccountFailed: 'Could not delete your account. Try again.',
+    deleteAccountRejected: 'Could not delete your account. Contact support.',
   },
   ko: {
     title: '__GAME_TITLE__',
@@ -54,6 +109,36 @@ const messages = {
     rewardUnavailable: '이 타깃에서는 리워드 광고를 사용할 수 없음',
     analytics: '애널리틱스 이벤트: {count}',
     bootError: '게임 시작 실패',
+    restorePurchases: '구매 복원',
+    restoreWorking: '구매 복원 중...',
+    restoreDone: '구매 복원 완료 ({count}건 확인)',
+    restoreToDevice: '이 기기로 구매를 복원했습니다 ({count}건 확인)',
+    restoreHolderLimit: '이 구매는 이미 허용된 최대 기기 수에서 사용 중입니다',
+    restoreNothing: '새로 복원할 구매가 없습니다',
+    restoreIncomplete: '아직 확인되지 않은 구매가 있습니다. 나중에 다시 시도하세요.',
+    restorePartial: '{count}건 복원, 아직 확인되지 않은 구매가 있습니다. 나중에 다시 시도하세요.',
+    restoreNeedsSession: '구매를 복원하려면 게임 서버 세션이 필요합니다',
+    restoreNeedsConnection: '게임 서버에 연결하지 못했습니다. 다시 시도하려면 누르세요.',
+    restoreFailed: '구매를 복원하지 못했습니다. 나중에 다시 시도하세요.',
+    deleteAccount: '계정 삭제',
+    deleteAccountConfirm:
+      '계정을 삭제할까요? 진행 상황, 점수, 알림 설정이 지워지고 로그아웃됩니다. '
+      + '구매는 환불되지 않습니다. 환불은 구매한 스토어에 요청하세요. 한 번 구매한 항목(광고 제거 등)은 스토어 계정이 계속 보유하고 있으면 구매 복원으로 새 계정에서 다시 받을 수 있습니다. '
+      + '구매 기록은 거래기록 보존 의무에 따라 구매 또는 마지막 환불 시점부터 5년 동안 플레이어 ID 없이 보관됩니다.',
+    deleteAccountPendingPurchase:
+      '아직 처리 중인 구매가 있습니다. 지금 삭제하면 이 구매는 지급되지 않습니다. Google Play는 자동으로 환불하지만, App Store 구매는 Apple에 환불을 요청해야 합니다.',
+    deleteAccountConfirmButton: '영구 삭제',
+    deleteAccountCancel: '취소',
+    deleteAccountClose: '닫기',
+    deleteAccountWorking: '계정을 삭제하는 중...',
+    deleteAccountDone: '계정이 삭제되었고 로그아웃되었습니다.',
+    deleteAccountDoneLocalFailed:
+      '계정은 삭제되었지만 이 기기의 로그인 정보를 지우지 못했습니다. 앱 데이터를 지우거나 앱을 다시 설치하세요.',
+    deleteAccountSessionEnded: '세션이 종료되었습니다. 계정 삭제가 완료되었을 가능성이 높습니다.',
+    deleteAccountNeedsSession: '계정을 삭제하려면 로그인하세요.',
+    deleteAccountUnavailable: '여기서는 계정을 삭제할 수 없습니다. 개인정보처리방침에 연결된 삭제 페이지를 이용하세요.',
+    deleteAccountFailed: '계정을 삭제하지 못했습니다. 다시 시도하세요.',
+    deleteAccountRejected: '계정을 삭제하지 못했습니다. 고객 지원에 문의하세요.',
   },
 } satisfies Record<Locale, Record<GameMessageKey, string>>;