LinguaBites Privacy Policy
Last updated: September 28, 2026
LinguaBites provides vocabulary and phrase learning through its app and scheduled notifications. This policy explains the information processed when you use LinguaBites and the choices available to you. You do not need to create a separate LinguaBites account.
Information we process
Learning preferences and app activity. Your device stores preferences such as your familiar and learning languages, level, notification frequency and saved phrases. We also use Google Firebase and Google Analytics to measure app activity, including first opens, screens viewed, language and setup choices, notification interactions, subscription-offer interactions and purchase or restore outcomes. This measurement can include an app-installation identifier, app and operating-system versions, device characteristics, language, time zone and approximate location derived from your network address. We do not request GPS location or record your voice.
Subscriptions and purchases. Apple processes App Store payments. We use RevenueCat to validate purchases, manage subscription access and restorations, prevent fraud and understand subscription performance. RevenueCat processes an assigned customer identifier, transaction and receipt information, product and subscription status, purchase dates, prices, currency, trial and renewal information, and related app/device information. We do not receive your payment-card number or bank credentials from App Store checkout.
We associate the app's Firebase Analytics installation identifier with RevenueCat so subscription events can be related to app activity. These identifiers can distinguish an installation or customer record even though you have not supplied a name or created a login.
Notifications. Firebase Cloud Messaging and Apple's push notification service process notification-delivery tokens and technical information needed to route messages. When you enable notifications, your selected languages, level and frequency determine the topic subscriptions used for delivery. Notification permission is optional. Declining alerts does not disable all app analytics or all technical identifiers.
Advertising measurement. We use Meta technology to measure LinguaBites advertising, including app activation and setup events. With the required tracking permission, permitted advertising/device identifiers and Meta identifiers may be associated with app activity and subscription events to measure our ads on Meta services. RevenueCat's Meta integration is configured not to send subscription events when ATT consent is not authorized.
The app sends Apple AdServices attribution tokens to RevenueCat. RevenueCat stores these tokens and uses them to request attribution information from Apple. When available, Apple campaign information is stored with the RevenueCat customer record and used to understand how our Apple advertising relates to installations and subscription activity. Apple's standard attribution can operate without ATT authorization; access to more detailed attribution depends on Apple's rules and the available permission state.
Declining tracking does not mean that the app stops communicating with analytics, subscription or notification providers. Technical and app-event processing can continue for the purposes described here. LinguaBites does not display third-party ad placements in the app.
Diagnostics. We use Firebase Crashlytics to understand crashes, app errors and checkout reliability. Reports can include stack traces, installation and session identifiers, app and device information, and recent app events with their details supplied by Firebase Analytics. These event details can include the learning and setup choices, screens and subscription interactions described above. We also record checkout stages, operation timing, whether the app moved into the background or was opened again, typed error and outcome categories, and subscription-access check results. Random attempt and app-run identifiers help relate these records across an interrupted checkout. Diagnostic records can be associated with app-installation activity and subscription outcomes even though you have not supplied a name or created a login. Our custom checkout diagnostic fields do not include payment-card details, Apple account credentials or receipt contents. Other integrated SDKs may also process technical diagnostics and operational metadata to maintain reliability.
Support. If you email support, we receive the email address, message and information you choose to send. Do not send payment-card information or unnecessary sensitive information.
Why we use information and who receives it
We use this information to provide subscription access and learning notifications, restore purchases, maintain and improve reliability, understand use of the app, measure our advertising and respond to support requests.
Our providers include Apple, RevenueCat, Google/Firebase and Meta. Information can be processed on their systems in countries other than where you live. Provider processing and advertising measurement are subject to their applicable terms and privacy policies:
We may also disclose information when required by law or when necessary to address fraud, security incidents or threats to people's rights or safety. We do not ask for your email or contact details to match advertising conversions. Advertising-related sharing described above should not be understood as an assurance that no data is shared with advertising providers.
Retention
Retention depends on the data and its purpose. Local learning preferences and favorites remain on your device until removed through available device/app controls. Subscription records may need to remain with Apple or RevenueCat to validate access, support restorations, resolve billing issues and meet applicable recordkeeping requirements.
Our current Google Analytics settings retain event-level data for 2 months and user-level data for 14 months, with user retention extended by new activity. These settings do not impose the same limit on aggregate reports or on other providers' records. Notification delivery-ledger entries have a seven-day expiration, with deletion performed asynchronously. Other service and support records are kept for the purposes described in this policy and applicable operational or legal requirements. Removing the app or cancelling a subscription does not by itself delete all provider records.
The app keeps a small local record of recent checkout attempts so it can check what happened after an interruption. When the app next processes this journal, saved observations from checkout records at least 72 hours old are excluded from replay; the app can still report that a record expired. Local cleanup happens when the app runs and storage is available, so records may remain on a closed or unused device for longer. Diagnostic events sent to Google Analytics follow its applicable retention settings. Firebase states that Crashlytics keeps crash stack traces and associated identifiers for 90 days before beginning removal from live and backup systems. This does not promise immediate deletion of every diagnostic copy or other provider record.
Your choices and requests
Tracking: After setup, Settings → Optional ad measurement → Review tracking choice provides access to Apple's tracking prompt when a choice has not yet been made. You can later change permission in your device's privacy settings. Tracking permission is separate from purchasing access and notification permission.
Notifications: Choose Browse first during setup or manage notification permission later in the app or device settings. You can change your learning and notification-frequency preferences in LinguaBites.
Subscriptions: Manage or cancel your subscription through your Apple account's subscription settings. Deleting the app is not a cancellation.
Privacy requests: Email linguabitesapp@gmail.com with questions or requests about access, correction or deletion. Because the app does not require a named account, we may need information to locate the relevant records and verify the request. We will explain any identification limits or records that must be retained. Please do not send payment-card details.
The app does not currently provide a single switch that disables all analytics while retaining every other service. ATT and notification settings have the separate effects explained above.
Children
LinguaBites is not intended for children under 13 or the applicable minimum age in their jurisdiction. We do not knowingly collect personal information from children. If you believe a child has provided information, contact us so we can investigate and address the relevant records. The app does not implement age verification.
Security and updates
We use safeguards appropriate to the information and services involved, but no system can guarantee absolute security. We may update this policy as the app or its processing changes. The date at the top identifies the latest version. We seek any additional permission required for a new use rather than treating this policy as a substitute for that permission.
Contact: linguabitesapp@gmail.com