Public Offer for Otapush Services

Effective date: 28 August 2026 · Applies from the moment of publication at ota.aistastudio.ru

1. General provisions and definitions

1.1. This document is a public offer (Articles 435 and 437 of the Russian Civil Code) by Общество с ограниченной ответственностью «СТУДИЯ АИСТА» (OGRN 1267800056260, TIN (INN) 7814865711, KPP 781401001, address: 197706, г. Санкт-Петербург, вн.тер.г. город Сестрорецк, ул. Всеволода Боброва, д. 30, литера А, помещ. 1-Н, офис 13) — hereinafter the "Operator" — to enter into a paid services agreement on the terms set out below.

1.2. The Service (Otapush) is the software system available at https://ota.aistastudio.ru, comprising the website, the developer portal, the otapush command-line interface and the server implementation of the Expo Updates Protocol v1. The Service is intended for publishing and delivering over-the-air (OTA) updates for React Native and Expo mobile applications.

1.3. The Customer is an individual, a legal entity or a sole proprietor who has registered an account in the Service and accepted this offer.

1.4. An Application is the Customer's mobile application registered in the Service and requesting updates from it.

1.5. An Update is a build of JavaScript code and accompanying assets published by the Customer in the Service and delivered to the devices of the end users of the Customer's Application.

1.6. MAU (monthly active users) is the number of unique devices that request updates for the Customer's Applications from the Service during a calendar month. Counting is defined in section 6.

1.7. A Plan is a set of quantitative limits and capabilities of the Service; its price is stated in section 4 and on the pricing and billing page.

1.8. A Billing period is the period paid for: a calendar month or a calendar year, at the Customer's choice.

1.9. The relations between the parties are governed by the law of the Russian Federation.

2. Subject of the agreement

2.1. The Operator undertakes to provide the Customer with access to the Service within the scope of the selected Plan, and the Customer undertakes to pay for those services on the terms of this offer.

2.2. The services comprise: storing the Updates published by the Customer, delivering them to end-user devices over the Expo Updates Protocol v1, maintaining release channels (dev, staging, prod and any others created by the Customer), rolling a channel back to a previous update, signing updates with the Application's key, and providing statistics on device requests.

2.3. Exclusive rights to the Service belong to the Operator. The Customer is granted the right to use the Service for its intended purpose for the term of the agreement; this right may not be transferred to third parties.

2.4. Rights to the content the Customer publishes through the Service (update code, application assets, names and other materials) belong to the Customer. The Operator does not inspect or moderate the content of updates.

2.5. The rules for using the Service that are unrelated to payment are set out in the Terms of Use, which form an integral part of this agreement.

3. Conclusion of the agreement

3.1. This offer is accepted by any of the following actions of the Customer: completing account registration in the Service, signing in to the account, publishing an update, or paying for any paid Plan (Article 438(3) of the Russian Civil Code). From the moment of acceptance the agreement is deemed concluded in written form on the terms of this offer; no paper signature is required.

3.2. The Free plan is provided at no charge and without any consideration from the Customer. The terms of this offer apply to it insofar as they do not concern payment.

3.3. Payment for any paid Plan constitutes the Customer's agreement with the revision of this offer in force on the date of payment.

3.4. Services under the Enterprise plan are not provided on the terms of this offer: their scope, price and settlement procedure are agreed by the parties in a separate contract. A request to pay for the Enterprise plan through the portal is rejected programmatically.

4. Plans and pricing

4.1. The current Plans are:

4.2. Prices are stated in Russian rubles and are final. НДС не облагается в связи с применением упрощённой системы налогообложения (п. 2 ст. 346.11 НК РФ).

4.3. The capabilities of each Plan are shown on the pricing page and on the "Billing" page of the portal. The Operator may change the composition of Plans and their prices. Such changes do not apply to Billing periods already paid for: services for those periods are provided on the terms in force on the date of payment.

4.4. The prices in clause 4.1 are provisional as of the publication date of this offer and are subject to confirmation before commercial operation of the Service begins. The current price is always published on the pricing and billing page and in the portal.

4.5. The limit on the number of Applications is enforced when a new Application is created. The MAU limit is applied as described in section 6.

5. Payment procedure

5.1. Services are paid for in advance for the selected Billing period — a calendar month or a calendar year. Annual payment is calculated at the rate stated in clause 4.1.

5.2. Payment methods:

• bank card (MIR, Visa, Mastercard) or the Faster Payments System (SBP) — for individuals and legal entities on the Start, Pro and Business plans;
• invoice by bank transfer — for legal entities on the Pro and Business plans. Invoice payment is not available on the Start plan and is rejected at checkout.

5.3. Card and SBP payments are processed by T-Bank JSC (internet acquiring). Bank card details are entered by the Customer on the payment provider's page; they are neither transmitted to nor stored by the Operator.

5.4. A fiscal receipt is generated by the payment provider in accordance with Russian Federal Law No. 54-FZ of 22.05.2003 and sent to the email address of the Customer's account.

5.5. The Customer's payment obligation is deemed performed when the Operator receives confirmation of the payment from the payment provider (for invoice payment — when the funds are credited to the Operator's bank account).

5.6. The Plan is activated automatically once the Operator receives confirmation of a successful payment. For invoice payment the Plan is activated once the funds are credited; issuing an invoice alone does not activate the Plan.

5.7. Services are deemed duly rendered and accepted by the Customer if no substantiated claim has been received from the Customer during the Billing period in the manner set out in section 14. Service delivery certificates are issued at the request of a Customer that is a legal entity.

6. MAU counting and exceeding the plan limit

6.1. A device counts as active in a calendar month from its first request to the Service for an update to the Customer's Application. Checking for an update is sufficient; downloading the update is not required. Repeat requests from the same device within the same calendar month do not increase the counter. The counter resets on the first day of each calendar month.

6.2. A device is identified by the deviceId value sent by the Customer's Application. The identifier is set by the Application itself; the Operator neither generates it nor links it to the identity of an end user. If the Application does not send a device identifier, the request is not counted towards MAU, and the Service may reject the request depending on the server configuration.

6.3. MAU across all of the Customer's Applications is summed and displayed in the portal on the "Overview" and "Billing" pages.

6.4. Exceeding the MAU limit does not suspend the services. When the MAU included in the Plan is exceeded, the Service continues to serve update checks, downloads and installs as usual: delivery of updates to end-user devices is not blocked, throttled or otherwise restricted. The excess is shown in the portal as a warning suggesting an upgrade to a higher Plan.

6.5. The Operator does not charge automatically for MAU in excess of the Plan limit. Upgrading to a higher Plan is voluntary and takes effect immediately after payment; the new limit applies to the current calendar month.

6.6. Systematically exceeding the Plan limit entitles the Operator to propose that the Customer move to the corresponding Plan and, if the Customer refuses, to restrict the services on no less than 30 calendar days' prior notice. Updates continue to be delivered until that period expires.

7. Plan term and renewal

7.1. A paid Plan is valid until the end of the Billing period paid for. The end date is shown in the portal on the "Billing" page.

7.2. No automatic charges are made. The Operator does not store the Customer's bank card details and does not initiate recurring payments. To renew a Plan the Customer makes a new payment.

7.3. If payment is made before the current Billing period ends, the new period is appended to the remaining one: the Plan is extended from the end date of the current period rather than from the date of payment.

7.4. Once the paid Billing period expires, the Operator may move the Customer's account to the Free plan. Published updates, channels and Applications are preserved; delivery of updates continues within the Free plan, subject to clause 6.4.

8. Withdrawal and refunds

8.1. The Customer may withdraw from the agreement at any time by ceasing to use the Service.

8.2. Automatic subscription cancellation in the portal is not implemented as of the publication date of this offer. A withdrawal request is sent to privacy@aistastudio.ru from the email address of the Customer's account and is processed by the Operator manually.

8.3. A Customer who is an individual may withdraw from the agreement at any time upon reimbursing the Operator for the expenses actually incurred in performing it (Article 32 of the Russian Consumer Rights Protection Act, Article 782 of the Russian Civil Code). A refund is made for the unused part of the paid Billing period, pro rata to the remaining calendar days.

8.4. Refunds are made upon a request submitted as described in clause 8.2, to the same account or card the payment came from, within no more than 10 calendar days of receiving the request. There is no automated refund mechanism in the portal: the Operator initiates refunds manually through the payment provider.

8.5. The Operator may decline a refund for the part of the Billing period during which the services were actually provided, and where the agreement is terminated because the Customer breached the Terms of Use.

8.6. Termination of the agreement does not deprive the Customer of the right to export the updates they have published before the Applications are deleted.

9. Availability of the service and service level

9.1. The Service is provided "as is". The Operator takes reasonable measures to keep it running, but does not guarantee the absence of interruptions, errors or failures.

9.2. No service level agreement (SLA) has been concluded or published as of the publication date of this offer. The descriptions of the Business and Enterprise plans mention an SLA; the specific parameters — the guaranteed availability percentage, support response times, the compensation procedure — are agreed by the parties in a separate document and are not defined as of the publication date of this offer. Until such a document is concluded, the Operator's availability obligations are limited to this section, and any support response times are indicative only.

9.3. The Operator may carry out scheduled maintenance. The Operator gives advance notice of maintenance affecting the availability of the Service on the website or by email, except for emergency work.

9.4. The Operator may change the functionality of the Service. Such changes must not deprive the Customer of the capabilities included in the Plan they have paid for during the paid Billing period.

9.5. The Operator does not guarantee the preservation of the updates published by the Customer after the agreement is terminated and recommends that the Customer keep their own copies of the builds they publish. The procedure and frequency of the Operator's data backups are not disclosed and are not an obligation under this offer.

10. Obligations of the parties

10.1. The Operator undertakes to:

• provide access to the Service within the scope of the paid Plan;
• keep the private code-signing keys of the Customer's Applications confidential — they never leave the Operator's server;
• process personal data as set out in the Privacy Policy;
• notify the Customer of changes to the terms of service as described in section 13.

10.2. The Customer undertakes to:

• provide a valid email address and retain access to it: this address is used for legally significant notices and for fiscal receipts;
• pay for the services as described in section 5;
• comply with the Terms of Use and not use the Service for unlawful purposes;
• independently ensure the lawfulness of processing the data of the end users of their Applications and compliance with app store policies when shipping OTA updates;
• keep the account password and API keys secret and bear responsibility for actions performed with them.

11. Liability of the parties

11.1. The parties are liable for breaches of this agreement in accordance with the law of the Russian Federation.

11.2. The Operator is not liable for the content of the updates published by the Customer, for the consequences of installing them on end-user devices, for an app store rejecting the Customer's Application, or for the Customer's decisions about what to ship in an update.

11.3. The Operator does not compensate lost profit or losses caused by downtime of the Customer's own services, except where such limitation is not permitted by law. The aggregate liability of the Operator to a Customer that is a legal entity or a sole proprietor is limited to the amount actually paid by the Customer for the Billing period in which the grounds for liability arose.

11.4. The limitations in clause 11.3 do not apply to relations with a Customer who is an individual to the extent they conflict with the Russian Consumer Rights Protection Act.

11.5. The parties are released from liability for non-performance caused by force majeure, including acts of state authorities, failures of backbone communication networks and failures of infrastructure suppliers, where such circumstances directly prevent performance.

12. Personal data

12.1. The Customer's personal data is processed as set out in the Privacy Policy.

12.2. With respect to the device data of the end users of the Customer's Applications, the Customer is the personal data operator; the Operator processes that data on the Customer's instructions, to the extent necessary to deliver updates and count MAU. The division of responsibilities is described in section 5 of the Privacy Policy.

12.3. A Customer who is an individual gives consent to the processing of personal data when registering an account.

13. Amendments to the offer

13.1. The Operator may amend this offer. A new revision is published on this page with its effective date.

13.2. Amendments do not apply to Billing periods already paid for: services for those periods are provided on the terms of the revision in force on the date of payment.

13.3. Continued use of the Service after a new revision takes effect constitutes the Customer's agreement with it. If the Customer does not agree, they may withdraw from the agreement as described in section 8.

14. Dispute resolution

14.1. Before going to court, a party sends the other party a claim: to the Operator — at privacy@aistastudio.ru or in writing to the address stated in section 15; to the Customer — at the email address of their account. The deadline for responding to a claim is 30 calendar days from receipt.

14.2. If no agreement is reached, the dispute is heard by the court at the Operator's location. For disputes involving a Customer who is a consumer, this rule applies only insofar as it does not conflict with their statutory right to choose the court.

15. Operator details

• Operator: Общество с ограниченной ответственностью «СТУДИЯ АИСТА» (ООО «СТУДИЯ АИСТА»)
• OGRN: 1267800056260
• TIN (INN): 7814865711, KPP: 781401001
• Registered address: 197706, г. Санкт-Петербург, вн.тер.г. город Сестрорецк, ул. Всеволода Боброва, д. 30, литера А, помещ. 1-Н, офис 13
• Service website: https://ota.aistastudio.ru
• Contact address: privacy@aistastudio.ru
• Tax regime: НДС не облагается в связи с применением упрощённой системы налогообложения (п. 2 ст. 346.11 НК РФ)