Subtitle Translator Privacy Policy

Subtitle Translator helps translate and explain selected text and subtitles. The extension works in two modes, and data flows differently in each. The user chooses the mode in the extension settings.

What data is processed

• The extension reads subtitles on supported video sites and the text the user selects on the open page. To explain a phrase it may use neighboring lines, the nearest page text and the page title as context.
• Settings, entered API keys, tokens, selected phrases, dictionary cards and the temporary subtitle cache are stored in Chrome storage on the user's device. This data is not synced between devices.
• If the user signs in to a Learning account, the extension processes that account's email and password. They are sent once over HTTPS to the Learning server to obtain a session token. The extension does not store the password. Only the session token (valid for 30 days), the email shown in the settings, and the last received list of topics and description of the agent are stored: provider, model, effort and the last four characters of the key. The Learning server does not pass the agent's key itself to the extension.

Mode 1. Your own AI key

When a translation or explanation is requested, the selected text and its context are sent directly to the AI provider the user chose, using the user's API key. The provider is chosen in the settings: Anthropic, OpenAI, DeepSeek or any OpenAI-compatible address (the z.ai API by default). If the user turns on auto-translate, subtitles are sent to the same provider for translation. The extension does not use its own server in this mode.

Mode 2. Agent from Learning

If the user is signed in to Learning and has chosen a Learning agent, the translation or explanation request (the selected text, its context and earlier chat messages) is sent to the Learning server set in the settings (learning.budgetme.xyz by default). The server calls the AI provider the user chose in Learning, using the key stored there, and returns the answer. The key is stored on the server in encrypted form and is never passed to the extension. The Learning application does not store the text of these requests and does not write it to application logs; the logs keep only technical request data (method, path, response code, time, IP address). The AI provider processes the request under its own policy.

Saving phrases

When the user clicks "Save to dictionary", the card is first saved locally. If the user is signed in to Learning, or has entered a link and a token, the extension sends the prepared card (phrase, translation, explanation, example, source) to a server. After sign-in the card goes to the Learning server with the session token, into the topic the user chose. Without sign-in it goes with the token the user entered to the link the user entered: this may be Learning or any other service the user picked. The extension does not send cards to addresses the user did not enter. For services other than Learning, the topic is not sent. The link field holds learning.budgetme.xyz by default; without sign-in and without a token nothing is sent. What a service chosen by the user does with the received card is governed by that service's own policy. The contents of the request are shown by the ? button next to the save link in the extension settings.

Use and control of data

Data is used only for translation, explanation and saving phrases. The extension does not pass it on for advertising and does not sell it. The user can at any time:

• sign out of Learning with the "Sign out" button in the settings: the session token, email and topic list are removed from the browser. The session token has no server-side state and stops working after 30 days;
• change or delete API keys, tokens and server addresses in the settings;
• clear the subtitle cache in the extension settings, and delete all local data through Chrome settings or by removing the extension.

Cards already saved in a Learning account are deleted in Learning itself. Retention periods and the handling of data by external AI providers depend on the services the user chose and their own policies.

Use of information received through Google APIs complies with the Chrome Web Store User Data Policy, including the Limited Use requirements: data is used only for the extension's described features and is not sold or passed to advertising platforms.

Questions about the extension and its handling of data can be sent through the support page.