简体中文 · Project and feedback

Yezhi Translate · Privacy and data

Updated: 20 November 2026 · Source version 1.0.3

Yezhi Translate processes webpages and PDFs on your device. Text you translate is sent directly to your chosen translation service. PDF files and page images are not sent to that service. API keys stay on this device; general preferences may sync through Chrome. The extension includes no analytics or advertising code.

Webpage text

Clicking the floating button, a keyboard shortcut, a paragraph translation gesture, or a context-menu command starts the relevant translation. Automatic translation is off by default; when enabled, eligible visible text is sent automatically. Active page translation also handles new visible content. New requests pause while the page is hidden. Canceling ends that page's session.

Password fields, input values, editable areas, and protected code or formula content are excluded from whole-page translation. Open Shadow DOM and accessible frames follow the same collection rules. Closed Shadow DOM is not read. Translation requests do not deliberately include the page URL, browsing history, or entire page HTML. The selected text itself may contain names, links, account details, or other private information, which will be sent with the text.

PDFs, OCR, editing, and export

Local PDFs are opened on this device. Online PDFs are retrieved directly from an authorized source, up to 50 MiB. These requests omit cookies and Referer headers and reject redirects. The source server still receives the requested URL, IP address, and normal connection metadata. For protected or redirected files, download them first and open locally. Document passwords are used in memory for this opening only.

Starting PDF translation extracts text and runs OCR locally where needed. Only eligible extracted text and language parameters go to the translation service. Complete PDF bytes, page images, and OCR bitmaps are not uploaded. Layout, manual revisions, independent editor drafts, and export run locally. Saved drafts may contain images extracted from the page or inserted by you.

Changing reading modes, zoom, and rotation reuses existing results. Explicitly translating missing pages or translating again sends the corresponding text. Export does not change the source file or itself start new OCR or translation. Exported PDFs are separate files you manage.

Recipients and downloads

There is no Yezhi Translate translation relay server. The background worker connects directly to Google Translate, MyMemory, Baidu, or the selected AI endpoint. Providers set their own data retention, model-training, billing, and privacy policies. Configure your own local server and point a custom endpoint at the loopback address if you wish to keep translation text on your machine. Every network recipient can see normal connection metadata, including your IP address.

English and Simplified Chinese OCR models are bundled. Other supported language models and export fonts download from fixed sources when needed, after source permission is granted. Downloads are checked against expected size and SHA-256 and stored locally. The download host receives the resource request and normal network metadata, not your PDF pages. Provider websites opened for documentation or credentials are governed by their own policies.

This privacy page, when hosted on GitHub Pages, connects to GitHub's hosting service under its logging policies. It uses no tracking scripts, remote fonts, or external executable code.

AI prompt templates and testing

Prompt templates stay on this device and do not use Chrome Sync. AI translation requests include the selected preferences and additional instructions, alongside source text, to your chosen AI service. The entire template library is not uploaded. Local previews send no requests. Clicking the translation test or comparison button sends test text and instructions and may incur API charges. Test text and results remain only in the current settings page memory and are excluded from template exports. JSON imports, exports, and sample downloads for prompts and glossary entries run locally without contacting a translation service. Exported files may contain your own instructions and terminology; keep them secure.

Storage and synchronization

Older versions stored credentials in Sync. Migration prefers existing local settings, copies legacy credentials locally, and removes legacy Sync fields only after a successful local write. The extension cannot control historical copies retained by Chrome's synchronization service.

Browser permissions

What we do not do

Exceptions you should know about: the service you choose processes the text and normal connection metadata under its own policy; Chrome Sync transmits ordinary preferences according to your account settings; GitHub Pages records access to this page under its hosting rules. These are outside the extension's control.

Logs, security, and retention

Development diagnostics use task stages, counts, timing, status codes, and service identifiers. They must not record source/translated text, credentials, or sensitive request information. Release preparation disables extension logging in its temporary release copy. Runtime messages use Chrome-provided sender identity, and translation results are checked against cancellation and configuration generations.

Local storage is not an encrypted vault. Someone with access to your device or browser profile may access locally stored configuration and drafts. Use appropriate device security. Custom remote APIs require HTTPS; HTTP is limited to supported loopback endpoints. These controls cannot guarantee a third-party provider's behavior.

Saved configuration, drafts, revisions, models, and fonts do not expire automatically. They remain until deleted or the extension is uninstalled. Downloaded models/fonts can be managed in the reader; credentials and glossary entries can be edited or cleared in settings. Closing a page does not delete saved drafts. You manage separately exported glossary JSON and PDF files yourself. Provider-held data must be handled under that provider's deletion policy.

Items still to be confirmed

The following cannot be verified from the source code. They are policy or operating decisions and are not decided. This page makes no promise about them; update this document and the date above once they are decided.

Your choices and contact

The current store material configuration uses the public Chinese privacy page and English privacy page. Verify the deployed content and store dashboard URLs when releasing; retention or migration of older URLs is handled separately.

Leave automatic translation disabled, choose individual paragraphs or selections, cancel active tasks, change services, revoke site permissions, manage downloaded resources, or uninstall the extension. Change the interface language independently of the translation target. For questions, use the public issue tracker. Do not include keys, private documents, or unredacted requests.

This English explanation accompanies the Chinese privacy document. Both describe the implementation; neither promises how third-party services will process data. Public store approval and live service availability are separate from source-code behavior.