Terms of Service: Databases

1. General provisions

1.1. These Terms are Appendix No. 1 to Public offer in the current edition (hereinafter referred to as the “Offer”) and its integral part; Until version 3.0 comes into force, they supplement version 2.1 and apply to database orders from September 25, 2026. The terms are used in the meanings defined in the Offer and User Agreement. In terms of databases, the Terms take precedence over the general provisions of the Offer.

1.2. The Contractor provides the Customer with a managed PostgreSQL database (hereinafter referred to as the “Database”). The service includes creating a Database, connecting it to Service projects and over the network, setting up roles and rights, monitoring, backup within the selected options, and deletion.

1.3. The databases are located on the territory of the Russian Federation (Moscow): general - in the infrastructure of Yandex.Cloud LLC, dedicated - in the infrastructure of Timeweb LLC. The Contractor has the right to involve these and other subcontractors, while remaining responsible for their actions to the Customer.

2. Types of databases

2.1. Shared database is located on a common server with the databases of other customers with access control. Included in the Pro plan: one shared database per organization; The disk capacity and number of stored backup copies are indicated in the control panel and on the “Plans” page. There is no separate fee for the shared database. When the space runs out, writing to the Database stops, reading continues to work.

2.2. Dedicated database - a separate PostgreSQL cluster with the configuration selected by the Customer (processor, memory, disk). Paid separately from the plan, according to the rules of sections 3–7, and is available at any plan.

3. Order a dedicated database and payment

3.1. The price of the allocated database is indicated in rubles per calendar month in the order window before clicking the “Order for...” button. The price is fixed upon ordering and does not change until the configuration is changed by the Customer. VAT is not charged.

3.2. Acceptance of these Terms is by clicking the “Order for...” button in the order window. The account owner of the organization pays; payment - through the payment service YooKassa (LLC NPO YooMoney) with a linked payment method: bank card, SBP, T-Pay, SberPay, YooMoney or Alfa Pay.

3.3. Payment is preliminary, one calendar month in advance. When paying by card the amount per month freezes and is written off only after the Database is created and ready for use; If it was not possible to create a Database, the freeze is removed and the money is not debited. Other methods do not support freezing: the amount is debited upon ordering, and if it was not possible to create a Database, it is returned in full in the same way.

3.4. By clicking “Order for...”, the Customer agrees to the automatic monthly debiting of the price of the Database from the linked payment method until the Database is deleted or the renewal is refused. You can refuse at any time by deleting the Database or unlinking the payment method in the “Payment” section.

3.5. A receipt under 54-FZ is generated for each debit and return and is sent to the account owner’s email address. You cannot make a payment without an email address.

4. Renewal

4.1. Paid period - calendar month from the date of charge; the next one begins on the same day of the next month (if there is no such day in the month, on its last day).

4.2. 6 days before the end of the period, the Contractor sends a letter about the upcoming charge. The first charge attempt is 3 days before the end of the period; if unsuccessful, repeat attempts - no more than once a day until the end of the period.

5. If payment fails

5.1. If payment has not been received by the end of the paid period, access to the Database is closed: connections and requests are terminated, the data is saved.

5.2. If payment is not received within 3 calendar days after the end of the paid period, the selected cluster is deleted along with the data. Before deleting, the Contractor tries to make a backup copy with the infrastructure provider, but its creation and safety is not guaranteed.

5.3. The Contractor informs about the closure of access and the upcoming deletion by letter. You can pay and return access at any time before deletion.

6. Change configuration

6.1. When switching to a more expensive configuration, the additional payment for the remaining days of the current period is written off immediately; from the next period the new price will apply.

6.2. When switching to a cheaper configuration, the new price is valid from the next period; the difference for the remaining days of the current period is not refunded. Refusal of the entire Database - under section 7.

6.3. Changing the processor and memory may be accompanied by a short-term restart of the Database; the order window warns about this before confirmation.

7. Deletion and refunds

7.1. The Customer has the right to delete the Database at any time in the control panel. The deletion is performed immediately after confirmation and is irreversible: data, roles, backups and connections to projects are deleted. Before deletion, the Customer can download the data - the backup copy can be downloaded as a regular PostgreSQL dump.

7.2. If the allocated Database is deleted before the end of the paid period, the Contractor returns the cost of unused days in the same way as payment was made, within 10 calendar days. The amount is calculated proportionally: the price of the month × the number of unused days ÷ the number of days in the period; half a day is considered unused. The refund does not exceed the amount paid.

7.3. If the Customer is a consumer, he has the right to refuse the service at any time and receive payment for the unused period in accordance with Article 32 of the Law of the Russian Federation “On the Protection of Consumer Rights”; clause 7.2 does not contradict this and describes the calculation.

8. Backups

8.1. Backup is enabled by the Customer in the Database settings; the schedule and number of stored copies are selected there within the limits specified in the panel. For the general database, copies are included in the plan within the limits specified in the panel. For a dedicated database, copies are made and stored by the infrastructure provider; This is a paid option, its price is shown in the panel before confirmation and is debited from the linked payment method.

8.2. Backups are deleted along with the Database. The Contractor does not store copies of deleted Databases.

9. Data in databases

9.1. The Customer independently determines what data is stored in the Database and is responsible for the legality of their processing. If there is personal data in the Database, the operator of this data is the Customer, and the Contractor processes it on behalf of the Customer on the terms Instructions for processing personal data (Appendix No. 2 to the Offer).

9.2. The Contractor's employees do not access the contents of the Database, except in cases where this is required by support at the request of the Customer, elimination of an incident, or a legal requirement of an authorized body.

10. Liability

10.1. The Contractor makes reasonable efforts to ensure continuous operation of the Bases, but does not guarantee the absence of interruptions. If the allocated Database is unavailable due to the Contractor's fault for more than 24 hours in a row, the Customer has the right to demand a proportionate reduction in price for the period of unavailability.

10.2. The Contractor is not responsible for data loss caused by the Customer’s actions (deleting the Database, requests, changing rights), non-payment (section 5) or the Customer’s refusal to back up.

10.3. If the Customer is a consumer, the limitations of liability established by the Offer and these Terms do not apply to him to the extent that they conflict with consumer protection legislation.