Privacy Policy

1. General provisions

This Privacy Policy (the “Policy”) describes how the LLMoney service (the “Service”, “we”, “us”) collects, uses, stores, and protects user information when you use the llmoney.ru website (the “Site”).

This Policy is an integral part of the Terms of Service. Consent to optional analytics is requested separately.

2. What data we collect

2.1. Account and sign-in

The interface offers Yandex ID, Google and email/password sign-in; the API also supports VK. Provider sign-in stores the provider ID, name, email and avatar link when supplied. The Service does not receive your provider passwords. Email registration stores your address, supplied name, password hash (Argon2id), email verification status and account creation/update dates.

The server stores sign-in sessions with an ID, user, expiry and browser User-Agent string. Email verification and password reset store a one-time token hash, recipient address, purpose and expiry. These emails require configured delivery; configuration alone does not guarantee delivery. The interface shows a limitation when email is unavailable.

2.2. API keys

Your keys and additional connection parameters are encrypted on the server using Fernet. The provider, key label, last four characters for display, validation status and dates are also stored. The server decrypts the key to authenticate requests to the corresponding API on your behalf. For OpenAI, you can specify a custom compatible API address.

2.3. Calculator text and model responses

Calculator counting keeps text in your browser: a local Worker computes tokens and their breakdown. The model catalog and prices load separately, without your text. Stored API keys do not enable automatic text submission to providers.

• The explicit model-call button sends text through LLMoney to the selected provider (or custom API address). This is a paid call using your key.
• The public /calculate and /tokenize API endpoints process submitted text on the server. /calculate may use native GigaChat or Yandex tokenization with an applicable key. Counting does not start answer generation.

The application does not write calculation text or model responses to its database or send them to analytics. Calculation error logs exclude provider response contents. External providers process and retain text under their own terms.

2.4. Optional analytics

Yandex.Metrica loads only after you click Accept. The Site makes no Metrica requests before consent or after declining. Your choice is saved in this browser and can be changed below. Declining does not affect calculations or sign-in.

After consent, Metrica receives public pageview information, technical browser and device data, your IP address and its cookie identifiers. These data may distinguish repeat visits from a browser; we do not describe them as anonymous. Session Replay, click maps and link tracking are disabled. Calculator text, URL query parameters and fragments are excluded from pageview events. After consent, coarse calculator events include counting start and outcome, length category, accuracy, model group, context status and error category. Events contain no text, fragments, filenames or raw errors. The tag does not load on authentication or settings pages.

2.5. Cookies and browser storage

Sign-in uses an httpOnly session refresh cookie. The access token is held only in browser memory. sessionStorage holds OAuth state and a language redirect marker; localStorage holds language, currency, table layout, analytics choice, exchange-rate cache and country lookup cache. These functions are separate from analytics. You can clear this data in browser settings; doing so may reset preferences and sign-in.

2.6. Language selection and technical requests

Automatic language selection may send your IP address from the server to country.is, falling back to ipapi.co, to determine your country. The result is temporarily cached in server memory. This operates independently of analytics consent; an explicit language choice takes priority. Loading fonts contacts Google Fonts from your browser. Web servers and external services receive technical request data, including IP addresses.

2.7. Telegram

If alerts are configured and you connect the bot, the Service stores your chat ID, link date and price subscriptions (models, providers and change thresholds). Linking uses a one-time link. Alerts contain price changes, not calculator text. Subscriptions and linking are unavailable when the channel is not configured.

3. Purposes of data processing

We process your data for the following purposes:

• Providing access to the Service and its features
• Identifying and authenticating users
• Securely storing and using your API keys
• Notifying you about changes to the terms of use or this Policy
• Improving the quality and functionality of the Service
• Ensuring security and preventing fraud
• Complying with legal requirements

4. External data recipients

The functions above use sign-in providers (Yandex, Google, VK), model APIs, an SMTP email provider (recipient address and message contents), Telegram, country lookup services and Google Fonts. Metrica is connected only with consent. The website and database run on Yandex Cloud. Each external service has its own data processing terms; Russian hosting does not mean every external recipient is in Russia.

5. Data storage and protection

5.1. Security measures

We apply the following measures to protect your data:

• Encryption of all connections via HTTPS (TLS)
• Encryption of API keys at rest in the database
• Storing refresh tokens in httpOnly cookies (inaccessible to JavaScript)
• Storing access tokens only in the browser's memory (not in localStorage)
• Hashing passwords and one-time email tokens

5.2. Storage and deletion

Accounts, encrypted keys, sessions and subscriptions are stored in the server database. A key can be deleted in Service settings; this does not revoke it at the provider. Use the provider dashboard to revoke a key. The Service currently has no automatic account deletion period or account deletion button.

Retention periods for infrastructure logs, backups and Metrica data, and procedures for deleting from them, require clarification from the operator. This page does not set unconfirmed retention periods or guarantee immediate deletion of all copies.

6. Your rights

In accordance with Federal Law No. 152-FZ “On Personal Data” and other applicable legislation, you have the right:

• Right to information — to learn what data of yours we process and for what purposes
• Right of access — to request a copy of your personal data
• Right to rectification — to demand that inaccurate data be corrected
• Right to erasure — to request deletion of your account and associated data
• Right to withdraw consent — to withdraw previously given consent to data processing
• Right to lodge a complaint — to file a complaint with Roskomnadzor (rkn.gov.ru)

To exercise your rights, send a request to privacy@llmoney.ru.

7. Deletion requests

You can send an account deletion request to the published address privacy@llmoney.ru. A request does not trigger automatic deletion. Its scope and completion, including backups, require separate confirmation.

8. Third-party services

The Service may contain links to third-party resources and use third-party services. We are not responsible for the privacy policies of those services. We recommend that you review the data processing terms of the respective providers:

• OpenAI — Privacy Policy
• Anthropic — Privacy Policy
• Sber (GigaChat) — Legal Information
• Yandex — Privacy Policy

9. Age of users

The Service is not intended for persons under 18 years of age. We do not knowingly collect data of minors. If we become aware that we have received a minor's data without the consent of a legal representative, we will take steps to delete it.

10. Changes to this Policy

We may update this Policy. The update date appears at the top of this page. The current version is always available on this page.

11. Contact information

For questions related to personal data processing and this Privacy Policy, you can contact us:

• Email: privacy@llmoney.ru

12. Prevailing language

This document is originally drafted in Russian and governed by the law of the Russian Federation. The Russian version available at llmoney.ru/privacy prevails over this translation.