Veksha Privacy Policy

Effective date: October 19, 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, the address (URL) of the page where a word was selected or a reading feature was used, the title of a YouTube video when subtitle study is started, and an image crop when the user explicitly invokes area translation;
• a voice recording, only when the user presses the voice-input button, and the text the user asks to have read aloud;
• chat messages, saved vocabulary, training answers, learning history, language preferences, goals, settings, and feature state;
• AI and speech usage records, including the feature, model, timestamp, provider-reported token counts, and the number of characters or bytes of audio processed;
• an optional linked Telegram account identifier, subscription status, checkout details, and payment records when Telegram billing is used. Payment records include the Veksha account identifier, Telegram user identifier, Telegram payment identifier, purchased plan or features, amount in Telegram Stars, and a timestamp. For an auto-renewing subscription, Veksha also keeps its state (active, canceled, or payment failed) and a record of each renewal; a manually issued refund is kept as a record of the refunded payment. When crypto payment is used, Veksha keeps the same checkout and payment record with the amount in US dollars, the NOWPayments invoice and payment identifiers, and the payment status. Veksha does not receive or store bank card numbers or card security codes;
• technical server access logs, including IP addresses, request times, requested service URLs, response status, and browser or client information. These logs concern requests to Veksha's services, not a record of every website the user visits.

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. Payment records are used to activate and renew subscriptions, stop renewals the user cancels, prevent duplicate payment processing, and resolve payment support and refund requests. Technical access logs are used to operate the service, investigate errors, and protect against abuse. Veksha does not request GPS coordinates or use IP addresses to provide location tracking. AI usage counts are used for service operations, capacity planning, and cost monitoring. 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, Reading Coach, lesson, subtitle, OCR-related, or training features may be processed by OpenAI's API to generate the requested result. User-selected image crops may first be processed by Google Cloud Vision for text recognition; OpenAI vision is used when primary OCR is unavailable. Voice recordings and text to be read aloud are processed by a speech service that uses ElevenLabs for transcription and speech synthesis. Veksha does not save voice recordings. Complete generated samples may be cached in memory for up to 24 hours. Veksha also keeps the usage records described above. An infrastructure hosting provider processes the service's runtime and stored account data. Optional Google authentication is processed by Google. Optional subscription billing is processed through Telegram, which sends Veksha the checkout and payment information described above. Optional crypto payment is processed by NOWPayments, which receives only the amount and an order reference from Veksha, not the user's email or account name, and reports the payment's status back. Any information the buyer enters on the NOWPayments payment page, such as a wallet address, is governed by NOWPayments' own privacy policy. 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, Reading Coach analysis, grammar analysis, subtitle tools, deliberately started Reading Sessions, 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. Reading passages used for a comprehension question are kept in temporary server memory for up to 15 minutes and removed after the answer is checked; they are not added to the learning database. Area captures are kept temporarily in extension session memory, consumed once by the capture workspace, and are not written to browser storage.

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. Database backups made for releases and recovery are kept for up to 7 days. Payment and checkout records currently have no automatic time-based expiry. Technical server logs are rotated according to a size limit; older log files are removed as new logs are written, so their retention time depends on service traffic. Requests about retention or deletion can be sent to the contact address below. 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 sent to danfromomsk@gmail.com.

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.