Data retention policy

Last updated: 14 April 2026 · App: Hyderabad Metro Routes

This policy explains how long different categories of locally stored and cached data are kept when you use the Hyderabad Metro Routes app. It should be read together with our Privacy policy.

1. Summary

The App does not maintain a central database of your journeys on Publisher servers. Retention is governed by on-device storage, in-memory caches, and third-party services you trigger (such as place search).

2. Recent route searches

What: A small list of recent route queries (origin, destination, optional via points, and route preference).
Where: Device storage via the platform’s preferences storage (e.g. SharedPreferences on Android).
How long: The App keeps only the most recent few entries (capped at a maximum number). Older entries roll off automatically when you add new searches.
Deletion: Cleared when you clear app data, uninstall the App, or when the OS removes the App’s storage.

3. Place search cache

What: Cached place search results and resolved “nearest station” hints to improve responsiveness and reduce repeat network requests.
Where: A local JSON cache file in the App’s cache directory, plus in-memory cache while the App is running.
How long: Kept until the cache file is overwritten, deleted by the system, or removed when you clear app data or uninstall. The App does not guarantee a fixed calendar retention period; treat cached entries as ephemeral.
Deletion: You can remove this data using your device’s “Clear storage” / “Clear cache” options for the App, or by uninstalling.

4. Network map and images

What: A network diagram image may be loaded from the Internet when you open the map screen.
Retention: Any image caching is handled by the operating system or HTTP stack; the App does not define a separate long-term retention policy for those bytes.

5. Third-party services (Nominatim)

When you search for a place, the App may send your query text to OpenStreetMap Nominatim. That service may log requests according to its own policies. See Nominatim usage policy. The Publisher does not control retention on Nominatim servers.

6. No server-side retention by Publisher

The App, as shipped from this open-source project, does not upload your journey history to Publisher-operated databases. If a future release adds optional cloud features, this policy will be updated before release.

7. Contact

Questions about this policy can be directed to the Publisher via the contact information on the app store listing for Hyderabad Metro Routes.