This policy explains how RailMate India (“RailMate”, “we”, “us”) handles information when you use the RailMate India Android application and its related services.
1. Information we process
| Data | Why it is used | When it is used |
|---|---|---|
| Train number, train route, station, journey date, class and quota selections | To show train information, live status, availability, fares, station information and train comparisons. | When you use the relevant search feature. |
| PNR number and the journey information returned for it | To retrieve and display PNR status at your request. | Only when you enter a PNR number. |
| Precise device location | To provide the destination/approach alarm, calculate proximity to your destination, and optionally record app-install region for service operation and diagnostics. | Only after you grant location permission. Background location is used only while an alarm you started is active. |
| Alarm settings | To run your selected destination alarm, including destination, distance threshold and journey timing. | When you create an alarm. |
| Shared journey details | To create a journey-status link when you choose Share Journey Live. | Only when you choose to share. |
| Device, advertising and diagnostic information | To serve ads, measure ad performance, prevent fraud and diagnose reliability issues. | When the app or advertising SDK operates. |
2. How we use information
- Provide railway searches, live train status, station information, fares, seat availability and route comparison.
- Operate location-based destination and approach alarms you explicitly enable.
- Create a shareable journey link only when you request it.
- Maintain security, troubleshoot errors and improve service reliability.
- Display advertising and measure advertising performance.
3. Location data
RailMate requests location only for features that need it, principally the destination/approach alarm. You may use train search features without granting location permission. If you grant location permission, you can later withdraw it in Android Settings. Withdrawing it stops location-based alarm detection; time- or network-based information may still be shown where available.
RailMate does not sell precise location data. We do not use precise location to build a marketing profile. Location is not used in the background unless you have an active alarm that requires it.
4. PNR and journey data
A PNR number can reveal travel-related information. RailMate sends the PNR number only to retrieve the result you requested through our service providers. Do not share a PNR or a journey-status link with people you do not trust. Shared links may be accessible to anyone who receives the link.
5. Advertising
RailMate uses Google Mobile Ads (AdMob) to show advertisements. Google and its advertising partners may process device identifiers, IP address, app interaction data, approximate location inferred from IP address and other information described in Google’s privacy materials to deliver, limit and measure ads, including personalised ads where permitted and consented to. You can manage advertising preferences in your Android device settings and, where shown, in the consent choices presented in the app.
6. Sharing and service providers
We share data only as needed to deliver the service:
- Railway-data providers: selected train, station, date, PNR and related query information needed to return the requested result.
- Hosting and database providers: to operate RailMate’s API, alarms, shared-link service and security logs.
- Google/AdMob: to serve and measure ads as described above.
- People you choose: when you use the Share Journey Live feature.
We do not sell your personal information.
7. Retention and security
We retain information only for as long as reasonably necessary for the purpose described in this policy, including service operation, security, fraud prevention and legal obligations. Search and alarm preferences may be stored on your device. Server logs and shared-journey records may be retained for a limited period for operational and security purposes. We use reasonable safeguards, but no internet or storage system can be guaranteed completely secure.
8. Your choices and controls
- Do not grant location permission, or revoke it at any time in Android Settings.
- Stop or delete an alarm in the app to stop its ongoing monitoring.
- Choose whether to create or share a live journey link.
- Manage advertising preferences through Android/Google settings.
- Contact us to request access, correction or deletion of personal data we hold, subject to applicable law and identity verification.
9. Children
RailMate is not directed to children under 13. We do not knowingly collect personal information from children under 13. If you believe a child has provided personal information, contact us so we can investigate and delete it where appropriate.
10. Changes to this policy
We may update this policy when the app or applicable requirements change. We will publish the updated version on this page and revise the effective date.
11. Contact
For privacy questions or requests, email privacy@laanchpad.in.
Google Play Data Safety summary
This summary is provided to help keep the Play Console Data Safety form consistent with this policy. Review it against the exact build and every SDK before submitting.
| Data category | Collected | Purpose |
|---|---|---|
| Location – precise location | Yes, permission-based | App functionality (destination/approach alarms); optional service diagnostics/install region. |
| Personal info – other user-provided travel information (PNR) | Yes, when entered | App functionality. |
| App activity – in-app searches/interactions | May be processed | App functionality, analytics/diagnostics and advertising measurement. |
| Device or other identifiers | Yes, through advertising SDKs | Advertising, fraud prevention and analytics/diagnostics. |
Important: If a released build contains additional analytics, crash-reporting, login, payment or messaging SDKs, update both this policy and the Play Console Data Safety answers before release.