Privacy Policy

iOS App

1.1 Account Information

When you create an account using Apple Sign-In, Google Sign-In, or an email one-time code, we collect and store on our servers:

• Email address — for account identification and communication. If you use Apple's "Hide My Email", we only ever receive the relay address;
• Full name — for personalization (optional, depending on your sign-in method);
• Profile photo URL — for display in the App (if provided by your sign-in provider);
• User ID — a unique identifier generated by our authentication system;
• Device identifier — a random ID generated by the App to link your sessions and enforce usage limits. It is not the IDFA and is not used for advertising;
• Learning profile — your native language, the language you are learning, your level, and your learning goal.

1.2 Learning Data

As you use the App we store the following learning data. It is kept on your device and, when you are signed in, also synchronised to our servers so it is available across your devices:

• Saved words — words you save with translations, transcriptions, examples, and synonyms;
• Flashcard progress — review history, scheduling state, and your flashcard settings;
• Learning statistics — daily goals, streak count, correct/wrong answer counts, number of words translated;
• Dictation results — scores and history of your dictation practice sessions.

1.3 Browsing and Watch History

• YouTube watch history — titles, video IDs, thumbnails, and last watched timestamps of YouTube videos you watch in the App;
• Web browsing history — URLs of pages visited through the App's in-app browser;
• Bookmarks — URLs and titles you save as bookmarks;
• Search queries — search terms entered in the App's search bar.

This data is stored on your device. When you are signed in, your watch history — including the video title, URL, video ID, playback position, and the associated subtitle transcript — is also synchronised to our servers so you can resume on another device. You can delete individual items or your whole account at any time (see section 7).

1.4 Subtitle and Transcript Data

When you use the subtitle feature, the App retrieves YouTube subtitle data and sends it to our servers for AI-powered punctuation correction and translation. The text is processed in real time and is not retained by us or by our AI providers for that request. Where a transcript belongs to an item in your watch history and you are signed in, a copy is stored with that history item as described in section 1.3, and is deleted when you delete the item or your account.

1.5 Subscription and Payment Information

When you subscribe to LinguaCap Pro we store:

• Subscription status — active, expired, or cancelled;
• Plan type — monthly or yearly;
• Purchase and expiry timestamps;
• Billing events received from the app store via our subscription provider, retained for accounting and dispute handling.

Payment details (card numbers, billing address) are handled entirely by Apple and are never accessible to us.

1.6 Support Messages

If you contact us through the in-app support screen, we store your message, our replies, and the platform you wrote from, so that we can answer you.

1.7 Push Notification Token

If you allow notifications, we store the push token issued by Apple (delivered to us through Firebase Cloud Messaging) so we can notify you when support replies to you. Notifications are optional and no feature is gated behind them.

1.8 Product Analytics and Session Replay

We use PostHog to understand how the App is used and to improve it. This is analytics of our own product only — the data is not linked with third-party data, not used for advertising, and not shared with data brokers.

• Product events — app opened/backgrounded/installed/updated, screens viewed, and specific in-app actions such as starting onboarding, opening the paywall, starting a subscription, or rating the app;
• Profile properties attached to your analytics profile — your user ID, email address, subscription status, and learning profile (native language, learning language, level, goal);
• Session replay — a screen recording of your interaction, captured only on the onboarding and paywall screens and never elsewhere in the App. Text inputs and images are masked by the SDK before the recording leaves your device.

You can opt out. When you opt out, the SDK stops sending events and recordings entirely. See section 7 for how.

1.9 Feature Experiments

We use Firebase Remote Config to roll out features and run A/B tests (for example, which paywall variant you see). Which variant you were assigned is recorded as a property on your analytics profile so we can compare results.

1.10 Technical Diagnostics

Like any internet service, our servers process technical data so the Services can work and stay secure:

• IP address — received with every request. We use it for abuse prevention, rate limiting, and to determine your approximate country;
• Approximate country — derived from your IP address through IPinfo. We use it only to show region-appropriate help and support information in Settings. We do not derive or store your city, coordinates, or any finer location, and we never use the device's Location Services;
• Request diagnostics — the endpoint called, HTTP status, timing, your user ID, app platform and version, and the IP address. These are kept in a short-lived in-memory buffer of the most recent requests for live debugging and are lost whenever our server restarts;
• Usage counters — per-feature daily counts used to enforce free and Pro limits.

1.11 Audio Data

The dictation feature uses text input (keyboard typing). We do not record or collect any audio data from your microphone.

1.12 Information We Do NOT Collect (iOS App)

• We do not collect the advertising identifier (IDFA) and do not run advertising SDKs;
• We do not track you across other companies' apps or websites, which is why the App never asks for App Tracking Transparency permission;
• We do not use Location Services and do not collect precise location;
• We do not access your contacts, photos, camera, or microphone;
• We do not sell personal data or share it with data brokers.

Chrome Extension

1.13 Anonymous Session

On first use, the Extension registers an anonymous session with our own backend at api.linguacap.com. This generates a random user ID (UUID) used solely for rate-limiting translation requests. Unless you sign in, no email, name, or other personally identifiable information is collected by the Extension.

1.14 Device ID

A random UUID is stored locally in Chrome storage to identify the installation and is sent to our own backend with each request. It is not shared with third parties.

1.15 Saved Words and Preferences

Words you save to the dictionary, UI language, style settings, and feature toggles are stored locally in chrome.storage.local on your device. They are not uploaded anywhere unless you link the Extension to a LinguaCap account — in that case they are synchronised to our servers and governed by the iOS App sections above.

1.16 Translation Requests

When you click a word or enable auto-translate, the selected text is sent to our own backend, which calls third-party AI and translation providers (see section 4). Only the word or subtitle line is sent for translation.

If you are signed in, the Extension additionally saves a translation history entry containing the original text, its translation, the languages involved, and the page URL and page title where you made the translation, so you can review your history in your account. If you are not signed in, no page URL or title is stored.

1.17 Information We Do NOT Collect (Chrome Extension)

• General browsing history — we only ever receive the URL of a page on which you actively translated something, and only while signed in;
• Cookies or authentication tokens from visited websites;
• Video or audio content;
• Keystrokes or form data.

Android App

1.18 Account Information

You sign in with Google Sign-In, or with a one-time code from your LinguaCap account (for example, after signing in on our website with Apple or an email code). We store the same account information as for the iOS app (section 1.1): email address, name, profile photo URL, user ID, a random device identifier generated by the App, and your learning profile. The device identifier is not the Android advertising ID.

1.19 Learning Data

Saved words, flashcard progress and settings, learning statistics and dictation results are stored on your device and, when you are signed in, synchronised to our servers as described in section 1.2. When you are signed in, the App also shows the translation history saved in your account (section 1.16).

1.20 Watch History, Browser and Reading

• YouTube watch history — titles, video IDs, playback position and subtitle transcripts of the videos you watch in the App;
• In-app browser — your open tabs and bookmarks;
• Reading — books and articles you open in the reader, including EPUB files you import from your device.

This data is stored on your device only: the Android app does not upload your watch history, tabs, bookmarks or imported books to our servers. Books from the LinguaCap catalogue are downloaded from our servers.

1.21 Subtitle and Transcript Data

As in the iOS app (section 1.4), subtitle lines are sent to our servers for AI-powered punctuation correction, language detection and translation. The text is processed in real time and is not retained by us or by our AI providers for that request.

1.22 Subscription and Payment Information

LinguaCap Pro on Android is sold through Google Play Billing and managed through RevenueCat. We store the same subscription information as described in section 1.5. Payment details are handled entirely by Google and are never accessible to us.

1.23 Support Messages

If you contact us through the in-app support screen, we store your message, our replies, the platform you wrote from and any images you choose to attach. The Android photo picker gives the App access only to the image you select; the App resizes it before uploading it with your message.

1.24 Push Notification Token

If you allow notifications, we store the push token issued by Firebase Cloud Messaging so we can notify you when support replies to you. Notifications are optional and no feature is gated behind them.

1.25 App Analytics

We use Google Analytics for Firebase to see which screens of the App are used and whether notifications arrive. It records the screens you view and the arrival of a notification, together with the data the Firebase SDK collects automatically: an app-instance identifier, device model, Android and App versions, first open and session events, and an approximate location (country, region, city) that Google derives from your IP address.

The Firebase SDK may also read your device's Android advertising ID if your device settings allow it. We do not use it for advertising or to track you across other companies' apps, and you can reset or delete it in your Android settings. The Android app does not use PostHog or session replay.

1.26 Rating Requests

When you are signed in, the App tells our servers when you have opened a video (an identifier of the video and a random event ID). We use this only to choose a good moment to ask you to rate the App through Google Play's in-app review.

1.27 Technical Diagnostics

Our servers process the same technical data for the Android app as described in section 1.10: IP address, approximate country, short-lived request diagnostics, and usage counters.

1.28 Information We Do NOT Collect (Android App)

• The App does not request access to your microphone, camera, contacts or location, and does not collect precise location;
• The App does not show ads and does not run advertising SDKs;
• The App reads files from your device only when you choose them: EPUB files you import and images you attach to a support message;
• We do not sell personal data or share it with data brokers.