Public Offer for Otapush Services

Saint Petersburg, Russia. Revision 1.0 of 30 September 2026, effective from the moment of publication at ota.aistastudio.ru

This English text is a translation. In case of discrepancy the Russian version at https://ota.aistastudio.ru/ru/offer prevails.

1. General provisions and definitions

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

1.2. Service (Otapush) means 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, intended for publishing and delivering OTA updates of mobile applications built with React Native and Expo.

1.3. Customer means an individual, a legal entity or an individual entrepreneur who has registered an account in the Service and accepted this offer. A Customer that is a legal entity or an individual entrepreneur is hereinafter the "Business Customer".

1.4. Application means a mobile application of the Customer registered in the Service and requesting updates from it.

1.5. Update means a build of JavaScript code and related assets published by the Customer in the Service and delivered to the devices of the end users of its Application.

1.6. End User means a user of the Customer's Application whose device requests updates from the Service.

1.7. MAU (monthly active users) means the number of unique devices that requested updates for the Customer's Applications from the Service during a calendar month, as determined under Section 6.

1.8. Plan means a set of quantitative limits and features of the Service whose price is stated in Section 4 and on the pricing and billing page.

1.9. Billing Period means the period for which payment has been made: a calendar month or a calendar year, at the Customer's choice.

1.10. The relations of the parties are governed by the law of the Russian Federation. The language of the contract is Russian.

2. Subject of the contract

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

2.2. The services comprise: storage of Updates published by the Customer, their delivery to End User devices over the Expo Updates Protocol v1, management of distribution channels, rollback of a channel to a previous Update, signing of Updates with the Application key and provision of device request statistics.

2.3. The exclusive rights to the Service belong to the Contractor. The Customer is granted the right to use the Service for its intended purpose during the term of the contract, without the right to transfer it to third parties.

2.4. The rights to the content published by the Customer through the Service belong to the Customer. The Contractor does not check, moderate or control the content of Updates.

2.5. The rules for using the Service are set out in the Terms of Use, which form an integral part of this contract. The Privacy Policy governs the processing of personal data for which the Contractor is the operator.

3. Conclusion of the contract

3.1. Acceptance of this offer is the performance by the Customer of any of the following actions: completing the registration of an account in the Service, signing in to the account, publishing an Update or paying for any paid Plan (clause 3 of Article 438 of the Civil Code of the Russian Federation). From the moment of acceptance the contract is deemed concluded in writing.

3.2. The Free Plan is provided free of charge. This offer applies to it except for the provisions on payment.

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

3.4. Services under the Enterprise Plan are not provided under this offer: their scope, price and settlement procedure are set out in a separate contract. Payment for the Enterprise Plan through the portal is not accepted.

4. Plans and prices

4.1. Current Plans:

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

4.3. The Contractor may unilaterally change the composition of the Plans and their prices by publishing the changes on the pricing page. The changes take effect upon publication and do not apply to Billing Periods paid before publication.

4.4. The limit on the number of Applications applies when a new Application is created. The MAU limit applies under Section 6.

5. Payment

5.1. Services are paid in advance for the selected Billing Period.

5.2. Payment methods:

• by bank card or through the Faster Payments System, on the Start, Pro and Business Plans;
• by invoice to a bank account, for Business Customers on the Pro and Business Plans.

5.3. Card and Faster Payments System payments are accepted by JSC "TBank". Bank card details are entered on the payment provider's page and are neither transmitted to nor stored by the Contractor.

5.4. A fiscal receipt is issued in accordance with Federal Law No. 54-FZ of 22 May 2003 and sent to the email address of the Customer's account.

5.5. The Customer's payment obligation is fulfilled when the Contractor receives confirmation of the payment from the payment provider, and for invoice payments, when the funds are credited to the Contractor's bank account.

5.6. The Plan is activated after the Contractor receives confirmation of a successful payment. Issuing an invoice does not by itself activate the Plan.

5.7. Services for each month of the Billing Period are deemed duly rendered and accepted by the Customer unless a reasoned claim is received from the Customer under Section 16 within 5 (five) business days after the end of that month. Service acceptance certificates are drawn up at the request of a Business Customer.

6. MAU accounting and exceeding the Plan limit

6.1. A device is counted as active in a calendar month from its first request to the Service for an Update of the Customer's Application; downloading an Update is not required. Repeated requests from the same device in the same month do not increase the count. Calendar months are counted in Coordinated Universal Time (UTC).

6.2. A device is identified by the deviceId identifier set and sent by the Customer's Application. The Contractor does not generate this identifier and does not link it to the identity of an End User.

6.3. The Contractor's accounting data is the sole basis for determining MAU. MAU across all Applications of the Customer is summed and shown in the portal.

6.4. Exceeding the MAU limit does not suspend delivery of Updates and is shown in the portal as a warning. No automatic additional charge is made for the excess.

6.5. If the Plan limit is exceeded systematically, the Contractor may offer the Customer a move to the appropriate Plan and, if the Customer refuses, restrict the services. The Contractor may notify the Customer of the restriction by email in advance.

7. Plan term and renewal

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

7.2. No automatic charges are made. To renew a Plan the Customer makes a new payment.

7.3. If the same Plan is paid for before the end of the current Billing Period, the Plan term is extended from the end date of the current period.

7.4. Paying for a different Plan before the end of the current Billing Period is a move to the new Plan: its terms and limits apply immediately after the payment is confirmed, and its term is extended from the end date of the previous period, without recalculation and without refund of the price of the previous Plan.

7.5. After the paid Billing Period expires, the Contractor may move the Customer's account to the Free Plan.

8. Termination by the Customer and refunds

8.1. The Customer may withdraw from the contract by sending a request to ivd@aistastudio.ru from the email address of the account. The request must allow the Customer and its account to be identified.

8.2. Only the price of services not rendered is refundable. Services for each started month of the Billing Period are deemed rendered in full. For annual payments, the part of the payment attributable to the full months of the Billing Period that have not started on the date the request is received is refunded, at one twelfth of the annual price per month.

8.3. Refunds are made within 10 (ten) business days of receipt of the request, by the same method and to the same details from which the payment was made. Bank and payment system fees withheld when the payment was made are not refundable.

8.4. No refund is made on a move to another Plan (clause 7.4) or on the Contractor's withdrawal from the contract due to the Customer's breach of this offer or the Terms of Use (clause 14.2).

8.5. The Customer may download the Updates it has published within 30 (thirty) days of the date the contract terminates; the data is then deleted. The Contractor is not obliged to keep the Customer's data after that period.

9. Service availability

9.1. The Service is provided "as is". The Contractor does not warrant uninterrupted or error-free operation of the Service, its conformity with the Customer's expectations or its fitness for a particular purpose.

9.2. No service level agreement (SLA) has been concluded. A reference to an SLA in a Plan description does not create any obligation of the Contractor as to availability of the Service or support response times until the parties sign a separate document.

9.3. The Contractor may suspend the Service for maintenance, and may notify the Customer of this in advance.

9.4. The Contractor may change the functionality of the Service.

9.5. The Contractor does not guarantee the preservation of Updates published by the Customer. The Customer keeps its own copies of published builds. Backing up Service data is not an obligation of the Contractor.

9.6. Failures of communication networks, equipment and software of the Customer and End Users, and decisions of app stores, are not a defect of the Contractor's service.

10. Obligations of the parties

10.1. The Contractor undertakes to:

• provide access to the Service within the paid Plan;
• not disclose the private code-signing keys of the Customer's Applications to third parties;
• process the personal data for which it is the operator in accordance with the Privacy Policy.

10.2. The Customer undertakes to:

• provide a valid email address and maintain access to it;
• pay for the services under Section 5;
• comply with the Terms of Use and not use the Service for unlawful purposes;
• ensure on its own the lawfulness of processing the data of the End Users of its Applications and the compliance of Updates with app store rules;
• not place in deviceId or other parameters sent by the Application to the Service any information that identifies an End User, including email addresses, names, phone numbers and other personal data;
• keep the account password and API keys secret. All actions performed with them are deemed performed by the Customer.

10.3. The Customer monitors changes to this offer and the Plans on the Service website on its own.

11. Personal data

11.1. The Contractor is the operator of personal data only with respect to the Customer's account data, payment details and the Customer's inquiries. Their processing is governed by the Privacy Policy.

11.2. The operator of the End Users' personal data is the Customer: it determines the purposes of processing and the data the Application sends to the Service. The Contractor does not accept instructions to process personal data and is not a person processing personal data on behalf of an operator (Part 3 of Article 6 of Federal Law No. 152-FZ of 27 July 2006).

11.3. The Contractor keeps records of device requests under the technical identifier set by the Customer's Application in order to account for the volume of services rendered and to provide statistics to the Customer. Obtaining End User consents, informing End Users, responding to their requests and filing notifications with the authority for the protection of the rights of personal data subjects are the responsibility of the Customer.

11.4. Requests from End Users received by the Contractor are forwarded to the Customer.

12. Liability

12.1. The Contractor is not liable for indirect losses or lost profits, including those caused by downtime of the Customer's applications and services. The Contractor's aggregate liability to the Customer, except for liability for intentional breach, is limited to the price of the services actually rendered to the Customer during the 1 (one) calendar month preceding the event giving rise to the losses.

12.2. The Contractor is not liable for the content of Updates published by the Customer, the consequences of installing them on End User devices, decisions of app stores regarding the Customer's Applications, or the Customer's compliance with personal data legislation. The Contractor is not liable for the consequences of delivering Updates, including in the event of unauthorised access to the Service or compromise of keys, if the Customer has not enabled update signature verification (clause 7.2 of the Terms of Use).

12.3. The Customer shall compensate the Contractor for losses caused by a breach of this offer or the Terms of Use, including amounts recovered from the Contractor by End Users, rights holders, app stores and government authorities, including administrative fines, and documented legal defence costs (Articles 15 and 393 of the Civil Code of the Russian Federation).

12.4. The parties are released from liability for non-performance caused by force majeure (clause 3 of Article 401 of the Civil Code of the Russian Federation), including acts of government authorities, failures of communication networks and failures of infrastructure providers.

13. Special terms for Business Customers

13.1. The Business Customer represents to the Contractor (Article 431.2 of the Civil Code of the Russian Federation) that on the date of acceptance and throughout the term of the contract:

• the person who accepted the offer is authorised to act on behalf of the Business Customer;
• the Business Customer has lawful grounds for processing the personal data of End Users, including for sending them to the Service to the extent determined by the Application;
• the Application does not send to the Service the information that clause 10.2 prohibits sending;
• Updates published through the Service do not infringe the rights of third parties, the legislation of the Russian Federation or app store rules.

The Contractor relies on these representations as material.

13.2. The Business Customer shall indemnify the Contractor for property losses (Article 406.1 of the Civil Code of the Russian Federation) arising from the inaccuracy of the representations in clause 13.1 or from claims brought against the Contractor by End Users, rights holders, app stores and government authorities in connection with the Business Customer's Applications and Updates or its processing of personal data, including administrative fines imposed on the Contractor and legal defence costs. The losses are indemnified regardless of the Business Customer's fault and regardless of the contract being held not concluded or invalid. This clause does not apply to losses resulting from the Contractor's own breach of the requirements for the protection of personal data for which it is the operator (Article 19 of Federal Law No. 152-FZ) or to administrative fines for such breaches.

13.3. For each breach of the representations in clause 13.1 and of the prohibitions in Section 5 of the Terms of Use, the Business Customer shall pay the Contractor a penalty of 10,000 (ten thousand) roubles. The penalty does not deprive the Contractor of the right to compensation for losses in excess of it.

13.4. The Contractor may withhold the penalty, losses and indemnity amounts from the funds refundable to the Business Customer or set them off against such funds (Article 410 of the Civil Code of the Russian Federation), notifying the Business Customer by email.

13.5. Disputes with a Business Customer are heard by the Arbitrazh Court of Saint Petersburg and the Leningrad Region.

14. Suspension and termination

14.1. The Contractor may, without prior notice, suspend the services and restrict access to the account, an Application or an individual Update if the Customer breaches this offer or the Terms of Use, if unauthorised access to the account is suspected, or at the request of government authorities.

14.2. In the event of systematic or material breaches, including publishing malicious code, infringing the rights of third parties and non-payment, the Contractor may unilaterally withdraw from the contract without refunding the price of paid services.

14.3. The Contractor may withdraw from the contract without giving reasons by notifying the Customer by email and refunding the price of services not rendered under Section 8.

15. Changes to the offer

15.1. The Contractor may unilaterally change this offer. A new revision is published on this page with its number and date and takes effect upon publication unless it specifies another date.

15.2. Continued use of the Service after a new revision is published means the Customer's agreement with it. If the Customer disagrees, it may withdraw from the contract under Section 8.

16. Claims and disputes

16.1. The pre-trial claim procedure is mandatory. Claims are sent to the Contractor at ivd@aistastudio.ru or in writing to the address in Section 17, and to the Customer at the email address of its account. A claim is considered within a reasonable time.

16.2. If no agreement is reached, the dispute is heard by the court at the Contractor's location, unless clause 13.5 provides otherwise.

16.3. Legally significant messages (Article 165.1 of the Civil Code of the Russian Federation) are sent to the Contractor at ivd@aistastudio.ru and to the Customer at the email address of its account. The risk of non-receipt due to an outdated address is borne by the party to which the address belongs.

17. Contractor details

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