ENRU
Sign inGet started

Terms of Use

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/terms prevails.

1. Definitions

1.1. Service (Otapush) means the software system available at https://ota.aistastudio.ru: the website, the developer portal, the otapush command-line interface and the server implementation of the Expo Updates Protocol v1 intended for delivering OTA updates to mobile applications built with React Native and Expo.

1.2. Contractor means Общество с ограниченной ответственностью «СТУДИЯ АИСТА», OGRN 1267800056260, INN 7814865711, address: 197706, г. Санкт-Петербург, вн.тер.г. город Сестрорецк, ул. Всеволода Боброва, д. 30, литера А, помещ. 1-Н, офис 13.

1.3. User means a person who has registered an account in the Service.

1.4. Account means the User's record in the Service, created with an email address.

1.5. Application means a mobile application of the User registered in the Service. An Application owns channels, updates, API keys and a code-signing key pair.

1.6. Channel means a named distribution line for updates within an Application. Channel state is kept separately for iOS and Android.

1.7. Update means a build of JavaScript code and assets of an Application published by the User.

1.8. End User means a user of an Application whose device requests updates from the Service.

1.9. API key means a secret with which the command-line interface authenticates to the Service on behalf of an Application.

2. Status of the Terms

2.1. These Terms are a contract of adhesion (Article 428 of the Civil Code of the Russian Federation) and set out the rules for using the Service.

2.2. The Terms are accepted by completing registration, signing in to the account or actually using the Service (Article 438 of the Civil Code of the Russian Federation).

2.3. Paid services are provided under the public offer. In case of discrepancy between these Terms and the offer, the offer prevails.

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

3. Subject of the Terms

3.1. The Contractor grants the User the right to use the Service to publish OTA updates of its Applications and deliver them to End User devices within the selected plan.

3.2. The native expo-updates client in an Application requests the update manifest from the Contractor's server and downloads the build and assets. The Service documentation forms part of these Terms to the extent it describes how the Service works.

3.3. The Service records device requests: update check, download and launch events. These records are used to build statistics in the portal and to count unique devices per calendar month (MAU), on which the Service is billed.

3.4. The Contractor is not a party to the relations between the User and End Users.

4. Account

4.1. An account is created with an email address, a name and a password of at least eight characters. The password is stored only as an irreversible hash.

4.2. Email address confirmation is not implemented in the Service: the account is created immediately. The User undertakes to provide a valid address and maintain access to it: legally significant notices and fiscal receipts are sent to it.

4.3. There is no automatic password recovery in the portal. Access is restored on request to otapush@aistastudio.ru from the email address of the account.

4.4. The User is responsible for keeping the password and API keys secure. All actions performed with them are deemed performed by the User. A portal session is valid for 30 days from sign-in.

4.5. Sharing access to the account with third parties is not permitted. The User may issue separate API keys to its build systems.

5. Rules of use

5.1. The User must not:

  • violate the legislation of the Russian Federation or the rights of third parties;
  • attempt unauthorised access to the Service, other users' Applications and data, or circumvent plan limits and protection mechanisms;
  • create load in excess of normal use of the Service;
  • publish malicious code or code whose purpose is contrary to law through the Service;
  • deliver executable native code through the Service bypassing app store update mechanisms (Section 9);
  • resell access to the Service to third parties without the Contractor's written consent;
  • impersonate another person or organisation;
  • send to the Service, in deviceId or other Application request parameters, personal data of End Users, including email addresses, names and phone numbers.

5.2. The User determines the content of published updates and is responsible for the lawfulness of their distribution.

5.3. The Contractor may, without prior notice, suspend delivery of an update that in the Contractor's opinion violates clause 5.1.

6. Updates published by the User

6.1. The rights to the content of updates belong to the User. The Contractor stores and delivers them to provide the services and acquires no rights to them.

6.2. Publishing an update points the channel of the selected platform to the new build. A rollback returns the channel to the previous update; rolling back past the first published update returns devices to the build embedded in the store app.

6.3. A rollback applies only to the current update of a channel.

6.4. Deleting an Application deletes all its channels, updates, API keys, stored builds and statistics. End User devices stop receiving updates and stay on the last downloaded build. The action is irreversible.

6.5. The User keeps its own copies of published builds. Backing up Service data is not an obligation of the Contractor.

7. Code-signing keys and API keys

7.1. When an Application is created, the Service generates a code-signing key pair. The private key is stored on the Contractor's server and is not issued to the User or third parties; the User embeds the public key and the self-signed certificate in the build of its app.

7.2. Updates are signed with the private key of the Application. Signature verification is performed by the expo-updates client on the End User's device if the User has enabled it in its build.

7.3. An API key is shown once when created. The Contractor stores only its SHA-256 hash and prefix and cannot show the key again.

7.4. Safekeeping of API keys issued to the User's build systems and their timely revocation are the User's responsibility.

8. End User device data

8.1. End User devices are identified by the deviceId identifier set and sent by the Application. The Contractor does not generate or verify this identifier and does not link it to the identity of an End User.

8.2. The operator of the End Users' personal data is the User. The Contractor does not accept instructions to process this 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).

8.3. The lawfulness of processing End User data, obtaining their consents, informing them, 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 User.

8.4. Requests from End Users received by the Contractor are forwarded to the User.

9. App store rules

9.1. The User ensures on its own that the OTA updates it releases comply with App Store and Google Play rules. The "App store policies for OTA updates" page is for reference only and is not legal advice.

9.2. Only interpreted code may be delivered through the Service: JavaScript builds and related assets. Delivery of native executable code (.dex, .jar, .so and similar) is prohibited.

9.3. The Contractor is not responsible for decisions of app stores regarding the User's apps.

10. Plans and paid services

10.1. The Service is available on a free plan with the limits stated on the pricing and billing page.

10.2. Paid plans, payment, renewal, withdrawal and refunds are governed by the public offer.

10.3. The limit on the number of Applications applies when a new Application is created.

11. Service availability

11.1. The Service is provided "as is". The Contractor does not warrant uninterrupted or error-free operation of the Service or its fitness for the User's purposes.

11.2. No service level agreement (SLA) has been concluded.

11.3. The Contractor may suspend the Service for maintenance and change its functionality.

12. Ending use

12.1. The User may stop using the Service at any time. Applications are deleted by the User in the portal.

12.2. Automatic account deletion is not implemented in the portal. An account is deleted on request to privacy@aistastudio.ru from the email address of the account.

12.3. Before ending use, the User checks on its own that its apps do not depend on the delivery of updates by the Service.

12.4. The Contractor may, without prior notice, restrict access to the account and the Service if the User breaches these Terms or the public offer, if unauthorised access to the account is suspected, or at the request of government authorities. The grounds and procedure for terminating the contract are set out in Section 14 of the public offer.

13. Liability

13.1. The Contractor is not liable for the content of the User's updates, the consequences of installing them on End User devices or the User's decisions on the content of released updates.

13.2. The Contractor is not liable for indirect losses or lost profits, including those caused by downtime of the User's applications and services. The Contractor's liability is limited under Section 12 of the public offer.

13.3. The User shall compensate the Contractor for losses caused by a breach of these Terms, including amounts recovered from the Contractor by End Users, rights holders, app stores and government authorities, including administrative fines, and documented legal defence costs. For a User that is a legal entity or an individual entrepreneur, the representations, indemnity and penalty set out in Section 13 of the public offer also apply.

14. Personal data

14.1. Users' personal data is processed under the Privacy Policy.

14.2. By registering in the Service, a User who is an individual gives consent to the processing of personal data.

14.3. Web analytics is enabled only after the website visitor's consent given in the cookie banner (Section 7 of the Privacy Policy).

15. Changes to the Terms

15.1. The Contractor may unilaterally change these Terms. A new revision is published on this page with its number and date and takes effect upon publication.

15.2. Continued use of the Service after a new revision is published means the User's agreement with it. The User monitors changes to the Terms on its own.

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 User 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, and a dispute with a legal entity or an individual entrepreneur by the Arbitrazh Court of Saint Petersburg and the Leningrad Region.

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