Privacy center

Privacy Policy

Information about data and device permissions when you use G Navigation on an Android phone and on a paired Huawei, Xiaomi/Redmi Vela, or Amazfit Zepp OS watch.

Version 10Updated September 12, 2026Data controller: Nguyen Thanh Hung

At a glance

No advertisingNo data sales or advertising SDKs. Map SDK data is described below.
Purpose-limitedLocation and journey data support search, routing, and guidance.
Your controlWithdraw consent, decline optional access, or delete local data.
01

App information

Google and Petal Maps icons. Google/Google Maps names and icons in G Navigation identify a Google service or a control that opens Google Maps. The Petal Maps icon identifies controls for opening or setting up Petal Maps; when it is installed, G Navigation reads its app icon from the phone. Available controls vary by release and installed apps.

Google, Google Maps and their related icons are trademarks of Google LLC. HUAWEI, Petal Maps and their related icons belong to the respective Huawei rights holders. G Navigation is independently developed by Nguyen Thanh Hung; displaying these names or icons does not imply sponsorship, endorsement or joint publication by Google or Huawei.

Displaying an icon does not itself grant permissions or send data to the named app. When you open Google Maps or Petal Maps, that app operates under its own permissions and policies. G Navigation reads guidance from sources supported by the release only after you enable the feature and grant notification access, to relay necessary directions to your selected watch. Map SDK, sign-in and other service data are described separately under Data sources and recipients.

App name
G Navigation
Android identifier
com.gnavigation.mobile
Huawei watch identifier
com.gnavigation.watch
Platforms
Android, Huawei Watch Full/Lite, Xiaomi/Redmi Vela, and Amazfit Zepp OS
Developer / data controller
Nguyen Thanh Hung
Privacy contact
hng89tn@gmail.com
02

Data processed

  • Approximate or precise location, location-service status, and — during an active navigation session — the current fix sent from a Huawei Lite watch to the phone (coordinates, altitude, accuracy, and timestamp). Fixes that are not accurate enough are discarded.
  • Search queries, destinations, origins, routes, route geometry, journey progress, and guidance steps.
  • When you explicitly enable notification access: Google Maps guidance content and, if call alerts are enabled, the caller name, source app (Zalo, Telegram, or Viber), ringing/video-call state, and action labels on a call notification.
  • Pairing, connection, and watch-capability state; network/Wi-Fi connection state; the installation state of specifically declared companion/store apps and, when setup guidance needs it, the companion app's installer source. The app does not scan the full installed-app list.
  • Minimized technical diagnostics required to detect connection or navigation-session failures.
  • When you use a trial or Premium: account identifier, name/email when returned by the sign-in provider, session token, a hashed app-scoped Android identifier (or random installation fallback), trial times, and Premium entitlement state. For a Google Play transaction, the system processes the product ID, purchase token, and purchase/verification/revocation times to grant or restore access; G Navigation does not receive the card number or full payment details.
  • The Google Play build processes app, licence, and device-integrity verdicts plus one deviceRecall bit recording that the device received a trial. To limit trial abuse, the server also creates a salted one-way daily hash derived from the IP address; Cloudflare and service providers may process standard network data such as an IP address under their own policies.
  • A consent record containing the policy version, acceptance time, and selected language.

Before you accept the policy, the app shows only setup, policy, and help screens; it does not initialize maps, location, Wear Engine, journey caches, or navigation-related network requests.

03

Purposes

  • Showing maps, finding places, and ranking results for your current area.
  • Calculating car, motorcycle, bicycle, or walking routes; following a route; and rerouting when needed.
  • Maintaining a foreground navigation session that you start and displaying turn alerts.
  • Receiving Google Maps guidance or relaying Zalo, Telegram, or Viber call alerts and answer, decline, or hang-up actions when you enable each corresponding optional feature.
  • Sending guidance, route geometry, and journey state to your paired Huawei watch.
  • Remembering consent, settings, and state required for reliable app operation.
  • Authenticating accounts, limiting trials per account and device, preventing fraud, and restoring Premium.
04

Device permissions and access

Approximate / precise location

ANDROID · WATCH FULL

Determines position, biases search results, follows routes, and provides real-time guidance.

Background location

ANDROID · OPTIONAL

Used only to help continue trip tracking when the app is no longer in the foreground or the foreground service is interrupted by the system. It is not a core requirement and is offered separately after setup.

Notifications

ANDROID

Shows the active foreground-navigation notification and navigation alerts and, on supported Android versions, asks the system to present the active trip as a Live Update.

Notification access

ANDROID · OPTIONAL

Android grants system-level notification access. Only after your consent and opt-in, G Navigation filters Google Maps for guidance or Zalo, Telegram and Viber for caller names, state and answer/decline/end actions, including in the background or while not navigating. Unrelated notifications are ignored; chat message contents are not saved or forwarded. Necessary names and state pass through Android or the companion app to your selected watch, without upload to G Navigation servers. Temporary contact entries and technical logs are described under retention.

Nearby devices (Bluetooth)

ANDROID

Used to find and keep the link to your paired watch. The app does not derive location from Bluetooth and requests no audio-recording permission.

Read and write Contacts

ANDROID · OPTIONAL

READ_CONTACTS and WRITE_CONTACTS are separately explained and requested to create a temporary entry from a notification name and representative number, check collisions, and find and clean up G Navigation's entries. Matching contact results may be read to avoid overwriting data; the app does not upload the address book or edit existing contacts. Temporary entries may appear in Contacts and be read by the companion app to display names on the watch. WRITE_SYNC_SETTINGS disables synchronization of the app-owned contact account on newer Android versions; the app does not initiate cloud sync for this account. Declining still allows navigation and call alerts, but names may not appear.

Manage app-owned calls

ANDROID · OPTIONAL

MANAGE_OWN_CALLS creates a local bridge call; MODIFY_AUDIO_SETTINGS supports Bluetooth audio during the conversation. Watch actions are passed to the source notification's buttons. No paid cellular call is placed, call log read or audio recorded. Optional MANAGE_ONGOING_CALLS access through REQUEST_COMPANION_PROFILE_WATCH is requested separately solely to identify the app/state of Telegram/Viber calls already handled by Android and avoid duplicates; that observer does not read caller names/numbers or control those calls. Zalo does not require this observer access. Release builds do not request phone-state permission.

Foreground service and wake lock

ANDROID

FOREGROUND_SERVICE, FOREGROUND_SERVICE_LOCATION, FOREGROUND_SERVICE_CONNECTED_DEVICE and WAKE_LOCK maintain navigation or watch call functionality you enabled. Call standby has its own notification and may run without navigation; it stops when you disable the feature or withdraw consent. RECEIVE_BOOT_COMPLETED and REQUEST_COMPANION_START_FOREGROUND_SERVICES_FROM_BACKGROUND help restore an enabled feature when Android allows it. The app does not bypass system background-start restrictions.

Battery-optimization exemption

ANDROID · OPTIONAL

Opens the system dialog so you can decide whether to keep the connection alive on long trips. Declining does not block core features.

Internet

ANDROID

Loads maps, searches for places, calculates routes, signs in, verifies trial/Premium access, and checks for store-managed updates.

Network and Wi-Fi state

ANDROID

Checks connectivity before network requests and lets the relevant identity/store service (Google or Huawei) perform sign-in, billing, or update checks. G Navigation does not use this access to read Wi-Fi passwords.

Visibility of declared apps

ANDROID

Checks only companion, navigation, store, and vendor battery/security-management apps named in the manifest to guide pairing, choose a transport, keep the link reliable, and determine the appropriate update or billing channel. It does not request QUERY_ALL_PACKAGES or visibility of every installed app.

AppGallery update and installer hand-off

ANDROID · APPGALLERY BUILD

Huawei App Service/Update SDK adds AppGallery common-data access and REQUEST_INSTALL_PACKAGES so the app can check its version and open an AppGallery/system-managed update screen. G Navigation does not silently install or install arbitrary APKs.

Restart and watch-readiness service

ANDROID

Uses RECEIVE_BOOT_COMPLETED, a connected-device foreground service, and companion background-start access to restore watch readiness after the phone starts, but only when call alerts are enabled or an active link requires it.

System sign-in and biometrics

ANDROID · DEVICE DEPENDENT

The Android/Google system sign-in sheet may use a passkey, fingerprint, or other biometric to confirm identity. G Navigation receives only the authentication result/token, not a face image, fingerprint template, or raw biometric data.

Watch position

HUAWEI WATCH LITE

During navigation, the watch may send its current fix to the phone for route following. Inaccurate fixes are discarded and the watch does not retain a location history.

Local watch storage

HUAWEI WATCH LITE

Stores consent, settings, and a minimal current-session cache; journey cache expires after no more than five minutes.

Vibration

HUAWEI WATCH

Provides haptic turn and navigation-state alerts on supported devices.

05

Data sources and recipients

Depending on the feature you choose to use, data may leave the device to load maps, search or calculate a route, connect a watch, sign in, verify trial/Premium access, process a purchase, or check for updates. This section identifies the relevant data categories, recipients, and purposes.

Where your position comes from and what it does. Position is read through Android's location service on the phone and — while navigation is active on a paired Huawei Lite watch — from the watch receiver and sent to the phone over the watch channel. It is used to show you on the map, keep the map/arrow oriented, measure the next turn, follow the route, and reroute. When you search for a place or request a route, the phone sends the position needed for that request to the G Navigation server over HTTPS; the server calls the relevant provider and does not retain the search text or route coordinates as history. The app does not upload location on a schedule while you are not using these features.

Where the map comes from. The map data is OpenStreetMap, and the drawing is done on your device by MapLibre GL from the OpenFreeMap styles liberty for the light map and fiord for the dark one, both served from tiles.openfreemap.org. A tile request contains the coordinates of the map area on screen and standard network metadata such as an IP address; G Navigation does not intentionally attach an account, destination, or search text to that request. If you select the Google or satellite base map, picture tiles are fetched from Google's tile hosts while that view is selected.

How it travels. App network requests use HTTPS. In a release build, route and place-search requests go through the G Navigation server, which checks the session/entitlement, calls the upstream provider, and returns the result. The upstream provider therefore normally sees our server rather than your device, and its service credentials are not stored in the app. Map tiles and requests made by identity, store, or watch SDKs go directly to the relevant provider and may include standard network/device metadata under that provider's policy.

  • OpenFreeMap / MapLibreLoads map styles and tiles. Open source: github.com/hyperknot/openfreemap and github.com/maplibre/maplibre-native.
  • Photon or NominatimProcesses search queries and location bias when needed. Open source: github.com/komoot/photon and github.com/osm-search/Nominatim.
  • A paid place indexOnly when you choose the Google search index: our server passes the search text and the rough position used to rank results to a commercial place index it holds the credential for. Your phone never contacts that index and carries no key for it.
  • openrouteservice or an OSRM serverCalculates routes from origins, destinations, and a vehicle type according to the release configuration. Open source: openrouteservice and OSRM.
  • Privately operated ValhallaCalculates motorcycle routes from origins, destinations, and a travel profile. Open source: github.com/valhalla/valhalla.
  • Google Maps SDK for AndroidGoogle Play build only, and only when you choose the Google map view: loads Google's base map together with the standard device information that accompanies its requests. When you use Google map mode, the Google Maps SDK collects device/request metadata, IP address, a pseudonymous SDK identifier, crash information and map interactions such as panning/zooming to operate and improve Google services. See the Google Maps SDK data disclosure. This SDK data is separate from G Navigation’s local call diagnostics.
  • Huawei Wear Engine, Mi Fitness/Vela, or Zepp OSTransfers current-session data between the phone and paired watch.
  • Huawei ID/HMS Core or Google Identity/Google Play IntegrityDepending on the distribution, authenticates an account using an authorization code/ID token and supplies an account ID, display name, or email when the user/provider permits. The system provider may process device and biometric/passkey information without giving raw biometric data to G Navigation. The AppGallery build also checks for store-managed updates after consent.
  • G Navigation entitlement serverStores an account ID and hashed session token; limits trials by account/device/network; processes integrity results; and keeps the product ID/purchase token and verification state needed to grant or restore Premium.

Main services and endpoints used by the current release. Google, Huawei, Xiaomi, or Zepp SDKs may use additional vendor endpoints according to the device/SDK version and that vendor's privacy policy; G Navigation does not control those dynamic hostnames.

  • tiles.openfreemap.orgMap styles and vector tiles. Contacted directly by the phone whenever the map is drawn.
  • mt0.google.commt3.google.comGoogle's picture tiles. Contacted directly, and only while the Google or the satellite base map is the one you have selected.
  • g-navigation-get.gg-huawei.workers.devThe app's own download and update page, asked whether a newer build exists.
  • photon.komoot.io, nominatim.openstreetmap.orgThe OpenStreetMap search services that answer a place query. In the released app our server calls them; a development build with the gateway switched off calls them directly.
  • api.openrouteservice.orgA route service that may be called by the G Navigation server according to the release configuration; the phone does not send directly to this endpoint.
  • An OSRM server and a privately operated Valhalla serverRoute calculation. Only our server holds their addresses, and the released app never contacts them itself. A development build with the gateway off uses the public routing.openstreetmap.de and valhalla1.openstreetmap.de instead.
  • Huawei, Google, Xiaomi and Zepp servicesSigning in, checking a store for an update and pairing a watch are carried out by each vendor's own SDK, which contacts that vendor's servers under that vendor's privacy policy. G Navigation adds nothing of its own to those requests.

G Navigation does not sell data or use advertising networks. The app has no separately integrated analytics or crash-reporting service; the map SDK may collect operational data as described above.

06

Retention and deletion

  • The current phone route, up to eight recent destinations, and saved favourite places are stored locally until replaced, removed by you, or cleared with Delete local data.
  • Watch Lite journey cache is retained for no more than five minutes.
  • G Navigation does not keep names or notification contents as call history. Names may be written into temporary contact entries for watch lookup. App-created entries are cleaned after about 30 seconds without a call; if Android stops the app, cleanup retries when it runs again. Entries you edited or merged are preserved against data loss and can be deleted in Contacts. Up to 300 technical events are stored locally, containing times, source app type, state, action results and errors, but no caller names/numbers, notification contents or audio. Events older than 48 hours are pruned while the app runs or logs are written/read; data may remain on the phone while the app is stopped. Disabling call alerts, withdrawing consent or clearing app data deletes these logs. Logs are not automatically uploaded. Android, the watch and companion apps may retain received data under their own settings; G Navigation cannot delete those copies on their behalf.
  • Consent records store the policy version, acceptance time, and selected language.
  • Account sessions and account-linked trial records are retained as needed to authenticate, prevent abuse, and prevent repeat trial grants, then deleted when the account is deleted. A hashed device marker that is not linked to the account profile is retained for up to three years to prevent repeat trials; daily network hashes are retained as needed for the same purpose. The Google-managed anti-abuse deviceRecall bit may be retained for up to three years after its most recent read or write.
  • For a purchase, the product ID, purchase token, and verification/revocation state and times are retained as needed to grant or restore access, prevent fraud, and meet transaction obligations; the store handles full payment details.
  • The G Navigation server does not retain successful-login history, installation-source reports, search text, or route coordinates. Place and route capacity counters are service-wide totals and contain no account or device identifier.
  • The Android app disables system backup of its app data.

In G Navigation, open Settings > Account > Delete account to delete the profile and its account-linked server data. Deletion does not reset trial eligibility: a new account on the same device will not receive a second trial. The hashed device marker described above is not linked to the account profile and may be retained for up to three years solely to enforce this limit. You can also review this policy, withdraw consent, delete local data, revoke system permissions, or uninstall with system tools. If you cannot access the app, email hng89tn@gmail.com with the subject “G Navigation account deletion” and identify the sign-in provider and account email, but never send a password. After identity verification, G Navigation-controlled data will be deleted except records that must be retained for legal, transaction, security, or anti-fraud obligations.

07

Choice and consent

  • Consent is versioned. When a material change increases the policy version, the app asks you to decide again.
  • Withdrawing consent stops navigation-data processing and returns the app to its limited setup shell.
  • Background location, notification access, Contacts/call alerts, and the battery-optimization exemption have separate explanations or choices.
  • Declining optional access does not block core OpenStreetMap navigation.
08

Data security

Store releases allow map, search, routing, identity, and policy endpoints to be configured only with HTTPS. G Navigation limits locally retained data to its stated purposes, disables Android system backup, and does not retain Google Maps guidance or call notifications as history.

No transmission or storage method is completely secure. If you identify a security or privacy issue, contact the address at the end of this policy.

09

This policy site

This static document is hosted by GitHub Pages. It sets no cookies, runs no JavaScript, and uses no analytics, advertising, third-party fonts or tracking tools. GitHub may process IP addresses and network request data to provide and secure its hosting service under its own policies.

10

Policy changes

The update date and version appear at the top of this page. If a change materially affects data handling, G Navigation will increase the policy version and request consent again in the app.

11

Contact

For support, access, or deletion requests concerning data controlled by the app (never send a password):

Nguyen Thanh Hung
hng89tn@gmail.com