Terms of Use

1. Acceptance

By using My Train Rescue, you agree to these Terms. If you do not agree, do not use the service.

2. Independent passenger-assistance service

My Train Rescue is an independent passenger-assistance service, not Indian Railways, IRCTC or NTES. Current in-app ticket issuance and live payment are disabled. If approved in-app booking becomes available, an authorized ticketing partner, rather than a search result or MTR prediction, must issue the railway ticket. Train numbers, station names and railway terminology are used to describe passenger journeys.

3. Railway data can change

Seat availability, PNR status, coach position, platform, train running information, arrival/departure times and refund outcomes may change. Provider endpoints can also disagree or update at different times. Always verify time-critical or safety-critical information with official railway channels, station displays or announcements.

4. Rescue recommendations

“Best”, “Smart Rescue”, alternate-date and similar recommendations are decision-support suggestions, not guarantees of seat confirmation, connection success or journey completion. Before booking or changing a trip, verify the final train, origin run date, boarding date, stations, class, quota and fare in the actual booking channel.

4A. Accounts, travel plans and possible booking

You may use basic journey search without an account. If you create an account, protect your credentials and save passenger details only with their authority. A saved berth choice is a preference, not an allocation. A travel plan saved in My Trips on this device is not a reservation, paid booking or ticket; it has no issued PNR.

If an authorized partner booking integration is enabled later, an exact fare quote and booking eligibility must be checked again for the selected train and run. Quotes expire and availability can change before payment. Two-leg journeys require separate tickets; paying for or receiving one ticket does not guarantee the second, a connection, the same coach or the same berth.

4B. Payment and ticket status

Live payment is currently unavailable in MTR. If approved checkout becomes available, the payment processor may confirm an order or capture money before the railway partner issues a ticket. MTR will label that state as pending and show a PNR only after authoritative ticket issuance. Do not travel on a payment receipt or device plan as though it were a railway ticket. A failed or unresolved issue after capture requires refund and support follow-up under the applicable partner and railway rules; MTR does not promise an automatic refund while those arrangements are unapproved.

4C. PayU sandbox check

A PayU test checkout is available only through an explicit account payment-test page when test credentials and account storage are ready. It uses PayU’s test site for a fixed ₹10.00 simulated transaction. It is separate from railway booking, does not make a real charge and cannot create a ticket or PNR. A returned success screen alone is not MTR verification; MTR checks the signed return and PayU’s transaction record first. Use test methods only and do not enter live card or bank credentials.

5. Refund and railway-rules tools

Rule summaries and refund estimates are informational. Actual eligibility, deduction, TDR acceptance and final refund are determined by the applicable railway rules and the competent railway/booking authority. Exceptional cases may require manual review.

5A. Voice actions

Cloud voice requires your explicit choice and microphone permission. A recording may stop after a quiet pause, with a maximum of 25 seconds; you can also stop or cancel it. A clear transcript can automatically start a read-only train search or live-status check and may receive a spoken browser reply. Uncertain station, train or date details should prompt clarification. Voice does not automatically book a ticket or start payment. Browser speech services and cloud transcription providers may handle audio under their own terms; available spoken voices vary by device.

6. PNR and passenger information

You should submit a PNR only when you are authorized to view that journey. Do not misuse the service to obtain or share another passenger’s information.

6A. Booking reminders and live watches

Calendar exports and reminders saved on this device remain separate from account reminders. On-page checks and their notifications or sound require the Alerts page to stay visible and your device to stay awake. Your calendar app controls alerts after you import a calendar file.

When the background service is available, a signed-in passenger may explicitly enable browser notifications and register a booking-opening or Tatkal reminder with their account. The server calculates the reminder from the train’s origin date, selected class and applicable opening-time rule; a shorter reservation window requires your confirmation. A declaration or reminder does not verify train-specific entitlement, hold a seat or guarantee that booking is available. Current-seat and station watches are not registered for server background delivery by this feature.

A status saying that the browser Push service accepted a send does not prove that your device displayed it or played a sound. Delivery can be delayed or suppressed by browser, operating-system, battery, permission or network restrictions. You can cancel future attempts or disable background alerts on this device from Alerts; a notification already accepted or in flight may still arrive. Account reminders can be viewed while signed in on another device, but a reminder is sent to the particular browser subscription chosen when it was registered. Keep a calendar reminder as a backup.

A station alarm requires fresh verified train progress and arrival estimates; a stale live status or timetable alone does not trigger it. Current-seat watches require provider-reported current-booking inventory and do not reserve a seat. Railway operations and provider outages can affect checks. Verify your journey through official railway announcements, station displays or other official channels, and do not use a station alarm as the only safeguard against missing your stop.

Navkar Wake and custom background audio are not available in this release. They will not be enabled or inferred without explicit user choice, documented audio rights and separate reliability proof.

6B. Account data controls

Your Account offers saved-passenger removal, a download of MTR account records and self-service deletion for accounts without payment-linked or unresolved bookings. Deletion requires your account email and the word DELETE. Accounts with a payment order, issued ticket, pending issuance or refund need support review before account records can be removed. Device-only travel plans must be removed separately in My Trips or by clearing browser storage. See the Privacy Policy for what MTR and its providers store.

7. WhatsApp sharing

When a share action opens WhatsApp, you are responsible for choosing the recipient and sending the message. Check the content before sharing passenger or journey information.

8. Prohibited use

• Do not attempt to bypass API limits, access controls or security.
• Do not scrape or bulk-extract data in a way that violates provider terms.
• Do not use the service for fraud, impersonation or unauthorized passenger-data access.

9. Availability

We may change, suspend or limit features when authentication, database, payment, ticketing, data-provider, hosting or railway systems are unavailable or change their interface. An unavailable booking or payment feature will not be presented as a completed ticket.

9A. Third-party railway data

Railway information may be supplied by third-party providers, including RailRadar. My Train Rescue uses that information only to provide customer journey functionality. It does not sell, resell, bulk-export or provide a separate downloadable copy of provider data. Live, availability and PNR data is cached only when reasonably necessary for performance or recovery; old information is clearly marked and is not presented as LIVE.

10. Liability

To the extent permitted by law, My Train Rescue is provided as an informational assistance service without a guarantee that every result is complete, current or error-free. Users remain responsible for checking final journey and ticket details. This clause does not replace any rights that cannot lawfully be excluded.

11. Operator and contact

Operator: Praveen Kumar Bhansali, India.

My Train Rescue is operated under the My Train Rescue brand by Praveen Kumar Bhansali. For product help, use the Help & Support page. A dedicated support email will be added after the official My Train Rescue domain is activated.