← Back to home

Data & privacy

Privacy policy

How we handle the content you choose to translate.

Translation text, necessary context and matching glossary entries are processed within our self-hosted server environment. Original PDFs and subtitle files are parsed on your device and are not uploaded.

The Precise Translate server does not persist translation text or output. Translation content is not used for model training.

We run open-source models in a self-hosted environment. Translation-related data is not sent to or shared with model providers. See “AI models and data processing” in our privacy policy.

AI models and data processing

Effective date: October 27, 2026

Last updated: October 28, 2026

Precise Translate is operated by Yang Jian. This policy covers our website, browser extensions, related account and translation services, and support communications. Website: www.precisetranslate.app. Privacy contact: support@precisetranslate.app.

Information we handle and why

Accounts and authentication

Precise Translate uses Google sign-in. We process your Google account identifier, email and necessary account and session information to verify your identity, keep you signed in and manage your account. The extension saves sign-in status locally.

Google authorization does not give us access to your emails, contacts or Google Drive files.

Content you choose to translate

Translation requires an internet connection. We process webpage text, input text, extracted PDF text and subtitles you choose to translate. Contextual translation and explanations may also use relevant headings, nearby passages or captions, and matching glossary entries. Requests include necessary settings such as language, model and translation options.

Original PDFs and subtitle files are parsed locally and are not uploaded. We do not upload filenames, complete page DOMs or full page URLs as separate translation request fields. Personal information within the text or context is still processed with the request. Only submit content you are entitled to process and willing to share with us.

Manual translation starts with your action. Enabled automatic or shortcut translation also sends content according to your settings. You can disable features, stop tasks or revoke site access; these actions cannot recall requests already sent.

Page information and site access

The extension uses page addresses locally to match website preferences and provide relevant features. It does not read the browser history database or upload a browsing-history list.

One-time webpage translation normally uses temporary access to the current tab. Automatic translation and persistent controls require the relevant site permissions. Showing the floating page button across websites requires your separate permission to access all HTTP and HTTPS websites. Displaying the button alone does not start full-page translation.

Retrieving YouTube captions sends requests to YouTube and may use your existing sign-in status on that site. We do not send the site's cookies to the Precise Translate server.

Usage and security information

We store account-linked request identifiers, features, languages, models, times, processing status and usage for usage limits, troubleshooting and service security. These records do not contain translation text, prompts or translated output.

Providing network services requires us and our infrastructure providers to process IP addresses and necessary technical information. The application uses sign-in security records to prevent abuse. Operational logs support troubleshooting and security checks and do not contain translation text, output, full prompts or sign-in credentials.

Local data

Translation preferences, site rules, glossary entries, local usage, imported files, tasks and completed translations are stored in your current browser. Translation caches are also local when enabled. This data is not cloud-synced, but text and glossary entries needed for a translation are still sent to the server. Protect your device and exported files.

Website visits and support

The website saves language preferences locally; you can remove them by clearing website data. It does not use analytics or advertising cookies or third-party analytics, advertising or session-replay services. Website visits and downloads require the server to process IP addresses, request paths and browser information.

The sender address, message and attachments you send to our support email are used to answer questions and handle privacy requests. Email service providers handle delivery, storage and necessary security checks. Do not send passwords, session tokens or unnecessary sensitive material.

Recipients and processing locations

We provide relevant information to the following providers only to deliver the service and for necessary security and operational purposes:

RecipientInformation and purpose
Hosting provider VultrServers and data storage supporting translation, accounts, usage and security
GoogleSign-in authorization and identity verification, governed by the Google Privacy Policy
CloudflareDomain name resolution
Support email service providersReceiving, storing and delivering support messages, with necessary security checks

Translation and account data is processed on servers in Tokyo, Japan. Google sign-in, domain name resolution and support email services use global infrastructure and may process related information in the United States and other countries. Using the service may involve international transfers depending on your location.

We may disclose necessary information to meet legal obligations or address security, fraud or abuse. A transfer in connection with a merger, acquisition or asset sale will require your prior explicit consent and remain subject to this policy's purpose limitations.

When you subscribe, we send Stripe your account email and information needed for the subscription. We retain customer, subscription, invoice and refund identifiers and statuses to manage payments, renewals and quotas. Stripe handles card details directly; we do not store full card numbers or security codes, or send translation text to Stripe. Stripe uses global infrastructure and processes this information under its privacy policy. Stripe

AI models and data processing

We deploy and manage self-hosted open-source models. Translations and explanations run within our server environment. Translation text, necessary context, matching glossary entries and translation settings are used only to complete requests you initiate or enable through your settings.

The server does not persist translation text or output. Translation-related data is not sent to or shared with model providers and is not used for model training. Account emails and sign-in credentials are not submitted as model inference content. Personal information within the text or context is still processed with the request.

AI translations and explanations may contain errors or omissions. Check important information against the original. You can remove sensitive information before submission or disable features such as automatic translation.

Data-use commitments

We use data only for the services and security purposes described here. We do not sell user data, use it for personalized advertising, creditworthiness or lending decisions, or provide it to data brokers.

Account information obtained through Google sign-in is used only for authentication, account management and service security. Our use and transfer of this information complies with the Limited Use requirements in the Google API Services User Data Policy.

Human access is limited to your explicit consent for specific data, necessary security investigations, legal obligations, or internal operations using aggregated and anonymized data.

Retention

  • Translation text and output: Used only during server request processing and not persisted. Local tasks and caches follow the rules below.
  • Local translation cache: Valid for 30 days. Expired entries are no longer used and are removed on later access or writes. You can also clear the cache yourself.
  • Local files, tasks, preferences, glossary and usage: Kept until you delete the data, clear extension storage or uninstall the extension. Exported files must be deleted separately. Disabling caching does not clear existing entries.
  • Sign-in records: Short-lived authorization and security records are periodically removed after expiry, so cleanup may be delayed. Sessions last at most 30 days from issuance.
  • Account and usage records: Kept while the account exists. Verified deletion requests follow the process below. Any exception required by law or necessary for security will include an explanation of its scope, reason and duration.
  • Logs and backups: Logs rotate; retention depends on log volume. Existing backups are used only for recovery and have no fixed rotation schedule. Deletion requests cover identifiable related backup data, and completed deletions are applied before restoring a backup.
  • Support messages: Kept for 180 days after issue resolution, then we delete the messages and attachments under our control. Email service providers' own security, delivery and backup records follow their policies.

Your choices and deletion requests

You can disable automatic translation, shortcuts and caching, revoke site permissions, and separately clear local caches, file tasks, glossary entries, site rules and usage. Settings and glossary entries can be exported. Settings exports do not include sign-in credentials.

Signing out stops translation, clears the local session and attempts to revoke the server session. The interface indicates if revocation cannot be confirmed. Signing out or uninstalling does not delete your server account. Signing out also retains local files, translations and preferences.

To access, correct or delete account-related personal information, email support@precisetranslate.app from your account email address and describe the request and its scope. There is currently no self-service account deletion control. We respond within seven calendar days, verify identity when necessary, and complete the request within 30 calendar days after verification. We do not ask for passwords or session tokens.

Account deletion covers the Google account link, sessions and identifiable related request, usage and backup data. Aggregate statistics without a personal association may remain. Clearing local data does not delete information already processed by service providers; requests involving those providers are handled under the applicable arrangements.

Security and policy changes

We use HTTPS, access controls and other measures to protect data. No measure guarantees absolute security. We address incidents affecting personal information and provide notifications as required.

Updates are published on our website with a revised update date. For changes to data types, purposes, recipients or processing methods, we provide notice before the relevant processing begins and obtain consent when needed.