Skip to main content
WordHalo
LegalSupport

Plain-language policy

Privacy should be as quiet as the reading.

WordHalo helps language learners understand text they intentionally highlight. This policy explains what the extension and website process, why they process it, and what they do not collect.

Last updated: July 25, 2026

The short version

After you consent, the extension sends only the text you intentionally highlight, up to 1,000 characters of nearby text, your chosen interface language, and the webpage's language hint when available to WordHalo's backend. This is used to detect the highlighted language and return a definition, translation, and contextual explanation.

WordHalo does not collect your full URL, browsing history, full webpage, keystrokes, or clipboard contents. It does not sell personal information or use reading data for advertising.

1. The extension's single purpose

WordHalo provides reading help beside text that a user intentionally highlights on an HTTPS webpage. It is not a browsing history tool, full-page translator, advertising product, or general webpage data collector.

2. Information processed

When you ask for reading help

  • The exact word or passage you intentionally highlight.
  • Up to 1,000 characters from the nearby page element, so the result can explain the selection in context.
  • Your selected interface language and the webpage's language hint, when available.

The extension shows a disclosure before the first request. Nothing listed above is sent until you choose Use highlighted text.

Saved words and practice

When you choose Save, the extension stores that selection, its definition, translation, pronunciation, example, detected source language, and review progress on your device. Optional saved-word highlighting compares page text with that local list inside your browser. It does not send the page, matching words, or URL to WordHalo.

Product analytics

After consent, WordHalo may record product events such as an install, selected interface language, help card or tab opened, request outcome, seven-day return, upgrade interest, and referral conversion. These events use a random identifier or an account ID. Analytics do not contain highlighted text, nearby text, page titles, full URLs, or browsing history.

Optional account, waitlist, and payment information

If you choose to join early access or create an account, WordHalo may process your email address, preferences, saved words, usage counters, referral relationship, and subscription status. Accounts are not required for the beta reading interaction. Payments are not active today. If activated later, Stripe will process payment details; WordHalo will store subscription status rather than complete card numbers.

3. Service providers

  • WordHalo's hosted backend receives the selection, nearby context, interface language, and page-language hint so it can detect the source language and coordinate the requested result.
  • Free Dictionary API receives a single English word when a dictionary definition is requested.
  • OpenAI API may receive the selection, nearby context, interface language, and page-language hint for language detection, translation, and contextual help. Requests are sent with application storage disabled. OpenAI may retain API abuse-monitoring logs for up to 30 days under its default policy. OpenAI does not use API data for training by default unless the service owner explicitly opts in. WordHalo must verify its organization setting before store submission.
  • Supabase is used when configured for optional accounts, saved words, referrals, and privacy-conscious analytics.
  • Cloudflare Turnstile verifies that public form submissions are made by a person rather than an automated abuse tool. Turnstile receives technical request information needed to perform that security check; its secret key remains server-side.
  • MyMemory may receive demo text and a language pair when you use the translation interaction on the public product demo. The Chrome extension does not use MyMemory.
  • Google and Stripe are used only if you choose Google sign-in or, after billing is activated, make a payment.

4. Retention

  • Reading-help response cache: up to 1 hour.
  • Dictionary response cache: up to 24 hours.
  • Rate-limit identifiers: network and device identifiers are salted, irreversibly hashed, and stored in expiring usage buckets. Raw network addresses are not stored in the application database.
  • Product analytics: targeted for deletion after 90 days. Cleanup runs during normal analytics processing, so deletion can be delayed until the next analytics event if the service has no traffic.
  • On-device saved words: until you remove the word, clear extension storage, or uninstall the extension.
  • Synced saved words and optional account records: until you delete the item or account, subject to service-provider backup cycles and legal or security needs.
  • OpenAI abuse-monitoring logs: up to 30 days by default, and potentially longer when required for legal or abuse investigation.

Hosting providers may keep operational security logs under their own retention practices. WordHalo must verify and document those periods before public store submission.

5. Your controls

  • Choose Not now when the first-use disclosure appears.
  • Uninstall the extension or clear its local storage to remove local preferences, saved words, consent, and the random analytics identifier.
  • Delete individual saved words from the on-device library or, after syncing launches, from your account.
  • Use Delete account to request deletion of account data.
  • Use the account export control to download supported account data.
A monitored support address has not yet been published. WordHalo will add that contact channel before a public Chrome Web Store submission so waitlist and anonymous-data deletion requests have a working destination.

6. Limited Use and sharing

WordHalo's use and transfer of information follows the Chrome Web Store User Data Policy, including its Limited Use requirements. Data is used only to provide or improve the user-facing reading product, maintain security, comply with law, or provide support the user requests. It is not sold, used for personalized ads, transferred to data brokers, or used to determine creditworthiness.

Humans do not routinely read highlighted text. Access may occur only when needed for security or legal obligations, or when a user intentionally includes information in a support request.

7. Changes

Material changes will be posted here. If a change expands what the extension collects or how it is used, the extension will show a new prominent disclosure and request consent before the new collection begins.

Get supportTry the demoAccount controls