Privacy Policy

1. Information and purposes

• Accounts: Firebase UID, email/display name/nickname, provider, account status, signup/login times and counts, device model, OS/app version, language and region settings support membership, synchronization and abuse prevention. Methods depend on the login screen, including Google/Apple; iOS email/password authentication is handled by Firebase Authentication. We do not receive your social-account password.
• Reading/study: library/downloaded books, position, time and progress, vocabulary/quizzes, study plans/rewards/usage counts, notes and preferences are stored on-device or with your account as required by the feature.
• Purchases: product identifiers, purchase/renewal/expiry state, receipts or purchase tokens, transaction identifiers, points and spending/reward records support access checks, restoration and accounting. The store handles payment details such as card numbers.
• Notifications: FCM/APNs device tokens, installation information, notification preferences and reading-reminder/announcement records support delivery.
• Support/operations: email, message and attachments, reports, blocks and handling records support service safety and dispute handling. Web login counts may be stored separately from app login counts in the shared profile.

Country information derived from language/region or network information is different from GPS. Phone numbers, Kakao/Facebook use and GPS are not mandatory data for every member. We process necessary data on an applicable legal basis, such as service performance, and separately notify/obtain consent where required.

2. Recordings, speech, AI and sharing

Recordings: with microphone permission, reading practice may store voice files, duration and book/sentence references locally. Attaching a recording to a SpoonNote post/share can upload it and associated information to server storage for the relevant audience. Not every recording stays only on your device.

Speech input/default TTS: Android’s selected recognition provider and Apple/iOS speech services may process audio or reading text online depending on the device, language and engine.

AI: selected passages/book context, your question, prompt and conversational context are sent through the server to OpenAI APIs for answers/images. Request/response identifiers, errors, usage/point records and saved/registered outputs can remain on-device or on servers. Do not submit sensitive information or others’ personal data. You need not submit or share this data when you do not use the optional feature.

Sharing: SpoonNote, book comments and shared text/images/audio may display your nickname, post, related book, reactions and comments. Public sharing differs from private notes; others may view or retain published material.

3. Analytics, diagnostics and advertising

Google Analytics for Firebase processes events such as signup, preview use, vocabulary additions, quizzes, purchases and study plans, with book/product references and app/device/installation information. Crashlytics processes crashes, traces, diagnostics and installation information. On iOS, a signed-in UID may be associated with analytics and crash reports.

Where ads are shown, Google AdMob may process IP addresses, ad/app interactions, diagnostics and device/advertising identifiers for delivery, measurement and fraud prevention. Scope depends on SDK, permissions, consent and platform settings. We do not describe the mobile app as having no advertising or analytics tracking.

Manage microphone, speech and notification permissions and advertising/tracking choices in device settings. Limiting ad personalization does not stop every ad or diagnostic request. We do not promise an in-app switch for all analytics; contact support for further requests.

4. Providers and international processing

• Google LLC: Firebase authentication, Firestore, Storage, Functions, Messaging and Crashlytics, plus Google Analytics and AdMob provide the relevant authentication, storage, delivery, operations, analytics and advertising. Firebase Authentication processes in the US. Our shared Firestore is currently in Seoul (asia-northeast3); content/upload Storage is in the US (US-CENTRAL1). Global networks, SDKs and operations may process data abroad.
• OpenAI: optional AI prompts, context and results are processed through APIs in the US and other provider processing environments. Retention depends on API, settings and security policies; immediate deletion or zero retention is not promised.
• Apple/selected device services: Apple login, App Store, APNs and speech services process relevant account/transaction/device-token or audio/text information. Google Play and the selected Android speech provider have their own applicable policies.

Transfers occur through encrypted network requests when using authentication, synchronization, uploads, AI or SDK functions. Categories/purposes are described above; retention follows the criteria below and provider settings. Necessary international outsourcing/storage and other transfers must meet applicable requirements, including Korea’s PIPA Article 28-8, with separate consent where required. Contact support to object or inquire; essential account services may be unavailable if authentication cannot be processed, while optional features can be avoided.

Provider details/contact: Firebase, Google, OpenAI, Apple. We do not sell or disclose personal information to unrelated third parties without a lawful basis.

5. Retention, deletion and local files

Account, reading, learning and entitlement data are managed for service provision and handled on withdrawal/deletion requests subject to legal retention. Support/reports are kept as needed for their purpose or disputes. Where applicable records are held and statutory duties apply, Korean rules specify five years for contract/payment records, three for consumer complaints/disputes and six months for advertising records.

There is no single automatic deletion period for all public posts, uploaded recordings/images and AI-related records. Deleting authentication does not automatically erase them or every child record. Identify the desired deletion scope. Current iOS withdrawal includes authentication deletion and profile deactivation; remaining profile/shared data requires separate review.

Firebase states authentication removal from active/backup systems may take up to 180 days after deletion is initiated; Crashlytics starts clearing relevant diagnostics after 90 days. Other SDK/AI retention follows applicable provider policies/settings.

Downloaded books/covers/audio, imported EPUB files, local notes/recordings, preferences and authentication storage may remain on-device. Use applicable cleanup/deletion functions and OS app-data removal. Withdrawal/sign-out does not delete exported files, separate backups or copies held by others. Data selected for destruction is handled to prevent restoration; legally retained records are distinguished.

6. Your requests and optional permissions

Request access, correction, deletion, suspension, consent withdrawal or account deletion through offered app functions or email. Provide your account, scope and reply address. After proportionate identity checks we explain the result or lawful limitations. Do not send passwords or verification codes. Consider shared app/web records and separately managed store subscriptions.

Microphone, speech, notifications and file/photo selection are requested for relevant features. Refusing can limit those features, not imply that unrelated permissions are required for ordinary reading. Where guardian consent is required, including consent-based processing for children under 14 under Korean law, a lawful process is necessary; contact support before signup if that process is unavailable.

7. Safeguards, contact and changes

We apply authentication, access restrictions and HTTPS protections. SRP content encryption is not a statement that every personal record uses the same encryption or a guarantee against incidents.

Controller: Veritas Lux Mea (VLM). Privacy officer: HyeonJoon Yoon (VLM representative). Contact the email below. You may also seek help from the KISA Privacy Infringement Center or Personal Information Dispute Mediation Committee.

We announce changes/dates on policy pages or in the app and follow any separately required notice/consent process. See the web Privacy Policy (Korean) for web-specific processing.