1. Overview and scope

Lingo Translate (“the Extension”) runs in your browser and provides local dictionary matching and optional model-based translation. This policy describes data handling, network requests, and controls in the Extension and this static website.

The Extension has no registration system or telemetry endpoint that uploads translation content, browsing history, or API credentials to the developer. When using a cloud model, text is sent to the provider you configure. Client-side execution does not mean every feature works without network access.

2. Page processing and local records

Scripts are injected when permitted pages load to read page text and match local dictionaries. GitHub uses dictionary mode by default. Other translation can be triggered by a button, shortcut, context menu, or automatic translation and site rules you enable.

• Text and attributes: Translation processes page text and supported text attributes such as labels and tooltips. Processing occurs in batches based on display mode, scrolling, and page updates, and is not strictly limited to the current viewport.
• URLs and domains: These are used for site rules, language profiles, and translation cache associations. Local cache records may include the page URL, source text, translation, target language, access time, and usage count. These records are not uploaded to the developer as browsing history.
• Accounts and analytics: No account is required. The Extension and this static website do not integrate third-party behavioral analytics scripts. Configured endpoints still receive network information needed to handle a connection.

3. Network requests and destinations

• Local matches: Bundled dictionaries, custom dictionaries, and cached translations can supply a result locally without a model request for that text.
• Translation and connection tests: Model requests go directly from your browser to the API endpoint you configure. They include text, prompts, model and language parameters, and use your configured API key for authentication. Connection tests also contact that endpoint. Translation requests do not pass through a relay operated by Lingo developers.
• Dictionary updates: Manual GitHub dictionary synchronization contacts the configured source, which defaults to the project dictionary on raw.githubusercontent.com. Once a remote dictionary or custom source exists, background checks attempt a silent update when more than 24 hours have passed since the last update. Before any synchronization or custom source is configured, the bundled dictionary is used. These download requests do not include page text or your API key.
• Website and external links: Visiting the website, downloading files, or opening provider or extension store links makes ordinary network requests. The respective operator is responsible for its server logs and data processing.

4. Local storage and backups

• Extension settings: API keys, endpoints, models, languages, display preferences, custom dictionaries, and site rules are stored in chrome.storage.local. Runtime state uses chrome.storage.session, with a local-storage fallback in browsers that do not support it.
• Translation cache: IndexedDB stores source text, translations, and related URLs for reuse and site-based management.
• Page preferences: The website and documentation pages use localStorage for preferences such as theme and language. Website storage is separate from the installed Extension’s storage.
• Credentials and exports: The Extension does not add API key or backup encryption. Configuration exports may include API keys, provider settings, and site rules. Cache exports may include source text, translations, and URLs. Protect these files and do not share them publicly. Settings and cache are exported and imported separately, with no automatic cross-device synchronization.

5. Browser permissions and script injection

The current manifest declares the following permissions. Browser-restricted pages and the site access you grant may still limit availability.

• storage: Saves Extension settings, dictionaries, site rules, and runtime state.
• unlimitedStorage: Supports local dictionaries and larger translation histories; available space remains subject to device and browser limits.
• activeTab / scripting: Supports translation actions, script execution, and content updates on the current page.
• contextMenus: Adds page translation and translation-editing context menus.
• notifications: Displays a cleanup reminder when cached translations reach the configured size limit.
• All-site access <all_urls>: Allows reading and translating supported pages and contacting user-configured model and dictionary endpoints. General content scripts run at document_start in matching pages and frames; the GitHub dictionary script matches GitHub domains only. Script injection does not itself mean a cloud model request is made; requests depend on translation mode and site rules.

6. Model and dictionary providers

Cloud model providers receive and process text you submit. Their retention, training-use, region, and account-tier rules are governed by their own policies and API terms. Review the terms of your chosen provider before use.

• OpenAI: API data controls
• Alibaba Cloud: Privacy Policy
• Google Gemini: Gemini API Additional Terms
• Local Ollama: Translation requests stay with a local endpoint only when both your configured endpoint and model run locally. A remote endpoint receives the text remotely. Other network features, such as dictionary synchronization, operate independently.
• Dictionary sources: GitHub hosts the default dictionary file. A custom source receives download requests when configured.

7. Controls and deletion

• You can change or remove API keys, adjust automatic translation and site rules, and limit site access or disable the Extension using your browser’s extension settings.
• Storage management can clear all cached translations or a specific site’s records. Clearing cache does not automatically remove API settings.
• Restoring the bundled dictionary removes remote overrides and the custom source. In the current implementation, this also stops subsequent remote dictionary checks until you synchronize again or configure a source.
• Uninstalling removes Extension data managed by the browser. Downloaded backups, website preferences, and data already received by a provider are not removed and must be managed separately.

8. Updates and feedback

This page and its revision date will be updated when features or data handling change.

For questions, use the support or feedback option on the browser extension store listing from which you installed Lingo. Do not include API keys, unredacted page content, or backup files in your feedback.