Office Document Translator BETA privacy policy

Effective date: 2026-10-07. Contact: xinchunma226@gmail.com.

This policy describes version 0.2.0, which requires the user's own API key. Publication of this policy does not mean the extension has been approved or published in the Chrome Web Store.

Local processing and retention

The extension parses, stores and rebuilds user-selected PPTX, DOCX and XLSX files inside the current browser. IndexedDB stores projects, original files, extracted text, translations, glossaries and translation memory. Interface language preferences are local. There is no automatic expiration period; deletion, uninstalling, clearing browser data or browser storage behavior may remove data. Download important documents and export glossaries.

It does not read ordinary webpages, browsing history, cookies, contacts or cloud drives. It needs no product login account and includes no developer analytics, advertising, telemetry or crash-reporting service.

Model requests

Terminology suggestions, translation, selected retranslation and connection tests go directly to the model API configured and authorized by the user, not a developer-operated translation gateway. Document operations send necessary text, nearby context, applicable glossary entries, language direction, model name and internal segment identifiers. Original Office packages, images, media and original filenames are not included in model requests.

Remote endpoints require HTTPS; user-operated localhost/127.0.0.1 servers may use local HTTP. The selected provider receives request content, API authentication and network information such as IP addresses. Its infrastructure may have logging, retention, training or human-review policies. Check those terms before processing documents. Providing your own key does not waive provider regional, age, data-use or billing restrictions. The extension does not promise free use or zero retention.

Gemini, DeepSeek and OpenAI are configuration presets; users may supply other compatible APIs. The developer does not centrally proxy them. Requests are sent only to the user-authorized endpoint; there is no default developer backend receiving document text or API keys.

API keys

Keys are kept in extension session storage by default and cleared when the browser session ends. Selecting Remember the key stores it in extension-local storage. Unchecking that option and saving removes the locally retained key and uses session storage. Keys are sent as authentication only to the configured API, not in prompts or public files, and are not synced to the developer.

Browser storage is not an operating-system keychain and currently has no additional application-level encryption. People with access to the browser profile or a compromised device may gain access to its data. Protect your device, browser profile and model account, and revoke keys when appropriate. Uninstalling or clearing extension browser data removes stored settings and credentials.

Uses, access and deletion

The developer does not sell extension data or use it for advertising, profiling or generalized model training, and has no remote feature for reading local documents. External model processing is governed by the user's provider agreement; this is not a universal promise that every provider has no training or human review.

Deleting a project deletes that project's original file and project record, but retains shared translation memory. Glossaries can be deleted separately. Clear translation memory clears its entries. Factory reset clears projects, original files, glossaries and translation memory, but not model settings or interface language preferences. Uninstalling or clearing extension browser data removes all local extension data. Downloaded files remain outside the extension. Request deletion of provider-held data through that provider's mechanisms.

Policy and contact

Use of user information is restricted to the disclosed Office translation, terminology, review and export functionality, not advertising or selling data. These purpose restrictions apply to the extension's handling of data; publication of this policy is not a security certification or a guarantee of Chrome Web Store approval. Material changes will be disclosed in the policy and interface where necessary.

Contact xinchunma226@gmail.com for support. By default, share only error descriptions or non-sensitive samples, not real API keys, personal data or unauthorized client documents. Any support access to specific content voluntarily supplied by the user requires separate consent for that content.