1. Using MetroPing
These Terms apply when you use MetroPing. By selecting “Agree and continue” or using the Application, you agree to these Terms and acknowledge the Privacy Policy. If you do not agree, do not use the Application.
2. What MetroPing provides
MetroPing provides route planning, nearby-station assistance, active journey progress, destination and interchange alerts, reminders and related metro features. Features, supported cities, route information and availability may change as the service improves.
MetroPing is an independent utility and is not affiliated with or endorsed by Delhi Metro Rail Corporation or another transit operator unless the Application expressly states otherwise.
3. Travel and safety
Routes, station detection, journey progress and alerts may be inaccurate, delayed, duplicated or unavailable because of underground signal loss, connectivity, device restrictions, permissions, battery settings, transit changes or software defects. Always follow official signs, announcements, staff instructions and local safety guidance. MetroPing is a convenience and must not be your only source of travel or emergency information.
4. Permissions and notifications
Some features need location, background location or notification permission. You control these permissions in MetroPing and your device settings. Denying a permission may prevent the related feature from working. Stronger alarm features should be used only for journeys you deliberately start.
5. Optional account and sync
Core local route and destination-alert features do not require an account. If you choose Google or Apple sign-in, MetroPing may link this installation to a MetroPing account and sync supported completed journeys, recent destinations, station visits and account settings so they can be restored on signed-in devices.
Keep your identity-provider account and device secure. Signing out stops that account session but does not delete the server copy. External beta builds may offer “Deactivate beta account,” which blocks access but deliberately retains the account and linked beta data. That option is not deletion. Use “Delete account permanently” or the account-deletion pageto erase the account as described in the Privacy Policy.
5.1 Required production operational check-in
After you accept these Terms, Android and iOS production builds send a first-party operational check-in when the app starts or returns to the foreground. It contains a random app installation/session identifier, timestamp, app/build, platform, operating-system version and general device model/type so MetroPing can verify service and release compatibility and investigate affected versions. It excludes account, advertising-ID, location, route, journey, search, screen, tap and user-entered data and is not forwarded to third-party analytics services. Optional product analytics remains a separate choice.
If you grant notification permission, a production build may also register a Firebase Cloud Messaging or Apple push token with MetroPing for operational service and release-update delivery. Registration is associated with a random installation identifier, platform, production distribution mode, app variant, supported service-city scope, and notification-preference flags. Marketing topics remain separately consent-gated, and production promotions remain disabled.
6. Internal and closed testing builds
Internal and closed-testing builds are pre-release software and may be less stable, may change without notice and may be withdrawn. Testers must use the build only through the Google Account and opt-in route authorized for the relevant Play testing track.
A closed-testing build uses the reviewed store-safe rider surface. Remote experimental activation remains disabled. After notification permission is granted, it may register a distribution-scoped token for operational notifications. Marketing delivery remains off until you separately opt in through the in-app marketing prompt; after consent, categories start enabled and can be adjusted or fully disabled in notification settings. It sends no tester analytics or automatic diagnostics before acceptance. After the tester separately selects “I agree to required tester diagnostics” and presses “Accept terms and start testing,” the build sends its required high-detail testing tier: a first-party operational heartbeat plus app/session identifiers, build and general device data, interactions, selected and current stations, routes, journey progress, alert and background-reliability outcomes, coarsened connectivity observations, crashes, errors and performance diagnostics. Current-station and station-segment context can reveal or infer precise physical location even though the testing events exclude raw GPS coordinates and continuous location trails. Firebase Analytics receives filtered product events, Microsoft Clarity receives screens viewed and tap interactions with on-screen text masked, and Sentry receives filtered crash, error and performance reports. Advertising storage remains denied. The collection also excludes advertising identifiers, passwords, verification codes, contacts, messages and private files. The telemetry control is unchecked initially and the final action remains disabled until the tester selects it. Selecting it gives the separate affirmative telemetry choice; pressing “Accept terms and start testing” accepts these Terms and acknowledges the Privacy Policy; Additional data terms for the smaller internal testing programme are in the Internal Testing Terms.
Required closed-test collection cannot be turned off while continuing to use the testing build. To withdraw and stop future collection, leave the Closed test and uninstall the build. You may request deletion of first-party tester records MetroPing can locate; information already processed by service providers follows their applicable retention and deletion controls.
6.1 Google Play open testing
An open-testing build is pre-release software that any eligible Google Play user may choose to join. It may be less stable, change without notice, or be withdrawn. You must install it through the official Google Play open-test opt-in route.
The build sends no tester analytics or automatic diagnostics before acceptance. After you separately select “I agree to required tester diagnostics” and press “Accept terms and start testing,” the open-testing build sends the required medium-high testing tier listed in its prominent in-app disclosure and the Privacy Policy. It uses the same disclosed data categories as Closed testing with coarser connectivity sampling and time buckets: app/session identifiers, build and general device data, interactions, selected and current stations, routes, journey progress, alert and background-reliability outcomes, crashes, errors and performance diagnostics. Current-station and station-segment context can reveal or infer precise physical location even though raw GPS coordinates and continuous location trails are excluded. Firebase Analytics, Microsoft Clarity and Sentry process only their disclosed subsets; advertising storage remains denied. The collection also excludes advertising identifiers, passwords, verification codes, contacts, messages and private files. If you do not agree, do not join the Open test. To withdraw and stop future required collection, leave the Open test and uninstall the build. You may also request deletion as described in the Privacy Policy; provider-held records remain subject to applicable provider retention and deletion controls.
After notification permission is granted, an open-testing build may register a distribution-scoped token for operational notifications. Marketing delivery remains off until you separately opt in through the in-app marketing prompt; after consent, categories start enabled and can be adjusted or fully disabled in notification settings.
7. Apple TestFlight external testing
An external TestFlight build is pre-release software provided for evaluation and feedback. It may be less stable, may change without notice, may expire, and may be withdrawn. You must obtain and use it through Apple TestFlight and comply with Apple's applicable TestFlight terms.
The external build requires the beta telemetry described in its in-app disclosure and the Privacy Policy. The current external profile sends first-party tester telemetry, Firebase Analytics, Microsoft Clarity and Sentry crash reports only after you select the separate required-diagnostics agreement and press “Accept terms and start testing”. If you do not agree, do not continue using the build. Leave the TestFlight programme and uninstall it to stop future beta collection.
A signed-in external tester may deactivate the beta account and retain its data for a later return, or separately choose permanent deletion. Beta deactivation is a supplementary pre-release option and never replaces permanent deletion, which remains separately available. The production Application presents permanent deletion as the primary account-removal action. Details and the email fallback are on the account-deletion page.
8. Responsible use
You must not:
- Use MetroPing in a way that creates danger or unlawful distraction;
- Attempt unauthorized access or bypass security or usage limits;
- Interfere with the service, another user or transit operations;
- Use any testing-only sharing feature to expose another person’s information without permission;
- Upload unlawful, harmful or infringing content.
9. Feedback and submitted material
If you submit feedback, corrections or other support material, you confirm that you have permission to share it. Closed-testing, open-testing and production builds do not offer screenshot or file attachments. You allow MetroPing to use that submission to respond, investigate problems, correct route information and improve the service. Do not submit passwords, verification codes or unrelated sensitive information.
10. Third-party services
MetroPing may rely on mapping or transit information, Google and Apple platform services, Firebase, hosting services and other providers described in the Privacy Policy. Their services and external links may be governed by their own terms. MetroPing is not responsible for an external service after you leave the Application.
11. Availability, updates and termination
MetroPing may add, change, suspend or discontinue features and may require an update for security, compatibility or reliability. Access may be limited or ended for misuse, security risk, legal requirements or discontinuation of the service. You may stop using MetroPing and uninstall it at any time.
12. Disclaimer and liability
To the extent permitted by law, MetroPing is provided “as is” and “as available” without guarantees that routes, alerts or the service will always be accurate, timely, uninterrupted or error-free. Nothing in these Terms excludes rights or liability that applicable law does not allow to be excluded.
13. Changes and contact
These Terms may be updated when MetroPing’s features, providers or legal obligations change. Material changes may require acceptance again. For questions, contact business24guru@gmail.com.