English | 한국어
Privacy Policy
- Published by
- Jeong Seong-yun (individual developer)
- App
- Onsaemigol (온새미골)
- Contact
- onsaemigol@gmail.com
This is an English translation provided for convenience. The Korean version is the binding text.
Jeong Seong-yun (the "Developer") values users' personal data and complies with the Personal Information Protection Act of the Republic of Korea. This Policy explains the categories, purposes and retention periods of the personal data processed by Onsaemigol (the "App"), and the rights of users.
1. Purposes of Processing
The Developer processes personal data only for the purposes below and will obtain prior consent if these purposes change.
- Account identification and save ownership — identifying the account created through Sign in with Apple (iOS) or Sign in with Google (Android) and linking game progress data to that account.
- Account management — the Google account email address that Firebase Authentication keeps in the account record when you sign in with Google is used only to verify your identity when you send an account deletion or other request by email. The App does not read this value, and it is not used for contact or marketing.
- Cloud save backup and restore — restoring game progress data after a device change or reinstall.
- Compatibility checks and bug fixing — checking the device, OS and app version, and analysing the causes of crashes.
- Usage statistics (optional) — reviewing pseudonymised usage statistics only where the user has given optional consent.
- Delivering tuning values and blocking abnormal clients — delivering game balance values and blocking access by tampered clients.
- Rewarded ads (optional) — Ads are shown, and rewards given, only when you choose [Watch ad] at an in-game ad entrance. The ad SDK processes device information for serving ads, frequency limits and fraud prevention. There are no forced ads.
- Playing with friends (optional, account users) — You add friends by friend code and play together in rooms only friends can join. Connection IDs and IP addresses are processed to connect devices. There is no free chat — only fixed greetings.
- Preventing duplicate nicknames — Nicknames are reserved so that two people cannot use the same one.
- Confirming in-app purchases — Purchase records (product ID, purchase time) are kept on the account to confirm and restore custom-look purchases. Payment-method details such as cards are handled by Apple and Google; the Developer does not receive them.
The App shows rewarded ads only when the user chooses to watch one, and sells custom-look items through in-app purchase.
2. Categories of Data and How They Are Collected
| Item | When / how collected | Purpose | Required / optional |
|---|---|---|---|
| Firebase uid (based on the Apple user identifier or the Google account identifier) | Generated automatically on Sign in with Apple (iOS) or Sign in with Google (Android) | Account identification, save ownership | Required when using an account |
| Name supplied by Apple | Returned by Apple once, on the first Sign in with Apple | Not used — discarded immediately on receipt; never stored, displayed or transmitted | — |
| Google account email address, name and profile photo URL | On Sign in with Google (Android), Google includes these in the sign-in token and Firebase Authentication keeps them in the account record. The App only passes the sign-in token to Firebase Authentication; it does not extract or read these values, display them, or put them in the game save, cloud save or usage statistics | Account management (the email address is used only to verify your identity when you send an account deletion or other request by email) | Required when using an account (Sign in with Google only) |
| Nickname | Entered directly by the user in the App | In-game name | Required |
| Game save (progress, inventory) | On cloud sync | Cloud restore | Required when using an account |
| Device model, OS version, app version | Automatically when the App runs | Compatibility checks, crash analysis | Required |
| Analytics app instance ID (pseudonymous) | Automatically on first launch after optional consent | Usage statistics | Optional |
| Approximate region (country / city level) | Estimated by Google Analytics from the IP address, after optional consent | Usage statistics | Optional |
| Firebase Installations ID | Automatically at app start (tuning-value and device attestation calls) | Identifying targets for tuning-value delivery, device attestation | Required |
| Crash logs (stack trace, device state) | Automatically when a crash occurs, after optional consent | Bug fixing | Optional |
| IP address | During communication with servers | Handling communications | Required |
| Advertising identifier (iOS IDFA / Android advertising ID) | Collected by the ad SDK (Unity LevelPlay) when you choose [Watch ad]; on iOS only if you allow it in the ATT prompt | Serving and measuring ads | Optional (ads and rewards still work without it — non-personalized ads) |
| Device information, IP, ad viewing records | Collected by the ad SDK when you choose [Watch ad] | Serving ads, frequency limits, fraud prevention | Only when watching an ad |
| Friend code (ONSAE-XXXX-XXXXX), friend / block lists, reports (fixed reason numbers) | When you use friend features (no names or photos) | Adding, blocking and reporting friends | When using friend features |
| Connection ID (Epic Online Services Product User ID), room ID, IP | When you create or join a friend room over the internet | Connecting friends' devices (via Epic relay if a direct connection is not possible) | When playing with friends over the internet |
| Local network address of devices on the same Wi-Fi | When playing with friends on the same Wi-Fi (not sent to any server) | Finding and connecting nearby friends' devices | When using same Wi-Fi play |
| Nickname reservation | When you set or change your nickname | Preventing duplicate nicknames | Required for account use |
| In-app purchase records (product ID, store, purchase time, app version) | When you buy a custom-look item | Confirming and restoring purchases | When purchasing |
Not collected: phone number, precise location information, contacts, reading photos or camera, payment-method information. Advertising identifiers are processed only by the ad SDK when you choose [Watch ad]; on iOS the IDFA is used only if you choose "Allow" in the App Tracking Transparency (ATT) prompt. The Developer's Analytics does not collect advertising IDs.
- Microphone and voice — Used only while you have allowed it and turned the mic on in karaoke (senior hall, coin karaoke, song contest). The app measures loudness on the device and plays your voice with echo through the device speaker. Only on your singing turn while playing with friends is your voice sent live to your friends' devices (directly between devices, or via the Epic relay if a direct connection is not possible). Your voice is never recorded, stored or sent to the Developer's servers. You can do the same activity with buttons without allowing the mic.
- Photo library — When you tap [Save to Photos] in the photo booth, the picture is only added to your photo library (the App does not read the library). Photos are not sent to the Developer.
- Email address — Sign in with Apple requests only the name scope, so no email address is received from users who sign in with Apple. For users who sign in with Google, the email address is kept by Firebase Authentication as shown in the table above.
- Location — precise location (such as GPS) is not collected. Only if you give optional consent to sending diagnostics and usage statistics does Google Analytics estimate an approximate country- or city-level region from the IP address.
- Photos — the Google profile photo file is not received. Only the photo URL in the table above remains in the Firebase Authentication account record.
Using the App without an account: if you play as a guest without Sign in with Apple or Sign in with Google, no account (uid) is created, and your nickname and game save are stored only on your device and are not transmitted to the Developer.
3. Processing and Retention Periods
| Item | Retention period |
|---|---|
| uid, nickname and game save in cloud save documents | For as long as the account exists; cloud document deletion is requested when the account is deleted |
| Firebase Authentication uid and sign-in account identifiers | For as long as the account exists; deletion is requested when the account is deleted. Removal from live and backup systems can take up to 180 days |
| Google account email address, name and profile photo URL | For as long as the account exists; deletion requested when the account is deleted. Removal of authentication data from live and backup systems can take up to 180 days |
| Name supplied by Apple | Not retained (discarded immediately on receipt) |
| Analytics data (including device information and approximate region) | User-level and event-level retention is set to 2 months. Expired data is processed through Google’s monthly deletion cycle; this setting does not apply to aggregate statistics |
| Crash logs | Retained for 90 days before removal from live and backup systems begins |
| Firebase Installations ID | Google's service processing period; reissuance stops when the App is deleted |
| IP address | Not stored separately by the Developer. Firebase Authentication keeps logged IP addresses for a few weeks for security and abuse prevention |
| Friend code, friend / block lists, connection ID, room ID | While the account exists. Deleted by the App on account deletion (including your code left in other users' friend lists and requests) |
| Nickname reservation | Deleted by the App when you change your nickname or delete your account |
| In-app purchase records | While the account exists (for restoring purchases). Deleted by the App on account deletion. Payment history held by Apple and Google follows each store's policy |
| Reports (fixed reason numbers) | Deleted within 1 year after review by the operator |
| Ad-related data | Not kept by the Developer. Per Unity retention policy |
| Epic Online Services connection data | Not kept by the Developer. Connection ends when the room closes; logs per Epic policy |
When you delete your account, the App immediately requests deletion of the cloud save and Firebase Authentication account. Authentication data may take up to 180 days to be removed from Google's live and backup systems. Crashlytics starts removing data from live and backup systems after 90 days of retention. See Firebase Privacy and Security for these service retention details.
4. Provision to Third Parties
The Developer does not provide users' personal data to third parties. The entrustment of processing described in sections 5 and 6 below is not provision to third parties.
5. Entrustment of Processing
To operate the service, the Developer entrusts the processing of personal data as set out below. When entering into an entrustment contract, the Developer includes provisions on the secure management of personal data in the contract and supervises whether the entrusted party complies with them.
| Entrusted party | Entrusted work | Entrusted data |
|---|---|---|
| Google LLC | Firebase Authentication (sign-in token verification, account identification, keeping the account record) | uid, Apple user identifier or Google account identifier, Google account email address / name / profile photo URL (when signing in with Google), IP, access time |
| Cloud Firestore (cloud save storage and restore; friend codes, nickname reservations and purchase records) | uid, nickname, game save, sync metadata, friend code / friend and block lists / connection ID / room ID, nickname reservation, in-app purchase records, IP | |
| Google Analytics for Firebase (usage statistics) — only with optional consent | App instance ID (pseudonymous), device model / OS / app version, event logs, approximate region estimated from IP, IP | |
| Firebase Crashlytics (crash cause analysis) — only with optional consent | Crash stack trace, device state, app version, IP | |
| Firebase Remote Config · App Check (tuning-value delivery, blocking abnormal clients) | Firebase Installations ID, App Attest attestation token (iOS), Play Integrity attestation token (Android), IP | |
| Unity Technologies (Unity LevelPlay · Unity Ads) | Serving and measuring rewarded ads — only when you choose [Watch ad] | Advertising identifier (if ATT allowed), device information, IP, ad viewing records |
| Epic Games, Inc. (Epic Online Services) | Friend rooms over the internet (lobby), device-to-device connection and relay — only when playing with friends over the internet | Connection ID, room ID, IP, live singing-turn voice (when relayed) |
6. Transfer of Personal Data Abroad
Under the entrustment in section 5 above, personal data is transferred outside the Republic of Korea. The legal basis for the transfer is disclosure in this privacy policy for entrusted processing and storage under the Personal Information Protection Act; no separate consent is obtained.
| Recipient | Destination country | Data transferred | Time and method of transfer | Purpose | Retention and use period |
|---|---|---|---|---|---|
| Google LLC (USA) Privacy officer contact: Google privacy inquiry form |
USA (Authentication infrastructure) | uid, Apple user identifier or Google account identifier, Google account email address / name / profile photo URL (when signing in with Google), IP, access time | Transmitted over HTTPS (TLS) at the time the service is used | Sign-in token verification, account identification, keeping the account record | For as long as the account exists |
| Stored in the Seoul region, Republic of Korea. May be accessed from the USA and countries where Google data centers are located in the course of operations and support | uid, nickname, game save, sync metadata, IP | Cloud save storage and restore | For as long as the account exists | ||
| USA and countries where Google data centers are located | App instance ID (pseudonymous), device information, event logs, approximate region, IP | Usage statistics | 2-month user/event retention setting, followed by monthly deletion (section 3) | ||
| USA and countries where Google data centers are located | Crash stack trace, device state, app version, IP | Crash cause analysis | 90 days before removal begins | ||
| USA and countries where Google data centers are located | Installations ID, App Attest attestation token (iOS) / Play Integrity attestation token (Android), IP | Tuning-value delivery, blocking abnormal clients | Google's service processing period | ||
| Unity Technologies (USA) Contact: Unity privacy policy | USA and countries where Unity data centers are located | Advertising identifier (if ATT allowed), device information, IP, ad viewing records | Sent over HTTPS (TLS) when you choose [Watch ad] | Serving and measuring rewarded ads | Per Unity retention policy |
| Epic Games, Inc. (USA) Contact: Epic privacy policy | USA and countries where Epic data centers are located | Connection ID, room ID, IP, live singing-turn voice (when relayed) | Encrypted transfer while playing with friends over the internet | Connecting and relaying friends' devices | Connection ends when the room closes (logs per Epic policy) |
How to refuse and the consequences: users may refuse the transfer abroad. To refuse, do not give the required consent on the notice screen shown at first launch, or, if you have already created an account, delete your account in the App. If you refuse, the cloud save (account features) cannot be provided, but you may continue to play with data stored only on your device, without an account.
7. Relationship with Apple Inc. and Google LLC
- Sign in with Apple (iOS) is an authentication method through which Apple provides a user identifier to the Developer. In this process the Developer does not provide users' personal data to Apple and does not entrust the processing of personal data to Apple. Apple's privacy policy applies to Apple's processing.
- Sign in with Google (Android) is an authentication method through which Google provides a user identifier to the Developer. In this process the Developer does not provide users' personal data to Google, and receiving the sign-in method itself is not an entrustment of the processing of personal data. Google's privacy policy applies to Google's processing of your Google account. Firebase Authentication keeping the account record after sign-in is the entrustment of processing described in section 5 above.
- For beta distribution through TestFlight, testers' email addresses and device information are processed by Apple under its own policies. The Developer does not separately collect or retain tester email addresses.
- For test distribution through Google Play, where testers are specified by an email list, the Developer adds the Google account email addresses of people taking part in the test to the tester list in the Play Console. These email addresses are used only to manage test participation, are kept only in the Play Console tester list, and are removed from the list when the test ends. Testers' installation and device information is processed by Google under its own policies.
8. Destruction Procedure and Method
- Personal data is destroyed without delay when the retention period ends or the purpose of processing has been achieved.
- When account deletion is requested, the App immediately requests deletion of the cloud documents containing the uid, nickname and game save, the in-app purchase records, the friend code with friend and block lists, the nickname reservation, and of the Sign in with Apple or Sign in with Google link (the Firebase Authentication account, including the Google account email address, name and profile photo URL). Removal from Google’s live and backup systems follows the procedures and periods in section 3. Electronic files are deleted by a method that makes them unrecoverable. How to remove the App from the connected-apps list on the Apple or Google account side is explained on the account deletion page in section 9 below.
- If in-app deletion fails, a request sent to the email address in section 13 below will be destroyed manually within 10 days.
- Analytics and Crashlytics data expire automatically under Google's processing procedures once the periods in section 3 above have passed. The Analytics identifier is also reset upon account deletion.
9. Rights and Obligations of Data Subjects and Legal Representatives, and How to Exercise Them
Users may exercise the following rights at any time:
- Request access to personal data · request correction where there are errors · request deletion · request suspension of processing
There are two ways to exercise these rights:
- In the App — under Settings > Account · Data you can change your nickname and delete your account yourself.
- By email — send a request to onsaemigol@gmail.com; it will be handled and the result will be sent to you within 10 days.
The account deletion steps, how to request deletion by email without the App, and which data is deleted or kept (and for how long) are set out on the account deletion page.
Users may also exercise their rights through a legal representative or a person to whom they have delegated authority. In that case, a power of attorney must be submitted.
10. Security Measures
- Encryption in transit — all communications are encrypted with HTTPS (TLS).
- Access control — security rules are applied to the cloud database so that a signed-in user can read and write only their own document. Other users' data cannot be accessed.
- Minimal administrator accounts — there is one administrative console account that handles personal data, and two-factor authentication is applied to it.
- Device attestation — device attestation based on Apple App Attest (iOS) and Google Play Integrity (Android) is used to block access by tampered clients.
11. Installation, Operation and Refusal of Devices That Automatically Collect Personal Data
The App does not use a web browser and therefore does not use cookies. The SDKs below collect information automatically while the App is running.
| SDK | Information collected | How to refuse |
|---|---|---|
| Firebase Authentication | uid, IP (when signing in with Google: Google account email address, name and profile photo URL) | Does not operate unless you use Sign in with Apple or Sign in with Google |
| Cloud Firestore | Save data, IP | Does not operate unless you use Sign in with Apple or Sign in with Google |
| Google Analytics for Firebase | App instance ID (pseudonymous), device information, events, approximate region (estimated from IP) | Do not give optional consent, or stop it at any time by turning off Settings > Account · Data > Send diagnostics & usage stats (진단·사용 통계 보내기) |
| Firebase Crashlytics | Crash stack trace, device state | Do not give optional consent, or stop it at any time by turning off Settings > Account · Data > Send diagnostics & usage stats (진단·사용 통계 보내기) |
| Firebase Remote Config · App Check | Installations ID, attestation token (App Attest / Play Integrity), IP | Required for the App to operate, so individual refusal is not offered; collection stops when the App is deleted |
| Unity LevelPlay (ads) | Advertising identifier (if ATT allowed), device information, IP | The ad SDK is not started unless you tap [Watch ad]. On iOS you can turn it off in Settings > Privacy & Security > Tracking |
| Epic Online Services | Connection ID, IP | Does not operate unless you play with friends over the internet |
12. Personal Data of Children Under 14
The Developer does not collect personal data of children under the age of 14. The user's age is checked at first launch. If the user is confirmed to be under 14, account (Sign in with Apple / Sign in with Google) features are not provided, usage statistics and crash data are not collected, tuning values are not fetched, the ad entrances are hidden and the ad SDK and tracking prompt are never started, and playing with friends (including same Wi-Fi) and purchases are not offered. In that case, game data is stored only on the user's device and is not transmitted to the Developer.
13. Privacy Officer and Channel for Receiving and Handling Access Requests
- Privacy officer
- Jeong Seong-yun
- Position
- Developer (individual)
- Contact
- onsaemigol@gmail.com
Requests for access to personal data are received and handled at the email address above. Inquiries, complaints and requests for remedies relating to personal data protection may also be sent to the same channel, and will be answered without delay. The Developer does not operate GitHub Issues or social media direct messages as contact channels.
14. Remedies for Infringement of Rights
To obtain remedies for infringement of personal data, you may apply for dispute resolution or consultation to the following bodies (Republic of Korea).
| Body | Responsibilities | Contact |
|---|---|---|
| Personal Information Infringement Report Center (KISA) | Reporting personal data infringement, requesting consultation | 118 (no area code) · privacy.kisa.or.kr |
| Personal Information Dispute Mediation Committee | Personal data dispute mediation, collective dispute mediation | 1833-6972 · www.kopico.go.kr |
| Supreme Prosecutors' Office, Cyber Investigation Division | Investigation of personal data infringement | 1301 (no area code) · www.spo.go.kr |
| Korean National Police Agency, Cyber Investigation Bureau | Investigation of personal data infringement | 182 (no area code) · ecrm.police.go.kr |
In addition, if you object to the Developer's action on a request for access, correction, deletion or suspension of processing of personal data, you may file an administrative appeal under the Personal Information Protection Act.
15. Effective Date and Revision History
This Privacy Policy applies from October 22, 2026. When any content is added, deleted or modified, notice will be given in the App and on this page from 7 days before the effective date. However, changes that materially affect users' rights will be notified 30 days in advance. Revision v2 adds the processing for the newly released Android version; it does not reduce or change the processing that already applied to users of the iOS version and only adds a way to turn off diagnostics and usage statistics, which widens users' rights, so it applies from the date of posting. Revision v2.1 only adds an optional, on-device check that collects nothing, so it also applies from the date of posting. Revision v3 only adds the processing for new optional features introduced in update 1.0.2 (rewarded ads, playing with friends, custom-look purchases); it does not reduce or change existing processing, and those features run only when the user chooses them, so it applies from the date of posting.
| Version | Effective date | Changes |
|---|---|---|
| v1 | September 14, 2026 | Initial version |
| v2 | October 3, 2026 | Android release: added the data processed for Sign in with Google (email address, name, profile photo URL) with its retention, entrustment and transfer abroad; stated the approximate-region estimate and Play Integrity; added a link to the account deletion page and how to turn off diagnostics and usage statistics |
| v2.1 | October 4, 2026 | Added the optional on-device microphone loudness check in the senior hall karaoke activity (nothing is recorded, stored or sent); clarified retention wording for crash reports and Firebase installation IDs |
| v3 | October 22, 2026 | 1.0.2: added rewarded ads (Unity LevelPlay, advertising identifier, ATT), playing with friends (friend codes, Epic Online Services, same Wi-Fi, live voice on your singing turn), nickname reservation, custom-look in-app purchase records, and saving photo-booth pictures to the photo library. Children under 14 are not offered ads, friend play or purchases |