Effective 2 October 2026 · Operated by LoreUp
This English text is provided for convenience. The Korean version is the binding original, and it prevails in the event of any discrepancy.
1. What we collect
The following data is processed in order to provide the Service.
- Account and sign-in: email address (from email sign-up or Google/Apple sign-in), a password hash (for email sign-up), and the name and profile image provided by Google or Apple where applicable. A device account created with "Start on this device" in the app signs in with a random identifier that the app generates and stores on that device; the server keeps only an irreversible hash of it. Hardware device identifiers are not used. Deleting the app removes the identifier, after which that account can no longer be signed into
- Service usage: character name, chosen fields, XP, level and streak, quiz sessions and answers, review schedules, stats per field, exploration ticket balance (and ad reward balance where that feature is used), subscription and Lifetime plan status, referral code and relationships, and your display language (set from the language you signed up in, and changeable from your account)
- Authentication and sessions: session cookies and Auth.js session data used to keep you signed in
- Purchases and payments: store transaction identifiers (transaction ID and the like), product IDs and grant records for in-app purchases. Card numbers and payment passwords are never collected; payment is handled by the Apple App Store and Google Play.
- Advertising and device identifiers (mobile app, where applicable): where rewarded ads are enabled, an advertising identifier (IDFA/AAID and the like), device and app information, and ad interactions (whether an ad was watched and completed) may be processed through the ad SDK in order to serve ads from networks such as Google AdMob. On iOS, permission to track may be requested under App Tracking Transparency (ATT).
- Product analytics: where an analytics tool is configured, key steps (landing and shared-question page views, taps on the store install button, sign-in page views, sign-up, account linking, onboarding views and completion, exploration starts and completions, whether you allowed notifications, return visits, purchase attempts, cancellations, failures and completions) and the details attached to them (sign-up or linking method, question field and difficulty, product ID and store, why a purchase did not complete and the error message the store returned, web vs. app, display language, whether you arrived through an invite link, and the referral channel carried in link parameters as utm values) are recorded to improve the Service. Your IP address is not passed to the analytics tool and no location (country or city) is inferred. These records are linked to a random visitor identifier stored in your browser (a cookie) and to your member identifier, and the correct answers and your answer text are never transmitted.
- Technical logs: server logs and error information used to keep the Service stable (including an error tracking tool where configured)
Location data, contact lists and photo libraries are not collected.
2. Why we use it
- Identifying members and signing them in
- Providing daily quests, review, growth, tickets and usage limits
- Verifying in-app purchases, granting ticket and subscription benefits, and preventing fraudulent payments
- Granting ad rewards where rewarded ads are offered
- Improving the Service through usage analysis (statistics, retention and conversion)
- Preventing abuse and running the Service reliably
- Handling support enquiries, account deletion and refund support requests
3. Storage, processors and third-party SDKs
Data is stored in a PostgreSQL database and may be processed through web hosting (such as Vercel) and Google authentication infrastructure.
The following external services may be used to provide the Service.
- Google (sign-in)
- Google AdMob: ads in the mobile app where rewarded ads are enabled (advertising identifiers and similar data may be passed to advertisers and measurement partners)
- Apple App Store / Google Play: in-app payments, subscriptions and receipt handling. On Android, Google Play passes an install referrer value (see section 5) to the app at install time
- PostHog (product analytics): where an analytics tool is configured, the usage-step records described in section 1 are sent through our server
Please refer to each provider's own policy for how they handle personal data. When you delete your account, the related personal data and progress data are deleted without delay. Where the law requires retention (for example to handle payment or refund disputes), data may be kept for that period.
4. Sharing with third parties
Personal data is never sold to outside parties without your consent. The exceptions are requests made under the law, and the processing needed for the authentication, advertising and payment flows you chose.
5. Cookies and tracking
On the web, essential cookies are used to keep you signed in. Alongside those, first-party cookies are used for usage analysis and for displaying the site (a random visitor identifier, the date of your last visit, the referral channel and your chosen display language). These cookies are read only on the server and are not used for advertising. As a matter of principle, the web service itself does not use third-party advertising cookies.
In the Android app, the install referrer value provided by Google Play is read once, right after installation. It carries the invite code and referral channel (utm values) that were attached to the link you tapped before installing, and it is used only for the same purposes as the first-party cookies above. Where the app was installed by searching the store, the placeholder value Google Play returns is not recorded as a referral channel. There is no equivalent on iOS.
Where rewarded ads are enabled, AdMob ads in the mobile app may use the ad network's identifiers and measurement technology, and declining tracking under iOS ATT may limit personalised ads.
6. Your rights
You can delete your account at any time after signing in, from account deletion. Deleting removes your character, progress, answers, ticket balance and records of in-app subscriptions and paid benefits, and it cannot be undone. Cancelling a store subscription must be handled separately in your device settings. You can change app tracking permission in your iOS device settings.
7. Children
The Service is not directed at anyone under 14 years of age, and personal data of children under 14 is not knowingly collected. It includes paid features, and may include ads where the advertising feature is enabled, so guardian supervision may be needed.
8. Changes to this policy
Changes to this policy are published on this page. Where a change is significant, notice may also be given within the Service.
9. Contact
For privacy enquiries, follow the guidance on the account deletion page after signing in, or use the developer contact channel on the app store.