Gomgom Privacy Policy

1. A guardian-operated app

Gomgom is a learning tool whose account is created and operated by a parent or guardian aged 18 or older and used together with elementary and middle-school children. Children do not sign up or pay. Only the guardian creates and enters child profiles (nickname and grade), and a child’s learning activity, including entering writing, photos or speech, takes place in the guardian-operated account under the guardian’s supervision. Guardians manage child profiles and learning records and review AI responses together. A parent-managed account does not change the fact that a child’s writing, photos and voice are child data.

Guardian confirmation during onboarding is separate from permission to send information to OpenAI. The signed-out first experience uses built-in content and does not send input to AI. Use a nickname instead of a child’s legal name, and avoid unnecessary identifying details such as addresses, contact details and school names in writing, photos and speech.

2. Information and its purposes

• Guardian account: email address, account identifier, display name and basic profile details supplied by the selected sign-in service (Google, Apple, Kakao or Naver) are used for authentication and account management. The app currently does not offer email/password sign-up.
• Guardian consent verification: guardian name, confirmed account email, parent/legal-guardian relationship, notice version, a signed and dated PDF/PNG/JPEG form (up to 5 MiB), submission/review/revocation times and reviewer records are used to verify consent. Do not include a child’s legal name, photo, birth date or identity document. A separate reviewer must check the original and reject missing or unverifiable information. Software does not automatically authenticate identity or legal guardianship.
• Child profile: the nickname and school grade entered by the guardian, and the profile’s connection to the guardian account, are used for grade-appropriate content and keeping children’s records separate. We do not collect a child’s legal name, date of birth or contact details.
• Learning records: passage identifiers, reading progress and time, thoughts, essays, drafts, transcribed text, chat and debate text, AI replies, quiz answers and results, and creation times support learning continuity and guardian review. These records may be linked to an account and child profile.
• AI consent: adult guardian confirmation, consent version and time, text/image/audio purposes, and withdrawal time are recorded.
• Notifications: learning reminders run as on-device notifications. In versions before 3.13.1, we processed the guardian’s phone number and notification preferences when the guardian enabled AlimTalk, and device push tokens when remote push was used. Version 3.13.1 and later do not send AlimTalk messages or use remote push.
• Subscriptions: store product and transaction identifiers, verification receipts or tokens, subscription status and expiry support purchase verification and restoration of existing subscriptions. For web payments through PayApp, the order number, account identifier, amount, payment status and PayApp payment number are used to confirm payment and grant the access period. Card and other payment-method details are handled by the store or PayApp; we do not receive them.
• Diagnostics and usage: where configured, device, OS and app details, error and performance information, screen/feature events and associated account or learning identifiers support stability and service improvement. We do not describe all of this information as anonymous.

3. Device storage and account sync

From version 3.13.1, trials and learning records are stored on the device first. Sign-in or a checkbox alone does not permit uploading child records. Supported Supabase synchronization and record access require a separate administrator to review and approve a signed consent form linked to a confirmed guardian email. Failed verification, revocation, expiry or a changed account email blocks transmission. Device records remain available. Older installed versions may still send requests differently; please update to the latest version.

Original handwriting photos that you take or select are kept in the app’s device storage. The current app does not upload originals to Supabase Storage. Requesting AI transcription includes the image in a processing request: local storage does not mean the image never leaves the device. Transcribed text and learning results may be saved as learning records.

4. Optional sharing with OpenAI

When AI processing becomes available, a signed-in guardian must confirm they are at least 18 and separately agree after reviewing the text, image and audio information and purposes. Each selected feature uses the information it needs.

• Text and conversation: entered thoughts and essays, relevant recent writing and conversations for the selected child, the passage being read, school grade and nickname context where needed may be used for questions, feedback, quizzes and debate responses. Requests may include an account-linked safety identifier.
• Photos: selected handwriting images pass through our processing server to OpenAI when transcription is requested. We do not guarantee automatic, complete anonymization of names, faces or contact details within an image.
• Voice: starting real-time voice sends microphone audio and conversation context to OpenAI Realtime. A supported fallback uses on-device speech recognition and sends recognized text and the reply to be spoken for AI processing. The app does not save original conversation audio as a learning-record file, but transcripts and conversation text may be saved.

You can withdraw sharing consent in Account → Guardian AI settings. Withdrawal blocks subsequent AI requests; it does not automatically erase saved learning records or requests already processed.

Text generation requests use store:false. This limits response storage; it does not establish approved Zero Data Retention (ZDR). Retention depends on project controls and API/feature exceptions. We do not claim that ZDR activation has been verified for this service.

AI can produce incorrect or unsuitable responses. A guardian should review the content with the child. Spoken replies use synthetic speech, not a live person.

5. External services

These services process information when the relevant feature is configured and used. Processing locations and retention depend on provider infrastructure, settings and policies and may be outside your country.

Version 3.13.1 and later (including the current 3.14.1) disable the Firebase Analytics, Sentry and Cloud Messaging SDKs, and server-side AlimTalk delivery is disabled. This change does not retroactively erase information processed by older versions or store transaction records.

6. Retention, deletion and choices

Original consent forms are deleted immediately after approval, rejection or revocation; failed deletions are retried hourly. Unsubmitted drafts become eligible for deletion after 24 hours and pending requests after 30 days. Approved consent expires after one year, blocks access and is deleted. Rejected/revoked records are retained for 30 days, audit records for 365 days and reviewer document-access records for one hour. Scheduled execution and service failures can delay deletion. Revoking consent does not erase learning records already stored; use account deletion or contact us for deletion.

Device records support continuing a lesson; synced records support account history. You can manage records where individual deletion is offered or use Delete Account in the account screen.

After a successful server account-deletion request, the authentication account and database records configured for cascading deletion are removed. The app also clears learning caches, drafts and the handwriting-image folder on that device. Network or device-storage errors may prevent some steps from completing. Contact us to confirm deletion or request assistance with particular records.

Security or diagnostic logs, backups and payment-provider transaction records, where retained, follow the relevant provider’s retention and deletion processes. Deleting an app account does not cancel a store subscription. Manage subscriptions separately through the applicable store.

Disabling AlimTalk removes the phone number from the device and requests removal of the server-side number and notification preference. AI sharing consent, notifications and account deletion are separate choices.

7. Access, correction and deletion requests

Guardians can edit account and child-profile details and request access, correction, deletion or suspension of processing. Contact us if a child’s information appears linked to the wrong profile or processed without guardian consent. We will check the requester’s connection to the account and explain the scope and progress of the request.

Privacy and app support: contact@lionandthelab.com

8. Changes

We update the revision date when this page changes. If a change in shared information or purposes requires new consent, the app will explain it. Reading this policy or continuing to use the app does not itself grant permission to send data to OpenAI.

• October 15, 2026: clarified that accounts are created and operated by guardians aged 18 or older; listed sign-in providers (Google, Apple, Kakao, Naver), web payment (PayApp) data, the current pause of AI features and new purchases, and the status of notifications.
• October 6, 2026: added signed guardian consent review, upload restrictions, revocation, retention periods and disabled analytics/notifications in the latest release.
• October 4, 2026: updated guardian-led learning, linked child records, separate OpenAI consent and current processing restriction, external services and deletion procedures.
• February 14, 2026: initial version.