← Aibrify Translate

Privacy

Effective 2026-08-25, updated 2026-09-05 · Applies to translate.aibrify.com and the Aibrify Translate browser extension.

This English version governs; the Chinese summary below is for convenience.

What we collect on this site

• Waitlist: if you join the waitlist we store the email address you submit and which language version of the page you used, only to email you about the launch. We keep waitlist addresses only until launch announcements have been sent, then delete the list within 90 days — or immediately on request. Nothing else is collected — no analytics, no tracking scripts, no cookies set by us. We do not track visitors across other sites, so we do not respond differently to Do Not Track signals.
• Account pages: the pricing, account and sign-in pages load no analytics and set no cookies of ours by themselves. When you sign in, our API sets one cookie, abt_session (HttpOnly, Secure, scoped to /api, 30 days), which identifies your session and nothing else. The pricing page loads Paddle's checkout script; Paddle may set its own cookies and local storage on that page and inside the checkout, under Paddle's privacy policy.

Where it goes

Waitlist submissions are stored on servers operated by Aibrify. They are never sold, and never shared with anyone — they sit on server infrastructure we rent and operate ourselves, and access is limited to the developer. Aibrify Translate is built and operated by an independent developer; the data controller for the waitlist is Aibrify, reachable at support@aibrify.com.

Your rights and choices

To be removed from the waitlist at any time, email support@aibrify.com from the address you signed up with. You can also ask what we hold about you (for the waitlist that is only your email address and page language) and have it corrected or deleted. We honor these requests wherever you live; in some places (such as the EU) they are also your legal right. For accounts, the account page shows what we hold that matters day to day (email, plan, usage) and lets you delete it yourself; email us for a full copy, including the name and profile picture we received from Google.

The extension

The extension translates subtitles on YouTube, whole web pages, text you select, and text you type into an input box. None of that traffic goes through a server of ours: we never receive, log or store what you translate. Which translation engine you use decides who else sees the text — the section below spells that out for each of the three.

• No accounts, no analytics, no tracking. The extension works without registration and contains no analytics, telemetry or advertising code. We do not collect, receive, sell or share any personal data from the extension, and there is no cloud sync.
• Where it runs. On YouTube it reads the video’s own subtitle track. Anywhere else it does nothing until you ask: pressing the translate shortcut or clicking the toolbar button lets it work on that one tab, right then. It keeps running on a site only if you turn on “Always translate this site” for that site, or “Selection & hover on all sites” in Settings — both ask your browser for permission at that moment, and both can be revoked in Settings or in your browser’s extensions page at any time.
• Where your text goes when it is translated. There are three engines, and the request always leaves from your own browser — never from a server of ours, which is why we cannot see, log or keep what you translate:
  • Chrome’s built-in translator (the free default where your browser supports your language pair): the text is translated on your own computer and does not leave it.
  • A free public online engine (currently Google’s public web translation endpoint), used when the built-in one cannot handle your language pair. Your browser contacts that endpoint directly, so the text and your IP address are visible to that provider under its own policies. We are not affiliated with it, we do not proxy the request, and we receive nothing. You can switch this off in Settings and stay on the on-device engine only.
  • Your own API key (optional: DeepL, Google, OpenAI, DeepSeek or Gemini). The request goes directly from your browser to the provider you chose, using your key. The key is stored only on your device, is never displayed back to you, and never passes through Aibrify’s servers. That provider’s privacy policy applies to what you send it; you can remove the key and its site permission at any time in Settings.
• Documents. Documents (PDF / Office / text) opened in the extension's viewer stay in your browser. They are never uploaded to us. Paragraph text is sent only to the translation provider you chose (on-device, a public endpoint, your own key, or Pro), exactly as for web pages. Scanned pages have no text layer, so the viewer tells you which pages they are and leaves them untranslated — nothing is sent anywhere for them.
• Translations are not kept. Original and translated text is held in memory only — in the page while you have it open, and briefly in the extension’s background worker, which your browser shuts down on its own when idle. Nothing is written to disk, nothing is uploaded to Aibrify, nothing is synced between your devices, and there is no export or sharing feature for translated text. The one exception is a word you deliberately save, which goes into your local vocabulary book (IndexedDB on your device) along with the sentence and page it came from.
• What stays on your device. Your settings, your per-site “always / never translate” rules, your API key if you added one, a simple counter of how much you have translated (a number of segments and characters — not the text), and your vocabulary book. Uninstalling the extension deletes all of it (this is how Chrome and other Chromium browsers such as Edge work). Export to CSV/Anki is available anytime, free. Review history and the list of words you mark as known stay on this device; they are never uploaded (the same for Free and Pro).
• What the extension requests from us: a small static configuration file (JSON, so we can fix breakage quickly when a site changes its pages) and, if you use word lookup, dictionary packs for your language pair. On first install it opens this site’s welcome page once — an ordinary page visit with no analytics scripts. A dictionary-pack request names the language pair you picked and, like any web request, reaches our host together with your IP address; beyond that we ask for no personal data, and none of these requests carries anything about what you were translating.

The extension’s handling of the data described above adheres to the Chrome Web Store User Data Policy, including its Limited Use requirements. Page and subtitle content is used only to provide the translation and lookup features you asked for — never sold, never used for advertising, and never used for any unrelated purpose.

Accounts and Pro

Everything above stays true for the free features: no account, nothing leaves your browser through us. This section only applies if you choose to sign in — which is needed only for Pro.

• Signing in. When you sign in with Google we receive your email address, name and profile picture from Google and store them with a random account ID. We never see your Google password, and we do not keep Google access tokens beyond the sign-in itself. If you sign up with an email address and password instead, we store the email address and a bcrypt hash of the password — never the password itself.
• Payments. Pro is sold by Paddle.com Market Ltd ("Paddle"), our merchant of record. Paddle collects your payment details, billing address and tax information under its own privacy policy. Paddle's notifications also tell us the amount and currency of each payment so we can confirm a charge; we store only your subscription status, plan, billing period and Paddle customer and subscription references — never card numbers.
• Pro AI features. When you turn on an AI feature (an AI-translated subtitle track, or line-by-line explanations), the subtitle lines being shown at that moment are sent from your browser to our server and forwarded to Google's Gemini API on its paid tier, under Google's data-processing terms, which do not allow using your data to train models. We do not store the original text or the translations. Our server logs record only request metadata — method, path, status, timing and internal event ids — never the text, and never your email.
• AI explanations. When you ask for an explanation of a subtitle line, that line (plus the line before and after it, for context) goes to Gemini the same way. We store only the explanation we generated, under a keyed hash of the sentence (a pseudonymised key, so the next person who asks about the same line gets the cached answer instead of a new model call). A stored explanation may quote at most the word you asked about and one clause of the line; we never store the full line, and we do not store the explanations you read as part of your account. Entries that have not been used for 180 days are deleted, and we delete an entry on request.
• Usage counters. To enforce the fair-use quota we keep, per billing period, how many subtitle lines and AI explanations you have used, with timestamps. Counters for the current and the previous period are kept; older ones are deleted automatically within about a month.
• Credits. If you buy credits, we keep a ledger of each purchase, bonus, hold, charge, release and refund: the pack, the amount and currency Paddle reported, the number of credits, a job ID and a timestamp — never the file name or its contents. The ledger stays as long as your account exists and is erased with it 30 days after deletion.
• Emails. We send service emails about your account and subscription: to confirm your email address when you sign up, to reset your password when you ask us to, to tell you when your password was changed, when your quota reaches 80 % and 100 % of the fair-use allowance, and before any change to Pro terms (at least 30 days ahead — a commitment we honor by hand, not by automation). If we ever have to suspend an account for abuse, we email you before doing so — also by hand. Paddle, as merchant of record, emails you about payments: receipts, failed payments and card updates. We do not send marketing email.
• Deleting your account. Settings → Account in the extension, or the account page on this site, deactivates your account immediately. If you sign in again to the same account (with Google or with your email and password) within 30 days, it is restored exactly as it was. Otherwise, after 30 days, we erase the account together with its subscription record and usage counters. Cancel any subscription first (Paddle keeps its own transaction records as required by tax law).
• Where it lives, how long. Account data is stored on servers we rent and operate ourselves, for as long as your account exists. Google (sign-in, Gemini) and Paddle may process data outside your country; for transfers from the EU/UK we rely on the EU–US Data Privacy Framework where the recipient is certified, and otherwise on Standard Contractual Clauses. Service emails are delivered through Resend, an email delivery provider, which receives your email address and the message text. Internal alerts about payments reach our team's Slack with your email address masked.
• EU and UK representative. We have not yet designated a representative under Article 27 GDPR / UK GDPR. Until we do, please contact support@aibrify.com for anything data-related; we answer every request ourselves.

Children

Neither this site nor the extension is directed at children under 13, and we do not knowingly collect personal data from them — the extension collects no personal data from anyone by design.

Changes to this policy

Any change will be posted here with a new “updated” date at the top. If a change materially affects how waitlist data is handled, we will email the waitlist before it takes effect. Pro has its own section above; it will be updated before any change in what is sent where.