Terms of Service (public offer)

Effective October 15, 2026.

If the English and Russian texts differ, the Russian text prevails.

1. General provisions#

1.1. These Terms of Service (the "Terms") are a public offer under Article 437 of the Civil Code of the Russian Federation. They are addressed to an indefinite group of persons and set the conditions on which the Contractor provides the Impact Relay service.

1.2. The Contractor is the person whose requisites are given in section 17.

1.3. The User is a legally capable individual aged 18 or over, or a legal entity or individual entrepreneur, who has accepted the Terms.

1.4. The Terms are accepted (acceptance under Article 438 of the Civil Code of the Russian Federation) at the earliest of: registering an account, the first top-up of the balance, or the first request to the API. From that moment the Terms are an agreement between the Contractor and the User.

1.5. The Terms use these definitions:

• Service — the website impact-relay.com and the API at api.impact-relay.com.
• Account — the User's account in the Service.
• API key — a secret key by which the Service recognizes the User's requests.
• Balance — the User's prepaid funds in the Service, counted in US dollars (credits).
• Model — an artificial intelligence model from a third-party developer that is available through the Service.
• Model Provider — the developer or owner of a Model, such as OpenAI, Anthropic, Google or xAI.
• Payment Provider — the organization that takes the User's payment: Lava (bank cards and SBP) or Heleket (cryptocurrency).

2. Subject of the agreement#

2.1. The Contractor provides the User with access to Models through one API and the Service's web interface. The Service receives the User's requests, passes them to the chosen Model, returns the result, keeps a record of usage and deducts the cost from the Balance.

2.2. The Service does not sell software, licenses, exclusive rights or other intellectual property. The Contractor does not develop the Models.

2.3. The Models, their names and trademarks belong to their owners. The Contractor is not a representative of the Model Providers and is not affiliated with them unless the Service states otherwise. Model names are used only to show which Model answers a request.

2.4. The list of available Models, their parameters and prices is on the Models page. The page is open without registration.

2.5. The User can connect their own accounts with Model Providers to the Service (BYOK). The documentation describes how. A Model Provider's terms may forbid this use. The User connects accounts at their own risk, and the Contractor is not responsible for what a Model Provider does to those accounts.

3. Account#

3.1. To use the Service you register with an e-mail address and a password, or sign in with GitHub or Google. Telegram can be linked to an existing account. The User gives accurate information and keeps it up to date.

3.2. The User confirms that they are 18 or over and legally capable. If they act for an organization, they confirm that they may enter into the agreement on its behalf.

3.3. The User keeps their password and API keys secret. Everything done with the Account and the API keys is treated as the User's own actions. If a key is compromised, the User revokes it in the dashboard at once and tells the Contractor. We recommend turning on two-factor authentication.

3.4. One User, one Account. Do not create extra accounts to get around a block or a limit, or to claim bonuses again.

3.5. The User can stop using the Service at any time. To delete the Account, write to the e-mail address in section 17. The remaining Balance is refunded under section 7. Payment records are kept where the law requires it (see the Privacy Policy for details).

4. Prices and the Balance#

4.1. The service is paid from the Balance. The cost of a request is the number of tokens processed times the Model's price per token, plus the cost of any additional tools, such as web search. Prices are on the Models page in US dollars and apply at the time the request is run.

4.2. Before a request runs, the Service may reserve on the Balance an amount that covers its expected maximum cost. After the request, the actual cost is deducted and the unused part of the reserve is released. If the Balance is too small, the request is rejected. In rare cases the actual cost exceeds the reserve and the Balance goes slightly negative. The next top-up first covers that difference.

4.3. The Balance is a prepayment for the Service. It is not a deposit, a bank account or electronic money, it earns no interest, and it cannot be transferred to another person or used to pay for anything outside the Service. The Balance does not expire.

4.4. The Contractor may grant bonus (promotional) credits, for example for actions named in the Service. Bonus credits are not the User's money, are not refunded and cannot be exchanged for money. They may be cancelled if they are abused.

4.5. The Contractor may change prices and the list of Models. New prices apply to requests run after they are published. Top-ups already credited are not recalculated.

4.6. The Contractor charges nothing for a top-up except the exchange-rate markup when paying in rubles (clause 5.3). A bank or a blockchain network may charge its own fee. For a cryptocurrency payment the sender pays the network fee.

5. Topping up the Balance and payment#

5.1. The Balance is topped up by bank card (Visa, Mastercard, Mir) or through the Faster Payments System (SBP) in rubles via the Payment Provider Lava, or by cryptocurrency via the Payment Provider Heleket. The available methods, coins and networks can change. The current set is shown in the top-up form.

5.2. The User enters the top-up amount in US dollars and chooses a payment method. The Service creates an invoice and shows the exact amount to pay. By card or SBP the User pays on the Payment Provider's page; by cryptocurrency, with a transfer to the address shown. The minimum and maximum amount of one top-up are shown in the top-up form.

5.3. The ruble amount is calculated at the Bank of Russia rate plus a markup that is shown in the payment form. The rate and the amount are fixed when the invoice is created and do not change. An invoice is valid for a limited time, shown on the payment page. An unpaid invoice closes by itself, and nothing is charged.

5.4. The Payment Provider processes the payment. The User enters card details on the provider's page: the Contractor does not receive or store them. The User's relationship with a Payment Provider is governed by the provider's terms: Lava and Heleket.

5.5. The Balance is topped up by the invoice amount after the Payment Provider confirms the payment. Card and SBP payments usually take a few minutes; cryptocurrency payments take from a few seconds to 20 minutes, depending on the network. A payment counts as made when it is credited to the Balance.

5.6. Cryptocurrency payments follow extra rules:

• a blockchain transfer cannot be reversed;
• send the exact amount in one transaction, in the coin and network shown, to the address shown;
• if a transfer goes out on another network or in another coin, to another address or with a mistake in the details, the funds may be lost. The Contractor is not responsible for that, but will try to help where it can;
• if only part of the amount arrives, send the rest to the same address before the invoice expires;
• if too much arrives, the Balance is topped up by the invoice amount and the excess is returned on request;
• a payment that arrives after the invoice has expired is credited by hand, on request with the transaction ID;
• the Payment Provider may hold a payment for review. The funds are credited when the review ends, and you do not need to pay again.

5.7. A payment that looks wrong (the amount or the invoice does not match, the payment was returned, it arrived after the invoice closed) is checked by hand. The Balance is adjusted after the check.

5.8. The Contractor issues and sends the User a cash receipt or a self-employed receipt in the cases and in the way that the legislation of the Russian Federation sets.

6. Delivery of the service#

6.1. The service is provided electronically. Nothing is shipped, so delivery costs and delivery times do not apply.

6.2. Access to the Service opens right after registration. API requests need an API key from the dashboard. Paid funds can be used as soon as they are credited to the Balance.

6.3. The service for each request is rendered at the moment the Service returns the Model's answer. If a streamed answer is cut short, the cost is deducted for the amount actually delivered.

6.4. The request log and the history of Balance operations are available in the dashboard. The request log is kept for 90 days.

7. Refunds and cancelling a payment#

7.1. Unused balance. The User may at any time give up the service and ask for the unused part of the Balance that was topped up by payments to be refunded (Article 782 of the Civil Code of the Russian Federation, Article 32 of the Russian Federation Law "On Consumer Rights Protection"). Only the expenses actually incurred for the refund itself, such as a blockchain network fee, are deducted from the amount refunded.

7.2. How to ask for a refund. Write to the e-mail address in section 17 from the address on the Account, and give the payment ID (it is in the top-up history) and the way you want to be refunded. For security the Contractor may check that the Account owner is the one asking.

7.3. Where and when. The money goes back by the same method and to the same details the payment came from: to the card or through SBP via the Payment Provider; cryptocurrency to the sender's address in the same coin and network. If that is not possible, the method is agreed with the User. The Contractor refunds the money within 10 days of receiving the demand (Article 31 of the Russian Federation Law "On Consumer Rights Protection"). How long the bank or the blockchain network takes to credit it does not depend on the Contractor.

7.4. Funds already spent. The cost of requests already run is not refunded: the service for them has been rendered in full.

7.5. Wrong charges and payments not credited. If a request fails through the Service's fault, the cost is charged twice, or a payment is confirmed but not credited to the Balance, the Contractor checks the request within 10 days and puts the amount back on the Balance, or refunds it in money under clause 7.3.

7.6. Bonus credits are not refunded and cannot be exchanged for money.

7.7. Cancelling a payment. An unpaid invoice can simply be left unpaid: it closes by itself and nothing is charged. A payment that went through is cancelled by a refund under this section. Before you dispute a payment with your bank, write to the Contractor: it is usually faster.

7.8. If the User closes the Account on their own initiative, the remaining Balance is refunded under this section. If the Contractor closes the Account, section 13 applies.

7.9. Nothing in this section limits the consumer's rights under the law.

8. Acceptable use#

8.1. The User uses the Service in line with the legislation of the Russian Federation, the legislation of the country where they are, and the rules of the Model Providers.

8.2. It is forbidden to use the Service:

• for activity the law forbids: laundering of criminal proceeds, financing of terrorism, evading sanctions, fraud, pyramid schemes, illegal trade in narcotics, weapons and counterfeit goods, illegal gambling;
• to create or spread material that contains sexual abuse of children, pornography, calls to terrorism, extremism, violence, ethnic, racial or religious hatred, or calls to other offences;
• for phishing, creating or spreading malware, hacking, denial-of-service attacks and unauthorized access to other people's systems;
• to infringe the rights of third parties, including intellectual property rights and rights to personal data;
• to impersonate another person or to give knowingly false information;
• to get around limits, technical restrictions and blocks, to create multiple accounts, or to overload the infrastructure on purpose.

8.3. The User is responsible for what their requests contain, for having the rights to the data they send, and for how they use the Models' answers. Personal data of third parties may be sent in requests only where there is a lawful basis.

8.4. A Model's answers may be inaccurate, incomplete or wrong. They do not replace professional legal, medical, financial or other advice. The User checks the answers before relying on them.

8.5. The Contractor may check compliance with this section using request metadata, and may disclose information where the law requires.

9. Sanctions and payment checks#

9.1. The User confirms that they and, if they are an organization, their beneficial owners are not subject to sanctions that are in force in the Russian Federation or apply to the Contractor and the Payment Providers, and do not use the Service to evade sanctions.

9.2. The Balance must be topped up with the User's own funds of lawful origin.

9.3. To counter the laundering of criminal proceeds and the financing of terrorism, and at a Payment Provider's request, the Contractor may ask the User for information and documents about their identity, the source of funds and the purpose of using the Service. Until it has the answer, the Contractor may hold the crediting of a payment, suspend use of the Service, refuse an operation or return the funds to the sender. Refusing to provide the information is grounds for refusing an operation or for suspension.

9.4. A Payment Provider may hold or reject a payment on its own. The Contractor does not control the providers' decisions, but will help the User with an appeal.

9.5. Information about the User and their payments may be passed to state authorities and Payment Providers in the cases the law provides.

10. Availability and limits#

10.1. The Service is provided "as is" to the extent the law allows. How the Service works depends on third parties: Model Providers, communication networks and Payment Providers. The Contractor does not guarantee uninterrupted operation, response speed or the constant availability of a particular Model.

10.2. The Service may set limits on how often requests are made and on context size. Models can change, be replaced and be withdrawn. If a Model is withdrawn, the Balance stays: it can be spent on other Models or refunded under section 7.

10.3. The Contractor may carry out planned and unplanned maintenance. The reason a request was refused is shown by the API error code (error codes).

11. Data#

11.1. Personal data is processed under the Privacy Policy.

11.2. The Contractor does not store the text of requests and answers. They are passed to the chosen Model's Provider and processed under its terms, as a rule outside the Russian Federation. Do not send through the Service anything that must not be passed to third parties.

11.3. The Contractor stores usage metadata: the time, the Model, the number of tokens, the cost and the status of the request.

12. Intellectual property#

12.1. The rights to the content of requests stay with the User. The rights to results are set by the law and by the Model Provider's terms. The Contractor claims no rights to results and does not use requests and answers to train models.

12.2. The website, the interface, the Service's software, the documentation, the design, and the name and logo of Impact Relay belong to the Contractor. The User gets a non-exclusive right to use the Service for its intended purpose for the term of the agreement. These may not be copied or reproduced without the Contractor's consent.

12.3. The names and trademarks of the Models and the Model Providers belong to their owners.

12.4. A rights holder who believes their rights are infringed can write to the e-mail address in section 17. The Contractor will consider it and take the steps the law requires.

13. Suspension and termination#

13.1. The User may stop using the Service at any time.

13.2. The Contractor may suspend access, revoke API keys or delete an Account if the Terms are breached, if the law or a Payment Provider requires it, on suspicion of fraud, or if security is at risk. The Contractor gives warning in advance unless harm has to be stopped at once.

13.3. If an Account is closed because the Terms were breached, the unused Balance is refunded under section 7. The Contractor may deduct from it any sums owed to the Contractor as damages or as a debt. If the law, a Payment Provider or a public authority requires otherwise, the funds are returned only to the sender of the payment or in the way they set.

13.4. Termination does not release the parties from obligations that arose before it.

14. Liability#

14.1. The parties are liable to each other under the legislation of the Russian Federation.

14.2. The Contractor is not responsible for:

• the content and accuracy of a Model's answers and what follows from using them;
• the actions of Model Providers, Payment Providers, banks and blockchain networks;
• losses from the User's own mistakes: the wrong network, address or amount, lost keys, third parties getting into the Account;
• lost profit and indirect losses;
• failures at third parties, and force majeure, including sanctions, government action, cyberattacks and network outages.

14.3. The Contractor's total liability under the agreement is limited to the amount the User actually paid for the services in the three months before the event that gave rise to the liability. This limit applies to the extent the law allows, and does not cover liability for intent or consumer rights that the law does not allow to be limited.

14.4. The User compensates the Contractor for losses that arise from the User's breach of the Terms, including claims by third parties and penalties imposed by Payment Providers.

15. Changes to the Terms#

15.1. The Contractor may change the Terms. The new version is published on this page with a new date and takes effect when published. For material changes the Contractor will, where it can, tell the User by e-mail or in the dashboard.

15.2. If the User keeps using the Service after the changes take effect, they accept the new version. If they disagree, they stop using the Service and are refunded under section 7. Changes do not affect services already rendered.

16. Governing law and disputes#

16.1. The agreement is governed by the law of the Russian Federation.

16.2. The parties try to settle a dispute by negotiation. A claim must be sent in writing to the e-mail address in section 17. The Contractor answers a demand for a refund within 10 days and other claims within 30 days. For Users who are not consumers, the claim procedure is mandatory.

16.3. If a dispute is not settled, a court decides it under the legislation of the Russian Federation. A consumer may sue at their place of residence or at the place where the agreement was made or performed (Article 17 of the Russian Federation Law "On Consumer Rights Protection").

16.4. The Russian text of the Terms prevails. The English text is given for convenience.

17. Contacts and requisites#

Name

Not specified

Legal status

Not specified

Taxpayer ID (INN)

Not specified

Registration number (OGRN / OGRNIP)

Not specified

Address

Not specified

E-mail for support and requests

[email protected][email protected]

Telegram support

@impact_sup

Phone

Not specified

General questions can go to support in Telegram. Send refund demands, claims and personal data requests to any of the e-mail addresses above: that lets the Contractor check that the Account owner is the one asking. In your message give the e-mail address of the Account and the payment or request ID if the question concerns one.