Privacy Policy

1. Summary

This policy explains what the Readlang Mobile app and the readlang-mobile.com website collect, why, and who else receives it. In short:

• We keep your email address and sign-in identifier to run your account, the words you translate to build your vocabulary, and usage data to improve the app.
• Translation runs either on your device with Apple Translate or through our server with Google Cloud Translation.
• We use service providers for analytics (Amplitude), push notifications (OneSignal), subscriptions (RevenueCat), email (Resend) and practice exercises (Anthropic).
• We send hashed identifiers and sign-up and purchase events to Meta to measure our advertising, and the website uses the Meta Pixel.
• We do not sell personal information for money, and we do not collect your advertising identifier (IDFA), contacts, photos or precise location.
• You can delete your account in the app. Section 7 explains exactly what that removes and how to ask us to delete the rest.

2. Information We Collect

2.1 Account

• Your email address. If you sign in with a code, the code is sent to that address through Resend.
• Your name, if you enter it during onboarding or it comes from Sign in with Apple or Google.
• Your Apple or Google account identifier, if you use Sign in with Apple or Sign in with Google. If Apple does not share an email address, we store a placeholder address built from your Apple identifier.
• An internal user ID that we create for your account.
• A sign-in token that is valid for 30 days and is stored on your device.

2.2 Learning profile and activity

• Your native and learning languages and your answers to the onboarding questions (what you want to read, your level, your reading experience).
• Reading streaks, the number of words you have translated and reviewed, daily activity and how much of the free daily translation limit you used.
• Your device time zone and local date, so that streaks and daily limits follow your own day.
• Whether you have completed onboarding and in-app tutorials.

2.3 Words you translate and your vocabulary

• When you tap a word or a phrase, it is translated either on your device by Apple Translate or by Google Cloud Translation through our server. Apple Translate is used when you choose it in Account Settings, when Google cannot be reached (for example, offline) and, from app version 3.0.8, whenever its language pack for your language pair is already on the device; otherwise Google is used. With Apple Translate the text stays on your device and our server only receives the number of translated words, for the daily limit. With Google, our server sends the text and the language pair to Google and does not store the request.
• Every single word you translate while reading a book or a web page is saved to your vocabulary on our server, together with its translation, the language pair and the sentence it appeared in. This powers your word list and practice.
• To create practice exercises, our server sends a saved word, its translation and the language pair to Anthropic. The sentence and your account ID are not sent.

2.4 Books, articles and the in-app browser

• EPUB files you import stay on your device and are not uploaded. Analytics receives only an identifier derived from the file (a hash) and the file size.
• Your shelves, reading progress, favourite sites and settings are stored on your device.
• Web pages you open in the app are loaded by your device directly from the website, which can see your IP address and set its own cookies. Our server is not involved.
• As you type in the search field of the in-app browser, the text is sent to DuckDuckGo for suggestions. A search that is not a web address opens Google Search. Site icons are loaded from Google’s icon service using the site address.

2.5 Purchases

• Payments are processed by Apple. We never see your card details.
• RevenueCat receives your internal user ID, your purchases and subscription status, and an Apple Search Ads attribution token. It sends us purchase events (product, price, currency, country and dates), which we store with your account.

2.6 Usage analytics

• The app sends usage events to Amplitude: sign-up and onboarding steps, books opened and reading and listening sessions, words translated (word length, languages and translation engine, not the word itself), words added, practice exercises, paywall views and purchases, notification permission, rating prompts and streaks.
• Events are linked to your internal user ID and to your device’s identifier for vendors (IDFV), and include device model, iOS version, app version, language and mobile carrier. Amplitude receives your IP address and uses it to estimate your country and city.
• Two things you type are included: the text you enter when searching for a language during onboarding (up to 40 characters), and the domain of a web page you save to favourites.
• Amplitude does not receive your email address, your name, or the words and sentences you read.

2.7 Push notifications

If you allow notifications, OneSignal receives a push token, your device model, iOS version, language and time zone, your internal user ID and tags describing how you use the app: premium status, streak, number of words, last activity and reading dates, paywall views and onboarding status. We use them to send reminders and, sometimes, offers. You can turn notifications off in iOS Settings at any time.

2.8 Support

Emails you send to support@readlang-mobile.com are received through Resend and stored on our server. A notification with your email address, the subject and the first part of your message is posted to our team’s private Telegram chat. Our replies are sent through Resend.

2.9 Our website

• Umami, hosted on our own server and using no cookies: pages visited, referrer, campaign tags in the address, country, browser and device type, and clicks on the App Store buttons.
• The Meta Pixel, on the website’s main pages (home pages, how it works, support, the /start quiz and landing pages) but not on the article and comparison pages: page views, App Store button clicks, quiz and demo steps and sign-up events, including your quiz answers. It sets the _fbp and _fbc cookies.
• Signing up on the website (/start): your email address, sign-in method, quiz answers and advertising click identifiers (fbclid and the Meta cookies) are stored on our server together with your IP address and browser user agent. The page loads Google and Apple sign-in scripts and keeps your sign-in token and click identifiers in your browser’s local storage.
• Cloudflare delivers and protects the website. It processes your IP address and browser details and adds its own privacy-oriented web analytics.

2.10 What we do not collect

We do not collect your advertising identifier (IDFA), precise location, contacts, photos, or data from your camera or microphone.

3. How We Use Information

• To provide the app: your account and sign-in, translation, vocabulary and practice, reading streaks and the daily free limit.
• To manage subscriptions and restore purchases.
• To understand how the app is used and improve it.
• To send the notifications you allowed, including reminders and offers.
• To measure and optimize our advertising with Meta, as described in section 4.
• To answer your support requests.
• To keep the service secure and to meet legal obligations.

4. Who Receives Your Information

We share information only with the service providers below, for the purposes listed.

We do not sell personal information for money. Sending hashed identifiers and events to Meta may count as “sharing” or “targeted advertising” under some laws; section 10 explains how to opt out. We may also disclose information when the law requires it, to protect rights and safety, or as part of a sale or transfer of the app.

5. How Long We Keep Information

• Account, vocabulary and activity data: until you delete your account.
• Sign-in codes: deleted automatically after 10 minutes.
• Purchase records: as long as needed for accounting and legal obligations.
• Website sign-up records and support emails: until you ask us to delete them, unless we need them to handle an open request.
• Server logs: for a limited time, for security and troubleshooting.
• Data held by our service providers: according to their own retention policies.

6. Security

All connections to our server and website use HTTPS. Your sign-in token is stored on your device, and access to our server is limited to the developer. No method of storage or transmission is completely secure, so we cannot guarantee absolute security.

7. Deleting Your Account

You can delete your account in the app: Account Settings → Delete Account. This deletes your account, vocabulary, daily activity and saved web pages from our server, and signs you out of RevenueCat, Amplitude and OneSignal on your device.

Some information is not removed automatically:

• purchase records, which we may need to keep for accounting;
• website sign-up records and support emails;
• data already sent to Amplitude, OneSignal, RevenueCat and Meta;
• imported books, reading progress and settings stored on your device, until you delete the app.

Email support@readlang-mobile.com from the address of your account and we will delete what we can and ask our service providers to delete the rest, within 30 days. If you used Sign in with Apple, you can also stop using it for Readlang Mobile in your Apple ID settings.

8. Your Rights and Choices

• Access, correction, deletion or a copy of your data: email support@readlang-mobile.com from the address of your account. We reply within 30 days and may need to confirm that the account is yours.
• Objection to analytics or to advertising measurement: email us and we will stop using your data for these purposes.
• Notifications: turn them off in iOS Settings at any time.
• Website cookies: you can block or delete cookies in your browser settings.
• If you are in the EEA or the UK, you can also complain to your local data protection authority.

9. Legal Bases (EEA and UK)

• Performance of a contract: your account, translation, vocabulary, subscriptions and support.
• Legitimate interests: analytics, security and measuring our advertising. You can object at any time (section 8).
• Legal obligation: accounting records.

10. California Privacy Rights

In the last 12 months we collected identifiers (email address, internal user ID, device identifiers, IP address), commercial information (purchases), internet activity (app usage events and website activity), approximate location derived from IP addresses, and content you create (your vocabulary).

We do not sell personal information for money. We share identifiers and internet activity with Meta to measure our advertising, which may be “sharing” for cross-context behavioral advertising. To opt out, email support@readlang-mobile.com with the subject “Do not share my personal information”. You also have the right to know, correct and delete your personal information, and we will not treat you differently for using these rights.

11. Children

Readlang Mobile is rated 17+ in the App Store and is not directed to children under 13, or under 16 in the EEA and the UK. If you believe a child has given us personal information, email support@readlang-mobile.com and we will delete it.

12. International Transfers

The app is developed in Uzbekistan. Our server is run by a hosting provider, and most of our service providers are based in the United States. Your information may therefore be processed outside your country, where data protection laws may differ from yours.

13. Changes to This Policy

When we change this policy, we update this page and the date at the top. If a change is significant, we will also try to let you know in the app.

14. Contact

Questions and requests about your data: support@readlang-mobile.com. Developer: Alisher Fayzullaev, Uzbekistan.