AI Translator
Privacy Policy

ihor@dev:~$ cat privacy.md

Privacy at a glance

This Privacy Policy explains how IHOR.DEV / Ihor Kharchyshyn handles information when you use AI Translator. Its purpose is: translate requested text with AI, authenticate access, enforce source-character allowances, manage subscriptions and reservations, and operate the translation service.

1. Information processed or collected

The extension performs only the processing required to provide the feature or service requested by the user:

• The extension reads the text you enter or select, or eligible visible page text when you start page translation. In the default icon mode, selecting text alone does not send it for translation. Optional instant mode sends selected text automatically.
• Page translation replaces text nodes while preserving page structure. Original text needed for restoration stays in the page memory and is discarded when that page closes.
• Language, tone, selection, interface, and theme settings stay in Chrome-managed storage. Local history stores source text, translations, selected languages, and translation options in this Chrome profile: up to 1,000 entries or 25 MiB, removing the oldest when needed. Free shows the latest 20 entries; Pro gives access to up to 1,000. Downgrading alone does not delete older entries. History is not synchronized across devices; you can disable recording, delete individual entries, or clear it. Popup session drafts and pending requests can also be stored locally to resume work. History is isolated by account and billing environment and retained locally after sign-out; signing out clears the authentication session.
• The extension skips form controls, editable areas, code blocks, hidden content, and its own interface. It does not send full page HTML, browsing history, cookies, passwords, or form field values. Visible page text can still include personal information; request translation only for text you want processed.
• When you enable Pro page context, up to 2,000 characters of visible surrounding page text are transmitted to the backend and AI provider with the translation. Input fields, passwords, hidden text, and page HTML are excluded from context. Tone and language choices accompany the request. Page context is optional; do not include text you do not want processed.
• An optional review prompt keeps a device-local counter of up to five successful job identifiers, dismissal count, and next eligible time without translation text or review analytics. A local welcome flag prevents the onboarding page from reopening after the first installation.

2. How permissions are used

HTTP and HTTPS site access lets the packaged content script display selection controls and translate eligible page text and accessible frames. Page text is sent only when you request a translation or enable instant selection mode. Permissions are used for translation and its associated controls.

host permissions (http://*/* and https://*/*)

Allows selection controls and requested page translation on ordinary webpages and accessible frames where site access is allowed.

activeTab

Lets the extension access the current tab for actions you invoke, including reading the current selection.

scripting

Runs packaged extension scripts in the active webpage to read a selection or initialize translation controls.

contextMenus

Adds right-click actions for translating selected text and, with Pro, the current page.

storage

Stores local preferences, translation history, popup session drafts, pending input, and active translation state in Chrome-managed storage.

identity

Uses Chrome Identity for Google sign-in with basic account scopes: openid, email, and profile. It does not request access to Gmail, Drive, or contacts.

webNavigation

Tracks document and frame navigation to associate translation with the correct page and cancel outdated jobs.

Permissions are not used for advertising, profiling, analytics, creditworthiness, or any purpose unrelated to the project's user-facing functionality.

3. Remote code

4. Storage, retention, and deletion

Firestore translation jobs temporarily contain source text, optional context, output, account ownership, and job state. Job and idempotency records expire 24 hours after creation; Firestore TTL deletion is asynchronous and may happen later. Character counters and active reservations contain quantities and periods rather than page text or URLs. Subscription records contain account and Stripe identifiers, revisions, status, and paid-through dates to grant and revoke access. Historical purchase records retain original payment terms, units, refunds, disputes, and settlement data for accounting and support; they are not automatically converted or deleted during the subscription transition. Account, payment, and authentication records have separate retention purposes and are not promised deletion after 24 hours. Local history remains in this Chrome profile until removed, cleared, evicted under the 1,000-entry or 25 MiB storage cap, or local extension data is cleared. Uninstalling removes local extension storage but does not cancel a subscription or delete server records.

5. Sharing, sales, and advertising

Requested text, optional context, selected languages, and tone are sent to the authenticated translation backend and its AI service at balubenko-ai.web.app, which uses OpenAI. Google/Firebase handles basic account information, authentication, job data, quotas, and subscription access. Local history is not synchronized to a server. AI Translator does not sell page text or use it for advertising. Stripe processes card details on hosted Checkout and billing portal pages; billing receives payment identifiers, subscription status, and paid-period information, not full card details. See https://stripe.com/privacy.

6. Security

Production service connections use HTTPS. The backend verifies Firebase authentication and restricts job access to the owning account. Authentication tokens stay in the extension’s trusted context and are not shared with webpages. Operational logs are designed to exclude translation text and credentials. Protect your browser profile and use translation only for content you want sent to the service.

7. Chrome Web Store Limited Use

Google account information is used for sign-in and account display. Translation text is used to fulfill requested translations and operate that service. These data are not used for personalized advertising or unrelated profiling.

8. Cloud processing and optional context

9. Google account information

10. Your controls and deletion requests

11. Historical image jobs

12. Character allowances and subscriptions

13. Changes to this policy

Changes to functionality or data handling will be reflected on this page with an updated revision date.

14. Contact

For privacy questions about AI Translator, contact IHOR.DEV / Ihor Kharchyshyn at ihorkharchyshyn@gmail.com.