Terms of use

Last updated: 12 October 2026

These terms cover Leron: Hana, the AI reservations manager for restaurants, the Leron dashboard, the booking pages we run for restaurants, and this website. They are written to be read in full, on a phone, in a few minutes.

1. Who we are

Leron makes Hana, an AI reservations manager for restaurants and restaurant groups. In these terms, Leron, we and us mean Leron Systems, operated by Pranav Gupta as a UK sole trader. A limited company is being registered to take Leron over, and when it has been we will name it here with its company number.

Our postal address is 188 Port Tennant Road, Swansea. You can reach us at pranav@leronsystems.com.

2. What these terms cover

These terms apply when you use this website, the Leron dashboard, or a booking page Leron runs for a restaurant. By using any of them, you agree to these terms.

A restaurant that uses Leron signs a service agreement with us, which sets out the service, the price, how it is paid, the term and how to end it. If that agreement and these terms disagree, the agreement wins.

Our privacy notice at /privacy explains how we handle personal data.

3. The service

Depending on what a restaurant switches on, Leron:

  • answers the calls a restaurant diverts to Hana, at any hour;
  • answers texts and WhatsApp messages, and drafts or sends replies to emails, in the restaurant's name;
  • takes, changes and cancels bookings, and sends guests confirmations, reminders and booking links;
  • runs a booking system for the restaurant, with its diary and table plan, and a booking page and booking widget;
  • takes card holds, deposits and prepayments on the restaurant's own Stripe account, under the policy the restaurant sets;
  • keeps guest profiles and booking history, and shows the restaurant's team every conversation on the dashboard.

Features change as we improve Leron. A restaurant's service agreement says what we provide to it.

4. Access and accounts

Access to the dashboard is by invitation. We set up each restaurant's account and the logins its team uses. You can request an invite from our demo page at /demo.

Keep your sign-in details to yourself, and tell us straight away if you think someone else has used them. You are responsible for what happens under your login. A restaurant is responsible for who on its team has access, and should tell us when someone leaves.

5. Hana is an AI

Hana works from the information a restaurant gives us: its opening hours, tables, menus, booking rules and policies. She can misunderstand a caller, mishear a detail, or give an answer that is out of date if the restaurant's information has changed. The restaurant's team should check the dashboard, and should keep its information with us up to date.

Hana passes on what guests tell her about allergies and dietary needs, but she is not a source of allergen advice. The restaurant remains responsible for the food it serves and the allergen information it gives.

Hana is not an emergency service and should not be relied on for anything urgent or safety-critical.

6. The restaurant's responsibilities

A restaurant that uses Leron is responsible for:

  • giving us accurate information, and telling us when it changes;
  • having a lawful basis for the guest data we handle for it, and a privacy notice that tells guests about Leron's part, which can link to our call recording notice at /privacy/calls;
  • keeping the recording notice on each phone line Hana answers;
  • sending news and offers only to guests who agreed to receive them;
  • any payments it takes from guests through its own Stripe account, including deposits, card holds, charges and refunds, and the terms it shows guests for them.

7. Guest data

A restaurant's guests are the restaurant's. For its guest data, the restaurant is the controller and Leron is its processor. We handle that data only to provide our service to that restaurant and on its instructions. We do not sell it, share it with another restaurant, or use it to market anything other than that restaurant.

We keep conversation history, including call recordings, until the restaurant or its guest asks us to delete it. The restaurant can ask us to delete its conversation history, or a named guest's records, at any time. When a restaurant stops using Leron, it chooses whether we delete or return its data.

8. If you are a guest

When you book through Hana or a booking page Leron runs, you are booking with the restaurant, not with Leron. The restaurant's own terms apply to your booking, including any deposit, card hold or cancellation policy it shows you before you book.

Nothing in these terms affects your rights as a consumer.

9. Acceptable use

You must not:

  • use Leron for anything unlawful, or to send messages people have not agreed to receive;
  • try to reach data or accounts that are not yours, or to get around the limits on the voice demo and booking pages;
  • interfere with the service, overload it, or scrape it with automated tools;
  • upload anything harmful, or content you have no right to use;
  • pretend to be someone else, or make bookings you do not intend to keep.

We may suspend access that breaks these rules.

10. Payments

A restaurant pays for Leron as its service agreement sets out, by Direct Debit through GoCardless.

When a restaurant asks a guest for a card or a payment, the payment is made on the restaurant's own Stripe account, and the restaurant is the seller. Leron does not take a share of it.

11. Other services we rely on

Leron runs on services from other companies, including telephone networks and providers of voice, messaging, email, AI and hosting. Our privacy notice lists them. We cannot promise that Leron will always be available, and we are not responsible for an outage at one of them. If Leron is unavailable, calls a restaurant diverts to Hana may go unanswered, so a restaurant should keep a way to reach its team.

12. Ownership

Leron owns the software, the dashboard, the booking pages and this website. A restaurant owns its own content, such as its menus, photographs and logo, and its guests' data, and lets us use them only to provide the service. If you send us feedback or ideas, we may use them without owing you anything.

13. Liability

Nothing in these terms limits liability for death or personal injury caused by negligence, for fraud, or for anything else the law does not allow to be limited.

Otherwise, for a restaurant that uses Leron, our total liability is limited as its service agreement sets out. We are not liable for lost profit or lost bookings caused by an outage at a provider we depend on, including the telephone network, or by information we were not given.

14. Ending access

A restaurant ends its use of Leron as its service agreement sets out. We may suspend or end a login that breaks these terms, or that puts the service or other people's data at risk.

15. Changes to these terms

We update these terms when Leron changes, and change the date at the top. A change does not alter a service agreement a restaurant has already signed.

16. Law

These terms are governed by the law of England and Wales, and the courts of England and Wales can hear any dispute about them. If you are a consumer living in Scotland or Northern Ireland, you can also bring proceedings in your local courts.

Questions about these terms: pranav@leronsystems.com. See also our privacy notice.

Back to home