Game privacy policy
Palimpsest Game Privacy Policy
This translation is provided for your convenience. If it differs from the Korean version, the Korean version prevails.
MyHome (the “Operator”) maintains this privacy policy to protect the personal information of the data subjects who use the mobile game “Palimpsest” (the “Game”). This policy applies to the game app and its account backup feature. The website's release notification, inquiries and visit statistics are covered by the website privacy notice.
1. Purposes of processing personal information
The Operator processes personal information for the following purposes and does not use it for any other purpose.
- Identifying logged-in accounts
- Backing up and restoring episode progress and game settings on the server
- Compiling statistics from play records to adjust episode difficulty
- Counting daily users to run the service (from October 24, 2026)
- Aggregating play statistics regardless of login: progress and clears per episode, missions where players get stuck, and the number of users (from October 25, 2026)
- Counting users by language and region, and deciding which languages to translate into (from November 10, 2026)
- Aggregating the gameplay feedback users send (difficulty, rating, one-line comment) and improving the game
- Finding the causes of app errors and login failures (crash reports)
- Showing the display name on the account screen
Email addresses are not used for collecting statistics.
2. Personal information processed
① The following items are processed only if you log in with a Google or Apple account. Logging in is optional.
- Account identifier, email address
- The display name provided by the login provider
- Authentication information to keep you logged in, time of last login
- Dates of app use: the dates on which the app was used with the logged-in account (once a day; the time is not kept)
- Episode progress, game settings
- Play records: when you finish an episode, whether you cleared it, the time taken, score, number of items obtained, number of hints used and number of wrong answers, and for each mission whether its hints were viewed and whether it was completed, with their times
- Records of consent to the collection and use of personal information (purpose of consent, policy version, time of consent)
② Regardless of login, from October 25, 2026, the following items are processed while ‘Send Play Statistics’ in the settings is on.
- Install identifier: a random value issued by the Operator's server the first time statistics are sent from the device where the app is installed. It is not an advertising identifier or a device serial number, and it disappears from the device when you delete the app. The server keeps this value only in a form that cannot be restored (a hash).
- The device's operating system (Android or iOS), the app version, and the dates of app use (once a day; the time is not kept)
- The language chosen in the game, and the device's language and region (country) settings (from November 10, 2026). These are the values chosen in the device settings, not a country inferred from location information or the IP address.
- Play statistics: episode starts and continues, hint views per mission, and, when you finish an episode, whether you cleared it, the time taken, score, number of items obtained, number of hints used and number of wrong answers, with their times
- The time a store rating request was shown and the app version at that time (the store does not tell the Operator whether you left a rating or what it said)
- If you are logged in, the account that used that install identifier
③ If you send gameplay feedback: the difficulty and rating for each episode, a one-line comment (optional, up to 300 characters) and the app version at the time it was sent are processed. Feedback is not made public. Please do not include anything in a one-line comment that could identify a person, such as a name or contact details.
④ Google Firebase is used for app crash reports and usage analytics (sections 6 and 7 ④). Crash reports (Crashlytics) send the device model, operating system version, app version and the location of the error when the app terminates abnormally. From November 9, 2026, the same items, the step that failed and the error details are also sent when a login fails. The account's email and login token are not sent. Usage analytics (Analytics), from October 25, 2026, sends the app instance identifier, device information and the play statistics in ② above only while ‘Send Play Statistics’ is on, and from November 10, 2026 it also sends the language chosen in the game.
⑤ A guest's progress (save) is stored only on the user's device, and no information other than ② to ④ above is stored on the Operator's server.
3. Processing and retention period of personal information
① Account identifiers, email addresses, backup data, play records and consent records are kept until the account is deleted.
② Dates of app use are kept for 35 days and then destroyed; after that, only daily user counts not linked to any account remain. Dates of app use are also destroyed when the account is deleted.
③ Install identifiers and the play statistics, rating request records and gameplay feedback attached to them are kept for 13 months from the date of collection and then destroyed. An install identifier's dates of app use are kept for 35 days and then destroyed; after that, only daily user counts not linked to any install identifier remain. An install identifier linked to an account is destroyed, with the records attached to it, when the account is deleted.
④ Information processed by Google Firebase is kept according to Firebase's retention settings (user-level analytics data for up to 14 months, crash reports for 90 days).
⑤ Materials that must be kept by law may be kept separately for the required period.
⑥ The Operator does not keep the progress stored on the device; it can be removed by clearing the app's data or deleting the app.
4. Right to refuse consent and its consequences
① Users may refuse consent to the collection and use of personal information and continue to use the Game without logging in.
② A guest's progress is stored on the device and is not backed up to the server. It may not be recoverable if you delete the app or change devices.
③ Guest progress is not merged into a logged-in account automatically and stays on the device.
④ If you turn off ‘Send Play Statistics’ in the settings, the collection of the play statistics described in 2 ② and of Firebase usage analytics stops, and statistics not yet sent from the device are deleted. This does not affect your use of the Game.
⑤ Gameplay feedback is processed only when the user sends it, and not sending it does not affect your use of the Game.
5. Provision of personal information to third parties
The Operator provides personal information to third parties only in the cases set out in Articles 17 and 18 of Korea's Personal Information Protection Act, such as with the data subject's consent or under a special provision of law. No personal information is currently provided to third parties.
6. Entrustment of personal information processing
① The Operator entrusts the processing of personal information as follows.
- Processor: Google LLC (Google Firebase) · Entrusted work: reports of app crashes and login failures, usage analytics
② Under this entrustment, personal information is transferred overseas (Article 28-8 of the Personal Information Protection Act).
- Recipient: Google LLC; contact: Google privacy inquiries
- Countries of transfer: the United States and other countries where Google operates data centers
- Time and method of transfer: sent over the network from time to time while the app is in use
- Items transferred: the crash report and usage analytics items described in 2 ④
- Purpose of use and retention period: app error analysis and usage statistics, for the periods described in 3 ④
- How to refuse and its consequences: if you turn off ‘Send Play Statistics’ in the settings, usage analytics is not transferred. Crash reports are necessary to provide the app reliably and cannot be refused; to refuse them, you must stop using the app.
③ If the entrusted work or the processor changes, we will disclose it through this policy in accordance with Article 26 of the Personal Information Protection Act.
7. Use of external services
① If you choose to log in, you are taken to the Google or Apple sign-in screen, and that provider's privacy policy applies to the process.
② Opening the web novel link in the lobby takes you to Munpia. This link does not pass on the email address of your game account.
③ In the mobile version, rewarded ads may be shown when you open a hint, and Google AdMob is used to show them. In this process, Google may collect and process the advertising identifier, device information and the like, and Google's privacy policy applies to that processing. You can reset the advertising identifier and limit personalized ads in your device's settings.
④ Google Firebase (Crashlytics, Analytics) is used for the app's crash reports and usage analytics. The items processed are described in 2 ④ and the entrustment and overseas transfer in 6, and Google's privacy policy also applies to that processing.
⑤ After you clear an episode, the Google Play or App Store rating window may be shown. Ratings and reviews stay in each store, and the Operator does not receive their content through the app.
8. Rights and obligations of data subjects and their legal representatives, and how to exercise them
① Data subjects may exercise the following rights concerning the protection of personal information against the Operator at any time.
- Request to access personal information
- Request for correction of any errors
- Request for deletion
- Request to stop processing
② Account deletion can be requested in the app's account settings. Please send other requests to the privacy officer using the contact information below, and we will handle them without delay.
9. Destruction of personal information
① If you request deletion in the app's account settings, we delete the account on the server and the data linked to that account.
② Materials that must be kept by law are destroyed after the relevant period has passed, in accordance with 3 ③ above.
10. Installation and operation of tools that automatically collect personal information, and how to opt out
The game app does not use ‘cookies’ that store and retrieve the data subject's usage information from time to time. The processing of the advertising identifier is as described in 7 ③ above. The install identifier for play statistics and Firebase's app instance identifier are as described in 2 ② and ④, and turning off ‘Send Play Statistics’ in the settings stops the collection of statistics.
11. Privacy officer
① The Operator has designated the following privacy officer, who has overall responsibility for the processing of personal information and handles data subjects' complaints and remedies for damage related to that processing.
- Name
- Lee Sang-in
- Title
- Representative
- Contact
- leein3293@kakao.com
② Data subjects may contact the privacy officer about any inquiries, complaints, remedies for damage and other matters concerning the protection of personal information that arise while using the Game. The Operator will answer and handle data subjects' inquiries without delay.
12. Changes to this privacy policy
① This privacy policy applies from its effective date. If its content is added to, deleted or corrected under laws or this policy, we will give notice on the website from 7 days before the changes take effect.
② Revised October 5, 2026: organized into articles, and the processed items and the content on advertising (7 ③) were stated in detail. The purposes of collecting and using personal information for account backup and its retention period did not change.
③ Revised October 13, 2026: added the play records of logged-in accounts to the processed items (2 ①) and their aggregate statistics to the purposes (1). Guests' play records stay only on the device, as before.
④ Revised October 17, 2026 (effective October 24, 2026): added the dates of app use to the processed items (2 ①), counting daily users to the purposes (1), and their retention period (3 ②). Dates of app use are not recorded before the effective date.
⑤ Revised October 18, 2026 (effective October 25, 2026): added play statistics regardless of login and the install identifier (2 ②), gameplay feedback (2 ③), crash reports and usage analytics using Google Firebase (2 ④, 7 ④), their purposes (1) and retention periods (3 ③ and ④), how to refuse with ‘Send Play Statistics’ (4 ④), entrustment of processing and overseas transfer (6), and the store rating window (7 ⑤). Play statistics and usage analytics are not recorded before the effective date.
⑥ Revised November 1, 2026 (effective November 9, 2026): added login failure reports to the crash reports (2 ④). They are not sent before the effective date.
⑦ Revised November 3, 2026 (effective November 10, 2026): added the language chosen in the game and the device's language and region settings to the play statistics (2 ②) and usage analytics (2 ④), and counting users by language and region to the purposes (1). Location information and IP addresses are not used. The language and region information is not sent before the effective date.