Privacy Policy

When you use the app (members)

• Account information: (required) email, (required) display name, (required) date of birth, (optional) gender. If you sign in with a social account such as Kakao, we receive the account identifier and email provided by that social account provider. We block sign-up by children under 14 (age verification) through a step at sign-up in which you confirm that you are 14 or older and through the date of birth you enter, and we store the time of that confirmation as a consent record. We use your date of birth to block sign-up by children under 14, to tailor screens by age group, and for statistics. Gender is optional: you can use the Service without entering it, and if you enter it, we use it for statistics. The birth-year range and gender you enter are also pseudonymized under Section 12 and used for statistics and scientific research. Date of birth is required at sign-up in app version 1.1 and earlier and from app version 1.2.2, and was optional in app versions 1.2.0 to 1.2.1, so members who signed up with those versions without entering a date of birth may have no date of birth stored.
• Consent records: the time you agreed to the Terms of Service and to the collection and use of personal information and confirmed you are 14 or older, and (optional) whether and when you agreed to receive news and offers.
• Usage settings (from app version 1.3.0): your app language setting (Korean or English), device time zone (a time zone name such as Asia/Seoul) and the date and time it was last changed (used to limit time zone changes to once every 20 hours), and store account country (the country code set on your App Store or Google Play account) are stored and linked to your account. The app language is first set from your device language and can be changed in Settings, and the device time zone is read by the app from your device settings. After you sign in, we check the store account country by looking it up with our payment processor (RevenueCat) using your internal member ID (see Section 6), and the checked value is also kept on your device for the next launch. Before you sign in, or while the store account country cannot be checked, we use the previously checked value or your device region and language settings only to decide what the screen shows (such as whether to show the Kakao login button), and your device region setting is not stored in your account.
• Onboarding survey: how you heard about the Service, your current AI use (level of experience), and your answers to the learning style quiz (what you do, the tasks you mainly handle, what you want to do with AI, employment type, and reason for learning).
• Learning records: your question history and answers to each question (the answer you chose or entered, whether it was correct, AI grading results for written-answer questions, and which attempt at the same question it was), XP and Level, track progress, streak days, badges earned, Weekly League records, and so on. From app version 1.1, the time spent on each question, its order within the lesson, and the app version and platform (iOS/Android) at the time of the answer are also stored with each answer, and from app version 1.3.0, the language in which the question was shown at the time of the answer (Korean or English) is also stored. From app version 1.2.2, in the activity where you write a prompt for a given situation, receive an AI output, and check your score (“Prompt Practice”), the prompt you enter, the output the AI created from it, your score (including scores by criterion), and notes on what could be improved are stored.
• Character and practice: the face photo you upload to create your character (avatar) (kept in private storage and used only to create the character), the generated character images, and outputs you create with practice tools (images and audio).
• Friend invitations and referrals: records of invite code use and referrer/referred relationships, and pseudonymized social account identifiers (one-way hash) used to prevent abuse such as claiming the same benefit more than once.
• Report and block records: if you report another user, the reason and details of the report and the reported user’s display name are stored, and if you block a user, the block relationship and that user’s display name at the time of blocking are stored.
• Usage restriction records (effective October 19, 2026): if we suspend or lift the suspension of a member account under Article 13 of the Terms of Service, the reason for the suspension, the suspension period (start and end, or indefinite), the reason for lifting it, and the time of each action are stored. We do not ask you to enter any new information for this.
• Membership tier (subscription status): your membership tier. After paid services go on sale, the subscription product and subscription status are added, and your internal member ID and store purchase history are passed to our processor (RevenueCat) to verify receipts and manage subscription status (see Section 6). We receive payment records from the processor (subscription product and period type, store used, times of payment, renewal, expiry, cancellation, refund, and payment failure, the end of the grace period set by the store when a payment fails, reasons for cancellation or expiry, records of purchases transferred between accounts, payment amount and currency, store transaction ID, and whether it was a test payment) and store them with your internal member ID. Payments themselves are processed through the Apple App Store and Google Play, and we do not collect payment method information such as card numbers.
• (Optional) Payback phone number (effective October 18, 2026): the mobile phone number you register in the app settings to take part in the first-payment payback event, the time you consented to its collection and use, the time the gift card (gifticon) was sent, and the payout round and store transaction ID (payout records). You can use the Service and your subscription without registering, but you cannot receive the payback without registering.
• Ad reward records: if you refill Energy by watching a rewarded ad, the time you watched the ad and the ad view transaction identifier issued by Google are stored and linked to your account. This is so our server can confirm that you finished watching the ad, give the reward, and prevent duplicate rewards, and for this purpose your account identifier is passed to Google AdMob (see Section 6).
• Push notifications: if you allow notifications, we use your device push token to send learning reminders, and when a reminder is sent, the push token and notification content are transmitted through our delivery processor (Expo) (see Section 6). Records of the date and time slot of each reminder and its delivery result (success or failure) are stored and linked to your account for 90 days so that we do not send more than one reminder in the same time slot, and are then deleted automatically. The title and body of sent notifications are stored and linked to your account for 90 days so that they can be shown on the notifications screen of earlier app versions, and are then deleted automatically. You can turn off notifications at any time in your device settings or on the My Info screen of the app (the notifications screen in earlier app versions).
• When you contact support: the content of your inquiry and records of how it was handled.
• Translation issue reports (from app version 1.3.0): if you use the Report a translation issue feature in the app, the reported item (question or screen), screen language, reason for the report, (optional) note (up to 300 characters), app version, and report time are stored with your internal member ID.
• Collected automatically (app): usage records (behavioral and performance information such as screen navigation, learning progress, and screen and request response times, and from app version 1.2.2, records of viewing event announcement pop-ups (the first and last time viewed, number of views, and the button tapped)), device information (model name, OS version, app version), when ads are shown, the advertising identifier and approximate location based on your IP address (processed by the ad SDK only to show non-personalized ads and not stored on our servers, see Section 6), error and crash information, and screen usage recordings when an error occurs (screen recording, with text and images masked so that the original content is not included). We remove the original text you entered before sending error and performance information so that it is not included.
• Behavior analytics and screen interaction records (from app version 1.1): to analyze usage flows, such as the screen where people stop learning, we send to our analytics processors (see Section 6) app usage records (screen navigation, learning and practice progress, results of using features), device information (model name, OS version, app version, language setting), your internal member ID and a random device identifier created when the app is installed, and category values used to compare usage flows between groups (the kind of work and AI experience level derived from your sign-up survey, the screen theme group based on your date of birth, membership tier, Weekly League tier, streak range, whether you signed up through an invite link, from app version 1.2, the category value for how you heard about the Service chosen in the sign-up survey and the install channel identified through ad performance measurement, and from app version 1.3.0, your app language setting and store account country). We do not send your original survey answers, your date of birth itself, or the campaign and ad creative names in the install source information. Text you enter yourself (written answers, prompts entered in Prompt Practice, character descriptions, inquiry content, nicknames, invite codes) is not included in what we send. The settings exclude advertising identifiers, IP addresses, and carrier information from what is sent, but because the app communicates directly with the processor’s servers, your IP address reaches those servers as part of how internet communication works.
• Screen interaction records (session screen recording, from app version 1.1): as part of the behavior analytics above, your app screens are recorded whether or not an error occurs and sent to our analytics processor. What you type into input fields is automatically covered and not recorded, and on screens that show personal information (My Info, profile editing, payback phone number registration (effective October 18, 2026), profile entry and survey at sign-up, photos uploaded to create a character, inputs and outputs of practice tools, and inputs and outputs of Prompt Practice), the whole area is covered in the recording. Other content shown on screen (learning questions, nicknames, buttons and guidance text, and so on) and the positions you tap remain in the recording.
• Ad performance measurement (from app version 1.2, collected automatically): to measure which ad or channel led to your app install and what happened afterwards, app install and launch events from the first time you install and open the app, and then sign-up, lesson completion, subscription screen visit, and purchase result (subscription product, payment amount and currency) events each time they occur, are sent with the time they occurred to our ad performance measurement processor (see Section 6). The items sent with them are device identifiers (a random device identifier created by the measurement processor at install, the iOS identifier for vendors (IDFV), and the Android install referrer), advertising identifiers (on iOS, the IDFA only if you allowed it in the app tracking prompt; on Android, the advertising ID), device information (model name, OS version, app version, language setting), your IP address, and, if you are signed in, your internal member ID. We do not send your email, phone number, or display name. The install source information we receive as a result of measurement (install channel, campaign, ad creative name, and the time received) is stored and linked to your account once after install. Of this, the install channel is also sent to our analytics processors from app version 1.2 as a category value for comparing groups in behavior analytics (see the behavior analytics item above and Section 6). On iOS, even if you do not allow app tracking, the items above other than the advertising identifier (events and the time they occurred, device identifiers, device information, IP address, internal member ID) may be sent to Meta through the measurement processor so that the ad platform (Meta) can measure ad performance in aggregate (Aggregated Event Measurement, AEM) (effective October 20, 2026, see Sections 6 and 8). Section 8 explains how to refuse the collection of advertising identifiers.
• Publicly shown items: your display name, character image, Level and XP, Weekly League tier, badges earned, and streak days may be shown to other users through leaderboards and profile cards.

When you use the web trial (non-members)

• Pre-registration and launch notice: (required) phone number, (required) record of confirming that you are 14 or older, (optional) whether you agree to receive marketing information, and preferred store (iOS/Android).
• Trial inputs: photos you upload (pixel avatar trial, which may include a face) and the prompts, lyrics text, and song titles you enter. These are sent to external AI providers for AI generation and for screening whether the input is appropriate (see Section 6). We do not store uploaded photos or prompts in our database. The lyrics and song title of the music trial (including a title you enter yourself) are kept with the generated output for up to 48 hours to show them on the result screen and share page, and are then destroyed (see Section 3).
• Generated outputs: image and music files generated in the trial, destroyed automatically 48 hours after generation (see Section 3).
• Survey answers: age group, gender, occupation category, current AI use, and so on. We do not ask for your name or contact details, but because the answers are stored with the trial session identifier, they may be linked to a phone number if you registered one in the same session.
• When you take part in the AI Arena: nickname (optional, shown publicly on the leaderboard) and quiz scores and records.
• Collected automatically (web): IP address (as a pseudonymized hash), browser information (User-Agent), referral source (UTM), cookies, and service usage records (behavioral information such as page visits and clicks, error information, and screen usage recordings with input content masked).

• Identifying your account and providing the Service: saving and resuming learning records, running the personalized recommendation algorithm, and producing learning statistics.
• Managing membership tiers: after paid services go on sale, applying subscription benefits, verifying receipts, responding to payment inquiries and preventing fraudulent payments, and keeping transaction records as required by law.
• (Optional) Payback phone number (effective October 18, 2026): sending first-payment payback gift cards, confirming eligibility (checking for refunds or account deletion before the payout date), and preventing duplicate payouts.
• Giving ad rewards and preventing duplicate rewards.
• Usage settings (from app version 1.3.0): we use your app language setting to show screens and notifications in that language, your device time zone to calculate daily features such as streaks, daily usage limits, and learning reminder times, and your store account country to decide whether features offered only in Korea (Kakao login, first-payment payback, and so on) are available and to decide which country’s Weekly League you join (it closes at 23:59 on Sunday in that country’s time).
• Translation issue reports (from app version 1.3.0): reviewing and fixing reported translation issues and improving translation quality.
• Sending learning reminder push notifications: if you have not studied yet that day, reminders are sent in set time slots (morning, evening, night), and once you finish studying, no more reminders are sent that day.
• Running social features such as leaderboards and profile cards, handling reports and blocks, and protecting users.
• Usage restriction records (effective October 19, 2026): carrying out suspensions and lifting them under Article 13 of the Terms of Service, informing you of restrictions during a suspension, responding to objections, and checking for repeated violations.
• Responding to errors, statistical analysis to improve the Service, and customer support.
• Measuring ad performance and improving marketing efficiency (from app version 1.2): measuring which ads and channels led to installs, sign-ups, learning, and subscriptions (install source analysis), and passing install and conversion results to ad platforms to improve ad efficiency and show more relevant ads.
• Statistics and scientific research using pseudonymized learning records: to analyze learning effects and improvements in AI skills, we pseudonymize learning records, answers to each question, onboarding survey answers, and similar data so that individuals cannot be identified, and then use them. Under Article 28-2 of the Personal Information Protection Act (PIPA) of Korea (개인정보 보호법), we process this as pseudonymized information without the data subject’s consent. Section 12 describes the items, methods, retention period, and safeguards.
• (Optional) If you agree to take part in further research: where the app offers this consent item, we ask only members who agreed to take part in further research conducted in an identifiable form, such as follow-up surveys and interviews. If you do not agree or withdraw your consent, this does not affect your use of the Service or the pseudonymized processing above.
• Phone number (pre-registration): sending one launch notice (SMS) and confirming eligibility for pre-registration benefits.
• Record of confirming that you are 14 or older: preventing the collection of personal information of children under 14 without the consent of a legal representative, and proving that the confirmation step took place.
• Consent records (app members): confirming and proving that you agreed to the Terms of Service and to the collection and use of personal information, and managing (optional) consent to receive news and offers. You can use the Service without agreeing to optional items.
• (Optional) If you agree to receive marketing: sending news such as launches and events. You can use the Service without agreeing.
• Trial inputs and generated outputs: generating and providing AI trial results and letting you view them (download and share).
• Survey and automatically collected information: statistical analysis to improve the Service, error diagnosis, and preventing abuse (including bot checks).

• Member account data (account information, consent records, onboarding survey, learning records, character images, uploaded face photos, practice outputs, report and block records, usage restriction records (effective October 19, 2026), ad reward records, membership tier (subscription status), install source information, records of viewing event announcement pop-ups (from app version 1.2.2), usage settings (app language, device time zone, store account country, from app version 1.3.0), and so on): when you delete your account, kept for a 14-day grace period and then destroyed. If you sign in again within the grace period, you can restore your account. Consent records (consent to the Terms and to the collection and use of personal information, confirmation that you are 14 or older, and the time of optional consent to receive communications) are kept with your account information and destroyed in the same way. Retention of pseudonymized learning records follows the item below and Section 12.
• Accounts that did not complete the consent step: account information created during sign-in is destroyed 3 days after the account was created. Because no use agreement has been formed, it is deleted without a restore option. If you sign in again before then and complete the consent step, your account and learning records are kept as they are and the member account data rule above applies from then on.
• Where the law requires information to be kept, we keep it separately from other personal information for the required period and then destroy it: records of contracts or withdrawal of offers, 5 years; records of payment and supply of goods, 5 years; records of consumer complaints or dispute handling, 3 years (Act on the Consumer Protection in Electronic Commerce, Etc. (전자상거래 등에서의 소비자보호에 관한 법률)). The payment records in Section 1 are kept separately from other personal information for 5 years from the transaction date (the day a payment, renewal, cancellation, refund, or similar event occurred), including after account deletion, and are then destroyed. Records of app review and test payments (payments in a test environment where no actual charge is made) are destroyed 90 days after the transaction date.
• (Optional) Payback phone number (effective October 18, 2026): destroyed 30 days after the gift card is sent. Numbers that are not eligible or did not receive a payout are also destroyed by January 29, 2027, 30 days after the last payout date (December 30, 2026). Payout records used to prevent duplicate payouts (payout round, payout date, store transaction ID) are kept after the number is destroyed and are destroyed by January 29, 2027. If you delete the number in the app settings, it is deleted immediately, and if you delete your account, the number and payout records are destroyed together with your member account data.
• Friend referral records: when you delete your account, the link between the referral records and your account is removed, and only the pseudonymized identifier (one-way hash) used to prevent abuse such as claiming the same benefit more than once is kept after deletion. Because this value is pseudonymized with a one-way hash, it cannot identify an individual on its own.
• Pseudonymized learning records: learning records pseudonymized under Section 12 may be kept after account deletion within the scope of statistics and scientific research purposes. They are kept until the research purpose is achieved and are destroyed no later than 5 years after the date of pseudonymization. These records do not include information that can identify an individual, such as email, display name, or photos.
• Push tokens: deleted when you sign out and destroyed with your account data when you delete your account. Reminder delivery records (used to prevent duplicate reminders in a time slot, including the delivery result) and notification records (notification title and body) are each deleted automatically after 90 days, and any remaining records are destroyed with your account data when you delete your account.
• Translation issue reports (from app version 1.3.0): destroyed 1 year after the report date. If you delete your account before then, they are destroyed together with the member account data above.
• Automatically collected usage statistics and error and performance information (app): kept according to each processor’s retention policy and then destroyed automatically (usage statistics up to 14 months; error and performance information and screen recordings on errors up to 90 days).
• Behavior analytics records and session screen recordings (from app version 1.1): behavior analytics records are destroyed automatically in the processor’s system 14 months after collection. Session screen recordings are destroyed 1 month after recording, according to the processor’s stated policy.
• Ad performance measurement records (from app version 1.2): events and identifiers sent to the measurement processor and ad platform (Section 6) are kept according to each processor’s retention policy, and when the outsourcing contract ends or you request deletion (Section 7), we ask the processor to delete them. Install source information stored in our database is destroyed together with the member account data above.
• Phone number (pre-registration): destroyed without delay once the period for confirming pre-registration benefits (7 days) has passed after the launch notice SMS is sent (if you agreed to receive marketing, that number is kept until you withdraw consent). It is also destroyed without delay if you cancel your request or withdraw consent, and in any case no later than 1 year after collection. Your consent choices and the record of confirming that you are 14 or older are kept in the same record as the phone number and destroyed with it.
• Trial photo uploads and prompts: not stored on our servers, and deleted without delay from the transmission path once AI generation is finished.
• Trial generated outputs and the lyrics and song titles of the music trial: kept for 48 hours from generation and then destroyed automatically. The lyrics and song title text are deleted in the same cleanup step as the files, and metadata that cannot identify an individual, such as file size, may be kept for statistics.
• Arena nicknames and records: kept until the Arena (leaderboard) is discontinued.
• Survey answers: kept with the trial session identifier for statistical analysis to improve the Service, and destroyed without delay if you request deletion (Section 7).
• Automatically collected information (web): kept for the period set by each processor’s (Section 6) retention policy.

Personal information whose retention period has ended or whose purpose has been achieved is destroyed without delay. Information in electronic files is permanently deleted in a way that cannot be recovered.

• Data of deleted accounts: once the 14-day grace period has passed, an automatic destruction process permanently deletes the database records and storage files (including uploaded face photos, character images, and practice outputs).
• Accounts that did not complete the consent step: 3 days after the account was created, an automatic destruction process permanently deletes the database records and storage files.
• Lyrics and song titles kept with trial generated outputs: once the retention period (48 hours) has passed, the system deletes them automatically (file deletion and text removal).
• Payment records: once the retention period in Section 3 has passed, an automatic destruction process that runs daily permanently deletes the database records.
• Learning reminder delivery records and notification records: after 90 days, an automatic destruction process that runs together with reminder delivery permanently deletes the database records.
• Translation issue reports: 1 year after the report date, an automatic destruction process that runs daily permanently deletes the database records.
• (Optional) Payback phone numbers and payout records (effective October 18, 2026): once the retention period in Section 3 has passed, an automatic destruction process that runs daily permanently deletes the database records. The delivery list file created to send gift cards is deleted when the payout is recorded as complete.

We do not provide your personal information to third parties. However, as described in Section 6 below, we outsource part of the work needed to provide the Service to outside providers, and some of this processing takes place outside Korea.

Time and method of transfer: data is sent over the network when you use each feature (using the app, running a trial, visiting a page, sharing, or watching an ad; from app version 1.1, behavior analytics and screen recording while using the app; from app version 1.2, ad performance measurement at app install and launch, sign-up, lesson completion, subscription screen visit, and purchase; after paid services go on sale, in-app payments; and from app version 1.3.0, checking the store account country when the app is opened while signed in or when you sign in). You can refuse the cross-border transfer of your personal information (contact details in Section 10), and if you refuse, you may not be able to use the related features.

About ads: banner ads may be shown on the app home screen, and rewarded ads on the refill screen can be watched by any member whenever they want, whether or not they subscribe. Ads shown in the app are general, non-personalized ads whether or not you allow app tracking. From app version 1.2, the app tracking permission requested on iOS is used to link ads you saw in other apps and websites with your app install and usage results to measure ad performance and to let the ad platform (Meta) show more relevant ads, and you can use the app in the same way even if you do not allow it (see Section 8).

Contact details of recipients: you can check and contact each provider through its privacy policy page: OpenAI (openai.com/policies/privacy-policy), MiniMax (www.minimax.io), Supabase (supabase.com/privacy), Cloudflare (www.cloudflare.com/privacypolicy), PostHog (posthog.com/privacy), Google (policies.google.com/privacy), Amplitude (amplitude.com/privacy), Functional Software (sentry.io/privacy), RevenueCat (www.revenuecat.com/privacy), AB180 (www.airbridge.io), Meta (www.facebook.com/privacy/policy), 650 Industries (expo.dev/privacy), Kakao (www.kakao.com/policy/privacy).

You may at any time request access to, correction of, deletion of, or suspension of processing of your personal information. Members can edit their profile and delete their account themselves in the app settings, and if you cannot use the app, you can make a request by following the steps on the account deletion page or through the Chief Privacy Officer’s contact details below (Section 10). We act on requests without delay. You have the right to refuse consent, and providing a phone number (pre-registration) is optional: you can use the trial without providing one. However, information pseudonymized under Section 12 and used for statistics and scientific research is excluded from requests for access, correction, deletion, or suspension of processing under Article 28-7 of the Personal Information Protection Act (PIPA) of Korea (개인정보 보호법).

The web service uses cookies and similar technologies (browser local storage) for usage analytics, error diagnosis, and keeping your trial progress. You can refuse cookies or delete stored cookies in your browser settings.

• Chrome: Settings > Privacy and security > Third-party cookies / Delete browsing data
• Safari (iOS): Settings > Safari > Advanced > Block All Cookies / Clear website data
• Edge: Settings > Cookies and site permissions > Manage and delete cookies and site data

If you refuse cookies, visit statistics and error diagnosis information are not collected, and some features, such as keeping your trial progress, may not work. The app does not use cookies, and Sections 1 and 6 describe the items the app collects automatically and how advertising identifiers are handled.

From app version 1.2, we process advertising identifiers to measure ad performance. On iOS, we collect the advertising identifier (IDFA) only if you allow it in the app tracking prompt shown once after sign-up, and on Android, we collect the device advertising ID. You can refuse the collection of advertising identifiers or withdraw your permission at any time as follows.

• iOS: Settings > Privacy & Security > Tracking > turn off Aingo (or turn off “Allow Apps to Request to Track”)
• Android: Settings > Google > Ads > Reset advertising ID or Delete advertising ID

Refusing the collection of advertising identifiers does not limit your use of the Service. If you refuse, advertising identifiers are not collected, and install performance is measured by methods that work without advertising identifiers, such as the method by which Apple reports install results to ad platforms in a form that cannot identify individuals (SKAdNetwork) and the ad platform’s (Meta) Aggregated Event Measurement (AEM). Even in this case, the ad performance measurement items in Section 1 other than the advertising identifier are processed, and on iOS, those items (including your IP address) may be sent to Meta through the measurement processor for Aggregated Event Measurement (effective October 20, 2026). The app tracking setting does not stop this transfer, so if you do not want it, you can request suspension of processing under Section 7.

• Administrative measures: we limit access to personal information to the minimum number of people needed for the work and regularly check how it is processed.
• Technical measures: all connections are encrypted with HTTPS, and the database blocks direct outside access with row-level security (RLS), and data is processed only with server-side privileged keys. IP addresses are pseudonymized with a one-way hash before storage. Original face photos uploaded to create a character are kept in private storage, used only to create the character, and never exposed through public links, and practice outputs are accessed through signed links that are valid only for a limited time so that only you can view them. We remove the original text you entered from error and performance information before sending it, and an automatic deletion process handles data with a retention period.
• Safeguards for pseudonymized information: the additional information used for pseudonymization (the hash key) is kept separately from the pseudonymized information by the person responsible for operations, and we do not create mapping tables that could restore the original state. Access to pseudonymized information is limited to the minimum number of people needed for research analysis, and processing records are created and kept (see Section 12).
• Physical measures: personal information is kept in the data centers of the cloud providers in Section 6, and the physical access control policies of those providers apply.

• In charge: Aingo operations team
• Contact: ysiig78@gmail.com

In the app, you can also submit privacy inquiries through Contact support (Help > Contact support).

To seek a remedy for an infringement of your personal information, you can apply to the organizations below for dispute resolution or counseling.

• Personal Information Dispute Mediation Committee (개인정보 분쟁조정위원회): 1833-6972 (www.kopico.go.kr)
• Personal Information Infringement Report Center, Korea Internet & Security Agency (개인정보 침해신고센터, 한국인터넷진흥원): 118 (privacy.kisa.or.kr)
• Cyber Investigation Division, Supreme Prosecutors’ Office (대검찰청 사이버수사과): 1301 (www.spo.go.kr)
• Cyber Crime Reporting System, Korean National Police Agency (경찰청 사이버범죄 신고시스템): 182 (ecrm.police.go.kr)

A person whose rights or interests are infringed by a disposition or omission of the head of a public institution regarding a request under Article 35 (access to personal information), Article 36 (correction and deletion), or Article 37 (suspension of processing, etc.) of the Personal Information Protection Act (PIPA) of Korea (개인정보 보호법) may file an administrative appeal as provided by the Administrative Appeals Act (행정심판법).

We process pseudonymized information as follows under Article 28-2 of the Personal Information Protection Act (PIPA) of Korea (개인정보 보호법).

• Purpose: statistics and scientific research (such as analyzing learning effects and improvements in AI skills).
• Items: learning records (including answers to each question and answer dates), onboarding survey answers, sign-up date, birth-year range (if you entered a date of birth), gender (if entered), membership tier, and so on. Information that can identify an individual, such as email, display name, and photos, is excluded.
• Method: we replace your internal member ID with a one-way hash value, keep only a 5-year birth-year range from your date of birth, and merge small groups with other groups so that no specific individual can be identified without additional information.
• Retention period: kept until the research purpose is achieved, and destroyed no later than 5 years after the date of pseudonymization. It may be kept for this period after account deletion (see Section 3).
• Provision to third parties: we do not provide pseudonymized information to third parties. Research results are published only as statistics and figures that cannot identify individuals.
• Safeguards: the additional information (hash key) is kept separately from the pseudonymized information by the person responsible for operations, and we do not create mapping tables that could restore the original state. Access to pseudonymized information is kept to a minimum, and processing records are created and kept. We do not process pseudonymized information to identify a specific individual, and if information that can identify an individual is created during processing, we stop processing immediately and retrieve and destroy that information.

If anything in this Policy is added, deleted, or changed, we will post the changes and the effective date on this page. However, changes that significantly affect your rights, such as collecting more items, adding purposes of use, or newly providing information to third parties or outsourcing processing, will be posted 30 days before the effective date.

Revision history: the September 28, 2026 revision newly adds the processing of pseudonymized information (Section 12), the purposes of statistics and scientific research, the retention period of pseudonymized learning records, the explicit listing of answers to each question, and information about optional consent (taking part in further research). It also includes the revision on the behavior analytics processor (Amplitude) that was posted on September 14, 2026 and was scheduled to take effect on October 14, 2026, and it takes effect on its posting date, September 28, 2026.

The October 8, 2026 revision reflects the storage of payment records for paid services (Section 1), their separate retention for 5 years from the transaction date and the destruction of test payment records (Section 3), and the explicit statement that pre-registration phone numbers are also used to confirm benefit eligibility, with that confirmation period (7 days) (Sections 2 and 3), and takes effect on its posting date, October 8, 2026. Payment records are information processed to perform paid service contracts and to keep transaction records as required by law. The collection, purposes of use, retention period, and destruction of the (optional) payback phone number for the first-payment payback event and the outsourcing of gift card delivery, added in the same revision, were scheduled to take effect on November 8, 2026 after 30 days’ notice, but the October 16, 2026 revision moved that date forward to October 18, 2026 (see the supplementary provision below).

The October 9, 2026 revision states explicitly in behavior analytics (Section 1) and in the items sent to analytics processors (Section 6) the category values used to compare usage flows between groups (the kind of work and AI experience level derived from the sign-up survey, the screen theme group based on date of birth, membership tier, Weekly League tier, streak range, and whether you signed up through an invite link) and the random device identifier created when the app is installed. Original survey answers and the date of birth itself are not sent. These items make more specific the behavior analytics transfer that begins with app version 1.1; the revision is posted before that transfer begins and takes effect on its posting date, October 9, 2026.

The October 15, 2026 revision states that learning reminder delivery records include the delivery result (success or failure) (Section 1), sets the retention period of those records to 90 days, the same as notification records, so that they are deleted automatically after that period (Sections 3 and 4), and takes effect on its posting date, October 15, 2026. The delivery result is a record of whether a notification we sent was delivered, not information newly collected from you, and this change newly sets and shortens a retention period, so it takes effect on the posting date.

The October 16, 2026 revision, in line with the release of app version 1.2, changes the date of birth at sign-up from required to optional and states that being 14 or older is checked through a confirmation step (Sections 1 and 12); reflects the ad performance measurement that begins with app version 1.2 (the collection of advertising identifiers, device identifiers, install source information, and measurement events, and their purposes and retention period), the transfer to the ad performance measurement processor (AB180 Inc., stored on servers in Japan) and to the ad platform (Meta Platforms, Inc.), and how to refuse app tracking and the collection of advertising identifiers (Sections 1, 2, 3, 6, and 8); and takes effect on its posting date, October 16, 2026.

On October 16, 2026, we also post a revision that moves the effective date of the collection and use of the (optional) payback phone number for the first-payment payback event and the outsourcing of gift card delivery forward from the original November 8, 2026 to October 18, 2026. This is so that new users who came through ads can apply for the payback right after their first payment, and we were not able to give the 30 days’ notice in Section 13 for this change. Registering a payback phone number is optional, and we accept registrations from October 18, 2026.

The October 19, 2026 revision states the collection items (Section 1), purposes of use (Section 2), and retention period (Section 3; kept with member account data and destroyed after the grace period when the account is deleted) of the usage restriction records (reason, period, reason for lifting, and time of each action) stored when we suspend or lift the suspension of a member account under Article 13 of the Terms of Service, and takes effect on its posting date, October 19, 2026. Usage restriction records are records of carrying out measures against members who violate the Terms, not information newly entered by users, and members subject to a measure are told the restriction period in the app, so the 30 days’ notice in Section 13 does not apply to this change.

The October 20, 2026 revision states that on iOS, even if you do not allow app tracking, the ad performance measurement items (excluding the advertising identifier, including your IP address) may be sent to Meta through the ad performance measurement processor for the ad platform’s (Meta) Aggregated Event Measurement (AEM) (Sections 1, 6, and 8), and takes effect on its posting date, October 20, 2026. We were not able to give the 30 days’ notice in Section 13 for this change.

The October 21, 2026 revision, to compare the usage flows of users who installed through ads with those of other users, adds to the category values for comparing groups in behavior analytics the category value for how you heard about the Service chosen in the sign-up survey and the install channel identified through ad performance measurement, and states that these are sent to analytics processors (Google, Amplitude) (Sections 1 and 6), and takes effect on its posting date, October 21, 2026. Original survey answers and the campaign and ad creative names in the install source information are not sent. We were not able to give the 30 days’ notice in Section 13 for this change.

The October 27, 2026 revision, because app version 1.2.2 removes the notifications screen and moves the notification on/off setting to the My Info screen, corrects how to turn off push notifications and the purpose of storing notification titles and bodies (showing them on the notifications screen of earlier app versions); reflects that from app version 1.2.2 the date of birth is again required at sign-up (Section 1); states that from app version 1.2.2 records of viewing event announcement pop-ups (time viewed, number of views, button tapped) are stored and destroyed with account data when the account is deleted (Sections 1 and 3); states that payback payout records include the store transaction ID that we already receive as part of payment records (Sections 1 and 3); and takes effect on its posting date, October 27, 2026. The collection items and retention periods do not change.

The second October 27, 2026 revision adds that in Prompt Practice, newly introduced in app version 1.2.2 (an activity where you write a prompt for a given situation, receive an AI output, and check your score), the prompt you enter and the AI output and score are stored as learning records and sent to OpenAI to generate and grade outputs (Sections 1 and 6), and takes effect on its posting date, October 27, 2026. The retention period does not change (these records are also destroyed when the account is deleted, like other learning records). We were not able to give the 30 days’ notice in Section 13 for this change.

The October 28, 2026 revision, in line with English support and the overseas release in app version 1.3.0, reflects the storage of the app language setting, device time zone, and store account country (usage settings) and their purposes of use (showing screens and notifications in your language, calculating daily features, and deciding whether features offered only in Korea are available and which country’s Weekly League you join), checking the store account country of signed-in members through the payment processor (RevenueCat), storing the display language with answers to each question, the storage and retention period (1 year from the report date) of translation issue reports, and sending the app language setting and store account country to analytics processors (Google, Amplitude) (Sections 1, 2, 3, 4, and 6), and takes effect on its posting date, October 28, 2026. We were not able to give the 30 days’ notice in Section 13 for this change.

Supplementary provision: matters concerning the collection and use of the (optional) payback phone number and the outsourcing of gift card delivery take effect on October 18, 2026 (moved forward from the original November 8, 2026 by the October 16, 2026 revision).