Privacy Policy

LivingTranslate browser extension · Updated and effective: August 11, 2026

Summary: LivingTranslate processes account information needed for sign-in. When you actively use translation, summarization, or chat, the extension sends the relevant content directly to the AI service you select. By default, the authentication server does not receive webpage text, PDF text, chat content, or AI API keys. It receives and encrypts AI configuration only when you opt in to cross-device sync.

1. Scope and operator

This policy applies to the LivingTranslate Chrome/Edge extension, livingtranslate.easyclin.cn, and the authentication service at yiwenapi.statray.cn. “Developer” means the LivingTranslate store publisher (易科临科技 easyclin). “AI service” means DeepSeek, Kimi, Qwen, SiliconFlow, Claude, Ollama, or another compatible endpoint you select or configure.

2. Data we process

2.1 Sign-in and account data

• WeChat QR sign-in: The extension obtains a temporary QR code and login serial number and polls for confirmation. After you confirm in WeChat, the authentication service processes the WeChat OpenID, display name, internal user identifier, source channel, and QR login status needed to create or recognize your account.
• Account/password sign-in: The account name or phone number and password you enter are sent over HTTPS to yiwenapi.statray.cn for verification. The extension does not store the password locally. The server verifies a password hash; an account record may include username, phone number, internal user identifier, source channel, and password hash.
• Local sign-in state: After a successful sign-in, the extension stores an internal user identifier and display name in chrome.storage.local. Signing out removes both local values.

This data is used only to create or identify an account, provide sign-in and access control, protect the service, and handle support. It is not used for advertising profiles.

2.2 Translation, PDF, summarization, and chat data

Only when you invoke a related feature does the extension send data required for the request to your selected AI service. This may include:

• the AI endpoint, model name, and API key;
• page title, webpage text, selected text, and text extracted from a local PDF;
• chat messages, quoted content, and conversation history sent for context;
• built-in system prompts and connection-test text.

These requests go directly from your browser to the selected AI service and do not pass through the developer's authentication server. The selected service handles the content and API key under its own privacy policy. You are responsible for evaluating a custom endpoint. With local Ollama, data is sent only to your configured local address.

2.3 Data stored locally

The extension uses chrome.storage.local to store AI settings and API key, language and display preferences, internal user identifier and display name, sign-in session token, up to 60 recent chat messages, and update status. Chrome sync is not used. The API key and relevant content are nevertheless transmitted to the selected AI service when you make an AI request, as described in Section 2.2.

2.4 Optional cross-device AI configuration sync

Sync is off by default. Only after you turn on “Cross-device AI configuration sync” and save does the extension send the AI provider, endpoint type and address, API key, model name, target language, and display preferences to yiwenapi.statray.cn. The authentication service verifies each device with a separate short-lived access token and encrypts the configuration at rest with a server-side key. Webpage text, PDF text, chat content, sign-in password, and browsing history are not sent to the sync service.

When you first sign in to a blank new device with an account that already has sync enabled, the extension restores that account's configuration automatically. You may also restore it manually from any signed-in device, turn sync off, or delete the cloud copy. Deleting the cloud copy does not remove local configuration. Signing out revokes the current device token but does not automatically delete the cloud copy.

2.5 Service requests and technical logs

The extension fetches announcements from livingtranslate.easyclin.cn/content.json. Development-mode installations also fetch version.json for update checks. When you access the website, authentication service, or these files, the servers and their hosting/security providers may generate standard logs containing IP address, browser or User-Agent, request time, requested path, response status, and security events. Logs are used for operations, troubleshooting, abuse prevention, and security, not advertising.

2.6 User feedback

When you submit feature feedback, the extension sends the category, message, optional contact information, and extension version that you provide. This is used to evaluate, respond to, and improve the product. Feedback does not include webpage text, PDF text, chat content, or AI API keys. Do not include passwords, API keys, identity documents, or other sensitive information in feedback.

3. Sharing and disclosure

• Your selected AI service receives the API key and content in Section 2.2 to perform the requested feature.
• WeChat and the authentication service process QR status and a WeChat account identifier for QR sign-in. yiwenapi.statray.cn verifies both sign-in methods and maintains account records. When you opt in to cross-device sync, it also receives and stores your encrypted AI configuration.
• Infrastructure providers may process necessary account data and technical logs on the developer's behalf solely to host and secure the services.
• Legal requirements: necessary information may be disclosed where required by law, legal process, or protection of users and the service.

The developer does not sell user data or use it for personalized advertising, credit decisions, or purposes unrelated to the extension's core functionality.

4. Retention and deletion

• Local settings and sign-in state remain until you remove them, sign out, or uninstall. “Clear” in the side panel removes local chat history.
• If you enable cross-device sync, the encrypted cloud AI configuration remains until you delete the cloud copy in the extension or request deletion of account data. Signing out revokes the current device token but does not automatically delete the cloud configuration.
• The extension does not store your password locally. Server account records are retained while the account remains active for sign-in and abuse prevention.
• Technical logs are kept only as long as reasonably needed for operations, security, troubleshooting, and legal compliance, then deleted or anonymized.
• User feedback is retained for no more than 24 months, or deleted or anonymized earlier when it is no longer needed. Optional contact information is used only to respond to the related feedback.
• You may request access, correction, or deletion of server-side account data using Section 8. After verification, data that is no longer needed will be deleted or anonymized unless retention is legally required.

5. Your choices

You may choose either sign-in method and your AI provider, including local Ollama, and may leave cross-device AI configuration sync disabled. Content is read and sent only after you invoke a feature. You may clear chat history, sign out, clear extension storage, uninstall, or delete the cloud configuration to remove data.

6. Security

Developer authentication and content services use HTTPS. Preset cloud AI services use HTTPS. If you configure an HTTP or other custom endpoint, transport security depends on that endpoint and your network. API keys are local by default; when you opt in to sync, the authentication service encrypts the configuration at rest with a server-side key and limits access with a separate device token. No network or storage system can be guaranteed completely secure.

7. Changes

If data handling changes materially, the developer will update this page and its date and, where appropriate, provide notice through the extension or store listing.

8. Contact

For privacy questions or account-data access, correction, or deletion requests, contact the developer through the LivingTranslate website or the publisher support channel on the Chrome Web Store listing. Provide enough information to locate the account, but never send a password or API key.