Skip to content
Aitechestvo

Public Offer for the Right to Use the Aitechestvo Service

Version 2026-10-14 · Edition for the Russian region

LAWYER-REVIEW — draft. This text was prepared by the engineering team from the actual design of the Service and is not legal advice. Before it is published in production, a lawyer (and an accountant for tax matters) must review the whole document and confirm every place marked LAWYER-REVIEW; every {{…}} value must be filled in. While this notice is present, the document is not an effective version and is not an offer.

This English text is a convenience translation of the Russian original. In case of any discrepancy, the Russian version prevails.

Version: 2026-10-14. Effective date: {{EFFECTIVE_DATE}}.

1. General provisions

1.1. This document is a public offer (Article 435 and Article 437(2) of the Civil Code of the Russian Federation) made by {{RU_OPERATOR_NAME}}, INN {{RU_OPERATOR_INN}}, OGRN {{RU_OPERATOR_OGRN}} (the Licensor) to legal entities and individual entrepreneurs (the Customer). It contains all material terms of the agreement on the right to use the Aitechestvo service (the Agreement). [LAWYER-REVIEW: decide whether self-employed persons and individuals are admitted; if consumers are admitted, consumer protection law applies and Sections 7 and 14–16 must be reworked.]

1.2. Acceptance. The Offer is accepted (Article 438(3) of the Civil Code) when the Customer's organisation is registered in the Service Console and a person acting on behalf of the Customer ticks the box accepting the Offer. The Agreement is concluded at that moment. The accepting person confirms that they are authorised to act on behalf of the Customer. Paying an invoice or making any other payment under the Agreement also confirms acceptance.

1.3. Documents forming part of the Agreement:

  • the Plans published at /en/pricing and in the Console (the Plans);
  • the Personal Data Processing Instruction (/en/legal/dpa);
  • the Recurring Payments Terms (/en/legal/recurring-payments) — for Customers who enable auto-renewal;
  • for reference: the Personal Data Processing Policy (/en/legal/privacy) and the Cookie Policy (/en/legal/cookies).

1.4. The Agreement does not need to be signed on paper. The parties recognise the legal effect of actions performed in the Console after logging in to an account, and of messages sent to the email addresses provided by the Customer and the Licensor.

2. Definitions

  • Service — the Aitechestvo software provided by the Licensor through remote access over the Internet (SaaS) in the Russian region: the website, the Console, the web chat, the Gateway and the masking API.
  • Gateway — the Service's API, compatible with the OpenAI and Anthropic APIs, through which the Customer sends Requests to language models.
  • Request — a call to the Gateway containing text and other data addressed to a language model or to the masking API.
  • Masking — detecting values of certain categories in a Request (names, company identifiers, contact details, credentials, etc.) and handling them under the Masking Policy: replacing them with placeholders (pseudonymisation) that are restored in the response, replacing them with generalised values, passing them with a warning, passing them unchanged, or blocking the Request.
  • Masking Policy — the rules for data categories, lists and custom patterns that the Customer configures in the Console.
  • Organisation — the Customer's account in the Service; Users — the natural persons the Customer admits to the Organisation.
  • Platform models — language models made available by the Licensor under its own contracts with providers and paid from the Balance.
  • Own connection — a connection to a language model under the Customer's contract with a provider, or to an endpoint controlled by the Customer.
  • Balance — the Customer's prepaid account for paying for Platform model usage.
  • Subscription period — a paid period (month or year) of Service use under the selected plan.

3. Subject of the Agreement

3.1. For the term of the paid Subscription period (or the trial period) the Licensor grants the Customer a simple (non-exclusive) licence to use the Service by remote access for its intended purpose in accordance with its functionality within the selected plan, and the Customer pays the licence fee. The licence is granted without the right to sublicense, worldwide; the Russian-region Service is, however, intended for Customers registered in the Russian Federation.

3.2. In addition, the Licensor provides, at the Customer's request, services giving access to Platform models, paid from the Balance (Section 8).

3.3. [LAWYER-REVIEW: legal qualification of the agreement (licence agreement, services agreement or mixed agreement, Article 421(3) of the Civil Code). The VAT exemption of the licence fee (Article 149(2)(26) of the Tax Code) is available only after the software is entered in the unified register of Russian software and only for the licence part; it never applies to Balance top-ups.]

3.4. The exclusive right to the Service belongs to the Licensor. The Customer receives no source code and no right to modify the Service.

4. Service functionality

4.1. The Service detects values of the categories listed in the Console in Requests, handles them under the Masking Policy, sends the Request to the selected model provider and restores the original values in the response, including streamed responses. The Service also provides the Console (policies, keys, connections, members, alerts, Request and audit logs, analytics, billing), the web chat and the masking API.

4.2. The Service does not store Request content. Texts, attachments, model responses and pseudonym tables are processed only in memory for the duration of one Request. The Request log contains metadata only (no content). Web chat history is stored only in the User's browser. The masking API restore token is kept by the Customer.

4.3. The Licensor may develop and change the Service's functionality. Changes that materially reduce the capabilities of a paid plan take effect no earlier than the end of the current Subscription period, or with the Customer's consent.

4.4. Plan changes and the end of a subscription never delete or weaken stored Masking Policy rules: the Service applies all stored rules regardless of the plan.

5. Registration, accounts and keys

5.1. The Customer grants access to Users, assigns their roles and is responsible for their actions. The User who registered the Organisation becomes its owner.

5.2. The Customer keeps passwords, API keys and tokens confidential, promptly revokes compromised keys and is responsible for all Requests made with its keys and its Users' accounts. The Licensor recommends enabling two-factor authentication.

5.3. The Customer keeps a current security notification email address in the Console; if none is set, notifications go to the Organisation owner.

6. Plans, trial period and limits

6.1. The features, the number of seats (Users and open invitations), the number of connections, the number of Requests per month, rate and concurrency limits, the Request log retention period and the price are set by the Plans. Use of the Service through API keys is not limited by seats but counts towards the Request limit.

6.2. Request counting. Every Request accepted by the Gateway after the key, subscription status and rate limit checks counts towards the monthly limit — including Requests later blocked by the Masking Policy or ending in a provider error, and masking API calls. Unmask calls, model list calls and the website demo do not count. The monthly window starts on the start date of the Subscription period.

6.3. Trial period. A new Organisation may receive a free trial for the period stated in the Plans (14 days at the date of this version) with the features and limits of the trial plan, and a starting credit to the Balance for Platform models. A trial is granted at most once per owner email address and per INN. If the Organisation's INN has already been used for a trial, the trial ends and the unspent starting credit is written off. The starting credit is not the Customer's money and is neither refunded nor paid out. When the trial ends, no paid subscription starts automatically; no card details are requested for the trial.

6.4. Plan changes. An upgrade to a higher plan is paid pro rata for the remaining part of the current Subscription period and takes effect on payment. A downgrade or a change of billing period takes effect at the start of the next Subscription period. A plan change is not possible while current usage (seats, connections) exceeds the limits of the new plan.

6.5. The Licensor may change the Plans. New prices do not apply to paid Subscription periods; for existing subscribers a price change applies only after at least 30 days' notice.

7. Prices and payment

7.1. The licence fee is paid in advance for the Subscription period (month or year) in roubles at the Plan prices. VAT is charged in the manner and at the rate set by the Tax Code of the Russian Federation and is shown in the invoice and the fiscal receipt. [LAWYER-REVIEW / accountant: tax regime, rate, use of the exemption.]

7.2. Payment methods: bank card, SberPay or the Faster Payments System (SBP) through the YooKassa payment service (NCO YooMoney LLC); bank transfer against an invoice. An invoice is payable within 7 calendar days of issue. To pay by invoice the Customer provides its details (name, INN, registered address). For every YooKassa payment the Customer receives an electronic fiscal receipt under Federal Law No. 54-FZ of 22 May 2003.

7.3. Payment is made when YooKassa confirms the payment or when the funds reach the Licensor's bank account.

7.4. Renewal. The next Subscription period is charged automatically only if auto-renewal is enabled, for which the Customer saved a bank card or SberPay and separately accepted the Recurring Payments Terms (/en/legal/recurring-payments). Without auto-renewal the Customer renews the subscription itself: a reminder with a payment link is sent 7 days before the period ends; Customers paying by invoice receive a renewal invoice 14 days before the period ends. SBP payments cannot be auto-renewed.

7.5. Grace period. If a renewal is not paid by the end of the Subscription period, access continues for a grace period of 7 days for card payments and 14 days for invoice payments, unless agreed otherwise. A new Subscription period paid during the grace period starts on the end date of the previous one (the grace days are part of the paid period). If no payment is received by the end of the grace period, access is suspended until payment.

7.6. Cancelling auto-renewal or the subscription in the Console takes effect at the end of the current paid Subscription period; the fee for the current period is not refunded.

8. Platform models and Balance

8.1. Platform models are available to an Organisation only after its owner or an administrator confirms in the Console that they have read the Platform models notice (the list of providers and the payment from the Balance). The version of the confirmed notice is recorded. The confirmation can be withdrawn; after that, Platform models are not served.

8.2. Providers. In the Russian region, Platform models are provided by Yandex.Cloud LLC (YandexGPT) and Sberbank PJSC (GigaChat) [LAWYER-REVIEW: counterparty names and whether the provider contracts permit giving access to third parties]. Request content is sent to the provider after masking; the providers process it as engaged parties under the Personal Data Processing Instruction. Requests to YandexGPT are sent with an instruction not to log request data, where the provider supports it.

8.3. Payment. Usage is paid from the Balance at the prices per million tokens (input, output and cached tokens) shown in the Console for each model. If the provider does not report token counts, they are estimated from the volume of text sent and received. If the client disconnects, the Gateway keeps receiving the provider's response for up to 30 seconds to determine the actual volume; the volume consumed at the provider is payable.

8.4. Reservation and debt. While a Request is processed, an amount based on the output token limit is reserved. The Request is rejected if the Balance, taking reservations into account, is insufficient. The Balance may become negative by the credit limit set by the Licensor (0 by default) and by the difference between actual and estimated cost; the debt is covered by the next top-up.

8.5. A Balance top-up is an advance payment for Platform model access services. Trial starting credits are not refundable. Refunds of the unspent paid remainder follow Section 15.

8.6. Availability of Platform models depends on provider quotas; the Licensor may limit the rate and concurrency of Requests to them, including per Organisation.

9. Own connections

9.1. When using an Own connection, the Customer concludes its own contract with the model provider, determines the provider's data processing terms and is responsible for the lawfulness of transferring data to it.

9.2. The Customer may not use the Service to send Requests to providers that do not provide services in the Russian Federation or to circumvent restrictions established by law. The Service blocks known addresses of such providers. To connect an arbitrary OpenAI-compatible endpoint, the Customer confirms in the Console that the endpoint is under its control or belongs to a provider lawfully serving the Russian Federation, and that the Customer has filed a cross-border transfer notification (Article 12 of the PD Law) where one is required.

10. Personal data and roles of the parties

10.1. The Customer is the personal data operator for Request content and Request metadata; the Licensor processes them on the Customer's instruction under the Personal Data Processing Instruction (/en/legal/dpa), which forms part of the Agreement and is accepted together with the Offer.

10.2. For account, billing and enquiry data the Licensor is an independent operator and processes them under the Policy (/en/legal/privacy).

10.3. The Customer warrants that it has legal grounds for processing the personal data its Users and systems send to the Service, informs data subjects and obtains consents where required, and determines the Masking Policy and the model providers itself.

11. Masking limitations and residual risks

11.1. Masking is a risk-reduction measure, not a guarantee. No detector is 100% accurate. The "Baseline" policy template does not guarantee compliance with Federal Law No. 152-FZ; the Customer configures and tests the Masking Policy for its own data and obligations.

11.2. The Customer has been informed of the following residual risks:

  1. pseudonymised Requests remain personal data in context: the provider receives the surrounding text, and a combination of facts may allow a person to be identified;
  2. values of categories with the action "warn" or "allow" are sent to the provider unchanged;
  3. with the detector-error reaction "patterns only" (patterns_only), Requests for which name recognition is unavailable (an outage or exceeded limits) are processed without detecting personal and organisation names;
  4. personal and company names written without capital letters are not detected by the recognition model and are sent unmasked unless a dictionary or custom pattern covers them;
  5. unclassified provider request fields are only scanned, never masked: a detected value rejects the Request, but anything the detectors miss there (for example lowercase names, or names during a recognition outage under patterns_only) is sent as is;
  6. images, documents and audio passed with the action "allow" are not masked;
  7. data sent to the provider (including masked data) is retained under the provider's rules; if the endpoint or the client application keeps conversation history, it is kept outside the Service;
  8. unmasking reveals all original values to the recipient of the response (and to anyone holding the restore token);
  9. semantic obfuscation (descriptive, indirect, paraphrased, encoded or deliberately distorted information) is not detected;
  10. with Platform models, Requests of different customers reach the provider under the Licensor's shared credentials, and provider-side prompt caching creates a theoretical response-timing side channel: a faster response may suggest that the same initial fragment of a Request was sent recently.

11.3. Model output is untrusted. The Gateway restores original values in the model's response, including links and tool-call arguments. Instructions injected into the context (prompt injection) can make a model place restored values in a link, an image address or a tool call. Customer applications that render the response as markup or execute tool calls must treat model output as untrusted data.

12. Customer obligations and restrictions

The Customer shall:

  • use the Service in accordance with Russian law and the Agreement;
  • not send through the Service data that it may not lawfully process, and not use the Service to re-identify individuals;
  • not attempt to circumvent Service limits, access other customers' data, disrupt the Service, or run load tests or vulnerability scans without the Licensor's written consent;
  • not reproduce, decompile or modify the Service except where expressly permitted by law;
  • pay for the use of the Service on time;
  • keep its contact details in the Console current, including the security notification address.

13. Licensor obligations

The Licensor shall:

  • provide access to the Service according to the plan, except for planned maintenance (which the Licensor announces in advance where possible) and circumstances beyond the Licensor's control;
  • apply the data protection measures described in the Personal Data Processing Instruction;
  • notify the Customer of incidents affecting its data no later than 12 hours after detection;
  • provide technical support within the plan at {{RU_SUPPORT_EMAIL}} [LAWYER-REVIEW: support procedure and response times per plan].

A service level agreement (SLA) with guaranteed availability and service credits is concluded only as a separate document. [LAWYER-REVIEW: marketing materials mention a 99.9% SLA — this Offer contains no such guarantee.]

14. Suspension, Organisation deletion and termination

14.1. The Licensor may suspend access if the Customer breaches Section 9 or 12, if the security of the Service is threatened, or at the request of competent authorities, notifying the Customer where permitted.

14.2. The owner can delete the Organisation in the Console. The subscription then ends, saved payment methods and unpaid invoices are cancelled and API keys are revoked. After 30 days the Organisation's operational data (Request log, policies, keys, connections, etc.) are irreversibly deleted. Payment documents are kept for 5 years after the end of the year of the last payment as required by law.

14.3. If the Organisation's subscription has ended or expired and is not renewed within 180 days, the Organisation is deleted; the owner is notified 14 days in advance.

14.4. The Agreement remains in force until the Organisation is deleted. Either party may withdraw from the Agreement by notifying the other; the Customer does so by deleting the Organisation or by email to {{RU_SUPPORT_EMAIL}}.

15. Refunds

15.1. The fee for the current Subscription period is not refunded (in whole or pro rata) when the subscription is cancelled or the Organisation is deleted.

15.2. A payment received a second time for an already paid period, after the Organisation was deleted, or under an outdated quote for a plan change is refunded in full: a YooKassa payment automatically by the same method, an invoice payment to the Customer's bank account.

15.3. The unspent paid part of the Balance (excluding starting credits) is refunded on the Customer's written request during the retention period of payment documents, less any debt. A full refund of the payment for the current Subscription period (if the Licensor agrees to it) ends access.

15.4. Money paid through YooKassa is refunded by the same method with a refund receipt; money paid by invoice is refunded to the Customer's bank account.

16. Liability

16.1. The parties are liable under Russian law. The Licensor is not liable for the Customer's lost profits and indirect losses, for the actions of model providers and Own connections, for the consequences of Masking Policy settings chosen by the Customer, or for undetected values within the limitations set out in Section 11.

16.2. The Licensor's total liability under the Agreement is limited to the fees paid by the Customer for the 12 months preceding the event giving rise to liability. The limitation does not apply to intentional breach (Article 401(4) of the Civil Code). [LAWYER-REVIEW: amount and enforceability of the cap.]

16.3. The parties are released from liability for non-performance caused by force majeure.

17. Confidentiality

The parties keep confidential any non-public information received from each other, including credentials, Masking Policy settings and security information, and disclose it only as provided by law or the Agreement.

18. Changes to the Offer

18.1. The Licensor may change the Offer. A new version with a new version identifier is published at /en/legal/terms; Organisation owners are notified by email at least 30 days before the changes take effect, except for changes required by law.

18.2. Continued use of the Service after the changes take effect means the Customer accepts them. If the Customer disagrees, it may withdraw from the Agreement before the changes take effect.

19. Closing documents

The current version of the Service does not generate acts or universal transfer documents (UPD) automatically. They are provided as follows: {{RU_CLOSING_DOCUMENTS_PROCEDURE}}. [LAWYER-REVIEW / accountant: define the procedure (for example, UPD on request or via an EDI operator; acceptance absent a reasoned objection within N days).]

20. Disputes and governing law

The Agreement is governed by the law of the Russian Federation. Disputes are first settled by a written claim; the response period is 30 days. Failing agreement, the dispute is referred to {{RU_COURT}}.

21. Licensor details

  • {{RU_OPERATOR_NAME}}
  • INN {{RU_OPERATOR_INN}}, KPP {{RU_OPERATOR_KPP}}, OGRN {{RU_OPERATOR_OGRN}}
  • Address: {{RU_OPERATOR_ADDRESS}}
  • Bank details: {{RU_OPERATOR_BANK_DETAILS}}
  • Email: {{RU_SUPPORT_EMAIL}}