App: SOULRAIN (Google Play titles: "SOULRAIN: Black Star Survivors" / "SOULRAIN 검은별 영혼비: 로그라이크 슈팅"; formerly SOULRAIN: Black Star) · Developer: 집스튜디오 (JIP Studio Games) · Contact: support@jipstudiogames.com · Effective: November 3, 2026
This policy is set by 집스튜디오 (JIP Studio Games, "the developer"), the controller of personal data for this app under Korea's Personal Information Protection Act. It describes only what is actually in the app. The app includes four third-party SDKs: the Google Mobile Ads SDK (AdMob), the Google User Messaging Platform (UMP), the Google Play Billing Library and the Google Play In-App Review Library. There is no analytics SDK.
1. Personal data the developer collects or keeps: support and refund messages and order information
There are no accounts and no sign-in. The developer does not collect your name, email, phone number or precise location through the app, and runs no server. Game progress (stages, shards, settings, purchases and the purchase tokens of Shard packs) is stored in a file on your device (progress.json) and is never sent to the developer (for the backup to your own Google account, if on, see section 4). If you contact us by email (or by phone or text message), we use your address or number and your message only to reply, and delete them once the matter is closed. The in-game Contact button fills in the game version, device model and Android version in your mail app; you can delete them before sending. Withdrawal (refund) requests and complaints or disputes about purchases or payments are the exception: the law requires us to keep them, separately, for a set period (section 7).
For purchases, Google Play also gives us the information below. It does not come from the app.
| Data | How it reaches us | Purpose | Retention |
|---|---|---|---|
| Order information (the order number; under Google Play's terms this can include your name and email address) | Google Play may pass it to the developer to process orders and refunds (Play Console order management). It does not pass through the app | Checking orders and handling withdrawal (refund) requests | What is used to handle a support or refund request is kept as the retained items in section 7, for the periods in section 7, then deleted. Order records inside Play Console follow Google's policies |
| Sales reports and order records (order number, payment date and status, item, amount and tax, device model, and the buyer's state or province, city or district, postal code and country) | Google Play provides them in Play Console as sales reports and order lists. They do not pass through the app. The developer keeps downloaded copies and its tax ledger | Checking sales, filing taxes, keeping books and supporting documents | Kept for 5 years from the statutory filing deadline (7 years if it counts as an offshore transaction, 역외거래; the developer applies seven years to these records) under Article 85-3(2) of the Framework Act on National Taxes (국세기본법), then deleted. Records inside Play Console follow Google's policies |
2. Data the Google SDKs collect automatically (including behavioral data)
When the app requests or shows an ad, the Google SDKs inside it send the following directly to Google (the billing row applies when you buy and when the game checks your purchases; the review row applies only when you type and submit a review in the review card). The developer does not receive or store it, except that the developer can see a posted review, as the review row says. The information Google Play provides separately in sales reports for purchases (including device model) is listed in the section 1 table.
| Data | Collected by | Purpose |
|---|---|---|
| Advertising ID (AAID), app set ID | AdMob | Serving and measuring ads (analytics), fraud prevention |
| IP address (and the approximate location derived from it) | AdMob, UMP | Serving ads, deciding whether consent is required, fraud prevention |
| App interactions (app launches, ad views and taps, video views) | AdMob | Serving and measuring ads (analytics), fraud prevention |
| Diagnostics (app launch time, hang rate, energy use) | AdMob | Measuring SDK and ad performance (analytics), fraud prevention |
| Device information (model, OS version, language, connection type) | AdMob, UMP | Showing ads and the consent form |
| Purchase requests and purchase tokens, the billing library's diagnostic logs (device model, manufacturer, OS build, language, country, carrier code) | Play Billing | Processing and restoring purchases, Google's quality monitoring of the billing library |
| The star rating and review you type into the review card yourself | Google Play (In-App Review) | Posting a review on the Play Store. The app does not receive it. A posted review is public like any other Play review and the developer can see it (on a closed test track it goes privately to the developer only); Google handles it under the Google Play Terms of Service |
- Personalized ads: the advertising ID and app interactions may be used to show ads based on your interests. Where consent is required (the EEA, the UK and similar), the app requests no ads until you have answered the Google UMP consent form. If you decline personalized ads, that choice is passed to Google with every ad request and you see non-personalized ads.
- Ad content rating: every ad request is capped at rating G (general audiences).
- Payment details (card numbers and so on) are handled by Google Play. Neither the app nor the developer receives them.
How to refuse or limit automatic collection
- Reset or delete the advertising ID: Android Settings → Privacy (or Google) → Ads → "Reset advertising ID" or "Delete advertising ID". Once deleted, the app cannot send it. Menu names vary by device.
- Change your personalized-ads choice: in the app, Settings → Data → Privacy settings reopens the Google UMP consent form. Where consent is not required (Korea, for example), the app may say "This device doesn't need consent settings" instead.
- Play offline: the game works without a connection. Offline, no ads are requested and none of the data above is sent.
- There is no in-app switch that stops ad requests entirely. Buying "Remove ads" stops interstitial requests, but the SDK keeps running for the rewarded ads you choose to watch (Revive, Double Shards).
3. Transfer of personal data outside Korea
The data below is sent or stored outside the Republic of Korea. It is described in two parts: data Google collects directly (3-1) and the data the developer receives and keeps (3-2: support and refund emails, sales reports and order records).
3-1. Data Google collects directly (the data in section 2 and the backup in section 4)
This data does not pass through the developer: the Google SDKs in the app, Android and Google Play send it to Google LLC directly. Google processes it independently under its own Privacy Policy, and the developer does not receive it (for a posted review, see the review row in the section 2 table; for the sales reports Google Play provides separately about purchases, see the section 1 table). The details of the transfer are listed below so that you know them.
| Item | Details |
|---|---|
| Recipient | Google LLC (1600 Amphitheatre Parkway, Mountain View, CA 94043, USA). Privacy contact: googlekrsupport@google.com |
| Country | The United States and other countries where Google operates data centers (https://datacenters.google/locations/) |
| Data | Everything in the section 2 table; the game save file (progress.json; up to version 1.0.4, all app data except caches and the like, section 4) if backup is on |
| When and how | Each time the app requests or shows an ad or the consent form, when you make a purchase, and when the game checks your purchases (at launch, on return to the game, at stage start, and when you use Restore purchases), over an encrypted (TLS) connection. A review is sent when you submit it in the review card. Backups are sent to your Google account whenever the device runs a backup |
| Purpose | Serving, measuring (analytics) and protecting ads from fraud, consent management, payment processing, posting a Play Store review, backing up your own data |
| Retention | As set by Google's Privacy Policy and data retention policy (https://policies.google.com/technologies/retention) |
| How to refuse, and what happens | Use the methods in section 2 (delete the ad ID, Privacy settings, play offline) and turn off backup (section 4). You can close the review card without submitting. Refusing does not limit the game. Offline, ads and in-app purchases are unavailable. With backup off, your progress is not restored automatically on a new device or reinstall, but you can move it yourself with Settings → Data → Save code |
3-2. Data the developer receives and keeps (support and refund emails, sales reports and order records)
Emails you send reach the developer's mailbox, and are stored there, through the services of the companies below. The sales reports and order records in the section 1 table are kept on the developer's computer, whose storage syncs to Apple iCloud.
| Item | Details |
|---|---|
| Legal basis | Article 28-8(1)(iii)(a) of the Personal Information Protection Act: entrusted processing and storage needed to handle support and refunds and to keep purchase records (performing our contract with you), with the matters listed in paragraph (2) of that Article disclosed in this policy |
| Recipients | Cloudflare, Inc. (101 Townsend St, San Francisco, CA 94107, USA; privacy contact: dpo@cloudflare.com): forwards email sent to jipstudiogames.com addresses (support@jipstudiogames.com and others). Google LLC (address and contact as in 3-1): stores the email in the developer's mailbox (Gmail). Apple Services Pte. Ltd. (7 Ang Mo Kio Street 64, Singapore 569086; the company that provides iCloud to users in Korea) and Apple Inc. (One Apple Park Way, Cupertino, CA 95014, USA); privacy contact: https://www.apple.com/legal/privacy/contact/ : store the sales report and order record files synced to iCloud |
| Country | The United States and other countries where each company runs servers (for Google, as in 3-1; for Apple, including Singapore, where the contracting company is) |
| Data | The emails you send (your address, the message and any attachments) and the developer's replies; the records of phone or text requests kept under section 7; the sales reports and order records in the section 1 table |
| When and how | Email sent to a jipstudiogames.com address passes through Cloudflare's email forwarding service on arrival and is stored in Gmail. The email the developer receives, and its replies, stay in Gmail until the developer deletes them under section 7. The sales reports and order records are sent by iCloud sync when the developer saves the files |
| Purpose | Cloudflare: forwarding email. Google: hosting the developer's mailbox. Apple: syncing and storing the developer's files |
| Retention | Cloudflare: while forwarding (forwarding records as set by Cloudflare's Privacy Policy, https://www.cloudflare.com/privacypolicy/). Google: until the developer deletes the email under section 7. Apple: until the developer deletes the files after the period in the section 1 table |
| How to refuse, and what happens | Emailing us is your choice. If you do not email us, no email is transferred, but we cannot reply to you by email. Mail sent straight to jipstudiogames@gmail.com does not pass through Cloudflare. Sales reports and order records exist only if you buy a paid item. They are tax records, so after a purchase they cannot be deleted within the retention period |
4. Backup (Android Auto Backup)
If Google backup is on for your device, Android backs up the game's save file (progress.json) to your own Google account and restores it on a new device or after a reinstall. Up to version 1.0.4, Android's default scope applies and all app data except caches and the like is backed up (the save file together with the settings and databases the ad and consent SDKs store on the device, WebView data and so on); from version 1.0.5, only the save file is. The operating system and Google handle this backup; the developer cannot access it. To turn it off: Android Settings → Google (or Accounts and backup) → Backup.
5. Usage stats (in the save file on the device, off by default)
If you turn on Usage stats in Settings, the app counts rounds finished, stage starts, clears and deaths, ads shown and rewarded, and purchase attempts, completions, restores and revocations in the save file on your device. There is no code that sends them anywhere, and they contain nothing that identifies you, your device or a session, and no timestamps. Because they are part of the save file, they go into the section 4 backup if backup is on, and into a save code if you make one. It is off by default, and turning it off also deletes what was counted (resetting the game does not).
6. Sharing and processors
The developer does not share personal data with third parties. The data in section 2 is sent to Google directly by the Google SDKs in the app, and Google handles it independently under its own Privacy Policy (https://policies.google.com/privacy); see 3-1. To receive support and refund emails, the developer entrusts email forwarding to Cloudflare, Inc. and stores the emails it receives in Google LLC's email service (Gmail). The sales reports and order records are kept in storage that syncs to Apple's iCloud. Their transfer abroad is described in 3-2.
7. Retention and deletion
Data on your device is removed when you uninstall the app (a backup copy in your Google account, section 4, is managed in your Google account's backup settings). In the game, Settings → Data → Reset erases your progress (stages, Shards, achievements and stats, but not the usage stats in section 5) and keeps your settings and purchases (Remove ads, Pilot Pack). The developer runs no server. Support emails are deleted once the matter is closed. The records below are the exception: under Article 6 of the Act on the Consumer Protection in Electronic Commerce and Article 6(1) of its Enforcement Decree, we keep them for a set period from the day the matter is closed.
- Requests about withdrawal (refunds), payment or delivery of items: 5 years (Decree Article 6(1)(ii) and (iii), records of contracts or withdrawal of offers, and records of payment and supply of goods)
- Other complaints and disputes about purchases or payments: 3 years (Decree Article 6(1)(iv), records of consumer complaints or dispute handling)
- What is kept: your email address (or phone number, if you asked by phone or text message), the dates of the request and its handling, the order number, what you asked for, and the outcome
- Kept separately: under Article 21(3) of the Personal Information Protection Act, these records are stored apart from other mail and records and are used only to keep them as the law requires and to handle disputes. For a request made by phone or text message, the items above are written down in the same separate store.
- How we delete: support emails (with our replies), text messages and call-log entries once the matter is closed, and records whose period has ended, are permanently deleted so that they cannot be recovered (for email, trash included).
The sales reports and order records in the section 1 table are separate from the records above: they are kept for the period in that table, then deleted in the same way.
8. Your rights
You may ask at any time to see, correct, delete or stop the processing of your personal data, and the legal guardian of a child under 14 may ask the same in the same way. The only personal data the developer holds is support messages still being handled (with our replies), the support and refund records in section 7, and the sales reports and order records in the section 1 table; for those, email us at the contact below (records still within a legal retention period are deleted when that period ends). Delete on-device data as described above, and manage what Google processes in your Google account and advertising ID settings. Send any other request to the privacy officer below as well.
9. Security
The developer runs no server, and the only personal data it keeps itself is support messages still being handled, the support and refund records in section 7, and the sales reports and order records in the section 1 table. The section 7 records are stored apart from other mail in an email account only the developer can access. The sales reports and order records are kept on a computer only the developer uses and in the developer's iCloud account that it syncs to. The Google SDKs send data over encrypted (TLS) connections.
10. Children
This app is not directed at children under 14. Ad requests say so explicitly (tag_for_child_directed_treatment = FALSE), and ad content is capped at rating G.
11. Privacy officer
- Privacy officer: Jip Kim, representative of 집스튜디오 (JIP Studio Games)
- Department handling privacy matters and complaints: Customer Support, 집스튜디오 (JIP Studio Games)
- Contact: support@jipstudiogames.com
12. Where else to turn (Korea)
For advice or dispute resolution about personal data, you can contact the Personal Information Dispute Mediation Committee (1833-6972, www.kopico.go.kr), the Personal Information Infringement Report Center (118, privacy.kisa.or.kr), the Supreme Prosecutors' Office (1301, www.spo.go.kr) or the Korean National Police Agency (182, ecrm.police.go.kr).
13. Changes
If this policy changes, the new version is posted on this page with a new effective date.
- Effective: November 3, 2026
- History: v1.0 (effective September 27, 2026) → v1.1 (effective October 4, 2026) → v1.2 (effective November 3, 2026). v1.1 adds the controller's registered name, the retention of support and refund records, the two kinds of transfer abroad and the legal basis for the developer's own transfer, the email forwarding processor, the department handling privacy matters, and the backup scope by version. v1.2 adds the Google Play In-App Review Library to the SDKs in the app and lists the star rating and review typed into the review card in the section 2 table and in the transfer details in 3-1. It also lists, in section 1, the order information Google Play may pass to the developer to process orders and refunds and the sales reports and order records the developer keeps for tax purposes, and reflects them in the transfer details in 3-2 (adding storage in Apple iCloud) and in sections 6, 7, 8 and 9. It also adds the times the game checks your purchases to 3-1, and corrects where game data is stored in section 1, the billing timing and consent note in section 2, the list of usage stats and where they are kept in section 5, and what a reset covers in section 7.