Real Time Translator

Privacy

Effective date: 2026-11-21

Operator: Vladislav Bazaev. Individual operator.

What is processed

The service processes audio from the tab you select, source and translated text, and synthesized English speech to provide translation and captions.

Before the first translation, a notice explains how the audio will be processed and links to this policy. Choose Start translation to agree and begin. Stop ends audio forwarding. The extension asks again if the notice version, wording, privacy link or service address changes.

The translation service processes tab audio, text and synthesized speech in memory. The extension can briefly buffer tab audio in browser memory when you pause playback or the translation connection is interrupted. The service databases store account, allowance and usage records. They do not store recordings, transcripts, translations or synthesized speech.

Google sign-in and account records

Google sign-in requests the basic openid identity scope. The service stores an identifier derived from the verified Google account with an internal account ID. It does not request email or profile scopes or store a Google name, email address or avatar for sign-in. The extension keeps its service session in Chrome session storage.

We request Google's basic openid identity scope for sign-in. We use the verified Google issuer and subject to derive a SHA-256 digest and link it to a service account ID. We store hashes of service session tokens. For sign-in we do not request Google email or profile scopes or store an email address, name or avatar from Google. Sign-out removes the local service token and requests revocation of the current server session. The sign-in flow lasts five minutes, the one-time app sign-in code lasts one minute, and the service session lasts up to 24 hours. The authentication store clears expired sign-in flows, app codes, sessions and ownership proofs during later authentication operations. Signed-in users can generate a 24-hour ownership code in Settings to send to support. The operator's deletion tool verifies that code, requires settled accounting and stopped service writes. It creates a private pre-deletion snapshot, then removes the identity mapping, sessions, unexchanged app codes, ownership proof and account frame cursors. It records a hash of the used code with the original expiry to confirm completion on retry. The tool leaves settled accounting records in place.

Usage and local preferences

Account-linked usage records include allowance reservations, attempts, leases, provider references, timestamps and status. These records are not anonymous merely because their IDs are opaque.

The application records accepted audio duration and allowance balances for guest and signed-in sessions. Its usage and reconciliation databases keep internal account and attempt identifiers, provider request references, timestamps, reservation and settlement status, and completed usage and cost records.

The extension keeps playback preferences, hidden-site hostnames and the audio notice acknowledgement in your Chrome profile. It keeps the guest access credential in restricted local extension storage or in the extension's private IndexedDB, depending on the browser and its existing guest records. A separate non-exportable private key in IndexedDB lets this installation recover its guest allowance. Clearing that key can prevent recovery. The extension keeps the signed-in service token and expiry in Chrome session storage. It uses the selected tab URL and title locally to identify and display the source. Chrome also remembers whether you have signed in to this service before. This local yes-or-no setting lets the extension ask you to start translation again after a later sign-in.

Service providers and locations

Hosting: Fly.io. Region: Ashburn, Virginia, United States.

Google identity processing: Google may process sign-in information outside your country, as described in its privacy policy.. Google handles sign-in information under its own privacy policy. That policy describes retention by data type and purpose.

Google privacy policy

Soniox processes selected-tab audio, source and translated text, and synthesized speech. Region: The Soniox project for Real Time Translator is in the United States. Soniox may process operational and billing information in other locations.. Real Time Translator uses Soniox’s real-time APIs to recognize speech, translate it and generate the English voice. The extension’s service does not request file storage. Soniox says it processes these requests transiently and keeps operational records such as request IDs, durations and costs. Its policy describes exceptions for features, settings or agreements that require content storage.

Speech provider privacy information

When a guest starts translation, the service receives the audio notice acknowledgement, action ID and timestamps, and opaque player and video identifiers. For a guest allowance enrolled for recovery, the service stores a public installation key and its identifier with the guest record. The guest access token is valid for up to 24 hours. When it expires, the extension can sign a temporary one-time challenge to obtain a new token for the same allowance. Recovery does not send tab audio, start translation or add minutes. The private key remains in the Chrome profile. During translation the service receives tab audio, attempt identifiers, playback position and speed, and the amount of submitted audio. These application payloads omit the page URL and title. Soniox receives audio for recognition and translation, and English text for speech synthesis. The service receives and returns English captions and synthesized audio to the extension. Google is used for optional sign-in. Real Time Translator’s use of user data complies with the Chrome Web Store User Data Policy, including the Limited Use requirements.

Logs, access and backups

The service logs starts, stops and startup errors. Fly.io makes application logs available for seven days and keeps a US archive for 30 days. When its proxy encounters an error, Fly.io records the application identifier, hostname and request path. Fly.io also samples requests for troubleshooting. These traces include the client IP address and are processed in the US for up to 60 days.

Fly.io takes daily encrypted snapshots of the service volume and retains them for five days. They can contain account and usage records. Changes since the most recent snapshot may be missing after a recovery. Account deletion also creates a separate private pre-deletion database copy. That copy can contain the records as they existed before deletion.

The extension connects to the translation service over encrypted connections. Provider credentials stay on the server. If you email support, the operator can read your email address, message and any attachments you choose to send. You can report a problem by describing what happened and when. Keep passwords, session tokens and private recordings out of your report.

Sign-out and requests

Signing out clears the current service token from the extension. A successful sign-out request also revokes the current session on our server. If the service cannot be reached, the server session may remain valid until it expires. Account and usage records are kept separately. This release has no automated account-deletion feature. Expired sign-in flows, one-time codes and sessions are pruned during later authentication operations; expiry is not a promise of physical erasure at that instant.

For privacy questions and data requests, contact myrealtimetranslator.support@gmail.com. Email alone does not verify ownership of the Google-linked account. Do not send a Google password, API key or app-session token. To request account deletion, sign in to the extension, open Settings, and select Get account deletion code. Send that code only to the support address on this page and state that you want to delete your account. The code expires after 24 hours, can be used only for the deletion request, and is replaced if you generate a new one. If you cannot sign in, contact support for help recovering access to the linked account.

Audience and rights

For questions about your data, or to request access, correction or deletion, email myrealtimetranslator.support@gmail.com. For a signed-in account, open Settings, find Account and generate an ownership code. Send the code to support within 24 hours so the operator can identify the account concerned.