Privacy Policy
v1.9 | Effective: September 29, 2026
Exydos ("Company," "we," "us," or "our") provides this Privacy Policy to describe how we collect, use, disclose, and otherwise process personal information in connection with our multilingual language learning application DAYWIKA (the "Service"), and to explain the rights and choices available to individuals with respect to their personal information.
1. Information We Collect
1-1. Information You Provide
| Category | Specific Data | Source | Purpose |
|---|---|---|---|
| Account Information | Email address, name (nickname), profile picture URL | Google/Apple social login | Account creation, authentication |
| Login Method | Google or Apple identifier | Automatically recorded at login | Authentication processing |
| Device Platform | iOS or Android | Automatically detected | Service compatibility |
| Country Code | App Store / Play Store region | App Store / Play Store | Region identification |
| Year of Birth | Year only (month and day are not collected) | User input during onboarding | Age verification and age gating (all users); limited first-party internal statistics (minors excluded). Not used for advertising, third-party sharing, or tracking |
| Age Verification (is_adult) | Whether the user meets our minimum age requirement (derived from year of birth) | Derived at registration | Age restriction compliance |
1-2. Information Collected Automatically
| Category | Specific Data | Purpose |
|---|---|---|
| Device Information | OS version, device model, screen resolution, app version | Service compatibility, usage analytics |
| Learning Data | Vocabulary lists, quiz records, review schedules, memorization status, correct/incorrect history | Core service delivery |
| Character Learning Progress | Completed stages, current position, challenge mode records | Learning continuity |
| Learning Statistics | Streak count, experience points (XP), daily completion status, session records | Growth analysis |
| Learning Settings | Daily learning volume, learning mode, notification settings | Personalization |
| Subscription Status | Free/paid tier, store type | Premium feature access |
| Error Logs | Error content, email, nickname (only upon error occurrence) | App stability improvement |
| IP Address | Automatically collected upon server connection | Security, access log recording |
| Android Advertising Measurement Data | Google Play Install Referrer, onboarding-completion and first-meaningful-learning completion status, app/device/network context, and GAID only where the user is age 14 or older and has opted in to analytics | Install attribution, advertising measurement, and ad-delivery optimization |
| Android Advertising Conversion Data | Eligible trial start, first paid subscription, and first lifetime purchase status. Payment-card details processed directly by the app store are not included | Trial and paid-conversion measurement by campaign |
| iOS Aggregate Advertising Attribution Data | Conversion values, source/campaign-related values, and postback verification data provided by Apple through SKAdNetwork or AdAttributionKit. The Meta advertising path does not include IDFA, IDFV, fbAnonId, or a DAYWIKA account identifier | Aggregate campaign measurement, signature validation, and duplicate prevention without person-level attribution |
| Personalized Example Generation Data | Pseudonymous account identifier, learning language, target-word identifier, candidate words with spelling, reading and meaning, generated examples and audio | Example generation and validation, speech synthesis, request-volume management |
1-3. Automatic Collection of IP Addresses
We automatically collect your IP address when you access our Service. IP addresses are used for approximate geolocation, security monitoring, access log recording, and analytics purposes. We do not use IP addresses to determine precise geolocation.
1-4. Information We Do NOT Collect
We do not collect: location data (GPS), contacts, photos, camera access, or passwords.
Advertising Identifiers: We do not collect any advertising identifier on iOS (no IDFA, and no App Tracking Transparency prompt). On Android, we collect the Google Advertising ID (GAID) only from users aged 14 or older who have opted in to analytics. See Section 9 for details. We never collect advertising identifiers from users under 14.
1-5. Information Collected During Customer Support
Email correspondence to [email protected] may result in collection of your email address and support content (including text and images).
When you send in-app feedback or report a word in the app, we collect the message or report content, the reported word or example, the app version, your device operating system and version, and, if you are signed in, your account email and account identifier. You may optionally enter an email address for our reply; we collect it only if you enter it and use it only to respond to that inquiry.
2. How We Use Your Information
We use personal information for the following purposes:
- Account Management: Identity verification, fraud prevention, account administration
- Service Delivery: Language learning features, data synchronization, AI-powered learning optimization
- Paid Services: Subscription status verification, premium feature access, payment/refund processing
- Service Improvement: Error detection and stability, usage analytics, new feature development
- Notifications: Push notifications including learning reminders and streak maintenance alerts
- Usage Analysis: First-party analysis of service usage patterns and acquisition channels to improve the Service
- Advertising Measurement: On Android, measuring advertising results for installs, onboarding completion, first meaningful learning, eligible trial starts, and first paid conversions; on iOS, analyzing campaign performance using aggregate attribution information provided through Apple
3. How We Share Your Information
We do not sell your personal information. We share personal information only in the following circumstances:
3-1. Service Providers and Advertising Measurement Partners
| Provider | Location | Data Shared | Purpose |
|---|---|---|---|
| Supabase, Inc. | United States | Account information (including year of birth), all learning data | Cloud data sync and backup |
| Functional Software, Inc. (Sentry) | United States | Error content, email, nickname | App error monitoring |
| RevenueCat, Inc. | United States | Subscription status and payment platform; on Android, eligible trial start, first paid subscription, and first lifetime purchase status | Subscription management and Android advertising-conversion delivery. RevenueCat-to-Meta delivery is not used on iOS |
| Amplitude, Inc. | United States | Usage event data, device information, advertising identifier (Android GAID, with analytics consent only), IP address | First-party app usage analytics |
| Meta Platforms, Inc. and the applicable Meta affiliate | United States, Ireland, and other locations identified by Meta for applicable processing | On Android: GAID with analytics consent, advertising-acquisition information, onboarding-completion and first-meaningful-learning completion status, eligible trial start, first paid subscription and first lifetime purchase status, and app/device/network context | Advertising attribution, measurement, delivery optimization, and related advertising functions. No iOS identifiers or RevenueCat-to-Meta events are included in this path |
| Apple Inc. (SKAdNetwork / AdAttributionKit) | United States and other locations identified by Apple | Aggregate attribution conversion values and postback verification metadata without IDFA or a DAYWIKA account identifier | Privacy-preserving aggregate iOS advertising measurement |
| PowerSync (JourneyApps) | United States | Learning data (for offline sync) | Offline-first data synchronization |
| Cloudflare, Inc. | United States | IP address, access logs | Website hosting and CDN |
| Google LLC (Google Cloud) | United States | Pseudonymous account identifier, learning language, target-word identifier, candidate-word spelling, reading and meaning, generated examples | Personalized example generation and validation, task processing, speech synthesis |
| Backblaze, Inc. | United States | Generated audio files and non-identifying content identifiers | Example-audio storage and delivery |
| Plus Five Five, Inc. (Resend) | United States | In-app feedback and word-report content, reported word or example, app version, device OS and version, account email and account identifier if signed in, and the reply email address if you enter one | Delivering in-app feedback and word reports to our support mailbox |
We require service providers to process personal information only for the specified purposes and to apply appropriate safeguards. Advertising partners may act as service providers, contractors, or independent businesses depending on the processing purpose and applicable law. Where consent or an opt-out is required, we provide the corresponding choice as described below.
3-2. Authentication Partners
| Provider | Data Shared | Purpose |
|---|---|---|
| Google LLC | Email, name, profile picture | Social login authentication |
| Apple Inc. | Email, name, profile picture | Social login authentication |
3-3. Other Disclosures
We may also disclose personal information when required by law, to protect our rights or safety, or in connection with a merger, acquisition, or sale of assets.
4. Data Retention
We retain personal information for the periods described below, after which data is deleted or anonymized. Retention periods vary by data category to reflect differing legal requirements and business purposes.
Unless a row expressly names an external recipient, the period below describes DAYWIKA-controlled retention. The Meta row describes retention under Meta's own Business Tools terms and controls, not a period that DAYWIKA can unilaterally shorten.
| Data Category | Retention Period | Basis |
|---|---|---|
| Account Information (email, name, profile) | Retained while account is active; deleted upon account deletion | Service agreement |
| Learning Data (vocabulary, quiz records, progress, statistics) | Retained while account is active; deleted upon account deletion | Core service delivery |
| Shared Generated Examples and Audio | The creator-account link is removed upon account deletion; de-identified content may remain while it is provided as shared learning content | Reusable shared learning content |
| Year of Birth | Retained while account is active; deleted upon account deletion | Age verification; service agreement |
| Analytics Data (Amplitude) | 12 months from collection | Amplitude default retention policy; service improvement |
| Error Logs (Sentry) | 90 days from collection | App stability monitoring |
| Subscription/Payment Records | 5 years after subscription end | Tax law compliance and financial record-keeping requirements |
| Advertising Identifier (Android GAID) | Up to 12 months in DAYWIKA analytics systems, subject to earlier consent withdrawal and applicable provider controls | Usage analytics and Android advertising measurement |
| Android Raw Advertising-Delivery Records | Up to 180 days from collection, or until the purpose is completed after consent withdrawal, whichever occurs first | Delivery verification, duplicate prevention, and dispute handling |
| Event Data Received by Meta | Up to two years under the Meta Business Tools Terms, subject to applicable account controls and law | Advertising measurement and delivery optimization |
| Raw Apple Attribution Postbacks | Up to 180 days from receipt | Signature validation, duplicate prevention, and advertising-performance verification |
| Advertising Statistics Not Joined to Person-Level Identifiers | Up to 24 months from creation | Period-over-period campaign analysis |
| Customer Support Records | 1 year after resolution of inquiry | Service quality and dispute resolution |
5. Data Deletion
When you delete your account (via Settings > Account Management > Delete Account):
- Supabase: All account and learning data deleted
- RevenueCat: Anonymized (subscription itself managed by Apple/Google)
- Device: Local database, internal storage, and authentication tokens all deleted
- Sentry: Automatically deleted within 90 days (immediate deletion not possible)
- Advertising Delivery Records and Apple Postbacks: Deleted when the retention periods in Section 4 expire, unless a longer period is legally required
- Meta Event Data: Subject to deletion/withdrawal signals available to us and Meta's applicable policies; campaign statistics that are not joined to account information may remain for the aggregate-retention period in Section 4
Electronic records are permanently deleted in a manner that prevents recovery or reconstruction.
6. AI-Powered Automated Processing
Our Service uses the following automated systems to enhance your learning experience:
| System | Function | Description |
|---|---|---|
| AI Operations System | Daily learning volume adjustment | Analyzes learning history and workload to calculate optimal daily volume |
| AI Operations System | Review ratio optimization | Automatically balances new learning and review |
| FSRS Algorithm | Review schedule calculation | Determines optimal review timing based on memory strength |
| MMR System | Adaptive difficulty adjustment | Adjusts quiz difficulty based on accuracy and response patterns |
| AI Operations System | Learning mode recommendation | Recommends optimal learning modes based on user context |
| Google Vertex AI (Gemini) and Cloud TTS | Personalized example and audio generation | Generates and validates examples from the learning language and learned-word candidates, then synthesizes speech |
You may disable automated learning optimization in Settings > Learning Settings and switch to manual configuration at any time. Disabling automated features will not restrict your access to the Service, though learning optimization effectiveness may be reduced.
If you wish to raise an objection regarding automated processing, contact [email protected]. We will review your objection within 15 days.
7. Children's Privacy (COPPA Compliance)
Our Service is not directed to children under 13 (as defined by the Children's Online Privacy Protection Act, "COPPA") or under 14 (as required by Korean law, the Personal Information Protection Act). We apply the more restrictive age limit of 14 to all users worldwide. We do not knowingly collect personal information from children under 13 in compliance with COPPA, or under 14 in compliance with Korean law.
7-1. Age Verification
During registration, users are required to enter their year of birth. We store the year of birth (month and day are not collected) and derive from it whether the user meets our minimum age requirement (is_adult flag). The year of birth is used for age gating (all users) and limited first-party internal statistics (minors are excluded); it is not used for advertising, third-party sharing, or tracking. This threshold exceeds the COPPA requirement of age 13, providing additional protection for minors aged 13.
7-2. Multi-Layered Protection for Minors
If a user is determined to be under 14, the following measures are applied:
- Registration Blocked: The registration screen displays an age restriction notice and halts the sign-up process.
- Data Anonymization: If any data is inadvertently generated, it is anonymized.
- Analytics and Advertising-Measurement Exclusion: The user is excluded from Amplitude analytics, Meta App Events, GAID collection, and optional advertising-attribution events.
- No Ad Identifier Collection: No advertising identifier is collected (and on iOS no ATT prompt is shown).
- Payment Blocking: Access to in-app purchases (subscriptions) is blocked.
7-3. Post-Discovery Response
If we become aware that we have collected personal information from a child under 13 (COPPA) or under 14 (Korean law) without proper verification, we will promptly delete that information and the associated account. If you believe a child under 13 or under 14 has provided us with personal information, please contact us at [email protected].
8. Your Privacy Rights
8-1. Rights for All Users
All users may:
- Access their personal information via Settings > Account Management
- Request correction of inaccurate information
- Delete their account and all associated data
- Object to automated processing (see Section 6)
- Contact us at [email protected] for any privacy-related request
- Request a portable copy of their personal information
We will respond to all privacy requests within 10 business days.
While a correction or deletion request is being processed, we will suspend use of the relevant personal information until the request is resolved.
8-2. California Residents (CCPA/CPRA)
To the extent the California Consumer Privacy Act, as amended by the California Privacy Rights Act ("CCPA/CPRA"), applies to the Company or the relevant processing, California residents have the following rights. We may also honor equivalent requests voluntarily where the statute does not apply:
- Right to Know: You may request the categories and specific pieces of personal information we have collected about you.
- Right to Delete: You may request deletion of your personal information.
- Right to Correct: You have the right to request correction of inaccurate personal information that we maintain about you.
- Right to Opt-Out of Sale/Sharing: Where applicable, you may opt out of covered sharing or targeted-advertising processing as described in Section 8-3 below.
- Right to Limit Use of Sensitive Personal Information: We do not collect sensitive personal information as defined under the CPRA (see Section 8-5).
- Right to Non-Discrimination: We will not discriminate against you for exercising any of your CCPA/CPRA rights.
Categories of Personal Information Collected (Past 12 Months)
The following table describes the categories of personal information we have collected within the preceding twelve (12) months, mapped to the statutory categories defined by the CCPA (Cal. Civ. Code § 1798.140(v)):
| CCPA Statutory Category | Specific Data Elements Collected | Source | Business Purpose | Shared for Cross-Context Behavioral Advertising | Sold |
|---|---|---|---|---|---|
| A. Identifiers | Name (nickname), email address, device identifiers (device model, OS version), IP address, advertising identifier (Android GAID, with analytics consent only; not collected on iOS) | User-provided (social login); automatically collected | Account management, authentication, analytics, security, and Android advertising measurement | Potentially for Android Meta measurement; see Section 8-3 | No |
| B. Personal Information (Cal. Civ. Code § 1798.80(e)) | Name, email address | User-provided (social login) | Account management | No | No |
| F. Internet or Other Electronic Network Activity | App usage data, learning interaction history, session data, browsing/search activity within the app, error logs, app version | Automatically collected | Service delivery, service improvement, error monitoring, and limited Android advertising measurement | Potentially for the limited Android events described in Sections 1 and 9 | No |
| G. Geolocation Data | Approximate location derived from IP address; country code from App Store/Play Store region | Automatically collected | Region identification, security, analytics | No | No |
| K. Commercial Information | Subscription status (free/paid), store type (App Store/Play Store), purchase history | Automatically collected via RevenueCat | Subscription management, premium feature access, and Android first-conversion measurement | Potentially for the limited Android conversion events described in Sections 1 and 9 | No |
| L. Inferences | Learning patterns, vocabulary proficiency levels, memory strength scores, optimal review timing, adaptive difficulty levels | Derived from learning data via FSRS algorithm and AI systems | Learning optimization, personalized review scheduling | No | No |
- Categories Sold (Past 12 Months): None. We do not sell personal information.
- Categories Disclosed for a Business Purpose (Past 12 Months): Identifiers, internet/electronic network activity data, and commercial information, to the extent applicable to the service-provider and Android advertising-measurement paths described in Section 3.
To exercise your CCPA/CPRA rights, contact [email protected]. We will verify your identity and respond within 45 days. If we require additional time, we will inform you of the reason and extension period in writing, not to exceed an additional 45 days.
8-3. Do Not Sell or Share My Personal Information
We do not sell personal information for monetary or other valuable consideration. On Android, we may disclose limited device, app-event, and purchase-conversion information to Meta for advertising measurement and delivery optimization. Depending on the applicable law and Meta's role for a particular processing purpose, this disclosure may be treated as "sharing" or targeted-advertising processing.
Amplitude processes first-party analytics data on our behalf. Meta receives the limited Android advertising-measurement data described in Sections 1 and 3. DAYWIKA does not join campaign attribution data at the person level with a DAYWIKA account or individual learning and purchase histories.
Where applicable law gives you a right to opt out of sale, sharing, or targeted advertising, you may submit a request at [email protected]. You may also turn off optional analytics collection in the app, delete the Android advertising ID in device settings, and manage the advertising choices offered by Meta. These controls may operate differently and do not necessarily delete processing lawfully completed before the request.
8-4. Global Privacy Control (GPC)
Where technically supported and required by the CCPA or another applicable state privacy law, we will honor a valid Global Privacy Control (GPC) signal received on a supported web surface as an opt-out request. Until a particular surface supports that signal, or for native-app processing, you may submit the request through [email protected] and use the controls described in Section 9. For more information about GPC, visit https://globalprivacycontrol.org.
8-5. Sensitive Personal Information (CPRA)
We do not collect sensitive personal information as defined under the CPRA (Cal. Civ. Code § 1798.140(ae)), including but not limited to: Social Security numbers, driver's license or state identification numbers, financial account information (account log-in combined with access codes or passwords), precise geolocation, racial or ethnic origin, religious or philosophical beliefs, union membership, genetic data, biometric information for identification purposes, health information, information concerning sex life or sexual orientation, or the contents of mail, email, or text messages (other than communications directed to us).
8-6. Other U.S. State Privacy Laws
Where applicable, residents of Virginia (VCDPA), Colorado (CPA), Connecticut (CTDPA), Texas (TDPSA), Oregon (OCPA), Montana (MCDPA), and other states with comprehensive privacy laws may have rights to access, correct, delete, or obtain a copy of personal data and to opt out of covered targeted advertising, sale, or qualifying profiling. We honor requests required by laws that apply to DAYWIKA.
Right to Appeal: If we deny your privacy request in whole or in part, you have the right to appeal our decision. To appeal, contact us at [email protected] with "Privacy Appeal" in the subject line. We will acknowledge your appeal and respond with a written decision within 60 days of receipt. If we deny your appeal, we will provide you with information on how to contact your state's attorney general to submit a complaint.
Contact [email protected] to exercise your rights under any applicable state privacy law.
9. Cookies and Tracking Technologies
9-1. Cookies
The DAYWIKA app does not use cookies. Our external website (policy pages, etc.) may use essential functional cookies only. You may refuse cookie storage through your web browser settings.
9-2. Advertising Identifiers
iOS: In iOS app versions governed by this Policy, we do not request ATT permission, collect IDFA, use the Meta advertising-measurement SDK or Meta App Events, or enable RevenueCat-to-Meta delivery. Advertising performance may be measured through aggregate postbacks that Apple provides through SKAdNetwork or AdAttributionKit after applying privacy thresholds and delays. These postbacks may reflect stages such as app launch, onboarding or ordinary-learning progress, trial start, and first purchase. DAYWIKA's server may receive a copy of Apple's winning postback to verify its signature and remove duplicates. DAYWIKA uses the resulting information only as campaign-level statistics and does not join it at the person level with account, Amplitude-user, RevenueCat-customer, learning, purchase, or device histories.
Android: We may use the Meta SDK and Google Play Install Referrer to measure installs and advertising performance. App-to-Meta performance events are limited to onboarding completion and first meaningful ordinary-learning completion. On Android only, RevenueCat may deliver eligible trial-start, first-paid-subscription, and first-lifetime-purchase status to Meta. Renewal, cancellation, and refund status may be processed by RevenueCat for subscription management but is not included in our current initial Meta optimization-event set.
The Google Advertising ID (GAID) is processed only for users aged 14 or older who have opted in to analytics. Users who do not consent and users under 14 do not have GAID collected. Payment-card details handled directly by Apple or Google and not accessible to DAYWIKA are not included in Meta delivery.
- If You Do Not Consent: No GAID is collected. Declining optional analytics does not affect core learning features.
- Minors (Under 14): No advertising identifier is collected, and these users are excluded from Amplitude analytics, Meta App Events, and optional advertising-attribution events.
- Withdrawing Consent: You may turn off optional analytics collection at any time through in-app settings. On Android, you may also go to Settings > Security & Privacy > Ads > Delete advertising ID. Meta account holders may separately manage choices in Meta Accounts Center advertising settings.
DAYWIKA does not join advertising source or performance data with a DAYWIKA account or individual learning and purchase histories. Meta may process information it receives for measurement, ad-delivery optimization, and related advertising functions under its applicable terms and the user's Meta advertising settings. Withdrawing consent applies to future optional processing and does not affect processing lawfully completed before withdrawal. Operating-system aggregate measurement that does not use an advertising identifier may continue where permitted by law.
10. Security
We implement the following measures to protect your information:
- Encryption in Transit: All data transmissions use HTTPS (TLS) encryption.
- Server Security: Supabase managed security (TLS) with access controls.
- Device Security: iOS sandbox and Android app isolation (OS-level protection).
- Authentication Security: JWT token-based session management; no direct password storage.
- Access Control: Personal information access restricted to minimum necessary personnel.
11. Data Breach Notification
In the event of a data breach that compromises the security of your personal information, we will:
- Notify affected individuals in accordance with applicable state breach notification laws (including but not limited to California Civil Code §1798.82), providing details of the breach, the types of information involved, and steps individuals can take to protect themselves.
- Notify relevant authorities as required by applicable law.
- Timing: Notifications will be made without unreasonable delay, and in no event later than the timeframes required by applicable state laws.
12. Do Not Track and Online Tracking Disclosure (CalOPPA)
As required by the California Online Privacy Protection Act (CalOPPA), we disclose the following regarding online tracking:
Do Not Track (DNT) Signals: Our Service does not currently respond to "Do Not Track" browser signals. There is no industry consensus on how to interpret DNT signals, and we do not alter our data collection or use practices upon receiving a DNT signal.
Global Privacy Control (GPC) Signals: As described in Section 8-4, where technically supported and required by applicable law, we honor a valid GPC signal received on a supported web surface. Requests may also be submitted through the contact method in Section 13.
Third-Party Advertising Measurement: On Android, limited device, app-event, and purchase-conversion information may be provided to Meta as described in Sections 1, 3, and 9. iOS does not use Meta person- or device-level advertising measurement. You may manage optional analytics and advertising-identifier processing using the controls described above.
13. Contact Us
For questions, concerns, or requests regarding this Privacy Policy or our data practices:
- Name: Kim Doil
- Title: CEO / Privacy Officer
- Address: 105 Wausan-ro, 5F 174-A, Mapo-gu, Seoul, Republic of Korea
- Phone: +82-10-8237-3410
- Email: [email protected]
- Customer Support Team: [email protected]
14. Changes to This Privacy Policy
We may update this Privacy Policy from time to time. For material changes, we will provide advance notice by the method and within the period required by applicable law, and we will not begin processing that requires new consent until that consent has been obtained. Where permitted by law, changes required by law or a regulator, urgent security measures, or changes favorable to users may take effect promptly with notice provided without undue delay.
Change Log
| Version | Effective Date | Summary of Changes |
|---|---|---|
| v1.0 | February 23, 2026 | Initial version |
| v1.2 | February 25, 2026 | Age verification method changed (date of birth input → is_adult only), advertising identifiers now ATT consent-based, multi-layered child protection added, service providers added (Amplitude, Google Ads, PowerSync), COPPA compliance enhanced, contact information updated |
| v1.3 | June 16, 2026 | iOS advertising identifier (IDFA) collection and ATT removed; Android advertising identifier (GAID) now collected only with in-app analytics opt-in consent; Google Ads advertising-identifier sharing discontinued and removed from service providers, international transfers, and CCPA disclosures; clarified that we do not sell or share personal information for cross-context behavioral advertising |
| v1.4 | July 7, 2026 | Age verification changed to store year of birth (year only; month and day not collected) instead of recording only the is_adult boolean; is_adult is now derived from the stored year of birth and re-evaluated for automatic transition to adult status; year of birth is used for age gating (all users) and limited first-party internal statistics (minors excluded, not used for advertising, third-party sharing, or tracking); collection, retention, and children's-privacy sections updated for consistency |
| v1.5 | July 13, 2026 | Corrected the Account Information retention period in the Section 4 table, which stated retention continued for 1 year after account deletion; this contradicted Section 5, which states all account and learning data is deleted upon account deletion. The table now reads "retained while account is active; deleted upon account deletion," consistent with Section 5 and with the Korean and Japanese versions of this Policy |
| v1.6 | July 13, 2026 | Added a phone number to the Contact Us section (Section 13) |
| v1.7 | July 19, 2026 | Disclosed the Google Cloud (Vertex AI/Gemini and Cloud TTS) and Backblaze processing used for personalized examples, the data involved, and the de-identified retention of shared generated examples after account deletion |
| v1.8 | August 3, 2026 | Disclosed Android advertising measurement through the Meta SDK, Meta App Events, Google Play Install Referrer, and Android-only RevenueCat conversion delivery; clarified that iOS does not use ATT, IDFA, Meta advertising-measurement SDKs or RevenueCat-to-Meta delivery and uses Apple aggregate attribution; updated collection, disclosure, transfer, retention, user-choice, and children's-privacy terms; removed the deprecated level-test-results item |
| v1.9 | September 29, 2026 | Described the information collected through in-app feedback and word reports, including an optional reply email address, and added Plus Five Five, Inc. (Resend), which delivers those messages, to the service provider list |