Telli.sh

Telli.sh: Every Translator browser extension

Privacy Policy

Effective: September 30, 2026

This privacy policy applies to the Telli.sh: Every Translator browser extension. Telli.sh: Every Translator translates supported messages, articles and comments into the user's selected language, and provides optional page chat and saving to Telli.sh.

Translation is processed in the browser or by the configured provider. The optional Clip feature sends content to Telli.sh only after an explicit save action. Site support requests are submitted separately through the signed-in Telli.sh website.

Data Processed

  • Readable messages, article paragraphs, video descriptions and comments on supported sites.
  • Text entered by the user for outgoing translation before sending a reply.
  • Extension settings, including target languages, translation provider, display mode, Google Apps Script URL, Ollama URL, and Ollama model.
  • Optional Google Cloud Translation API keys and DeepL API keys provided by the user.

How Data Is Used

Text is used for requested translations, page chat and explicitly saved clips. Settings control automatic translation and display. Spotlight mode waits for the Translate button before submitting the selected text for translation.

Where Data Is Sent

The selected translation provider determines where translation text is sent. Supported providers include:

  • Google Translate and Google Cloud Translation API
  • DeepL Free API
  • A user-configured Google Apps Script endpoint
  • A user-configured Ollama endpoint, normally a local server such as http://localhost:11434
  • Claude, OpenRouter and user-configured OpenAI-compatible endpoints
  • Browser AI models where available, with any network fallback identified in the result

Eligible translation providers may fall back to Google Translate when unavailable; the result identifies the engine used. Provider credentials are not sent to Telli.sh.

Optional Telli.sh Features

Connecting Clip verifies the token with Telli.sh without creating a note. An explicit save sends the page URL, title, available description, selected text, or the conversation you choose to save. Telli.sh stores this material in your account and may retrieve publicly accessible content and generate AI summaries under its service policies. It does not bypass sign-in or paid-content controls. You can revoke the token in your account.

A site support request stores your account association, submitted URL, description and review status for administrators. Query strings and fragments are removed from the URL; the request intake does not fetch the submitted page. See the Telli.sh Privacy Policy for the website and account service.

Local and Synced Storage

Provider keys and the Clip token are stored with Chrome's chrome.storage.local API. Target languages, provider choice, display mode, Ollama URL, Ollama model, and Google Apps Script URL may be stored with Chrome's chrome.storage.sync API so the user's settings can persist across browser sessions. Depending on the browser profile configuration, Chrome may sync non-secret settings through the user's Google account.

Remote Code

Telli.sh: Every Translator does not load or execute remotely hosted JavaScript, CSS, WebAssembly, or other executable code. All executable extension code is included in the extension package. Network requests support translation, page chat, explicitly requested Clip operations, connection tests and the extension announcement feed.

Data Not Collected By The Developer

  • No analytics or telemetry is collected by the extension developer.
  • No advertising identifiers are collected.
  • No user data is sold or transferred for unrelated purposes.
  • No user data is used for creditworthiness, lending, or eligibility decisions.

Limited Use

The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements. User data is used only for the extension's disclosed features and user-requested actions.

User Control

Users can remove stored extension settings by removing the extension from Chrome, clearing extension storage, or overwriting saved settings in the extension popup.