Last updated: 2026-09-08
The developer does not operate a translation server. Translation and reading data are not automatically sent to the developer. The extension has no developer account or sign-in and no analytics or telemetry. If you choose to submit a problem report, the developer receives that report as described below.
Everything it does happens either locally in your browser, or as a direct connection from your browser to a service you chose and configured.
To translate, the extension sends the text of the page or the text you selected to the model connection you set up in Settings. That connection is one of:
127.0.0.1) — in this case the text never leaves your computer;The extension has no endpoint of its own and no fallback destination. If you have not configured a connection, no translation request is made at all.
Along with the text, a request may carry the page title and URL, target language, your question, and relevant context from the work's Series DB, including names, renderings and work details. API credentials authenticate requests only to their configured endpoint; a local bridge pairing token authenticates the helper.
Two features fetch a page from the site you are on, using your own browser session, exactly as opening the page yourself would:
These requests go to that site and nowhere else.
"Ask on AI site" opens or reuses the configured AI website and inserts your question and selected text, with any page context included by the configured prompt. This exposes that content to the website. The connection's submission setting determines whether the extension also submits it automatically or only prepares the input. Built-in ChatGPT and Claude connections default to automatic submission; a custom automatic form requires its configured submit selector. Choose prepare-only in Settings if you want to review the input before submitting.
The "Report a problem" link opens a pre-filled form. It carries the extension version, your target language, the kind of connection you use and its model name, and your interface language. The current page address and title are included only if you tick the box for them, which is off by default.
Opening the Google Form sends the pre-filled fields to Google in the URL query. The form lets you edit those fields before submitting the report, but editing them does not undo the URL data already sent to Google. The developer receives the completed report when you press Submit. Google's privacy policy applies to the form. You can open a report without including the source page information.
All of it is stored locally in your browser, using Chrome's extension storage:
These records are stored locally. Relevant content and credentials are used only in the disclosed requests above. Removing the extension clears its browser storage; saved/exported files and separate CLI accounts remain under your control. You can also manage individual works from the Series knowledge page.
You can use the extension on the active tab, enable it for selected sites, or explicitly grant all HTTP/HTTPS sites for the selection-tools setting. Chrome asks for the corresponding permission. Enabled-site content tools can load automatically. Next-page pre-translation can fetch an approved next page in the background when you enable that feature. Configured API and AI-website hosts also require the relevant access; localhost access is declared at installation.
Because you choose the connection, you decide where your text goes. If you point the extension at a model running on your own machine, the text being translated does not leave that machine. If you point it at a third-party API or subscription, that provider's terms and privacy policy apply to what is sent.
Problems and questions: the "Report a problem" link in the extension, or the issue tracker at https://github.com/zephyranthes03/ai-context-aware-subtitle-translator/issues.