Readlang Mobile Get it on the App Store

Readlang privacy

What data does the Readlang Web Reader collect?

On its Chrome Web Store listing, the Readlang Web Reader says it handles two kinds of data: "Personally identifiable information" and "Website content". The developer declares that this data is "Not being sold to third parties, outside of the approved use cases" and "Not being used or transferred for purposes that are unrelated to the item's core functionality". That is what the listing showed for version 0.9.45, updated 28 October 2026, when we checked on 1 November 2026. This page puts that listing next to the Firefox listing, the two versions of Readlang's privacy policy and the permissions the extension asks for, quoted as published, without a safety verdict of our own. Our iPhone app, Readlang Mobile, appears only in the last section; it is an independent app, not affiliated with Readlang (readlang.com).

Download Readlang Mobile for iOS

Free to start. iPhone and iPad. Readlang Mobile is a separate app by an independent developer, not affiliated with Readlang.

The short answer

According to Readlang's privacy policy, last updated on 20 October 2026, Readlang collects your account details (email address, username, a hashed password and the languages you learn), the texts you import and the words you look up and save, payment details through Stripe, and technical data such as your IP address. It names Google for "translation of the text you look up" and OpenAI for its AI features. It says "We do not sell your personal data" and that it uses "only the cookies that are strictly necessary to operate the Service".

On Firefox, the add-on listing declares two kinds of required data collection, "Website activity" and "Website content", and one required permission, "Access your data for all websites". You delete your account from the bottom of the Readlang Settings page, and Readlang's developer says the deletion is immediate and permanent.

What the Chrome Web Store listing for Readlang Web Reader says

The Chrome Web Store asks every developer to fill in a privacy form and prints the answers on the listing under "Privacy practices". These are the developer's own statements: Google's documentation describes the form as the place to "disclose and certify your data collection practices". On 1 November 2026 the Readlang Web Reader listing, version 0.9.45, updated 28 October 2026, said this, word for word:

Google's User Data FAQ for developers describes personally identifiable information as "including a person's name, address, telephone number, email address, and username". It lists "website content and resources" as user data without a separate definition. Readlang's own policy, quoted further down, shows what the two boxes cover in practice: account details on one side, and on the other the texts you import and the words you look up.

The listing links to readlang.com/privacyPolicy for details and gives steve@readlang.com as the developer contact. The store page lists no permissions; Chrome shows them in its prompt when you click Add to Chrome. Edge installs the same extension from the same listing, so the same declarations apply there.

What the Firefox add-on listing for Readlang Web Reader says

The Firefox version of the Readlang Web Reader lives on addons.mozilla.org (AMO). Its listing shows two things the Chrome listing does not: a "Permissions and data" block and the full text of a privacy policy. Both were checked on 1 November 2026 for version 0.9.45, updated 28 October 2026.

Data collection declared on addons.mozilla.org

Under "Required data collection, according to the developer" the listing shows "Website activity" and "Website content". There is no optional data collection. Mozilla's developer documentation defines website content as anything "visible on a website — such as text, images, videos, and links", plus embedded data such as cookies and page headers. Website activity covers "interactions and mouse and keyboard activity, such as scrolling, clicking, typing". Firefox 140 and later on desktop, and Firefox for Android 142 and later, show these categories in the install prompt, and for required categories "users must accept this data collection to use the extension".

The privacy policy shown on addons.mozilla.org

The AMO copy carries no date and does not mention the extension, cookies or how long data is kept. It is shorter than the policy on readlang.com and differs from it in several places; the comparison is two sections down. Installing and troubleshooting the add-on is covered on the Readlang on Firefox page.

What Readlang's privacy policy on readlang.com says

The policy at readlang.com/privacyPolicy is the one the Chrome listing links to. It opens with "Last updated: 20 October 2026" and describes Readlang SL as "a company registered in Spain". The contact address is steve@readlang.com; Steve Ridout, who makes Readlang, also answers questions on the official forum himself. The policy speaks of "the Service" throughout and does not name the browser extension, so it applies to Readlang as a whole, the Web Reader included.

What Readlang collects

Category What the policy says
Account information "email address, username, password (stored only in hashed form), and the languages you are learning". With Google sign-in, Readlang also receives "your name, email address, and profile picture"; with Sign in with Apple, a name and an email or private relay address.
Your content "the texts you import, paste, or link to in order to read them" and "the words and phrases you save, your translations, and your reading and study progress"
Billing information Stripe "collects your payment details and billing address"; "We do not store your full card number"
Usage and device information "technical data such as your IP address, approximate location derived from it", and how you use the Service: "pages visited, features used, actions taken"

Quoted from readlang.com/privacyPolicy (last updated 20 October 2026), checked on 1 November 2026.

Who receives it

The policy says "We do not sell your personal data" and that Readlang shares it "only with service providers who help us run the Service". It lists them under "These include:", each with a purpose:

Provider Purpose, in the policy's words
Google "translation of the text you look up, and Google sign-in"
OpenAI "AI features such as explanations, sentence-aware translations, conversations, stories, and transcription of recorded audio"
Linode (Akamai) "our hosting and storage provider", where the servers, the database and your stored content are
Microsoft Azure "text-to-speech for reading content aloud"
Stripe "payment processing and subscription billing"
Quaderno "invoicing and tax compliance"
Amazon Web Services "sending transactional and reminder emails"
Rollbar "error monitoring to help us diagnose and fix problems"
Apple "Sign in with Apple, subscriptions bought in our iOS app, and notifications to our iOS app"
Trustpilot On an upgrade to a paid plan, "we share your email address so you can be invited to review the Service"

Some of these providers are outside the European Economic Area, including in the United States; for those transfers the policy relies on "the European Commission's Standard Contractual Clauses or an adequacy decision".

Cookies, retention and your rights

The same policy also covers an iOS app: it says the app asks for permission to send "the text you look up to OpenAI and Google", and that "The app can't translate without it." On 19 October 2026 Steve Ridout asked for testers on the forum for "a beta version of the Readlang iOS app I’m working on", and on 20 October he wrote that he was waiting for Apple to approve a test version. That app is Readlang's own. It is not Readlang Mobile, which is a different app by an unrelated developer.

Where the Readlang policy on Firefox differs from the one on readlang.com

Two texts are published as the Readlang privacy policy: the copy the developer uploaded to addons.mozilla.org, and the page on readlang.com. On 1 November 2026 they did not match.

Copy on addons.mozilla.org Page on readlang.com
Date None shown "Last updated: 20 October 2026"
Company Readlang SL Readlang SL, "a company registered in Spain"
Data listed Name, email address, uploaded material, usage such as pages visited and links clicked Account, content, billing, and usage and device data, including IP address
Service providers Not named; purposes are monitoring and analysis, contacting you, and backup Named one by one, with a purpose each
Cookies Not mentioned Strictly necessary only; no advertising cookies or trackers
Retention and deletion Not described beyond the right to delete Kept while the account is active; rules for deletion, backups and cached translations
Minimum age Not addressed to anyone under 13 Not intended for children under 14
Contact steve@readlang.com steve@readlang.com

Both texts checked on 1 November 2026: the AMO copy through the public addons.mozilla.org API, the readlang.com page directly.

The readlang.com page is dated and is the one the Chrome listing links to. The AMO copy is whatever was last submitted to Mozilla, and AMO shows no date for it. We cannot tell from the outside which text Readlang treats as the one in force for Firefox users. If the difference matters to you, the contact address in both is steve@readlang.com.

Which permissions the Readlang Web Reader asks for, and why

Permissions are what the browser lets an extension do, as distinct from what the developer says it does with data. Mozilla publishes the manifest of each add-on version through its public API. For Readlang Web Reader 0.9.45 the list is short.

Permission in the manifest What Firefox shows What the permission allows Where it shows up in Readlang
<all_urls> "Access your data for all websites", required Reading and changing pages on any site Clicking words on any page you open
contextMenus Nothing separate Adding items to the right-click menu The right-click "Import to Readlang" item
activeTab Nothing separate Temporary access to the current tab when you click the extension Not described by Readlang
scripting Nothing separate Running the extension's code inside a page Not described by Readlang
storage Nothing separate Keeping data in the browser's extension storage Not described by Readlang
readlang.com, test.readlang.com, localhost "Access your data for…" each of the three, optional Access to those addresses only, if you grant it; localhost is your own computer Not described by Readlang

From the addons.mozilla.org listing and public API for version 0.9.45, checked 1 November 2026. The "allows" column follows the WebExtensions documentation on MDN. Readlang publishes no explanation of individual permissions.

The broad one is "Access your data for all websites". It is what lets the Web Reader turn the text of any page into clickable words, and it is also why Mozilla lists "Website content" among the data the add-on collects. In Firefox you can review the permissions in about:addons, on the extension's permissions tab.

Chrome is less transparent here: the Chrome Web Store page shows no permission list, and Chrome shows one only in the install prompt. The developer note on the Mozilla listing says the Firefox add-on contains the same code as the Chrome extension and that "the only difference is in manifest.json", the file where permissions are declared, so the Chrome list need not be identical. We did not inspect the Chrome package. After installing, open chrome://extensions and click Details to see its permissions and set "Allow this extension to read and change all your data on websites you visit" to "On select" or "On specific sites". We have not tested how the Web Reader behaves with narrower site access. Browser-by-browser install steps are on the Readlang extension page.

The Readlang bookmarklet in Safari and third-party cookies

Safari has no Readlang extension on macOS or iOS. Readlang offers a bookmarklet instead, and its forum guide from June 2024 says signing in through it requires third-party cookies to be allowed. The reason is technical: the bookmarklet loads Readlang inside someone else's page, and with cross-site cookies blocked, Readlang cannot see that you are signed in.

The privacy cost lies in the browser setting, not in Readlang. In Safari, allowing third-party cookies means turning off "Prevent cross-site tracking", and that switch applies to every site, not only readlang.com. Firefox is narrower: Readlang's Firefox bookmarklet guide adds an exception for https://readlang.com alone, under Settings, Privacy & Security, Manage Exceptions. Readlang's policy says its own cookies are strictly necessary ones, but a global setting also lets other sites' cookies through. The Readlang and Safari page goes through the bookmarklet step by step.

How to delete your Readlang account and data

Readlang has a self-service delete button. The steps below come from the official forum guide "Delete my account" (June 2024) and the privacy policy of 20 October 2026.

  1. Export what you want to keep. The policy says you can "Export your data at any time from your account settings."
  2. Cancel Premium first, if you have it. On the account page, click "Cancel Subscription". According to the forum guide, the delete link does not appear while a premium subscription is active.
  3. Delete the account. Open readlang.com/settings, scroll to the bottom, click "Delete my Readlang account and all associated data" and confirm.
  4. Remove the extension separately. Deleting the account does not uninstall the Web Reader, and uninstalling it does not delete the account. Use chrome://extensions in Chrome or Edge, or about:addons in Firefox.

There is no undo button. When a user asked for a deleted account back, Steve Ridout replied on 2 June 2026: "This results in immediate and permanent deletion of your account." He added that he keeps "database backups going back a couple of weeks" and asked the user to email steve@readlang.com. The policy says the same in its own terms: after deletion, personal data is removed except "invoices for tax purposes" and "limited copies" that "remain temporarily in routine backups".

How Readlang Mobile handles translation, for comparison

Disclosure: we make Readlang Mobile, a native iOS app for iPhone and iPad. It is an independent app and is not affiliated with Readlang (readlang.com), with Readlang SL or with the Readlang iOS app in beta. It has no browser extension, so the permission questions above do not arise. The translation question does, and the answer is similar to Readlang's.

Readlang Web Reader Readlang Mobile
What it is A browser extension for Chrome, Edge and Firefox A native app for iPhone and iPad, iOS 18 or later
Who translates a word you look up Google, per Readlang's policy; OpenAI for AI features Google Translate through the app's server by default; Apple Translate on the device if you switch to it in Settings
Access to the pages you browse "Access your data for all websites" None; you paste an article link into the app
Privacy policy readlang.com/privacyPolicy, updated 20 October 2026 readlang-mobile.com/privacy

Readlang column from its policy and store listings, checked 1 November 2026. Readlang Mobile column from our own app.

So with the default setting, a word you tap in Readlang Mobile also leaves the phone and goes to Google Translate. If the chosen engine is unavailable, the app tries the other one. If you would rather keep lookups on the device, switch to Apple Translate in Settings; offline it needs the language pack for your pair. Apple Translation covers about twenty languages, where Readlang covers more than a hundred. The free plan gives 30 translations a day; Premium is $8.99 a month, $59.99 a year or $99 once. Our data practices are on the privacy page, and the Readlang review weighs Readlang as a whole.

Questions people ask

Is the Readlang Web Reader safe?

We do not rate it. What is on the record: on the Chrome Web Store the developer declares personally identifiable information and website content and certifies that the data is not sold outside approved uses. On Firefox it requires "Access your data for all websites". The privacy policy on readlang.com, updated 20 October 2026, names the service providers it shares data with, each with a purpose.

Does Readlang sell your data?

Readlang says it does not. Its privacy policy states "We do not sell your personal data", and the Chrome Web Store listing certifies that data is "Not being sold to third parties, outside of the approved use cases". Both are the developer's own declarations.

Can the Readlang extension see every website I visit?

It has permission to. Firefox shows its required permission as "Access your data for all websites", which is what lets it make the words on any page clickable. The Firefox listing declares "Website content" and "Website activity" as required data collection. Chrome lets you narrow site access in chrome://extensions under Details.

Does Readlang send my words to Google?

Yes, according to its policy. It names Google for "translation of the text you look up" and OpenAI for AI features such as explanations and sentence-aware translations. Hosting is with Linode (Akamai), and some providers are in the United States.

How do I delete my Readlang account?

Cancel any Premium subscription first, then open readlang.com/settings, scroll to the bottom and click "Delete my Readlang account and all associated data". Readlang's developer says deletion is immediate and permanent. Uninstall the extension separately.

Who is behind Readlang's privacy policy?

Readlang SL, described in the policy as a company registered in Spain. Steve Ridout makes Readlang, and the contact address in the policy is steve@readlang.com. Complaints in the EU can go to the Spanish data protection authority, the AEPD.

Does Readlang use cookies?

Only strictly necessary ones, according to its policy, and no advertising cookies or third-party advertising trackers. The Safari bookmarklet, however, needs third-party cookies allowed in the browser, and in Safari that setting applies to every site.

Read the dated policy, not the store summary

The store boxes are short self-declarations; the dated policy on readlang.com is where Readlang names its providers, its cookies and its retention rules. The Firefox listing is where the permissions are visible. If you read on an iPhone and want a different setup, Readlang Mobile, an independent app, uses Google Translate by default and Apple Translate on the device if you choose it.

Download Readlang Mobile for iOS

Free to start. iPhone and iPad. Readlang Mobile is a separate app by an independent developer, not affiliated with Readlang.