Public offer

1. Definitions

Platform — the Smart Restaurant Cloud software suite: the web console, the till, the kitchen display, the staff and guest apps, the Telegram bots, the public API, and every update to them.

Restaurant (Tenant) — the legal entity or sole trader that holds an account on the Platform. One Tenant is one business; all of its branches live inside that account and never see another Tenant’s data.

User — an employee the Restaurant has added to the Platform: owner, manager, waiter, cashier, chef, storekeeper, accountant or order operator.

Guest — a customer of the Restaurant: someone who opens the QR menu, orders through the website or the app, or takes part in the loyalty programme. A Guest deals with the Restaurant, not with the Platform.

Plan — the monthly or annual charge for using the Platform. Current plans are published on the Pricing page and form an integral part of this offer.

Operator — the company that builds the Platform and provides the service; its details are in section 13.

2. What is offered

The Operator grants the Restaurant the right to use the Platform — software as a service (SaaS): the software runs on the Operator’s servers and is reached by the Restaurant over the internet. The Restaurant pays for the Plan it has chosen.

The subject is software only. The Operator does not cook, sell or deliver food, and is not a party to the Restaurant’s obligations towards a Guest. The quality, composition, price and delivery time of a dish are the Restaurant’s responsibility.

The service is provided to the extent of the functionality published. That functionality is listed on the Product and Pricing pages; a module outside the chosen Plan is not enabled.

The Operator develops the Platform continuously. Adding new functionality does not imply removing existing functionality: if an existing function is to be withdrawn, at least 90 days’ notice is given.

3. Acceptance of the offer

Under article 369 of the Civil Code, acceptance is made by any of the following: registering on the Platform, signing in for the first time to an account opened by the Operator, completing onboarding, or paying for a Plan.

From the moment of acceptance the contract is treated as concluded in writing and binds both parties. A separate paper contract is not required; at the Restaurant’s request it is signed carrying the text of this offer.

Whoever accepts confirms that they are authorised to act for the Restaurant. If acceptance is found to have been made without authority, the Operator suspends the account and restores both parties to their original position.

When the terms change, the new revision is published on this page. Changes that matter to the Restaurant — price, limitation of liability, how data is handled — are announced at least 30 days in advance by email and by a notice in the console. A Restaurant that does not agree may terminate within that period under section 11.

4. Plans and payment

Current plans and what each includes are published on the Pricing page. The price depends on the number of branches: every active branch on the Platform counts.

The billing period is a month or a year, at the Restaurant’s choice. Annual payment carries a discount and fixes the price for a year from the date of payment.

Prices are stated in Uzbek soum. Value added tax is charged as required by law and shown as a separate line on the invoice.

Payment is due within 10 (ten) calendar days of the invoice date. Invoices are issued electronically.

Late payment has two steps. Fourteen days after the due date the account becomes read-only: data stays fully visible and exportable, but no new order, payment or shift can be entered. Thirty days after the due date the service is suspended. Both steps are taken with at least 3 days’ warning.

Moving to a larger plan takes effect immediately, with the difference charged pro rata for the remainder of the period. Moving to a smaller plan takes effect from the next billing period.

The trial is 14 days, with full functionality, free and without a bank card. When it ends the account is not moved onto a paid plan automatically: the Restaurant confirms the payment itself.

5. Obligations of the parties

The Operator undertakes to: run the Platform at the availability level set out in section 7; back up data at least once a day; respond to a report that the service is down within 4 hours on working days; give advance notice of planned maintenance and material changes; and process data within section 6 and the Privacy policy.

The Restaurant undertakes to: keep its credentials — passwords, PINs, device tokens — confidential; grant each employee only the permissions their work requires and disable the account of anyone who leaves; be responsible for the accuracy and lawfulness of the data it enters; obtain for itself any consent needed to process Guest data; and pay for its Plan on time.

The Restaurant must not: decompile or reverse-engineer the Platform; resell, sublicense or present it under its own name; send bulk automated requests or run load tests without agreement; attempt to reach another Tenant’s data; or sell goods or services prohibited by law through the Platform.

Where unlawful activity or a threat to the stability of the Platform is found, the Operator may suspend the account without prior notice. In that case the reason is given in writing within 24 hours.

6. Ownership of data and export

All data the Restaurant enters on the Platform — menu, orders, customer base, employee records, financial reports, documents — remains the property of the Restaurant. The Operator claims no ownership of it.

Guest and employee data is processed by the Operator on the Restaurant’s instruction. It is not sold, not used for advertising and not passed to third parties — other than as required by law and to the service providers named individually in the Privacy policy.

The Restaurant may export its data at any time in machine-readable form (CSV and JSON). Export is available in the console and costs nothing extra.

After the contract ends or is terminated, the data stays available for export for 30 (thirty) days. After that period the data is deleted together with every backup and cannot be restored. A certificate of deletion is issued on request.

The Operator may use aggregated, de-identified figures to improve the service — only to a degree that identifies neither a particular restaurant nor a particular person.

7. Availability

The target availability is 99.5% per calendar month. Planned maintenance and outages outside the Operator’s control (internet provider, power supply, force majeure) are excluded from the calculation.

Planned maintenance runs between 03:00 and 05:00 Tashkent time and is announced at least 48 hours in advance by email and by a notice in the console. Urgent security updates are the exception; notice is given as far in advance as possible.

The till keeps working when the connection drops: orders, payments and the shift are stored on the tablet and sent to the server once the connection returns. This is part of the Platform, not a separate product, and it does not count towards availability.

Where monthly availability falls below 99.5%, a credit against the following month is granted on the Restaurant’s written request: 10% of the monthly charge for each incomplete 1%, capped at 50% of the monthly charge. Requests are made within 30 days of the end of the month in question.

8. Limitation of liability

The Operator’s total liability on any claim under this contract does not exceed the Plan charge paid by the Restaurant for the 1 (one) month preceding the date the claim arose.

The Operator is not liable for indirect loss: lost profit, a fall in customer numbers, damage to reputation, or the Restaurant’s obligations to third parties.

The Operator is not liable for loss caused by the Restaurant’s own acts: a price or recipe card entered incorrectly, excessive permissions granted to an employee, a disclosed password or PIN, or a fault in third-party hardware the Restaurant has chosen.

These limits do not apply to loss caused by the Operator intentionally or through gross negligence, nor to liability that cannot be limited by law.

9. Fiscalisation

A receipt is fiscalised under the Restaurant’s own contract with a fiscal data operator (OFD). The party to that contract is the Restaurant, not the Operator.

In this process the Platform is a technical instrument: it assembles the receipt data, submits it to the OFD and stores the response. The fiscal mark and the verification QR code come from the OFD and are printed on the receipt unchanged.

If the connection drops the receipt is queued and submitted within the 24-hour window the law allows. A reprinted copy carries the "NUSXA" mark and does not replace the fiscal document.

Responsibility towards the tax authority — recording the sale correctly, issuing the receipt, observing cash discipline, keeping the OFD contract in force — remains with the Restaurant.

10. Intellectual property

The Platform, its source code, design, trade mark and documentation belong to the Operator. Under this offer the Restaurant receives a right of use only — exclusive rights do not transfer and the licence may not be passed on.

The Restaurant retains all rights in its own content — logo, dish names and photographs, texts, customer base — and allows the Operator to display it solely in the course of providing the service. That permission ends with the contract.

The Operator uses the Restaurant’s name and logo in a customer list or as a case study only with written consent. Consent may be withdrawn at any time without giving a reason.

Improvements suggested by the Restaurant may be built into the Platform; rights in such improvements remain with the Operator, and this does not affect the Restaurant’s own content.

11. Termination

The Restaurant may terminate at any time, without giving a reason, through the console or by written notice. Termination takes effect at the end of the current billing period.

Refunds for a paid but unused period: on a monthly plan the current month is not refunded; on an annual plan the remaining whole months are refunded pro rata and the discount is recalculated.

The Operator may terminate on at least 60 days’ written notice. In that case the unused period is refunded in full and the export window is not shorter than 30 days.

Where payment is more than 30 days late, or the prohibitions in section 5 are breached, the Operator may terminate immediately.

However the contract ends, the 30-day export window in section 6 stays open and the limitation of liability in section 8 continues to apply.

12. Disputes and governing law

This contract is governed by the law of the Republic of Uzbekistan.

A dispute is first addressed through negotiation. A written claim is answered within 15 (fifteen) calendar days.

If no agreement is reached, the dispute is heard by the competent courts of the city of Termez in the manner established by law.

The Uzbek version of this document is the governing one. The Russian and English versions are provided for convenience; where the texts differ, the Uzbek text applies.

13. Operator details

The working name is "Smart Restaurant Campus" LLC. The registered name of the legal entity and its details are not confirmed yet, so the fields below are left empty: approximate details in a draft are worse than none at all.

For day-to-day questions and technical support, the phone, Telegram and email on the Contact page are live.