개인정보 처리방침

01 Purpose and information collected

We process only the information needed for the following purposes:

• Support: When you email us, we receive your email address and the contents of your message.
• Game service: Starting with Space Deepwake 1.1.3, your game account is kept on our server. Game progress, currency, heroes, gear, mining, daily goals, purchase records and battle records are stored on our server (Google Cloud Run, Singapore, asia-southeast1) and in Cloud Firestore, linked to an anonymous Firebase identifier (UID). Sorties, reward settlement, upgrades and the application of purchases are processed on the server, and your device keeps a mirror (copy) of the server state. Versions before 1.1.3 save game progress on your device. The game shows rewarded ads only when you choose to watch one. Google may process device and advertising information to provide those ads.
• Advertising information: This may include your advertising identifier (IDFA only if you allow tracking through iOS App Tracking Transparency), app- or developer-scoped device identifiers, IP address used to estimate approximate location, device, operating system and app information, ad views and interactions such as video views and taps, and crash or performance diagnostics.
• Advertising purposes: Serving ads and managing frequency, measuring and analyzing ad performance, preventing fraud, and improving the service.
• Game analytics: Starting with Space Deepwake 1.1.2, we use Firebase Analytics to analyze game usage. We collect it only if you consent; see below for the items collected and the consent process.
• Game account and cloud storage: Starting with Space Deepwake 1.1.3, we use Firebase Authentication, Google Cloud Run and Cloud Firestore to run your game account. In Space Deepwake 1.1.2, Firebase Authentication and Cloud Firestore were used for an optional cloud backup.
• Payments: Apple processes in-app purchases under its own policies. We do not collect payment card details. Our server verifies purchases and keeps purchase and refund records as described below.

In-game reports: To respond to bug reports and inquiries and fix issues, we process report text (up to 2,000 characters), category, a random installation ID, app version and build, operating system and platform, device model, locale, current screen or stage, and report and receipt timestamps. We do not collect screenshots or attachments. We do not store the original IP address; a one-way hash is used temporarily for abuse rate limiting.

Game account on our server (Space Deepwake 1.1.3 and later): On first launch, the app automatically signs you in with Firebase Authentication using an anonymous sign-in account, without asking for a name, email address, or phone number. Firebase assigns a unique UID that lets us recognize the same game account. Your game account is stored in Cloud Firestore through our server (Google Cloud Run, Singapore, asia-southeast1), linked to the anonymous identifier (UID) that Firebase issues. It contains your game progress, currency, heroes, gear, mining, daily goals, purchase records and battle records. The app sends requests to the server together with a Firebase ID token, and the server checks the account (UID) on each request. The app does not write your game state to Firestore directly; the server applies it. Starting the game, sorties, reward settlement, upgrades and other in-game economy actions need an internet connection, while a manual battle that the server has already started can continue offline. If an older offline save on your device is moved to your server account, the server keeps a copy of that original save and an index of what was imported, so that the same save cannot be applied twice.

Purchase verification (Space Deepwake 1.1.3 and later): When you make or restore a purchase, the app sends the Apple-signed transaction and a Firebase ID token to our game server (Google Cloud Run). The server does not store the signed data itself. It stores a digest (hash) of it together with the transaction ID, original transaction ID, product ID, purchase time, quantity, type, ownership type and environment verified with Apple, linked to your account (UID). Refunds and revocations are received through Apple's server notifications, and we record a digest of each notification and its outcome. Server accounts do not use the daily refund check described below for earlier versions.

Reward records for rewarded ads (Space Deepwake 1.1.3 and later): To grant an ad reward correctly and only once, our server records the reward request (intent), its source and placement, and the reward time, linked to your account (UID). These are our own reward records; they are separate from the advertising information that Google processes, which is described above.

Purchase verification in earlier versions (1.1.2 and earlier): To verify purchases, handle refunds, and prevent fraud, those versions send a random installation ID, App Store transaction IDs, product IDs, the time each purchase was first verified, and refund or revocation status and time to our Vercel/Upstash server (see section 04). The installation ID is generated randomly when the app is installed, is not derived from a device or Apple account identifier, and is not linked to directly identifying information such as a name or contact details. Reinstalling the app creates a new ID. Apple-signed transaction data was used only for verification there and was not retained. Our current server reads the earlier purchase ledger (read-only) only to confirm past purchases, and it handles installation IDs as hashes when it does so; the earlier ledger itself may hold the original random installation ID.

Game analytics (Firebase Analytics): Space Deepwake uses Firebase Analytics on iOS to analyze game usage. Firebase's advertising-related consent types are denied by default, and collection starts only when the consent value we read through Google's User Messaging Platform (UMP) at launch (analytics_storage) is granted or not applicable. If consent is denied or unavailable, we do not collect data and discard any queued events. When consent is granted, Firebase's SDK may automatically collect, together with in-game events such as tutorial progress, battle start/end, stage clear, hero join, store views, purchase start/completion (including product ID, price, and currency), and rewarded ad views: an app-instance identifier, app version, device model, OS version, language/time zone, an approximate location estimated from a masked IP address, and a device identifier (IDFV). Game code does not attach directly identifying information such as your name, email, or account identifier to these events, and we do not provide the advertising identifier (IDFA) to Analytics.

Optional cloud backup in Space Deepwake 1.1.2 (Firebase Authentication and Cloud Firestore): Space Deepwake 1.1.2 uses Firebase Authentication and Cloud Firestore on iOS so you can continue your progress after a device change or reinstall. On first launch, the app automatically signs you in using anonymous sign-in without asking for a name, email, or phone number. Firebase assigns a unique UID that identifies the game account. Only if you choose to in Settings > Cloud does the app link your account with Sign in with Apple; in that case we do not request the name or email scope, and only the identifier Apple issues is linked to your Firebase account. The cloud stores the same content as your local save — game progress, currency, heroes and gear, settings, daily goals, purchase records (product ID, store transaction ID, purchase environment, and grant/refund outcomes), and rewarded ad records — along with a summary used to resolve save conflicts (highest act/node reached, clear counts, etc.), save schema and app version, and the last backup time. This data is linked to the anonymous identifier (UID) Firebase issues and, if you use Sign in with Apple, to the identifier Apple issues. Data is stored on Google's servers in the Asia-Pacific region, and access rules restrict each account to reading and writing only its own save data. Space Deepwake 1.1.3 does not offer this optional Sign in with Apple link in its server account.

We do not knowingly collect personal information from children under 14. If we learn through a support request or other means that information from a child under 14 was collected without a parent or legal guardian's consent, we will destroy it without undue delay.

The studio website does not require registration or an account.

02 Retention period

Support emails and message contents are kept until the request and any follow-up support are complete, then deleted without undue delay, unless retention is required by applicable law. In-game report records are kept for 180 days from submission and then automatically deleted. Apple retains payment information it processes under its policies and applicable law. Information collected through Firebase Analytics and advertising information processed by Google AdMob are retained under Google's policies; we do not set a separate retention period for them.

Game account data on our server (Space Deepwake 1.1.3 and later):

• Active account data: Game progress, currency, heroes, gear, mining, daily goals, purchase records and battle records, and the state needed to provide your rights and prevent the same item from being applied twice, are kept while we provide the service to your account. The copy and index of an older save imported to your account are also kept while the account is active. If you delete your account, they are deleted (see section 04).
• Purchase and refund audit records: Kept for five years from the later of the transaction date and the actual refund or revocation date, then destroyed. Looking up or resending a transaction, for example when you restore a purchase, does not extend this period. These records are the signed-data digest, the verified transaction items, Apple notification digests and outcomes, linked to your account (UID). They are kept separately from your game data and remain for this period even if you delete your account.
• Minimum ownership information for active rights: For non-consumable purchases and time-limited rights that are still valid, we keep the minimum ownership information needed to provide the right and to prevent another account from claiming it, for as long as the right needs it. This is kept separately from the audit records and does not depend on the five-year audit period.
• After five years: When the audit records have been destroyed, non-consumable and time-limited rights can still be restored through Apple verification, for their original validity only; this grants no new currency and no extension of time. A consumable transaction older than five years is never granted again.
• Account deletion completion record: Kept for 30 days after the deletion is complete, then destroyed.
• Rewarded-ad reward records: For active accounts, kept for one year from the expiry or processing date, then destroyed. If you delete your account, they are deleted earlier.
• Block on re-importing deleted older saves: If you delete an account that had an older offline save imported, we keep a minimal identifier of that deleted save so it cannot be imported again, until 00:00 UTC on October 16, 2028, and then destroy it. Moving older offline saves to a new server account ends for everyone at that time. Accounts that have already imported a save, new accounts, and restoring purchases through Apple continue to work.

Earlier versions (1.1.2 and earlier): The earlier purchase ledger (Upstash) follows the same five-year schedule as the purchase and refund audit records above. Cloud backups made with Space Deepwake 1.1.2 are kept until you request deletion or we delete them, and there is no automatic expiry; each backup account keeps only its most recent save and one prior save, and older saves are overwritten and not kept.

A UID, installation ID, transaction ID, or a hash of one of them is not anonymous information, because it can be combined with other records to recognize a specific account. We do not treat a record as anonymous just because only an identifier or hash remains.

03 Destruction

When the retention period ends or the purpose is fulfilled, information is destroyed without undue delay. Electronic files are deleted so they cannot be restored; paper records are shredded or incinerated. Information retained by law is kept separately and destroyed after the required period. Records on our server whose retention period has ended are removed by an automatic cleanup process, which is run in an order that keeps purchase restoration and duplicate-grant prevention working after the removal.

04 Disclosure and processors

We do not sell personal information or provide it to third parties for purposes unrelated to those described here. Space Deepwake rewarded ads are provided by Google AdMob. The recipient is Google LLC, 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA. For privacy inquiries, use Google's privacy inquiry form. Information may be transferred to the United States and other countries where Google provides its advertising services when you request or watch a rewarded ad, and during ad SDK initialization and consent checks; it is sent over the network. The transferred information is the advertising information listed above, and the purposes are the advertising purposes described above. Google's policies govern its retention period. See the Google Privacy Policy and How Google uses information from apps that use its services. The reward records that our own server keeps for rewarded ads are described in sections 01 and 02.

Rewarded ads are requested and shown only when you choose to watch one. Even if you never watch an ad, the ad SDK may communicate with Google when the app starts, for example to check consent. If you do not watch an ad, you will not receive that ad bonus, but your game progress is unaffected; an Ad Pass gives you the same bonus without an ad. At launch, after the ad-consent check (UMP), the app requests App Tracking Transparency permission once, when the request is eligible. If you decline tracking through ATT, you can still watch ads; non-personalized ads are shown without IDFA. You can change your choice in iOS Settings > Privacy & Security > Tracking. Users in the European Economic Area, United Kingdom, and Switzerland are asked for ad-related consent through Google's User Messaging Platform (UMP).

Apple processes in-app purchases under its terms and privacy policy. Starting with Space Deepwake 1.1.3, when you make or restore a purchase, the Apple-signed transaction and a Firebase ID token are sent over an encrypted network, outside Korea, to our game server (Google Cloud Run, Singapore, asia-southeast1). The items stored are described in section 01 and their retention in section 02.

In-game reports in all versions, and purchase verification in Space Deepwake 1.1.2 and earlier, are sent to our Vercel/Upstash server. Reports are transferred when submitted; in 1.1.2 and earlier, purchase details are transferred when you make or restore a purchase, and refund checks run when the app starts (at most once a day). A refund check sends only the installation ID and transaction IDs. Information is transferred outside Korea over an encrypted network. Serverless hosting is provided by Vercel Inc. (United States), and the database is provided by Upstash, Inc. (United States and other service regions; the exact Upstash database region has not been confirmed). Report transfer items are the report text, category, random installation ID, app version and build, operating system and platform, device model, locale, current screen or stage, and timestamps; reports are automatically deleted after 180 days. Purchase transfer items in 1.1.2 and earlier are the installation ID, transaction IDs, product IDs, first verification time, and refund or revocation status and time. Apple-signed transaction data was also used for verification there and is not retained after verification. The retention of the earlier purchase ledger is described in section 02.

Information is also transferred to Google LLC for game analytics (Firebase Analytics, starting with Space Deepwake 1.1.2) and for your game account (Firebase Authentication, Google Cloud Run and Cloud Firestore, starting with Space Deepwake 1.1.3), based on your consent for analytics or on your use of the game account. The recipient is Google LLC, 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA. For privacy inquiries, use Google's privacy inquiry form. Analytics data is transferred whenever a consented event occurs; game account data is transferred whenever the app makes a server request, such as starting the game, a sortie, reward settlement, an upgrade, or a purchase or purchase restoration. The optional cloud backup in 1.1.2 transfers data whenever your local save updates (at least every 30 seconds, immediately after battle end, purchase updates, or when the app backgrounds). The transferred items and purposes are as described in section 01. The game server runs on Google Cloud Run in Singapore (asia-southeast1), and Cloud Firestore data is stored in Google's Singapore (asia-southeast1) region. Analytics data retention follows Google's policy; game account retention follows section 02 above. See the Google Privacy Policy for details of Google's processing.

To request deletion of an in-game report, email spacedeepwake@gmail.com with its approximate submission time and content. Include the random installation ID shown in the app if available; if the app does not show it, we will identify the report by its time and content.

Deleting your account (Space Deepwake 1.1.3 and later): Go to Settings > Account > Delete account. After you confirm:

• the server deletes your game state (progress, currency, heroes, gear, mining, daily goals and battle records), any cloud save, the copy and index of any older save imported to your account, and your rewarded-ad reward records;
• then your Firebase Authentication account is deleted; and
• progress on this device is also cleared.

A new account does not receive the deleted progress or currency. Only non-consumable and time-limited rights verified by the App Store can be restored, with their original expiry; consumable purchases are never restored as a new balance.

Records that remain after you delete your account: Deleting your account does not erase every record about you at once. To prevent duplicate grants, reverse refunds, restore purchases and block re-import of deleted saves, the following remain for the periods stated in section 02:

• Purchase and refund audit records, still linked to your UID, until five years from the later of the transaction date and the actual refund or revocation date.
• A record that your account deletion was completed (UID, identifier of the local save on the device, and time of deletion), for 30 days after completion.
• A minimal identifier of a deleted older save, until 00:00 UTC on October 16, 2028.

Information held by Apple, and by Google for Firebase Analytics and AdMob, is kept under their own policies, and in-game reports are handled as described above.

Optional cloud backup in Space Deepwake 1.1.2: To delete your cloud backup, use the "Delete cloud data" button in Settings > Cloud. After you confirm, this deletes your saved data (main and backup) from Firestore, unlinks Sign in with Apple if connected, and deletes the Firebase Authentication account itself; the app then signs you in again with a new anonymous account. Your local progress on this device is not affected.

If you cannot use the app or the in-app button does not resolve your request, you may instead email spacedeepwake@gmail.com to request deletion; we will process it without undue delay after verifying your identity.

The studio website does not use cookies or other automatic collection devices. For device and advertising identifiers processed by the app advertising SDK, see the advertising section above. When you visit the website, Vercel, the hosting provider, may process access records such as your IP address. See Vercel's Privacy Policy for details such as retention periods.

05 Your rights

You may request access to, correction or deletion of your personal information, or restriction of processing. Contact us below. We will verify your identity and respond without undue delay as required by law. Requests about payment information processed by Apple may need to be directed to Apple.

06 Security measures

We apply appropriate administrative and technical safeguards, including access controls and secure storage, transmission, and destruction practices, to protect personal information against loss, theft, disclosure, falsification, alteration, or damage.

07 Privacy contact

Business

onebillionstudio (sole proprietor)

Business registration no.

763-76-00464

Representative

Sungjoon Ha

Business address

30, Haeundaehaebyeon-ro, Haeundae-gu, Busan, Republic of Korea

Privacy officer

Sungjoon Ha

Privacy contact email

spacedeepwake@gmail.com

For complaints or consultation about privacy violations, you may contact:

• Personal Information Dispute Mediation Committee: 1833-6972, www.kopico.go.kr
• Personal Information Infringement Report Center: 118, privacy.kisa.or.kr
• Supreme Prosecutors' Office Cyber Investigation Division: 1301, www.spo.go.kr
• National Police Agency Cyber Investigation Bureau: 182, ecrm.police.go.kr

08 Changes and effective date

This policy is effective October 17, 2026. We will post notice on this website if the policy changes due to changes in applicable law or our services.

Change history: 2026-10-17: Space Deepwake 1.1.3 game accounts moved to our server (Google Cloud Run and Cloud Firestore); updated purchase verification, reward records, retention periods, account deletion, and the timing of the App Tracking Transparency request.

2026-09-26: Added Firebase Analytics (game analytics) and Firebase Authentication/Cloud Firestore (cloud save) sections; added in-game reports and purchase verification.