LingVa is a lightweight browser translation extension whose core function is to translate text you select on a webpage, or text you type into the extension's popup or floating panel.
LingVa does not run any backend server, and does not collect, store, or upload any user data to the developer. This policy explains what data the extension touches while it runs, where that data goes, and what each browser permission is used for — for reference by the Chrome Web Store review team and by users.
| Data type | Description | Leaves your device? |
|---|---|---|
| Text to translate | Text you select on a webpage, or type into the popup / floating ball input box | Yes — sent directly from your browser to whichever translation engine you're currently using (see Section 4); LingVa itself never handles or retains it |
| Translation result | The translated text returned by the engine | No — only displayed in the UI and optionally saved to local history |
| Translation history | Recent source/translation pairs, used for the history list at the bottom of the popup | No — stored only on-device in chrome.storage.local / localStorage, never synced or uploaded |
| API keys / credentials | Third-party translation service credentials you enter yourself in Settings (Baidu App ID/Token, Google API Key, Microsoft Subscription Key, Youdao App Key/Secret, custom endpoint URL and Token) | No — stored only in local chrome.storage.local; read only when you initiate a translation, and used solely to call the corresponding service |
| UI preferences | Display language, font size, theme mode, whether the floating ball is shown, common target languages, etc. | No — stored locally only |
LingVa does not collect: identity information, account information, location data, browsing history, health information, or financial information, and it does not use any analytics, tracking pixels, or third-party tracking SDKs.
The data above is used only to provide the core translation feature:
LingVa includes a ready-to-use built-in translation engine, and lets you optionally connect the following third-party translation services, or a custom translation endpoint:
When you choose any of the engines above to translate, the text to translate is sent directly from your browser to that provider's servers, without passing through any intermediary server operated by LingVa or its developer. How each third-party service handles data is governed by its own privacy policy — please review the relevant provider's policy before use. When using a custom endpoint, data is sent to the address you configure, and how that data is handled is your own responsibility.
chrome.storage.local or the page's localStorage, and are never synced to the cloud or to a developer server.LingVa declares the following permissions in manifest.json, all of which are required to provide the translation feature:
| Permission | Purpose |
|---|---|
activeTab | Reads the text you select on the current tab, in order to initiate selection translation; triggered only when you actively select text |
storage | Saves settings, translation engine credentials, and local translation history on-device; no remote storage involved |
scripting | Injects the UI scripts needed for the selection translation panel and floating ball; only renders UI and never modifies the page's existing content |
offscreen | Manifest V3's background service worker can be terminated by the system at any time; an offscreen document is used to keep the network request alive until a result is returned, so translations aren't interrupted |
Host permissions host_permissions | Selection translation needs to work on any webpage, so the content script must be injected on all sites; some translation engines and custom endpoints also require cross-origin requests |
LingVa is not directed at children under 13, and does not knowingly collect personal information from children.
If this policy changes due to feature updates, we will update the "Last updated" date at the top of this document and note the change in the release notes. We recommend checking back periodically for the latest version.
If you have any questions about this privacy policy or how your data is handled, please contact the developer at: