Hearlex

Privacy at Hearlex

Last updated November 3, 2026. Contact us at support@hearlex.com.

What the extension reads

Hearlex runs on the pages where you use it so you can select English text and read page sentences. Text extraction and highlighting happen in your browser. Free browser speech does not send page sentences to Hearlex. If you use Pro cloud voice while reading a page, each sentence is sent for audio as playback advances; reading the full article this way sends its sentences to Hearlex.

What leaves your device

History and account

Lookup history contains a word, lookup count, time, optional surrounding sentence, page title, and website origin (not the full page URL). Without an account, it stays in browser storage; ordinary entries are limited to about 100 words and 30 days, while starred entries remain. If you sign in, history syncs to our database until you delete your account. You can turn off sentence saving in extension settings; doing so clears saved sentences locally and from your account when the next sync succeeds.

An account stores your email address and subscription status. We use a device identifier and a hashed network address to limit abusive API use. Payments are handled by Stripe; Hearlex does not store your payment card number.

Feedback

Your message, optional contact details and screenshot are sent to Hearlex support to handle your feedback. Remove private information before sending.

Audio caching

Generated word and cloud sentence audio is cached in Vercel Blob storage. Audio files have unlisted public URLs: anyone who obtains a URL can play that audio. Avoid using cloud sentence voice for private text. Browser speech is available without sending that sentence to Hearlex.

Your choices

You can pause Hearlex on a website, turn off sentence saving, use the extension without an account, export signed-in history, or delete your account from the account page. Deleting the account removes its stored history; shared dictionary and audio caches are not tied to an individual account. Contact us for privacy questions.

Our use of information received from Chrome APIs follows the Chrome Web Store User Data Policy, including its Limited Use requirements.