Privacy policy
Last updated 21 September 2026
Tripzo is an Indian Railways travel app: train search, live running status, seat availability, fares, PNR status, and hotels near the station you arrive at. This page says what it does with information, in the same detail we would want to read.
There is no Tripzo account. You do not sign up, and we hold no profile of you. There is no advertising identifier, no analytics SDK, no crash reporter and no third-party tracker in the app.
What stays on your device
Stored locally and never sent to us:
- your recent searches, capped and de-duplicated;
- your favourite trains;
- a journey you checked the PNR of — the train, the date and which berth, so Trips can show it. Nothing about a passenger: no name, no age, no gender. This is the same PNR the table below says we do not log or cache, and both are true: it is on your phone because you typed it, and not on our server.
- a hotel stay you booked through Tripzo — the hotel, the nights, the price we quoted you and which booking site took it. Recorded only when the booking site's own confirmation page appears, so opening a hotel, or starting a booking and not finishing it, records nothing. What we keep is what we already showed you before you booked; we do not read that confirmation page. Never the confirmation link or its PIN, because that PIN can be used to change or cancel your booking.
- a flight you booked through Tripzo — the airports, the date and time, the airline, how many of you were travelling and the fare we quoted you. Exactly the same rule as the hotel stay above: recorded when the booking site's own confirmation page appears, or when you tap Save yourself, so searching flights records nothing. Never a booking reference, a passenger name or an email — we do not read that confirmation page, only the address of it.
- your theme and language preference.
All of it stays on the phone that made it. There is no Tripzo account, no copy on our server and no syncing between your devices, so a stay saved on your phone will not appear on another one — and nobody else can be shown it, including us.
Uninstalling the app removes all of it. Clearing the app's storage does the same.
The microphone
Voice search is optional. Permission is requested at the moment you tap the microphone, never at launch, and if you decline, everything else keeps working.
When you use it, Android's own speech recognition converts what you said to text. Tripzo does not record, store or transmit audio. Only the resulting text reaches the app, and it goes into the search field where you can edit it before anything is looked up.
What is sent to our server, and why
Tripzo's backend exists to hold the railway and hotel data credentials, so they are not inside an app anyone can unpack. Requests carry only what a lookup needs:
| What | Why | Kept? |
|---|---|---|
| Train number, station codes, date, class, quota | To look up schedules, running status, fares and berths | Provider replies are cached briefly to avoid re-buying the same answer. Not tied to you. |
| A PNR, when you check one | To fetch that booking's status | No. It is neither logged nor cached. Request paths are logged without their query strings precisely so a PNR cannot land in a log file. |
| A place name or station code, dates, guests | To search hotels and compare prices | Provider replies are cached. Not tied to you. |
| The sentence you ask the assistant | To read the stations and the date out of it | Parsed on the server and not stored. The planning is Tripzo’s own and runs on Tripzo’s own servers — nothing you type is sent to an outside AI provider, and no third party receives it. |
Your IP address reaches our server as it reaches any website, and appears in ordinary web-server logs. We do not build profiles from it.
What we count
We keep a count of how often each part of Tripzo is used — searches, live status checks, PNR lookups, hotel searches, assistant questions — so we can tell which features are worth improving and when something has broken.
These counts carry no identifier. There is nothing in them that could tell one traveller asking twice from two travellers asking once, no IP address and nothing derived from one, and no text you typed. They are totals, not histories, and they cannot be traced back to you.
Alongside a count we keep the resolved subject of the request where there is one: the two station codes a route search matched, or a five-digit train number. Those are values from the railway's own catalogue, not what you typed.
A PNR is never among them — not the number, not a masked version of it, not a hash. Checking a PNR adds one to a counter and nothing else. Assistant questions are the same: that one was asked is counted, what it said is not kept.
Counts are deleted after 90 days. They are visible only to us, on a page that is not part of the app.
Location
Tripzo reads your position on two screens, and for two different reasons.
On a train’s live status, your phone reports which station the train has reached. The railway’s own feed speaks only when a train passes a reporting point, so between two of them it has nothing to say — and some trains, the unreserved passenger and MEMU services, are carried by no feed at all. A phone aboard is the only thing that can fill either gap.
On the taxi screen, your position fills the pickup field so you only have to type where you are going. That position is used on your phone and sent to nobody: it goes into the link you tap to open Ola, Uber or Maps, and nowhere else. Tripzo never receives it.
You are asked for location once, by Android, and never again. Whether you allow it or refuse it, that is the end of it — Tripzo will not ask a second time. If you refuse, nothing else about the app changes.
What we keep is a station, not a location. Your position is matched against the stops on that train’s own route and the nearest one is kept; the coordinates are discarded in the same step that reads them and are never written down. What remains reads “54633 was near Barwala at 15:08” — no identifier, nothing naming you, and nothing that could link one report to another. If your position is not near any stop that train makes, the report is dropped rather than stored. Reports are deleted ten minutes after they are made.
Never while the app is closed. Tripzo holds no background location permission, so it cannot read your position unless one of those two screens is open in front of you. Nothing keeps running after you leave them, and there is no notification to dismiss because there is no service to notify you about.
It is on unless you turn it off, and the switch is in Profile → Live train position. We chose that way round honestly: a setting nobody finds would mean a network of nobody, and these trains have no other source. Turning it off stops your phone reporting and leaves everything else working.
Distances to hotels are computed from the station’s published coordinates, not from where you are.
Who else sees a request
Railway and hotel data comes from licensed third-party providers, reached by our server on your behalf. They receive the query — a train number, a route, a PNR, a city and dates — and not your identity, because we do not have one to send.
When you choose to book, you leave Tripzo for the provider's own site: IRCTC for a train ticket, a hotel site for a room. What happens there is covered by their privacy policies, not this one. Tripzo never sees your card details, and takes no payment.
Children
Tripzo is not directed at children and collects nothing that would identify one. A child's age can be entered when searching hotels, because room pricing depends on it; it is used for that search and not stored.
Your choices
- Decline the microphone permission — voice search is the only thing affected.
- Clear the app's storage to erase searches, favourites and preferences.
- Uninstall — since there is no account, nothing of yours remains with us.
Changes
If the app starts doing something this page does not describe, this page changes first. The date at the top is the date it last did.
Contact
Questions about this policy: tripzohome@gmail.com