Data Usage Policy

• Required

  INTERNET

  Needed to load OpenStreetMap tiles and serve AdMob advertisements.

• Optional

  ACCESS_FINE_LOCATION / ACCESS_COARSE_LOCATION

  Used for GPS route tracking and finding nearby stations. You can deny or revoke this at any time; core route planning works without it.

• Required (Play policy)

  AD_ID

  Declared as required by Google Play when AdMob is integrated. Only used by AdMob if you consent to personalised advertising.

• Optional

  POST_NOTIFICATIONS (Android 13+)

  Requested only when you start route tracking; used to display the foreground-service notification showing your current journey progress.

The following features operate entirely on your device with no network communication:

• Route planning and transfer calculation across M1–M5
• Timetable lookups and next-train calculations
• Station search and line filtering
• Door-opening direction indicators
• Station notes and favourite route storage
• Theme, language, and font-size preferences
• GPS route tracking progress display
• Crash report storage (until you send one)

The following are the only situations in which data leaves your device:

• OSM tile requests — when you open the map view, tile images are fetched from OpenStreetMap servers. These are standard HTTP GET requests; OSM servers may log your IP address per their own privacy policy.
• OSRM routing queries — when map-based navigation is active, waypoints are sent to an OSRM instance for routing calculations.
• AdMob ad requests — when ads are loaded, Google AdMob receives device and context signals (see Section 5).
• Crash report emails — only if you manually choose to send one from Settings → Crash Reporting.
• External app launches — opening a location in Google Maps or a similar app is initiated entirely by your tap.

Metrou București uses Google AdMob to display banner advertisements. AdMob is subject to Google's privacy policies and EU GDPR requirements.

On first launch the App shows a GDPR consent dialogue via Google's User Messaging Platform (UMP). Your choices:

• Consent granted — AdMob may show personalised ads using your Advertising ID, device model, OS, network type, and approximate location.
• Consent declined — AdMob shows contextual (non-personalised) ads. Some contextual signals (app context, general location) are still used.

For Google's full data practices see: Google Privacy Policy and AdMob data disclosure.

App data (local)

• Retained on your device until you clear app data or uninstall the app
• Station notes and favourites can be deleted individually within the app
• All local data is permanently removed when you uninstall Metrou București

AdMob data

• Managed by Google per their data-retention policies
• You can reset your Advertising ID at any time via Android Settings

Crash reports

• Stored locally until you delete them or send them via email
• Manageable from Settings → Crash Reporting

• Location access — grant or revoke in Android Settings → Apps → Metrou București → Permissions
• Ad personalisation — opt out via Android Settings → Google → Ads, or reset consent inside the app
• Crash reports — view, send, or delete individual reports in Settings → Crash Reporting
• All app data — clear via Android Settings → Apps → Metrou București → Storage → Clear Data, or by uninstalling

• All local data is protected by standard Android application sandboxing
• Network connections to OSM and AdMob use HTTPS/TLS
• No sensitive personal data (passwords, financial information, health data) is ever collected or stored
• The App does not implement its own user accounts or authentication

We will update this policy when data practices change materially — for example if new third-party services are added. Changes are indicated by the "Last updated" date above. Continued use of the App after the effective date constitutes acceptance.

For data-related questions or requests:

• Email: help@metroubucuresti.ro
• In-app: Settings → About → Contact
• Website: www.metroubucuresti.ro