Skip to main content

Privacy Policy

Effective date: 30 October 2026

fanyi.dev publishes translations of software documentation. In this policy, “fanyi”, “we” and “us” mean fanyi.dev, the operator of the site. This policy explains what information fanyi handles when you read the documentation or use the fanyi console at fanyi.dev/app, why, who else handles it, and how to reach us.

1. Reading the documentation

You can read every page on fanyi.dev without an account.

fanyi uses Cloudflare Web Analytics to see how the documentation is read: which pages are visited, from which countries, which sites link to them and how fast the pages load. When you open a documentation page, a small script from Cloudflare sends this to Cloudflare, which handles it under Cloudflare’s privacy policy. It sets no cookie and stores nothing in your browser. It is not used on the console at fanyi.dev/app or on the sign-in and sign-up pages. fanyi adds no advertising scripts, and fanyi itself does not set cookies on documentation pages.

Each documentation page counts how many times it has been opened. Once a page is on your screen, your browser tells our server which page it is, and the server adds one to that page’s count; that number is shown under the page’s title, and the total for the whole site in the footer. The count is all we keep. It does not record who opened the page: no cookie is set for it, and neither your IP address nor your browser’s user agent is stored with it. Search engines and other automated visitors, and pages your browser only loads ahead of time, are not counted.

fanyi is hosted on Cloudflare. Like any web server, Cloudflare receives the technical information every request carries — your IP address, your browser’s user agent, the address of the page you request and the page that linked to it — and uses it to deliver the page and to protect the site from abuse, under Cloudflare’s privacy policy. Our own servers may write error and operational logs that include the address requested; we use them only to keep the service running.

When you use search, what you type is sent to our server and looked up in fanyi’s own index. It is not sent to anyone else and we do not store it, though Cloudflare may keep a copy of the results for a few minutes so the same search is answered faster.

Your browser remembers a few display preferences for you — light or dark theme, and the framework, version, package manager or code tab you last picked — in its local storage. Choosing a framework or a documentation version also opens the page for it, so, like any page you open, its address (which names that framework or version) reaches our servers. The other preferences stay in your browser.

Content from other sites. Some documentation pages show images or videos the original documentation embeds, loaded straight from where the original keeps them — for example a YouTube video (from youtube-nocookie.com) or an image on the upstream project’s website. When your browser shows one, it connects to that service, which receives your IP address and the referrer information your browser allows it to send (usually just the site’s address, fanyi.dev), and handles them under its own privacy policy. A video is loaded when you scroll near it, not only when you press play.

2. Accounts

You can create an account with your email address and a password. An account lets you sign in to fanyi; it does not give access to the console at fanyi.dev/app, where fanyi’s operators manage translations — that access is granted by fanyi’s administrators. For each account we store:

  • your email address, the name you give, and an optional display name, together with an account identifier and when the account was created and last updated;
  • your password, only as a one-way hash — never in a form that can be read back;
  • whether your email address has been verified, and your account’s role;
  • for each signed-in session: a session token, when it was started, last updated and expires, and the IP address and browser user agent it was started from;
  • when you ask to reset your password, a short-lived record of the reset link we email you: which account it belongs to, a token for it and when it expires;
  • account administration records: whether the account has been suspended, the reason and until when, and, when an administrator signs in as you to help with a problem, which administrator did so.

Limiting repeated attempts. To stop automated sign-ups and repeated sign-in attempts, our server counts requests to its sign-in, sign-up and email-sending addresses by the IP address they come from. It stores your IP address, the address you requested and a count, and uses them only to count attempts.

Signing in with Google or GitHub. If you sign in with Google or GitHub, the provider shares your email address, your name and the address of your profile picture with fanyi, and we store them as above, together with the identifier the provider uses for your account and the tokens it issues for the sign-in. We ask only for your basic profile and email address — not for access to your contacts, files, repositories or anything else.

Signing in sets cookies that keep you signed in. They are needed for signing in to work and are not used for anything else.

We use this information to let you sign in, to keep the console secure, and to send the emails described below.

3. Emails

fanyi sends only two kinds of email:

  • a link to verify your email address, when you create an account and whenever you ask for another;
  • a link to reset your password, when you ask for one.

We do not send newsletters or marketing. These emails are delivered by postflare, our email delivery service, which receives your email address and the message to deliver it.

4. How pages are translated

Pages are translated by large language models, provided by DeepSeek by default, or by another provider we configure (OpenAI, Anthropic or OpenRouter). What we send them is the text of the documentation being translated — for a hosted site, the text its owner uploads, which may not be published yet — together with our instructions for translating it (a description of the project and a glossary). We do not send them any information about you or your account.

5. Where your information is stored

Account information is stored in a Cloudflare D1 database. Cloudflare runs its network worldwide, so your information may be processed in countries other than your own.

6. Who else handles your information

We do not sell your information or use it for advertising. It is handled by:

  • Cloudflare — hosting, network delivery, web analytics and the database (section 1, 5);
  • postflare — delivery of the two emails (section 3);
  • Google and GitHub — your sign-in information, only if you choose to sign in with them (section 2);
  • the services that host embedded images and videos, such as YouTube — the technical information your browser sends when it loads them (section 1);
  • DeepSeek, or the other language model provider we configure (OpenAI, Anthropic or OpenRouter) — which receive the documentation text being translated, never your information (section 4).

We may also disclose information when the law requires us to.

7. How long we keep it

We keep your account information for as long as your account exists. A session ends when you sign out or when it expires.

8. Your choices

To see, correct or delete the information we hold about you, or to delete your account, email support@fanyi.dev. When we delete an account we delete its sessions and its linked Google or GitHub sign-in with it. You can also remove fanyi’s access at any time from your Google or GitHub account settings.

The record of which account issued a hosted site’s upload token is kept after the account is deleted.

9. Changes to this policy

If we change this policy we will update this page and its effective date.

10. Contact

Questions about this policy or your information: support@fanyi.dev.