Privacy Policy
LexiDock is designed as a local-first browser reading assistant. This policy explains what data is processed when you use the extension, what stays on your device, and when information is sent to a server because you requested a cloud-backed feature.
Data stored on your device
Vocabulary, Reading Memory, ordinary settings, a generated device identifier, and optional BYOK AI credentials are stored locally in your browser by default. Activating Pro stores an opaque device token after activation; the raw license key is not retained by the extension.
Data sent when you request a feature
- Selection translation and dictionary: the selected text and language information needed to return the requested result may be sent to the LexiDock API and its configured translation or dictionary provider.
- Full-page translation: supported Chrome builds prefer the browser's on-device Translator API. When local translation is unavailable, only eligible text segments needed for the requested page translation are sent through the LexiDock gateway.
- Hosted AI: when you explicitly use a hosted AI explanation, AI page translation, or Pro vocabulary study note, the selected text, requested page segments, or saved vocabulary term together with its existing translation and bounded context are sent to the LexiDock API and configured AI provider.
- OCR: LexiDock never uploads the original PDF. When you explicitly start Pro OCR on a scanned page, a bounded raster image of that rendered page is sent to the LexiDock OCR service.
- Pro sync: Reading Memory and Vocabulary sync are separate opt-in features. When enabled, the records required for synchronization are stored on the LexiDock server so your licensed devices can merge them.
Local files and browsing activity
PDF and DOCX files are opened and rendered locally. LexiDock does not upload the original document file. LexiDock does not build or sell a general browsing-history profile. Reading Memory records only sources where you actually use LexiDock and remains local unless you explicitly enable its Pro sync option.
AI credentials
If you configure your own OpenAI-compatible endpoint and API key, those credentials stay in the browser extension's local storage and are used by the extension background process to contact the endpoint you selected. They are not sent to LexiDock servers.
Licensing and payments
Pro activation uses a high-entropy license key and a locally generated device identifier to issue an opaque device token. LexiDock stores hashed license information, entitlement status, device records, and service-usage counters needed to provide Pro. Paid checkout uses Stripe Managed Payments; payment-card details are collected and processed by Stripe, not by the LexiDock extension or LexiDock API.
Retention
The LexiDock application layer does not intentionally persist the text or page images submitted for ordinary translation, hosted AI, or OCR requests. Opt-in cloud synchronization records persist until they are cleared or the service is retired. License and entitlement records are retained as needed to provide, secure, and administer Pro access. Hosting infrastructure may process standard network and operational metadata needed to operate and protect the service.
Sharing and sale of data
LexiDock does not sell personal data. Information is shared with service providers only when needed to perform the feature you requested, operate the service, process a payment, or comply with legal obligations.
Your controls
You can delete local Vocabulary and Reading Memory data from LexiDock, disable cloud sync, clear synchronized Reading Memory where the product provides that action, deactivate a Pro device, or stop using the extension. Removing the extension deletes browser-managed extension storage according to the browser's normal behavior.
Changes and support
If this policy changes materially, the effective date above will be updated. For privacy questions or product support, email support@xuworks.cn or visit the LexiDock Support page.