1. Internal pre-release access
These terms supplement the main MetroPing Terms of Useand apply only to invited internal testers using a pre-release MetroPing build. The build may be incomplete, unstable, changed without notice, or withdrawn at any time. It is provided for testing and feedback, not as a guaranteed transport or safety service.
2. Journey and safety limitations
Journey progress, station detection, destination alerts and interchange alerts may be inaccurate, delayed, duplicated or unavailable because of underground GPS loss, connectivity, device restrictions, permissions, battery settings or software defects. Always follow official station signs, announcements and transport-operator instructions. Do not rely on MetroPing as your only source of travel or safety information.
3. Required first-party tester data
Internal builds collect limited telemetry needed to identify and fix functional defects. This can include random install and session identifiers, app/build and operating-system versions, device model, tester classification, timestamps, screens and features used, selected station and route names, service-city tags, station-segment duration, journey progress, tester-participation counts, alert and notification status, permissions, updates, errors, crashes and background-task health.
A notification delivery token may be registered with the random install identifier, platform and app variant so testing, service and update notifications can reach the device. MetroPing may record notification delivery, open and action status to evaluate reliability.
Passwords, verification codes, contacts, messages, advertising identifiers, typed private content, raw GPS coordinates, photos, videos, files and a continuous location trail are not included in required tester analytics. Material you deliberately submit to support or a sharing feature is handled under the Privacy Policy instead.
4. Default saved-journey reminders
To exercise reminder delivery during internal testing, the build turns on Saved journey reminders by default. These reminders are generated from on-device app-usage patterns and are sent shortly before a time when you usually use MetroPing. Delivery still depends on your device notification permission. You can turn Saved journey reminders off at any time in MetroPing's Notification settings or disable MetroPing notifications in your device settings.
5. Testing analytics and diagnostics
Accepting the combined internal-testing disclosure enables required first-party tester telemetry, Firebase Analytics, Microsoft Clarity and Sentry in the current internal profile. Firebase may receive product events and basic app, operating-system and device context. Clarity may receive screens viewed and tap interactions. Sentry may receive crash and error reports, with personal fields filtered before sending. Advertising storage, personalization and user data remain denied. These settings are fixed by the release profile and cannot be silently enabled by a local build file. If you do not agree, do not continue using the internal build.
MetroPing may also run a narrow PostHog pilot for invited Internal testing. The app does not connect directly to PostHog. MetroPing's backend forwards only allowlisted semantic events with one-way pseudonymous installation and event identifiers, bucketed values and fixed technical context. PostHog autocapture, session replay, person profiles and GeoIP enrichment are disabled. The forwarded data excludes station names, raw GPS coordinates, account identity, free text and arbitrary event properties. This pilot is not enabled for Closed, Open, External TestFlight or Production distributions.
A separate, bounded Supabase Storage pilot may hold administrator-uploaded promotion artwork in a private bucket so MetroPing's backend can serve selected artwork. It does not store tester telemetry, account or journey records, feedback text or feedback attachments in Supabase.
6. Optional account and sync
If you choose Google or Apple sign-in, MetroPing processes the identity information made available by that provider and Firebase, then links this installation to your MetroPing account. While signed in, supported completed journeys, recent destinations, station-visit timeline, credits and account settings may sync to the server and other signed-in devices. Account use is optional for core local route and destination-alert features.
7. Feedback
You may provide bug reports and suggestions. Where the current internal profile enables it, you may also select a screenshot after the in-app picker shows a separate disclosure. The picker does not accept recordings or general files. Supabase is not currently used for feedback attachments. You confirm that you have permission to share submitted material and allow MetroPing to use it to investigate, improve and test the service. Avoid including passwords, verification codes or unrelated personal information.
8. Responsible testing
Do not test in a way that creates danger, distracts you while walking or travelling, interferes with transport operations, attempts unauthorized access, exposes another person’s information, or violates applicable law.
9. Updates and termination
Test builds may require frequent updates. Older builds may stop working. MetroPing may suspend tester access, end a test, reset test data or ask testers to reinstall when required for reliability, security or privacy.
10. Privacy and deletion
The Privacy Policy explains data handling and choices. A pre-release build may offer “Deactivate beta account,” which blocks sign-in while keeping the account and testing data; it is not deletion. “Delete account permanently” remains available separately. Account or data-deletion requests can also be made using the account-deletion page or the contact address below.
11. No warranty
To the extent permitted by applicable law, the internal build is provided “as is” and “as available,” without guarantees of accuracy, availability, alert delivery or fitness for a particular journey.
12. Changes and contact
Material changes may require acceptance again. Questions can be sent to business24guru@gmail.com.