Privacy Policy

Last updated: 24 October 2026

This Privacy Policy explains what RailTrack — an Indian Railways passenger companion app for Android — does with information when you use it. The short version: RailTrack has no accounts, no sign-in, and no advertising trackers. Your searches, alarms, and favourites live on your phone, not on our servers.

RailTrack is developed and published independently. It is not affiliated with, endorsed by, or connected to Indian Railways, IRCTC, NTES, or ConfirmTkt. Questions about this policy can be sent to support@railtrack.app.

1. Information we do not collect

RailTrack does not ask for, and does not collect, your name, email address, phone number, contacts, photos, or any government identifier. There is no registration form, no login screen, and no profile. The app identifies an installation only — the same way any app on your phone is tied to that device — and that identifier is never linked to who you are.

2. Information stored on your device

To work, RailTrack keeps the following on your phone, in its own local database and preferences store:

• Your searches and history across routes, trains, stations, and PNRs;
• Your favourites and bookmarks;
• Alarms you set, including the train, station, and minutes-before-arrival offset;
• Settings such as language (English or Hindi), theme, and notification preferences;
• Cached timetables, station boards, and train data so results open instantly and work offline;
• Offline map regions you choose to download;
• Supporter tip state, so the app knows whether you have tipped.

None of this is uploaded to a developer server. It stays on the device until you delete it inside the app (for example, by clearing history), clear the app's storage in Android settings, or uninstall the app — any of which removes it.

3. Location

RailTrack uses your location for exactly two purposes, both of which you control:

• Nearby stations. With location permission, the app can show stations near you instead of making you type a station name.
• Journey tracking. While a journey you started is being tracked, the app may use location in the background through a foreground service, so live position updates continue when the app is not in the foreground. Background location is used only for the duration of that tracked journey.

Location data is used to answer your request — for example, to find nearby stations or to place your train on the map — and is not stored on a developer server, sold, or shared with advertisers. You can revoke location permission at any time in Android settings; nearby-station suggestions and background tracking will simply stop working until you grant it again.

4. Notifications and alarms

Wake-up alarms are the reason RailTrack asks for notification and exact-alarm permissions. An alarm you set is stored on your device and scheduled with the system alarm service, so it can fire even if the app process was closed, and it is re-armed automatically after your phone restarts. RailTrack does not send you marketing notifications.

5. Information sent over the network

When you use a connected feature, the app sends the minimum needed to answer your request:

• Route and station queries send station codes and dates to the app's first-party data source.
• Live status, station boards, and PNR checks send the train number, station code, or PNR you entered to rail data sources — directly where the source is public, and through the developer's own proxy server where the source requires credentials. Those credentials live only on the proxy server and are never embedded in the app.
• Map tiles and rail geometry are fetched from public map services (Esri tiles and OpenStreetMap-derived geometry), and currency display conversions, where shown, use a public exchange-rate source.

As with any internet service, those servers may log technical details such as your IP address in their own server logs; RailTrack does not attach your identity to these requests because it has none to attach. All app traffic uses HTTPS.

6. PNR numbers

A PNR is sensitive travel information. RailTrack sends a PNR only when you explicitly ask it to check one, and only to the rail data source that can answer. Your PNR history is kept on your device alone, never on a developer server, and you can delete individual entries from History at any time. Do not share screenshots of PNR details publicly — anyone with the number can look up the booking.

7. Purchases and supporter tips

Voluntary supporter tips are processed entirely by Google Play Billing. RailTrack never sees, handles, or stores your card number or any other payment credential; it receives only the purchase state (whether a tip went through) so it can show your supporter status. Google's own privacy policy governs the payment itself, and a monthly tip is managed — including cancellation — from your Google Play subscriptions, not from inside RailTrack.

8. Advertising and analytics

RailTrack carries no advertisements and no advertising SDKs, and it does not use third-party analytics or tracking SDKs to follow you across apps or websites. The supporter model exists precisely so the app does not need advertising revenue.

9. Sharing of information

RailTrack does not sell personal information, and it does not share information about you with third parties for their own marketing. Information leaves your device only as described in sections 5–7: to answer a query you made, to fetch a map or rate, or to process a tip through Google Play. If the law requires disclosure, we will disclose only what is legally required and only to the extent required.

10. Children

RailTrack is a general-audience travel utility. It is not directed at children, and because it has no accounts and collects no contact information, it does not knowingly collect personal information from children. A parent or guardian who believes a child has submitted information through the app can contact us at support@railtrack.app and we will help remove any on-device data where we are able to.

11. Security

All network traffic from the app uses HTTPS. Partner credentials for rail data sources are held server-side on the developer's proxy, never shipped inside the app. On-device data is protected by Android's own app-sandboxing: other apps cannot read RailTrack's storage without your device being compromised at the system level. No method of transmission or storage is perfectly secure, but the design keeps the sensitive surface as small as possible — mostly, by not collecting the data in the first place.

12. Retention and deletion

On-device data is kept until you delete it, clear the app's storage, or uninstall the app. Because there is no developer-side account or profile, there is no server-side copy of your journeys to request deletion of — removing the app removes the data. If you need help, write to support@railtrack.app.

13. Changes to this policy

If this policy changes in a way that affects what the app does with information, the updated policy will be published on this page and the “Last updated” date above will change. Continued use of RailTrack after a change means you accept the updated policy.

14. Contact and governing law

Questions, requests, or concerns about privacy can be sent to support@railtrack.app. This policy is governed by the laws of India.