Terms and Conditions
Consolidated Full Version · v6.0
trading as MorePraxis / Trainhub.io
Company No. 12431111 · 71–75 Shelton Street, London WC2H 9JQ
Last Updated: 20 February 2026
Governing Law: England & Wales
Website: www.trainhub.io
This document governs your use of the Trainhub.io payment interface only. It does not govern your train journey — that is governed by RAILWAY.UZ's own terms and conditions. For journey questions, contact RAILWAY.UZ at eticket.railway.uz.
INTRODUCTION
Please read these Terms of Service carefully before using the Trainhub.io website (www.trainhub.io, the "Website"). By accessing or using the Website, or by completing a payment transaction through the Website, you confirm that you have read, understood, and agreed to be bound by these Terms of Service in their entirety.
These Terms of Service govern solely the payment processing services provided by AI Analytics And Integrations Limited through the Website. They do not govern the sale of train tickets, the terms of carriage, journey conditions, or any other aspect of train travel, which are governed exclusively by the terms and conditions of the relevant train operator.
Throughout these Terms of Service, when we use the words "we", "us", or "our", we are referring to AI Analytics And Integrations Limited. When we use "you" or "your", we mean any person who accesses the Website or initiates a payment transaction through it. When we refer to "these Terms", we mean these Terms of Service.
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.
AI Analytics also trades under the name MorePraxis. All payment transactions processed through theWebsite will appear on your bank or card statement under the descriptor "Trainhub.io [RAILWAY.UZ]", reflecting both our payment processing role and the identity of the underlying train operator.
1.2 Our Role — Technology and Payment Services Provider
AI Analytics has been commissioned by the National Train Company ofUzbekistan, operating under the trading name RAILWAY.UZ (Uzbekiston Temir Yo'llari), to act as its exclusive technology and payment services provider for Stripe-based online ticket purchases. In this capacity, we:
- own and operate the Website, which serves as the Stripe-powered online payment interface for RAILWAY.UZ's e-ticket sales;
- process Stripe payments for RAILWAY.UZ e-tickets on behalf of RAILWAY.UZ, collecting payments through our own Stripe merchant account
- provide fraud detection and monitoring services to protect the integrity of payment transactions;
- manage counter-dispute processes in respect of payment chargebacks initiated by cardholders;
- process refunds to customers in accordance with RAILWAY.UZ's refund policy;
- remit net sale proceeds to RAILWAY.UZ's designated bank accounts after deducting our agreed commission and applicable Stripe transaction fees.
1.3 Critical Clarification — What We Are NOT
AI Analytics And Integrations Limited is NOT atrain operator. We do not operate trains, sell train tickets in ourown right, set fares or schedules, or assume any responsibility forthe provision of train services. We have no contractual role in, andaccept no liability for, any aspect of your train journey.
The contract of carriage — that is, the legal agreement governing your train journey, including your rights as a passenger — is made solely and exclusively between you and RAILWAY.UZ. That contract is governed by RAILWAY.UZ's own terms and conditions of carriage, which are made available to you on RAILWAY.UZ's platform(eticket.railway.uz) prior to ticket purchase and which you must accept separately.
Any queries, complaints, or claims relating to your journey —including delays, cancellations, lost tickets, seat reservations, and passenger rights — must be directed to RAILWAY.UZ directly and are subject to RAILWAY.UZ's terms and conditions and applicable Uzbek transport law.
2. DEFINITIONS
In these Terms of Service, the following words and expressions shall have the meanings set out below:Stripe's payment infrastructure; and
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 initiating a payment transaction through the Payment Interface, 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 the Payment Interface.
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.
4.4 Separate Terms Apply to Your Train Journey
These Terms govern your use of our Payment Interface only. They do not govern your train journey. By completing a payment, you also agree to RAILWAY.UZ's own terms and conditions of carriage, which are presented to you separately on RAILWAY.UZ's platform prior to purchase.
5. OUR SERVICES
5.1 Scope of Our Services
Trainhub.io provides the following services exclusively:
- a secure, Stripe-powered Payment Interface for the purchase of RAILWAY.UZ e-tickets;
- real-time payment authorisation, capture, and settlement via Stripe;
- fraud detection and transaction monitoring;
- chargeback management and dispute response on RAILWAY.UZ's behalf;
- refund processing to customers upon RAILWAY.UZ's instruction; and
- disbursement of net ticket sale proceeds to RAILWAY.UZ.
5.2 What We Do Not Provide
We do not provide, and expressly disclaim any responsibility for, the following:
- the operation, scheduling, or management of train services;
- ticket availability or inventory, which is managed exclusively by RAILWAY.UZ;
- passenger assistance, travel advice, or customer support relating to the train journey;
- lost property services, delay compensation, or any other passenger rights functions; or
- any service provided by RAILWAY.UZ or Stripe.
For everything relating to your journey — timetables, delays, seat queries, cancellations, passenger rights — please contact RAILWAY.UZ directly at eticket.railway.uz or call 1005 (Uzbekistan) or +998 71299 00 00 (international).
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 a payment error on our part.
6. PAYMENTS
6.1 Website Availability
We are not liable for any loss caused by temporary Website unavailability, provided the unavailability was not itself caused by a payment error on our part.
All payment transactions completed through the Stripe payment optionon the RAILWAY.UZ platform (eticket.railway.uz) are processed by AIAnalytics And Integrations Limited (trading as MorePraxis, the operator of www.trainhub.io) acting as the Merchant of Record forthose transactions.
In this capacity, AI Analytics And Integrations Limited collects payment from you on behalf of RAILWAY.UZ through its own account withStripe, Inc. ("Stripe"), a payment technology company incorporated in the United States of America. Stripe provides the secure technical infrastructure through which your payment card or digital wallet transaction is authorised and processed.
Important — Who You Are Paying: Although you are purchasing a train ticket from RAILWAY.UZ, your payment is collected by AI Analytics And Integrations Limited as Merchant of Record. This is why your bank or card statement will show the descriptor Trainhub.io[RAILWAY.UZ] — confirming both the payment intermediary and the underlying train operator. This descriptor does not indicate that AI Analytics is your train operator. Your Contract of Carriage remains solely with RAILWAY.UZ.
By proceeding with a Stripe payment on the RAILWAY.UZ platform, 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;
- AI Analytics And Integrations Limited has no liability for any failure, outage, error, or data handling issue attributable solely to Stripe's payment infrastructure; and
- the payment obligation for your train ticket is owed to RAILWAY.UZ, with AI Analytics acting only as the authorised collection agent.
6.2 Accepted Payment Methods
Through the Stripe payment interface, 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 Disbursement to RAILWAY.UZ
AI Analytics And Integrations Limited operates as a payment intermediary between you and RAILWAY.UZ. The following describes the flow of funds following a successful transaction:
For the avoidance of doubt, both the Stripe transaction fee and the AI Analytics commission are borne by RAILWAY.UZ as deductions from the ticket sale proceeds. Neither fee 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 [RAILWAY.UZ]
This descriptor reflects: (i) Trainhub.io — the website operated byAI Analytics And Integrations Limited, acting as Merchant of Record and payment intermediary; and (ii) [RAILWAY.UZ] — the National TrainCompany of Uzbekistan, on whose behalf the ticket was sold and whose services you have purchased.
If you do not recognise this transaction on your statement, please contact us at hello@trainhub.io before raising a dispute with your bank. Raising an unfounded chargeback may delay your refund, result in your account being suspended, and may have legal consequences.
6.5 Transaction Currency and Foreign Exchange
6.5.1 Default Transaction Currency
All transactions processed through the Stripe payment interface 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 RAILWAY.UZ's platform displays ticket prices in Uzbekistani Som (UZS) for informational purposes, the binding transaction amount will be theUSD equivalent calculated at the exchange rate applied by Stripe at the time of processing. AI Analytics And Integrations Limited has no control over and accepts no liability for the exchange rate applied by Stripe at the time of settlement.
6.5.2 Customer Responsibility for Foreign Exchange Costs
If your payment card or bank account is denominated in a currency other than USD, 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 AI Analytics And Integrations Limited and RAILWAY.UZ, and are entirely 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. AI Analytics And Integrations Limited and RAILWAY.UZ 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 adverse exchange rate movements is not recoverable from AI Analytics And Integrations Limited or RAILWAY.UZ.
6.6 Order Completion and Payment Authorisation
Your booking shall not be confirmed, and no Contract of Carriage shall come into effect with RAILWAY.UZ, until: (i) your payment has been successfully authorised and captured by Stripe; and (ii) a booking confirmation has been issued to the email address you provided during checkout.
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 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 RAILWAY.UZ platform or the Trainhub.io 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
By using the Stripe payment interface, you enter into a direct relationship with Stripe in respect of the technical processing of your payment. Stripe's role is limited to payment processing; Stripe is not a party to your Contract of Carriage with RAILWAY.UZ nor to these Terms of Service.
You are independently subject toStripe's Terms of Service (stripe.com/gb/legal/ssa) and Stripe'sPrivacy Policy (stripe.com/gb/privacy). We encourage you to review these documents before completing a transaction.
7. CONTACT US
Who does what: We are AI Analytics And Integrations Limited, the company behind Trainhub.io. We handle your payment — nothing else. We process your card, issue your e-ticket, and manage refunds when they are within our control. RAILWAY.UZ (Uzbekiston Temir Yo'llari) is the train company. They run the trains. Any question about your journey 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
7.2 Contacting Us — Payment Questions Only
We can only help with paymentmatters: charges to your card, refunds we have processed, andtechnical errors on our side. If your question is about the trainitself, please go straight 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 payment 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 — Everything About Your Journey
We cannot help with travel questions. We are a payment company. We have no access to train timetables, live running information, lost property records, or any other part of RAILWAY.UZ's operations. If you contact us with a travel question, we will not be able to help and you will lose time. 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 e-ticket, request a ticket change or cancellation, apply for a refund, 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, refund eligibility,passenger rights, and onboard 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.3 Scope of Our Complaints Process
Our complaints process covers payment matters only — charges, refunds, and technical errors on our side. Complaints about the train service, about RAILWAY.UZ's refund decisions, or about anything RAILWAY.UZ does must go to RAILWAY.UZ. We cannot investigate or escalate complaints about RAILWAY.UZ on your behalf.
7.5 Our Full Contact Details
Remember: We handle payments. RAILWAY.UZ runs the trains. For anything about your journey — 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). Contacting us with a travel question will not get you an answer.
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 act as the Merchant ofRecord for all card payments on Trainhub.io, your bank sends any charge back to us — not to RAILWAY.UZ. That is true even if your complaint is actually about the train service rather than the payment. We then handle the chargeback process on RAILWAY.UZ's behalf.
In plain terms: If you go to your bank and dispute a Trainhub.io charge, we will receive that dispute and deal with it. We are not the train company, but we are the payment company, 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 on RAILWAY.UZ's behalf. 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 GPS or time-stamp data provided 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 Liable If a Chargeback Is Upheld?
8.3.1 Three Types of Chargeback
8.3.2 When the Complaint Is Really About RAILWAY.UZ's Service (Situation B)
If your chargeback is about the quality of the train service — a delay, cancellation, poor conditions, or refused boarding — and the card network upholds it, we will return the money as required. But that does not settle things with RAILWAY.UZ. Specifically:
- Getting your money back from us does not cancel any debt you owe RAILWAY.UZ for a ticket that was issued and used or available for use.
- You may still owe RAILWAY.UZ the ticket price, and they can pursue that directly.
- We are not responsible for the train service failing — that is entirely RAILWAY.UZ's responsibility.
The right way to deal with a service complaint is to contact RAILWAY.UZ directly at eticket.railway.uz. They have a passenger rights process and may refund you without any charge back needing to be raised.
8.3.3 When the Chargeback Is Fraudulent (Situation C)
If you raise a chargeback after using your ticket — for example, after it was scanned at boarding, checked by a conductor, or confirmed at your seat — raising that chargeback is a breach of these Terms and may be treated as fraud.
In those circumstances:
- you remain liable to us and to RAILWAY.UZ for the full amount, even if the card network rules in your favour on a technicality;
- we may recover that amount through the courts of England and Wales; and
- we may report the abuse to fraud prevention databases, Stripe, card networks, and relevant authorities.
8.4 Administrative Fee for Groundless or Fraudulent Chargebacks
8.4.1 When We Charge a Fee
We may charge you an administrativefee (the "Chargeback Fee") if:
- the card network rejects your chargeback because the evidence clearly shows a valid ticket was issued and available; or
- your chargeback was fraudulent — you knew you had used the ticket when you raised the dispute; or
- you raised a chargeback without first contacting us or RAILWAY.UZ, when a quick conversation could have resolved things.
8.4.2 How Much the Fee Is
The fee covers our reasonable costs— staff time, evidence gathering, and any fees charged by Stripe orthe card network for the dispute process. It will not exceed £50 per transaction unless the circumstances are exceptional, in which casewe will tell you the amount before we try to collect it.
8.4.3 Paying the Fee
We will email you if a ChargebackFee is due. You will have 14 calendar days to pay. If you disagreethat the fee is owed, contact us using the details in Section 7 andwe will review it. Unpaid fees may be recovered through the courts.
8.5 Chargeback Waiver
When you buy a ticket and receive your e-ticket, you agree not to raise a chargeback, except in two situations:
- Unauthorised transaction: you genuinely believe someone else used your card without your permission; or
- Technical error: we charged you twice, charged the wrong amount, or took payment but no ticket was issued (see Section 9.2).
Once your e-ticket has been scanned, verified at your seat, or validated by a conductor, it has been used. Raising a chargeback after that point is a breach of these Terms, whatever the card network decides.
Please contact us first. Before calling your bank, email us at hello@trainhub.io. Most problems can be fixed quickly without a chargeback. If you go straight to your bank without contacting us first, that may be treated as bad faith and could result in a Chargeback Fee.
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 usethe following to investigate and challenge 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;
- GPS and 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: Whether you are entitled to a refund for your ticket is decided by RAILWAY.UZ — not by us. We do not set RAILWAY.UZ's refund rules and we cannot override them. Our job is to return the money to your card, once RAILWAY.UZ has told us to do so. The only exception is if something went wrong on our side with the payment itself (see Section 9.2).
9.1 Who Handles What — at a Glance
9.2 Refunds We Handle Directly — Payment Errors
9.2.1 When We Refund You Ourselves
We will investigate and refund you directly — without you needing to go to RAILWAY.UZ — 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 RAILWAY.UZ's system did not issue a ticket 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 RAILWAY.UZ's ticketing records. If we confirm a payment error, we will send the refund through Stripe straight away.
9.3 Refunds RAILWAYUZ Controls
9.3.1 RAILWAY.UZ Decides Whether You Get a Refund
For any refund not caused by a payment error on our part, only RAILWAY.UZ can authorise it. Their tariff and refund policy, published at eticket.railway.uz, sets out what you are entitled to. We have no power to override that, and we cannot approve a refund that RAILWAY.UZ has not approved.
9.3.2 Our Role: Returning the Money Once RAILWAY.UZ Says Yes
Once RAILWAY.UZ approves a refund and tells us the amount, we return the money to your card through Stripe.The five steps are:
9.3.3 RAILWAY.UZ Refund Rules — Summary
CIS-country and international routes have different deadlines and fees. Check RAILWAY.UZ's full policy at eticket.railway.uz.
9.4 Our Commission and Stripe's Fee on Refunds
Our commission and Stripe's processing fee are earned at the moment we process your payment successfully and issue your ticket. The payment service is complete at that point. So, if RAILWAY.UZ later approves a refund: our commission is not refunded and Stripe's fee is not refunded — both come out of RAILWAY.UZ's share, not from your pocket at the point of refund.
If a payment error on our side triggers a refund, we return the full amount that was wrongly charged without any deduction.
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 USD amount charged 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 or RAILWAY.UZ can compensate for.
10. DATA PROTECTION AND PRIVACY
10.1 Data Controllers
There are three separate data controllers or processors in respect of your e-ticket purchase: (i)AI Analytics And Integrations Limited, which processes your payment data and booking reference as data controller under the UK GeneralData Protection Regulation (UK GDPR) and Data Protection Act 2018;(ii) Stripe, which processes your card payment data as an independent data processor under its own privacy obligations; and (iii)RAILWAY.UZ, which processes data about your journey and ticket underUzbek law and its own privacy policy. Each party is independently 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 — RAILWAY.UZ's Side
11.1.1 The Basic Rule
We are not responsible for anything that goes wrong with the train service. That is RAILWAY.UZ's responsibility entirely. This applies even though "Trainhub.io [RAILWAY.UZ]" appears on your bank statement. That descriptor is there because we processed your payment— it does not mean we operate the trains or share responsibility for the service.
11.1.2 Specific Things We Are Not Responsible For
Wrong defendant warning: Taking legal action against us for something RAILWAY.UZ did would be misconceived. We are not the train operator. We have no contract with you for the train journey. Any such claim is likely to be struck out, and if you pursue it unreasonably after being told this, you may be ordered to pay our legal costs.
11.2 The Maximum We Will Pay You
11.2.1 Our Liability Is Capped at the Ticket Price
If we do something wrong in our payment processing role, the most we will ever pay you for any single claim is the price you paid for the ticket involved in that claim.Nothing more. This cap applies to all claims combined — you cannot multiply it by raising the same issue under different legal headings.
Example: you paid £25 for a ticket and we made a payment error. Our maximum liability for that incident is £25, regardless of how many legal arguments you make 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 Never Responsible For
11.3.1 Indirect and Consequential Losses
Even where we have done something wrong in processing your payment, 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 — of any kind, whether or not we could have foreseen it.
11.3.2 Why We Exclude These Losses
We are a payment processor. When you buy a ticket, we do not know why you are travelling, whether you have a connecting flight, what business meeting you are attending, or what the consequences would be if the train is late. We have no control over the train service at all. For consequential losses caused by train disruption, you should look to RAILWAY.UZ under their passenger rights process, and to any travel insurance you hold. We strongly recommend travel insurance for any journey where a disruption could cause you significant financial loss.
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.
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.5 We Are Not Responsible for Stripe's Failures
We are not liable for losses caused by Stripe's own systems going wrong — outages, data breaches, or technical failures within Stripe's infrastructure that are independent of how we have configured or used Stripe. Stripe is a separate company and their systems are not under our control. For problems with Stripe's own platform, contact Stripe atstripe.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.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, which courts can deal with disputes about them, and how to reach us formally. It applies to disputes about our payment processing role only. Disputes about your train journey are governed by RAILWAY.UZ's own terms and the laws of Uzbekistan.
12.2 Governing Law
12.2.1 English Law Applies to Our Payment Services
These Terms, and everything to do with how we run our payment platform — collecting payments, processing Stripe transactions, passing money to RAILWAY.UZ, detecting fraud, handling chargebacks, and processing refunds — are governed by the law of England and Wales.
That is the right choice because: we are incorporated in England and Wales (company number 12431111); we run our payment operations from the UK; our Stripe merchant account is held under Stripe's UK terms; and all our payment 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 Disputes About Our Payment Services Go to English Courts
Any dispute about these Terms or our payment platform — how we collected your money, processed it through Stripe, passed it to RAILWAY.UZ, handled a chargeback, or processed a refund — shall be decided by the courts of England and Wales, and only those courts.
By using the Website or making a payment, you agree to this. You also agree not to object to English courts on the grounds that they are inconvenient for you.
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. We are also not limiting 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
Wrong defendant: If your complaint is about the train — a delay, cancellation, refused boarding, seat problem, or any other aspect of the journey — your claim is against RAILWAY.UZ, not us. We have no liability for the train service. Taking action against us for a journey problem would be misconceived and is likely to be struck out.
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 ourPrivacy Policy and Cookie Policy, make up the whole agreement between you and us for our payment services. They sit alongside — and do not replace — your contract with RAILWAY.UZ for your train journey and Stripe's terms for card processing.
12.4.4 Third Party Rights
No one other than you and us has rights under these Terms, except that RAILWAY.UZ may enforce the clause about us passing them ticket sale proceeds (Section 6.3).
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 20 February 2026 and replace allearlier versions. v1.0 — 20 Feb 2026: First issue. v2.0 —Sections 7 and 8 added. v3.0 — Section 11 added. v4.0 — Section 2added. v5.0 — Plain language review: all sections rewritten forclarity; liability separation between AI Analytics and RAILWAYUZsharpened throughout. v6.0 — Full consolidation: all sections(Introduction, 1–12) merged into single document.
