Privacy Policy

Where is my Metro ("we," "us," "our," or "the App") is a privacy-first, offline-first Delhi Metro transit application. This Privacy Policy explains what information the App handles, how it is used, and the choices you have.

In short: there are no accounts and no personal profiles. Route planning and location processing happen entirely on your device. The App uses Google Firebase for anonymous crash reporting and aggregate usage analytics so we can fix bugs and improve the App — nothing that identifies you personally, and nothing is ever sold or shared with advertisers.

1. No Accounts, No Personal Profiles

We do not collect, store, or transmit:

• Names, email addresses, or phone numbers
• User accounts or login credentials
• Age, gender, or demographic information
• Your search queries or route history (these stay on your device)

You can use every feature of the App anonymously, without signing up.

2. Location Data

If you grant location permission, it is used exclusively to:

• Display your current position on the map
• Calculate distances to nearby metro stations
• Show live tracking progress during a journey and estimate arrival times

All location processing happens on your device. Your coordinates are never stored, logged, or sent to our servers. Location data is held in memory only while tracking is active and is discarded when you stop tracking or close the App. During live tracking the App requests location updates every few seconds to provide accurate real-time ETAs; if GPS is unavailable, it falls back to schedule-based estimates. You can revoke location access at any time in your device's Settings, and the App remains fully usable without it.

3. Data Stored on Your Device

The App stores the following data locally only:

• Commute History: your most frequent routes (station IDs, trip count, last-used time; up to 50 recent trips) to power quick-access "Favorites". Stored via Android DataStore in the App's private, sandboxed storage.
• Theme Preference: your dark/light/system theme choice.
• Map Cache: temporary map tiles, managed and cleared by the OS.

This data is stored in the App's private, sandboxed directory and is encrypted at rest using an AES-256 key held in the Android Keystore (hardware-backed where the device supports it). It is never synced to any cloud service, and uninstalling the App permanently deletes all of it.

4. Crash Reporting & Analytics (Google Firebase)

To keep the App stable and understand which features matter, the App includes two Google Firebase services:

Service	What it collects	Purpose
Firebase Crashlytics	Crash stack traces, device model, OS version, app version, device state at the time of a crash (e.g. free memory), and a rotating installation identifier	Detecting and fixing crashes and bugs
Firebase Analytics	Aggregate app events (e.g. screen views, feature usage counts), device model, OS version, app version, coarse region derived from IP address, and a rotating app-instance identifier	Understanding which features are used so we can improve the App

• This data is pseudonymous — it is not linked to your name, email, or any account, because the App has none.
• Your precise GPS location, searches, routes, and commute history are never included in analytics or crash reports.
• We do not use advertising SDKs, and we never sell or share data with advertisers or data brokers.
• Data collected by Firebase is processed by Google under Google's Privacy Policy and the Firebase Privacy documentation. Analytics data is retained by Google for a limited period (we use the shortest practical retention setting) and crash data is retained only as long as needed to diagnose issues.

5. Map Tiles & Other Third-Party Services

• Map tiles: to render maps, the App fetches tiles from public providers such as OpenStreetMap using the open-source MapLibre library. These requests carry standard technical information (your IP address and user-agent) and are governed by the tile provider's privacy policy. Offline schematic maps are available without a network connection.
• Google Play Services: the App uses Play Services location APIs (FusedLocationProviderClient). Data handled by Play Services is governed by Google's Privacy Policy.

6. Data Security

• Local data lives in the App's private directory, protected by Android's app sandboxing, and is encrypted at rest with AES-256-GCM using a non-exportable key in the Android Keystore; other apps cannot access it.
• All network traffic (map tiles, crash/analytics uploads) uses HTTPS encryption in transit.
• The App contains no remote-code-execution, self-update, or data-exfiltration mechanisms.

7. Children's Privacy

The App is designed for general audiences and does not knowingly collect personal information from children. It requires no account, no name, and no contact details from any user. The pseudonymous diagnostics described in Section 4 apply equally to all users and are not used to identify or profile anyone. If you are a parent or guardian with concerns, please contact us (Section 10).

8. Your Rights & Choices

• Delete local data: uninstall the App — Android automatically deletes all locally stored data (commute history, preferences, cache).
• Revoke permissions: Settings > Apps > Where is my Metro > Permissions.
• Analytics/crash data: this data is pseudonymous and not linked to your identity, so we cannot look up "your" records. If you have concerns, contact us and we will help, including resetting identifiers where technically possible.

9. GDPR & CCPA

GDPR (EU/EEA): the limited pseudonymous diagnostics data described above is processed on the legal basis of legitimate interest (keeping the App functional and stable). We do not process special-category data and we do not profile users. CCPA (California): we do not sell or share personal information as defined by the CCPA. This policy is provided in English; if a translation conflicts, the English version governs.

10. Contact Us

Questions, concerns, or feedback about this Privacy Policy:

Email: studioradiantnest@gmail.com
Subject: "Privacy Inquiry – Where is my Metro"

We aim to respond within 7 business days.

11. Changes to This Policy

We may update this Privacy Policy to reflect changes in the App, technology, or legal requirements. Material changes will be reflected on this page with an updated effective date. Continued use of the App after changes constitutes acceptance of the revised policy.