1. WHO WE ARE

1.1 Our Identity

The Website, Trainhub.io, is owned and operated by AI Analytics And Integrations Limited (“AI Analytics” or the “Company”), a company incorporated in England and Wales under company registration number 12431111, with its registered office at 71-75 Shelton Street, London, WC2H 9JQ, United Kingdom.

‍All transactions processed through the Website will appear on your bank or card statement under the descriptor “TRAINHUB.IO”, because your purchase is made from AI Analytics And Integrations Limited, trading as Trainhub.io, as Merchant of Record.

1.2 Our Role - Merchant of Record and Ticketing Service Provider

AI Analytics sells train e-tickets for journeys operated by the National Train Company of Uzbekistan, trading as RAILWAY.UZ (UzbekistonTemir Yo'llari), under a distribution arrangement with RAILWAY.UZ. When you buy through Trainhub.io, we sell you the e-ticket in our own name, as principal, and we act as the Merchant of Record for your payment. In this capacity, we:1.2 Our Role - Merchant of Record and Ticketing Service Provider

AI Analytics sells train e-tickets for journeys operated by the National Train Company of Uzbekistan, trading as RAILWAY.UZ (Uzbekiston Temir Yo'llari), under a distribution arrangement with RAILWAY.UZ. When you buy through Trainhub.io, we sell you the e-ticket in our own name, as principal, and we act as the Merchant of Record for your payment. In this capacity, we:

• own and operate the Website, through which you can purchase e-tickets for RAILWAY.UZ-operated journeys;
• sell the e-ticket to you and arrange its issuance and delivery to you in PDF format;
• collect your payment through our own Stripe merchant account;
• provide fraud detection and monitoring services to protect the integrity of transactions;
• handle and respond to payment chargebacks in our own right as Merchant of Record;
• process and pay refunds to you in accordance with the refund policy in Section 9; and
• account to RAILWAY.UZ for the carriage element of each sale under our distribution arrangement.

1.3 Important: Seller of the Ticket, Not the Train Operator

AI Analytics And Integrations Limited is the seller of your e-ticket and the provider of the Trainhub.io ticketing service. We are NOT a train operator: we do not operate trains, set fares or timetables, or perform the carriage itself, and we are not responsible for the on-board service.

Two contracts arise when you buy through Trainhub.io:

(a) a Purchase Contract between you and AI Analytics And Integrations Limited, trading as Trainhub.io, for the sale of the e-ticket and the provision of the ticketing service, governed by these Terms and the laws of England and Wales; and

(b) a Contract of Carriage between you and RAILWAY.UZ for the train journey itself, governed by RAILWAY.UZ's conditions of carriage (available at eticket.railway.uz) and applicable transport law.

Any queries, complaints, or claims relating to the performance of your journey - including delays, cancellations, seat reservations during travel, on-board conditions, and passenger rights - should be directed to RAILWAY.UZ and are subject to RAILWAY.UZ's conditions of carriage and applicable Uzbek transport law. Any queries relating to your purchase, your payment, your refund, or a chargeback should be directed to us.

2. DEFINITIONS

In these Terms of Service, the following words andexpressions shall have the meanings set out below:

3.  THE TRI-PARTY STRUCTURE — A SUMMARY FOR CUSTOMERS

To avoid any confusion, the following explains the relationship between the three parties involved in your e-ticket purchase:

4. ACCEPTANCE OF TERMS

4.1 How You Accept

By accessing the Website or making a purchase through it, you confirm that you have read, understood, and agree to be bound by these Terms of Service. If you do not agree to these Terms, you must not use the Website or make a purchase.

4.2 Age and Capacity

By using the Website and Payment Interface, you represent and warrant that: (a) you are at least 18 years of age; (b) you have full legal capacity to enter into a binding contract under the laws applicable to you; and (c) if you are acting on behalf of another person, you have authority to bind that person to these Terms.

4.3 Changes to These Terms

We may update these Terms of Service at any time. Changes will be published on the Website with an updated "Last Updated" date. Continuing to use the Website or the Payment Interface after the updated Terms are published constitutes your acceptance of those changes. We will try to give you reasonable advance notice of material changes. Changes will not apply retrospectively to purchases already completed.

4.4 Two Contracts - Your Purchase and Your Journey

When you complete a purchase through the Website, you enter into a Purchase Contract directly with AI Analytics And Integrations Limited, trading as Trainhub.io, for the sale of your e-ticket and the provision of the Ticketing Services. Separately, a Contract of Carriage arises between you and RAILWAY.UZ for the train journey itself, governed by RAILWAY.UZ's conditions of carriage, which are made available at eticket.railway.uz.

5. OUR SERVICES

5.1 Scope of Our Services

Trainhub.io provides the following services:

• the sale of e-tickets for RAILWAY.UZ-operated journeys, sold by AI Analytics in its own name as Merchant of Record;
• a secure online checkout for those purchases, with real-time payment authorization, capture, and settlement via Stripe;
• issuance and delivery of your e-ticket in PDF format to the email address you provide;
• fraud detection and transaction monitoring;
• chargeback handling and dispute response, in our own right as Merchant of Record;
• refund processing and payment in accordance with Section 9; and
• customer support for all purchase, payment, and refund matters.

5.2 What We Do Not Provide

We do not provide, and the Purchase Contract does not include, the following, which are matters for RAILWAY.UZ under the Contract of Carriage:

• the operation, scheduling, or management of train services;
• the allocation of seating inventory, which is managed by RAILWAY.UZ's reservation systems;
• passenger assistance during travel, lost property services, delay compensation, or other passenger rights functions arising from the journey; or
• any service provided by Stripe under Stripe's own terms.

For everything relating to the performance of your journey - timetables, delays, seat queries during travel, cancellations, passenger rights - please contact RAILWAY.UZ directly at eticket.railway.uz or call 1005 (Uzbekistan) or +998 71 299 00 00 (international). For everything relating to your purchase, payment, or refund, contact us (Section 7).

5.3 Website Availability

We aim to keep the Website and Payment Interface available at all times, but we cannot guarantee uninterrupted availability. Planned maintenance, technical failures, or circumstances outside our control may result in temporary unavailability. If the Website is unavailable, you can purchase tickets directly at eticket.railway.uz.

We are not liable for any loss caused by temporary Website unavailability, provided the unavailability was not itself caused by an error on our part.

6. PAYMENTS

6.1 Merchant of Record

All purchases completed through the Website, and all Stripe-based purchases completed through the RAILWAY.UZ platform (eticket.railway.uz) where Trainhub.io is presented as the payment option, are sales by AI Analytics And Integrations Limited (trading as Trainhub.io) acting as the Merchant of Record.

This means that:

• you are purchasing your e-ticket directly from AI Analytics And Integrations Limited, trading as Trainhub.io;
• we sell the e-ticket to you in our own name and on our own behalf, as principal, under our distribution arrangement with RAILWAY.UZ;
• you authorize us to charge your card or digital wallet for the full price of your order;
• the charge will appear on your bank statement as TRAINHUB.IO (see 6.4); and
• we are responsible to you for the transaction, including delivery of your e-ticket, refunds, chargebacks, and payment disputes (see Sections 8 and 9).

Stripe, Inc. (“Stripe”), a payment technology company incorporated in the United States of America, is engaged by us as our payment processor and provides the secure technical infrastructure through which your payment card or digital wallet transaction is authorized and processed. Stripe is not the seller of your ticket and is not a party to the Purchase Contract or the Contract of Carriage.

By proceeding with a payment, you acknowledge and agree that:

• your payment is processed through AI Analytics And Integrations Limited's Stripe merchant account;
• Stripe's own Terms of Service and Privacy Policy apply to the technical processing of your payment data, and you are encouraged to review those documents at stripe.com/gb/legal; and
• responsibility for failures, outages, or errors attributable solely to Stripe's infrastructure is addressed in Section 11.5.

6.2 Accepted Payment Methods

Through the Website, the following payment methodsare currently accepted:

Payment methods available may vary depending on your device, browser,or geographic location, and are subject to the capabilities of theStripe platform at the time of your transaction.

6.3 Funds Flow and Settlement with RAILWAY.UZ

As Merchant of Record, AI Analytics receives the full transaction amount into its own Stripe merchant account and then accounts to RAILWAY.UZ for the carriage element of each sale under our distribution arrangement. The following describes the flow of funds following a successful transaction:

For the avoidance of doubt, neither the Stripe fee nor the AI Analytics margin is an additional charge levied on you above the ticket price displayed at checkout, unless expressly disclosed otherwise.

6.4 Bank Statement Descriptor

All transactions processed through the Stripe payment option will appear on your bank, credit card, or payment card statement under the following descriptor:

Trainhub.io

This is the name of the seller: your purchase is made from AI Analytics And Integrations Limited, trading as Trainhub.io, as Merchant of Record. The train journey itself is operated by RAILWAY.UZ under your Contract of Carriage.

If you do not recognize this transaction on your statement, please contact us at hello@trainhub.io and we will help you identify it.

6.5 Transaction Currency and Foreign Exchange

6.5.1 Transaction Currency

All transactions processed through the Website are denominated and settled in United States Dollars (USD) as the default transaction currency, unless an alternative supported currency is displayed and selected during the checkout process. Where ticket prices are displayed in Uzbekistani Som (UZS) for informational purposes, the binding transaction amount will be the USD equivalent displayed at checkout. The exchange rate applied is determined by Stripe and the card network at the time of processing.

6.5.2 Customer Responsibility for Foreign Exchange Costs

If your payment card or bank account is denominated in a currency other than the transaction currency, your card issuer or bank will apply its own foreign exchange conversion rate and may charge you a foreign currency transaction fee. These charges are applied by your financial institution independently of us and are outside our control.

6.5.3 Refunds and Currency Fluctuation

Any refunds issued to you will be calculated by reference to the original transaction amount in the original transaction currency at the time of purchase. We do not guarantee that the refunded amount, once converted back into your home currency by your bank, will equal the amount originally debited from your account. Any shortfall resulting from exchange rate movements between the payment date and the refund date is not recoverable from us.

6.6 Order Completion and Formation of the Purchase Contract

Your Purchase Contract with us is formed, and your booking is confirmed, when: (i) your payment has been successfully authorised and captured; and (ii) a booking confirmation has been issued to the email address you provided during checkout. Your Contract of Carriage with RAILWAY.UZ in respect of the journey takes effect in accordance with RAILWAY.UZ's conditions of carriage upon confirmation of your booking.

A payment authorisation hold (pre-authorisation) placed on your account does not constitute a completed payment. If authorisation is declined, expired, or cancelled, no booking will be created, no Purchase Contract will be formed, and no funds will be collected.

We reserve the right to cancel or decline any transaction where: (a) payment authorisation is refused by Stripe or your card issuer; (b) we reasonably suspect fraudulent activity; (c) you have an outstanding unpaid balance from a previous transaction; or (d) the transaction triggers our fraud detection systems. In such circumstances, we will notify you and no funds will be retained.

6.7 Saved Payment Details

If you hold a registered account on the Website, you may be offered the option to securely save your payment card details for future transactions. Saved card data is stored and tokenised by Stripe in accordance with PCI DSS standards. AI Analytics And Integrations Limited does not store full card numbers on its own systems. You may view, manage, and delete your saved payment details at any time through your account settings.

6.8 Stripe's Terms of Service and Privacy Policy

Stripe processes your payment data as our payment processor. Stripe's role is limited to payment processing; Stripe is not a party to your Purchase Contract with us nor to your Contract of Carriage with RAILWAY.UZ.

7. CONTACT US

Who does what: We are AI Analytics And Integrations Limited, the company behind Trainhub.io. We sell you your e-ticket and we handle everything about your purchase: your payment, your e-ticket delivery, your refunds, and any chargeback or payment dispute. RAILWAY.UZ (Uzbekiston Temir Yo'llari) is the train company: they run the trains, and any question about the journey itself goes to them.

Before contacting us, please use the table below. It will save you time by pointing you straight to the right person.

7.1 Who to Contact — Quick Reference

Stripe's Terms of Service (stripe.com/gb/legal/ssa) and Stripe's Privacy Policy (stripe.com/gb/privacy) apply to the technical processing of your payment data. We encourage you to review these documents before completing a transaction.

7.2 Contacting Us - Purchase, Payment, and Refund Questions

We can help with anything about your purchase: charges to your card, your e-ticket not arriving, refunds, chargebacks, and technical errors on our side. If your question is about the operation of the train itself, please go to RAILWAY.UZ (Section 7.3).

7.2.1  Email — the best way to reach us

Email us at hello@trainhub.io. Tell us your booking reference, the date and amount of the charge, and what has gone wrong. We aim to reply within one working day and to resolve complaints within eight weeks.

7.2.2  Online Form

Fill in the form atwww.trainhub.io/railwayuz. You can attach screenshots or bank statements. We reply within one working day.

7.2.3  Live Chat on Telegram

Reach our team on the Telegram app,24 hours a day, seven days a week, for quick questions. For anything formal — a complaint, a refund request, a chargeback — please use email so there is a written record.

7.2.4  Phone

• From within Uzbekistan: 1005
• From anywhere else: +998 99 190 50 05
• Hours: 11:00 – 22:00 UK time, every day
• We can only discuss a booking with the person who made it. Please have your booking reference to hand.

7.3 Contacting RAILWAY.UZ - the Journey Itself

We have no access to train timetables, live running information, lost property records, or any other part of RAILWAY.UZ's operations. For those matters, please go straight to RAILWAY.UZ.

7.3.1  RAILWAY.UZ Online Portal

Go tohttps://eticket.railway.uz/en/home. From there you can check time tables, view your journey details, request a ticket change, and make a service complaint.

7.3.2  RAILWAY.UZ Phone

• Within Uzbekistan: 1005
• International: +998 71 299 00 00

The RAILWAY.UZ team handles: delays and cancellations, lost property, ticket changes, passenger rights, and on-board service complaints.

7.4  Making a Formal Complaint

7.4.1  How to Complain

Email hello@trainhub.io with the subject line "Formal Complaint". Include your name, bookingreference, a description of the problem, and the outcome you are looking for. Attach any relevant documents.

7.4.2 Scope of Our Complaints Process

Our complaints process covers your purchase: charges, e-ticket delivery, refunds, chargebacks, and errors on our side. Complaints about the performance of the train service must go to RAILWAY.UZ; we cannot investigate the operation of the train service on your behalf.

7.5 Our Full Contact Details

Remember: We sell you your ticket and handle everything about your purchase and payment. RAILWAY.UZ runs the trains. For anything about the journey itself - timetables, delays, cancellations, lost property, or the quality of the service - please contact RAILWAY.UZ directly at https://eticket.railway.uz or call 1005 (Uzbekistan) or +998 71 299 00 00 (international).

8.  CHARGEBACKS AND DISPUTES

8.1  What Is a Chargeback?

A "chargeback" is when your bank reverses a payment on your behalf — typically because yousay the transaction was unauthorised, the goods or service were never delivered, or what you received was not as described.

Because we are the Merchant of Record for all payments on Trainhub.io, your bank sends any chargeback to us, and we handle it in our own right. That is true even if your complaint is actually about the train service rather than the purchase.

In plain terms: if you dispute a Trainhub.io charge with your bank, we will receive that dispute and deal with it. We are the company you bought your ticket from, so the chargeback comes to us.

8.2  We Reserve the Right to Challenge Chargebacks

8.2.1  Our Right to Contest

If you raise a chargeback, were serve the right to challenge it. We will gather evidence and submit it to your card network. That evidence may include:

• your booking confirmation — showing that a booking was made and a confirmation email was sent to you;
• e-ticket records — showing that a valid ticket was issued and delivered;
• ticket usage data — boarding scans, seat occupancy records, conductor validations, and time-stamp data provided to us by RAILWAY.UZ;
• payment records — Stripe transaction logs confirming the amount and authorisation;
• terms acceptance — confirmation that you agreed to these Terms when you bought your ticket; and
• any messages — correspondence between you and us or RAILWAY.UZ before the chargeback was raised.

8.2.2  Your Consent to Us Sharing Your Data

By buying a ticket, you agree that we may share your booking and payment data with RAILWAY.UZ to compile chargeback evidence, and that we may pass that evidence to Stripe, card networks, and banks. We only share what is strictly necessary, and we do this in line with our Privacy Policy.

8.3 Who Is Responsible If a Chargeback Is Upheld?

8.3.1  Three Types of Chargeback

8.3.2 When the Complaint Is About the Journey (Situation B)

If your chargeback concerns the train service - a delay, cancellation, poor conditions, or refused boarding - and the card network upholds it, we will return the money as required. Refund entitlements for journey disruption are set by the tariff rules summarized in Section 9.3, which we apply as our refund policy; contacting us under Section 9 is usually faster than a chargeback and achieves the same result where a refund is due. Complaints about the quality of the service itself, beyond any refund of the price, are a matter for RAILWAY.UZ under your Contract of Carriage and its passenger rights process.

8.3.3  When the Chargeback Is Fraudulent (Situation C)

If you raise a chargeback claiming non-receipt or non-use after your ticket has in fact been used - for example, after it was scanned at boarding, checked by a conductor, or confirmed at your seat - that is a groundless dispute. In those circumstances:

• we may challenge the chargeback with the evidence described in 8.2.1;
• where the law allows, we may recover amounts you were not entitled to reclaim, through the courts of England and Wales; and
• we may report demonstrable fraud to fraud prevention databases, Stripe, card networks, and relevant authorities.

8.4 Administrative Fee for Fraudulent Chargebacks

8.4.1 When We May Charge a Fee

We may charge you an administrative fee (the “Chargeback Fee”) only where your chargeback was fraudulent - that is, the evidence demonstrates that you knew a valid ticket had been issued and used when you raised the dispute.

8.4.2  How Much the Fee Is

The fee covers our reasonable costs - staff time, evidence gathering, and any fees charged by Stripe or the card network for the dispute process. It will not exceed 50 GBP per transaction unless the circumstances are exceptional, in which case we will tell you the amount before we seek to collect it.

8.4.3  Paying the Fee

We will email you if a Chargeback Fee is due, with the evidence on which we rely. You will have 14 calendar days to pay or to dispute the fee. If you disagree that the fee is owed, contact us using the details in Section 7 and we will review it. Unpaid fees may be recovered through the courts.

8.5 Talk to Us First

If something has gone wrong, please contact us at hello@trainhub.io before raising a dispute with your bank. As Merchant of Record we can usually resolve duplicate charges, missing tickets, and refund questions within days - faster than the card network dispute process. Nothing in these Terms removes or limits your statutory rights or your rights under your card issuer's and card network's dispute rules.

8.6  Data We Use in Chargeback Cases

By using the Website and buying a ticket, you agree that we and RAILWAY.UZ may collect, keep, and use the following to investigate and respond to chargebacks:

• transaction records, payment authorisation data, and Stripe logs;
• e-ticket issue and delivery records;
• boarding scans, seat occupancy, and conductor validations from RAILWAY.UZ;
• time-stamp travel data from RAILWAY.UZ's systems; and
• any messages between you and us or RAILWAY.UZ about the booking.

This data may be passed to Stripe,card networks, and banks as part of the dispute process, in line with our Privacy Policy and UK data protection law.

9.  REFUNDSAND CANCELLATIONS

This section explains how refunds work. The most important thing to understand is that there are two separate processes — one run by us (AI Analytics) for payment errors, and one run by RAILWAY.UZ for everything else.

The key rule: as Merchant of Record, we are responsible for processing and paying every refund due to you, and we pay it to your original payment card. Whether a refund is due, and how much, depends on why you are asking: payment errors on our side are refunded in full (Section 9.2); refunds connected with your journey - cancellation, disruption, or a change of plans - are determined by the tariff rules summarized in Section 9.3, which are set by RAILWAY.UZ for its services and which we apply as our refund policy for purchases through Trainhub.io.

9.1  Who Handles What — at a Glance

9.2 Refunds for Payment Errors

9.2.1 When We Refund You in Full

We will investigate and refund you directly and in full if something went wrong on our side with the payment:

• Duplicate charge: your card was charged more than once for the same ticket;
• Wrong amount: we charged more than the price shown at checkout due to a system error;
• No ticket received: we took payment successfully, but no ticket was issued to you due to an API or integration failure; or
• Stripe error: a technical fault inside Stripe caused an incorrect or duplicate charge, as confirmed by Stripe's logs.

9.2.2  How to Report a Payment Error

Contact us within 30 days of the charge using the details in Section 7. Please include: your booking reference, the date and amount of the charge, what went wrong, and a screenshot of your bank statement if you have one. We will acknowledge within one working day and check Stripe's logs and the ticketing records. If we confirm a payment error, we will send the refund through Stripe straight away.

9.3 Refunds Connected with Your Journey

9.3.1 The Tariff Rules

Refund entitlements connected with the journey - cancellation by you, cancellation or material delay by RAILWAY.UZ, partly used tickets - are determined by the tariff rules applicable to RAILWAY.UZ services, published at eticket.railway.uz and summarized in 9.3.3. We apply those tariff rules as our refund policy for purchases made through Trainhub.io. We do not apply different or less favorable rules than the published tariff.

9.3.2 How a Journey-Related Refund Works

9.3.3 Tariff Rules - Summary

CIS-country and international routes have different deadlines and fees. Check the full tariff at eticket.railway.uz.

9.4 Our Margin and Stripe's Fee on Refunds

If a payment error on our side triggers a refund, we return the full amount that was wrongly charged, without any deduction.

For journey-related refunds, the amount you receive is determined by the tariff rules in 9.3.3, which may provide for deduction of admin and service fees. How our margin and Stripe's processing fee are treated between us and RAILWAY.UZ is a matter for our distribution arrangement and does not affect the amount due to you under the tariff.

9.5 How Long a Refund Takes

If you still have not received the refund after 15 working days, contact us and we will investigate with Stripe.

9.6  Currency and Exchange Rates

We calculate refunds based on the original amount charged in the original transaction currency at the time of purchase. We do not control what exchange rate your bank applies when converting that back into your local currency. Any difference caused by exchange rate movements between the payment date and the refund date is not something we can compensate for.

10.  DATA PROTECTION AND PRIVACY

10.1 Data Controllers and Processors

There are three parties handling data in respect of your e-ticket purchase: (i) AI Analytics And Integrations Limited, which, as seller and Merchant of Record, processes your booking, payment, and refund data as data controller under the UK General Data Protection Regulation (UK GDPR) and the Data Protection Act 2018; (ii) Stripe, which processes your card payment data in accordance with its own privacy obligations; and (iii) RAILWAY.UZ, which processes data about your journey and carriage under Uzbek law and its own privacy policy. Each party is responsible for its own data processing.

10.2  AI Analytics' Privacy Policy

Our full Privacy Policy, which sets out how we collect, use, store, and share your personal data, is available at www.trainhub.io/privacy. By using the Website, you confirm that you have read and understood that policy.

10.3  Data Used for Chargeback and Fraud Purposes

As described in Section 8.6, by purchasing a ticket you agree that we and RAILWAY.UZ may collect and retain transaction, booking, and travel data for the purposes of investigating chargebacks, detecting fraud, and complying with our legal obligations. We will only retain such data for as long as necessary, and in accordance with our Privacy Policy.

10.4  Your Rights

Subject to applicable law, you have the right to access, rectify, and (in certain circumstances) erase personal data held by us, to restrict or object to our processing of your data, and to data portability. To exercise any of these rights, please contact us at hello@trainhub.io. You also have the right to lodge a complaint with the Information Commissioner's Office (ICO) atico.org.uk.

11.  LIMITATION OF LIABILITY

Subject to applicable law, you have the right to access, rectify, and (in certain circumstances) erase personal data held by us, to restrict or object to our processing of your data, and to data portability. To exercise any of these rights, please contact us at hello@trainhub.io. You also have the right to lodge a complaint with the Information Commissioner's Office (ICO) atico.org.uk.

11.1 What We Are Not Responsible For - the Performance of the Journey

11.1.1 The Basic Rule

We sell you your e-ticket and are responsible to you for the purchase: the sale, payment, ticket delivery, refunds, and disputes. We are not responsible for the performance of the train journey itself. The journey is performed by RAILWAY.UZ under your Contract of Carriage, and matters arising during carriage are RAILWAY.UZ's responsibility under its conditions of carriage and applicable transport law.

11.1.2 Specific Carriage Matters We Are Not Responsible For

For these matters, your remedy lies with RAILWAY.UZ under the Contract of Carriage. Where a journey disruption gives rise to a refund entitlement under the tariff rules, that refund is paid by us under Section 9.

11.2 The Maximum We Will Pay You

11.2.1  Our Liability Is Capped at the Ticket Price

If we breach the Purchase Contract or these Terms, the most we will pay you for any single claim is the price you paid for the ticket involved in that claim. This cap applies to all claims combined arising from the same incident - the cap cannot be multiplied by raising the same issue under different legal headings.

Example: you paid 25 GBP for a ticket and we made a payment error. Our maximum liability for that incident is 25 GBP, regardless of how many legal arguments are made about it.

11.2.2  The Cap Does Not Apply to Our Most Serious Obligations

The cap does not apply where we cannot legally limit our liability — see Section 11.4.

11.3 Losses We Are Not Responsible For

11.3.1  Indirect and Consequential Losses

Even where we have breached these Terms, we are not responsible for any of the following:

• lost earnings or income — salary, wages, freelance income, or any money you could not earn because the train was late or cancelled;
• lost profit — business revenue you missed out on;
• missed connecting travel — a missed flight, ferry, connecting train, bus, or taxi booked around the RAILWAY.UZ service;
• hotel costs — unplanned overnight stays, cancellation fees, or accommodation change fees;
• event costs — non-refundable tickets to concerts, weddings, sports events, conferences, or anything else you could not attend;
• business losses — missed meetings, lost contracts, failed negotiations, reputational damage;
• loss of enjoyment — a ruined holiday, lost leisure time, or personal opportunities that cannot be recovered;
• replacement travel — taxis, car hire, or alternative tickets you had to buy; and
• any other indirect or consequential loss not reasonably foreseeable at the time of purchase.

11.3.2  Why We Exclude These Losses

When you buy a ticket, we do not know why you are travelling, whether you have a connecting flight, or what the consequences of disruption would be for you, and we have no control over the operation of the train service. For consequential losses caused by journey disruption, your remedies lie with RAILWAY.UZ under its passenger rights process and with any travel insurance you hold. We strongly recommend travel insurance for any journey where disruption could cause you significant financial loss.

We are not liable for losses caused by failures within Stripe's own infrastructure - outages, data breaches, or technical failures that are independent of how we have configured or used Stripe. For problems within Stripe's own platform, see stripe.com/gb/legal.

This does not apply to errors caused by our own configuration of Stripe — if we set something up wrongly and that caused your problem, we are responsible for it (see Section9.2.1).

11.4  What We Can Never Limit

Nothing in these Terms limits our liability for:

• death or personal injury caused by our negligence;
• fraud or fraudulent misrepresentation by us or our staff;
• anything we cannot legally exclude under the Consumer Rights Act 2015, Consumer Protection Act 1987, or any other law; or
• any other liability that English law does not permit us to limit.

11.5 Stripe Infrastructure Failures

Your rights as a consumer are protected. Nothing in this section removes your rights under the Consumer Rights Act 2015 or any other law that applies to you. For free, independent advice on your consumer rights, visit citizensadvice.org.uk.

11.6  Liability Summary

12. GOVERNING LAW, JURISDICTION AND CONTACT DETAILS

12.1 What This Section Covers

This section sets out which country's law governs these Terms and the Purchase Contract, which courts can deal with disputes about them, and other general provisions. Disputes about the performance of your train journey are governed by RAILWAY.UZ's conditions of carriage and applicable transport law.

12.2 Governing Law

12.2.1 English Law Applies to the Purchase Contract

These Terms, the Purchase Contract, and everything to do with the services we provide - the sale of your e-ticket, the operation of the Website, collecting payments, processing transactions, fraud detection, handling chargebacks, and processing refunds - and any dispute or claim arising out of or in connection with them (including non-contractual disputes or claims) are governed by the laws of England and Wales.

We are incorporated in England and Wales (company number 12431111), we operate from the UK, our Stripe merchant account is held under Stripe's UK terms, and our obligations as Merchant of Record are performed from the UK.

12.2.2 Which Law Applies to Each Relationship

12.2.3 Your Mandatory Consumer Rights Are Not Affected

If you live in a country whose laws give you rights that cannot be waived by contract, this choice of English law does not take those rights away.

12.3 Jurisdiction and Dispute Resolution

12.3.1 Courts of England and Wales

Any dispute about these Terms or the Purchase Contract shall be subject to the jurisdiction of the courts of England and Wales.

12.3.2 Your Statutory Consumer Rights

Nothing in Section 12.3.1 overrides any right you have as a consumer under applicable law to bring a claim in the courts of your own country, and nothing in these Terms limits any statutory protections you have under the Consumer Rights Act 2015 or the Consumer Contracts Regulations 2013.

12.3.3 Alternative Dispute Resolution (ADR)

Before taking legal action, please contact us first (Section 7) so we can try to resolve things quickly.If we cannot sort out your complaint within eight weeks of receiving it in writing, or if you are unhappy with our response, you may have the right to go to an Alternative Dispute Resolution (ADR) scheme. We will tell you which scheme applies in our final response or deadlock letter.

12.3.4 Disputes About Your Train Journey

If your complaint is about the performance of the journey - a delay, cancellation, refused boarding during travel, or the on-board service - your claim lies against RAILWAY.UZ under the Contract of Carriage. Claims about your purchase - the sale, the payment, the ticket's validity, refunds, or chargebacks - lie against us under the Purchase Contract.

12.4 Other Legal Provisions

12.4.1 Severability

If any part of these Terms is found to be invalid or unenforceable by a court, that part is removed and the rest continues in full force.

12.4.2 Waiver

If we do not enforce a right under these Terms on one occasion, that does not mean we have given up that right for the future.

12.4.3 Entire Agreement

These Terms, together with our Privacy Policy and Cookie Policy, make up the whole agreement between you and us for the sale of your e-ticket and the Ticketing Services. They sit alongside - and do not replace - your Contract of Carriage with RAILWAY.UZ and Stripe's terms for the technical processing of payments.

12.4.4 Third Party Rights

No one other than you and us has rights under these Terms.

12.4.5 Language

These Terms are in English. If a translation is provided for convenience, the English version controls in any conflict. Please send all complaints and legal correspondence in English.

12.5 Our Contact Details

12.6 Version History

These Terms are effective from [12 June 2026] and replace all earlier versions. v1.0 - 20 Feb 2026: First issue. v2.0 - Sections 7 and 8 added. v3.0 - Section 11 added. v4.0 - Section 2 added. v5.0 - Plain language review. v6.0 - Full consolidation. v7.0 - [12 June 2026]: Merchant of Record revision: AI Analytics And Integrations Limited (trading as Trainhub.io) identified throughout as seller of the e-ticket, provider of the ticketing service, and Merchant of Record; agent and intermediary references removed; refund, chargeback, and dispute responsibility consolidated with Trainhub.io; statement descriptor changed to TRAINHUB.IO; governing law provisions extended to the Purchase Contract; chargeback waiver removed.