Veksha Privacy Policy

Effective date: July 13, 2026

Veksha processes information only to provide the language-learning features requested by the user. This policy applies to the Veksha browser extension and the Veksha service used by the extension.

Information processed

Depending on the features the user chooses, Veksha may process:

• a display name and internal account identifier;
• authentication tokens and, for optional Google sign-in, the Google profile name and email address returned by Google;
• selected text, page text, subtitle text, OCR results, and the domain of the current website;
• chat messages, saved vocabulary, training answers, learning history, language preferences, goals, settings, and feature state;
• an optional linked Telegram account identifier and subscription status when Telegram billing is used.

How information is used

Information is used to provide translations, explanations, language analysis, vocabulary storage and synchronization, personalized training, lessons, chat, authentication, optional reminders, support, and optional subscription billing. Veksha does not sell personal data and does not use personal data for advertising, credit decisions, or purposes unrelated to the extension's language-learning features.

Information sharing and service providers

The extension sends the information required for a requested feature to the Veksha production service. Text submitted for translation, explanation, chat, grammar, immersion, lesson, subtitle, OCR-related, or training features may be processed by OpenAI's API to generate the requested result. Railway hosts the Veksha production service. Optional Google authentication is processed by Google. Optional subscription billing is processed through Telegram. These providers receive only the information needed to perform their respective services.

Browser permissions and local storage

Veksha accesses page content only to provide features the user enables or invokes, such as selection translation, immersion, grammar analysis, subtitle tools, vocabulary frequency, reminders, and OCR. The extension stores an authentication token, account identifier, preferences, and feature state in local browser extension storage so it can work across sessions. OCR JavaScript, WebAssembly, and language assets are packaged locally with the extension; Veksha does not download or execute remote code.

Retention and security

Local extension data remains in the browser until the user clears the extension's data or uninstalls it. Server-side account and learning data is retained while needed to operate the account and provide requested features. Veksha uses HTTPS for data transmitted between the extension and the production service and limits access to account data using bearer-token authentication.

User choices

Google sign-in and Telegram linking are optional. Users can disable optional page-analysis and reminder features in the extension settings, clear local extension data through the browser, unlink optional services, and stop using the service at any time. Requests concerning account data or deletion can be submitted through the developer contact shown on Veksha's Chrome Web Store or Firefox Add-ons listing.

Policy changes

This policy may be updated when Veksha's features or data practices change. The effective date at the top of this page identifies the current version.