flua · Version of 14 October 2026

Privacy policy

What data the flua service collects, what it is used for, who it is shared with and how long it is kept. We collect only what the service needs to work and never sell data.

1. General#

This policy covers the processing of data of users of flua.ink, the service's API and the flua Telegram bot. The data controller is the Provider named in the "Provider and contacts" section. The policy supplements the Terms of service; terms used here have the same meaning.

By using the service you confirm that you have read this policy. If you do not agree with it, do not use the service.

2. What we collect#

Account. Email, name, password hash (the password itself is never stored), sign-up date, plan, balance, settings. If you sign in with Google — your Google account ID, email and name from it. If you link Telegram — your Telegram ID, username and language. For two-factor authentication — the TOTP secret and backup codes.

API keys. Key name, a hash of the key and its last characters (the key is shown once and not stored), limits, the list of allowed IP addresses, last use date.

Request log. For every request to the API, the chat and the Playground: time, model, endpoint type, numbers of input, cached and output tokens, number of images, cost, response status, error text (if any), duration and the key used. The content of requests and responses is not written to the log.

Payments. Amount, payment method, status, the payment ID at the payment service, for cryptocurrency — the coin and amount, and the history of balance operations. We never receive or store bank card details: card and SBP payments are processed by FreeKassa, cryptocurrency by CryptoBot, Stars by Telegram.

Chat and Playground conversations. If you use the chat or the Playground on the site, your conversations — messages, model answers, attached images, the system prompt and settings — are saved to your account so you can come back to them (up to the 100 most recent conversations of each kind).

Support. Messages you send to support through the Telegram bot or by email, and the service records linking them.

Technical data. The IP address and browser details sent with every request to the site and the API. The IP address is used to protect against brute force and abuse (rate limiting) and to check keys' allowed address lists; in the database it is kept as a counter key until the rate-limit window ends. In addition, when you sign in or open the gift, an irreversible hash of the address is stored (never the address itself) — to notice several accounts of one person and not give them the gift and referral bonuses again.

3. Request content#

  • So that a model can answer, the content of your request (messages, files, images, parameters) is passed to the model's developer or a provider of access to it and processed under their rules. Such companies generally do not use data received through their APIs to train models, but each has its own terms.
  • The service does not store the content of API requests and responses in its database. When something fails, technical logs may contain a short fragment of the provider's error response — it is used only for diagnostics.
  • For support and abuse prevention, the service's administrators get a Telegram notification about every request: the model, the volume, the cost, and the start of the last message and of the model's answer (up to 300 characters each). These fragments are not stored in the service's database; they stay in the administrators' Telegram chat until deleted.
  • Chat and Playground conversations are saved as described above. You can delete any conversation.
  • Public links. If you create a "Share" link to a conversation, a copy of it (without the system prompt) becomes visible to anyone who has the link. You can revoke the link at any time.
  • Do not send models data you are not entitled to share — for example, other people's personal data without consent, passwords or keys.

4. Why we use data#

  • creating your account, signing in, confirming your email, recovering access and two-factor authentication;
  • running requests to models, counting tokens, charging their cost and showing statistics in the dashboard;
  • accepting payments, crediting funds, granting bonuses and referral rewards, refunds;
  • service notices: codes, low balance and key limit alerts, notices of changes to the terms;
  • user support and handling requests;
  • security: protection against account takeover, fraud, bonus abuse and breaches of the Terms;
  • complying with the law.

We do not sell data and do not use the content of your requests for advertising or for training models.

5. Who data is shared with#

Data is shared only to the extent needed for the task at hand:

  • Model developers and providers of access to them — request content, to produce the answer.
  • Cloudflare — hosting of the site and the API, the database, attack protection, the "I am not a robot" check (Turnstile) and anonymous visit statistics (Web Analytics, no cookies).
  • Resend — sending email: confirmation codes, password recovery, notices.
  • Google — signing in with a Google account, if you choose it.
  • Telegram — signing in and linking your account through Telegram, the bot, support, Stars payments, service notices to the administrators.
  • Payment services — FreeKassa (cards and SBP), CryptoBot (cryptocurrency), Telegram (Stars): payment details, and for FreeKassa also your email if it is passed to the payment form.
  • Public authorities — only on a lawful request.

Some of these companies process data outside your country. We choose services that ensure appropriate data protection.

6. Cookies and local storage#

The site uses only necessary cookies — no advertising or third-party trackers:

CookiePurposeLifetime
flua_sessionyour signed-in session30 days
flua_signed_intells the site header that you are signed in30 days
flua-localethe chosen language1 year
flua_refthe inviter's code from a referral link30 days
flua_ask_nameask for your name after a Google or Telegram sign-in1 day
flua_oauthprotects the Google sign-in10 minutes
flua_tg_loginTelegram sign-in10 minutes
flua_chat_model, flua_chat_effortthe model and reasoning mode in the chat1 year

The browser's local storage (localStorage and sessionStorage) keeps the chosen currency and interface settings. Cloudflare may set its own technical cookies to protect against bots. You can disable cookies in your browser settings, but without the session cookie you cannot sign in.

7. How long data is kept#

  • Account, keys, conversations, balance history — for as long as the account exists.
  • Request log — 180 days, then deleted automatically.
  • Service records of support conversations — 90 days; the messages themselves stay in Telegram or in email.
  • Sessions, confirmation codes, password reset links, IP rate-limit counters — until they expire (from a few minutes to 30 days).
  • IP address hashes for abuse protection — 90 days after the last sign-in from that address.
  • Payment records — as long as needed for accounting and dispute resolution, including after the account is deleted.

Database backups are made daily and are accessible only to the service's administrators. Deleted data may remain in previously made backups for some time.

8. How we protect data#

  • passwords are stored only as a hash (salted scrypt), API keys and one-time tokens as hashes;
  • connections to the site and the API are encrypted (HTTPS);
  • two-factor authentication (TOTP) with backup codes is available, and mandatory for administrators;
  • sign-in, password recovery and sign-up attempts are rate-limited, and sign-up is protected by Cloudflare Turnstile;
  • API keys can have a spending limit and a list of allowed IP addresses;
  • only the service's administrators have access to user data, and only to do their job.

No system is completely secure. If you notice suspicious activity in your account, change your password, revoke your keys and contact support.

9. Your rights#

You can:

  • view and correct your account data in the dashboard settings, and your request and balance history in the dashboard;
  • delete individual conversations, revoke public links and API keys, unlink Telegram;
  • delete your account in the dashboard settings — the request log, balance history, keys and conversations are deleted with it (the remaining balance is forfeited, see Refunds);
  • request a copy of your data, its correction or deletion, withdraw consent or object to processing — by contacting support.

We answer such requests within 30 days. To protect your account we may ask you to confirm that the request comes from you. If you believe your rights have been violated, you may also complain to the data protection authority of your country.

10. Children#

The service is not intended for people under 18. We do not knowingly collect their data; if you learn that a child has signed up, contact us and we will delete the account.

11. Changes to this policy#

We may update this policy, for example when we add features or data processors. A new version is published on this page with its date; we announce significant changes by email or in the Telegram bot.

12. Provider and contacts#

Service
The flua service (flua.ink)

Terms of service