goGPS Drive
English
Get the app
Menu
YOUR DATA AND CHOICES

Privacy policy

The policy below applies to the goGPS Android app.

Last updated: 5 September 2026

This privacy policy applies to the goGPS mobile app. App package name: com.netdestek.gogps.

Developer and contact

Developer: Net Destek. For privacy questions and data requests, use the contact channels at https://netdestek.net/ or the developer contact details in the Google Play store listing.

Data collected or accessed

goGPS requests only the permissions needed to provide its features and does not access sensitive data without user permission.

  • Approximate and precise location data: The app accesses the device location when the user grants Android location permission. Location data processed may include GPS information such as latitude, longitude, accuracy, speed, direction, altitude and timestamps. When certain internet-based features are used, necessary location information may be sent to the service providers described below.
  • Camera, video and live audio data: Camera permission is used for dashcam video recording, front/rear camera recording, recording previews and user-initiated Live View. During Live View, the remote camera image is streamed live and encrypted. This live session does not itself create video or audio recordings; separately enabled motion-detection recording may operate independently. The other device’s microphone is not activated and ambient sound is not sent to the main phone. Microphone permission is used only on the main phone to send live audio while the user holds the Push-to-Talk button. Push-to-Talk audio is not saved to a file or queued for later delivery when there is no connection.
  • Google Drive account information: If the user enables Google Drive integration, the email address of the connected Google account may be stored in the app and used to display Drive upload status.
  • Purchase and subscription information: Subscription status and purchase information may be processed through Google Play Billing and RevenueCat to verify Premium access.
  • Bluetooth and notification permissions: Bluetooth connection status may be used to start the app in situations such as connecting to a car, making it easier to use. Notification permission is used to show recording and background GPS status.

How location data is used

goGPS uses location data for the following app features:

Summary: goGPS accesses, collects, and uses location data, including precise and approximate latitude, longitude, accuracy, speed, direction, altitude and timestamps, for GPS route recording, live location, speed and altitude display, background GPS recording when enabled, navigation, weather, alerts and location-stamped video copies.

  • Live GPS tracking, route/history recording and displaying routes on the map.
  • Displaying speed, altitude, direction, movement and driving statistics.
  • Recording GPS points for geofence alerts, speed alerts and accident/evidence features.
  • Creating a separate location-stamped copy of selected videos with speed, date and coordinate overlays.
  • Providing map and navigation features.
  • Retrieving the temperature for the current location when the weather display is enabled.
  • Finding nearby electric vehicle charging stations and showing them on the map.
  • With separate user consent, finding nearby tyre shops and car services, showing them on the map and saving them on the device for offline use.
  • With separate user consent, finding nearby pharmacies and hospitals, showing them on the map and saving them on the device for offline use.

Background location use

If the user enables Background GPS Recording and grants the Android location permission “Allow all the time”, goGPS can continue GPS recording when the app is not visible on screen. This is needed to keep route and speed records uninterrupted while driving. A foreground service notification may be displayed while background GPS is running.

goGPS does not use background location for ad targeting or user profiling. Service providers’ processing of limited technical data for diagnostics, security and service improvement is subject to their own privacy terms.

Where is data stored?

Video and GPS recordings are stored by default on the user’s device in goGPS folders managed by the app. GPS recordings can be converted to route files such as JSON or KML. Users can delete recordings in the app or device storage; the device may delete app data when the app is uninstalled.

Sharing with third parties

goGPS does not sell personal or sensitive user data. Data is shared only through user-initiated features or necessary service providers:

  • Google Drive: If the user enables and authorizes Drive integration, camera videos, accident-locked videos, GPS KML recordings, geofence records and speed alert records may be uploaded to goGPS folders in the connected Google Drive account. The app uses goGPS/Video, goGPS/accidentlock, goGPS/GPS, goGPS/warning and goGPS/speed. During Live View + Push-to-Talk, only short-lived connection information needed to establish an encrypted WebRTC connection between devices may be written to the goGPS folder. It contains no video or audio content and is deleted at session end or during expiry cleanup. Depending on retention settings chosen by the user, some old Drive files uploaded or created by the app may be deleted; this does not delete local phone recordings.
  • WebRTC connection infrastructure: Live View + Push-to-Talk media is transmitted directly and encrypted between devices whenever possible. If network conditions prevent a direct connection, encrypted media may pass through a TURN relay service configured in the app. The app does not store live session media on that service for recording purposes.
  • Open-Meteo: When the weather display is enabled, current coordinates may be sent over HTTPS to the Open-Meteo API to retrieve the temperature.
  • Open Charge Map: When the user opens the nearby charging stations layer, the approximate or precise coordinates they have authorized are sent over HTTPS to the Open Charge Map API to retrieve nearby stations. Results may be cached briefly on the device for offline display.
  • Google Maps and Google Navigation: When online maps or navigation are used, current location, route and destination information may be processed by Google map/navigation services. The relevant Google SDKs may also process limited device, interaction and diagnostic data to provide and improve their services.
  • TomTom live traffic: If the user explicitly starts the optional “Start with Google Maps and monitor faster routes” or live traffic feature, the remaining planned route geometry and the route start and destination coordinates are sent over HTTPS to the TomTom Routing API to assess traffic travel time and suggest a faster route. GPS location history is not sent. goGPS does not read the route or arrival time chosen by Google Maps. Queries run roughly every 10 minutes while driving and less often during long stops; offline navigation is unaffected without internet. This transfer runs only when the user starts the feature and stops when ended from the persistent notification, when goGPS detects arrival, or after at most 8 hours.
  • Google Play and RevenueCat: These services may process payment and subscription information to verify purchase and subscription status.
  • System sharing: If the user manually shares a video or file, the selected app or service processes the data under its own privacy policy.

Data security

Tyre shop and car service search — OpenStreetMap / Overpass API: When this optional feature is first opened, a separate information and consent screen appears. If the user agrees, the current approximate or precise coordinates, search radius and business type filter are sent over HTTPS to overpass-api.de . The service may also see the IP address and technical HTTP headers identifying the app. GPS route history, camera recordings, account information and device advertising identifiers are not included. Queries run when the user opens or refreshes the layer; no separate continuous background location-tracking service is started. A user-initiated search waiting for a location may finish with the first suitable location; an open layer may be restored when the screen is recreated.

Business results, query centre, radius and retrieval time are stored in the app’s private SQLite cache for up to 12 search areas. Results for the same area can normally be reused for 24 hours without querying again. User-requested refreshes are limited to at least one minute apart; service errors may require longer waits. Saved nearby places can be shown offline; this feature does not pre-download businesses for a whole country. Results older than 30 days are not shown and are removed on the next successful save. The cache is excluded from cloud backup and device transfer. “Nearby places > Delete saved service points” deletes these records and revokes consent to share location with Overpass. Local deletion does not delete technical server logs the third party may already have processed. Business data is displayed with attribution to OpenStreetMap contributors / ODbL . Google Maps directions open only if separately selected by the user.

goGPS uses secure connections such as HTTPS for supported network transfers. goGPS does not sell location data or use it for ad targeting. Third-party SDKs and service providers may process limited technical data under their own privacy terms to provide features, maintain security, diagnose errors and improve services.

Pharmacy and hospital search — OpenStreetMap / Overpass API: When the user first opens either layer, a location-transfer notice is shown separately from tyre shop/car service consent. With consent, the current approximate or precise location, search radius and pharmacy/hospital type filter are sent over HTTPS to overpass-api.de . The service may see the IP address and technical HTTP headers. Health history, diagnoses, medication information, account data and GPS route history are not collected or sent in this search; the service can see that the requested types are pharmacies and hospitals. Viewing a place does not mean the user visited it or has a health condition.

Pharmacy/hospital results, search centre, radius and retrieval time are stored separately from car services in the healthcare_places.db SQLite cache. Up to 12 search areas are kept; normal freshness is 24 hours and offline display is limited to 30 days. Older records are removed on the next successful save. The cache is excluded from cloud backup and device transfer. Queries may run when the user opens/refreshes the layer, when a search waiting for location completes, or when an open layer is restored after screen recreation; there are no continuous background queries. “Nearby places > Delete saved pharmacy and hospital points” deletes only these records and revokes their location-transfer consent; charging and car-service records are unaffected. Local deletion does not remove third-party server logs. These data do not guarantee on-duty pharmacies, current opening status or emergency-service availability. Google Maps directions open only if separately selected. Business data is displayed with attribution to OpenStreetMap contributors / ODbL .

Data retention and deletion

Local recording retention depends on the user’s app settings and file management in device storage. With Google Drive integration enabled, user-selected retention settings may apply to camera and accident-locked recordings on Drive. GPS KML recordings may remain in the connected Drive account unless the user disables the relevant Drive storage option. Video and transmitted audio in Live View + Push-to-Talk are not stored permanently; they are processed only in short-lived memory buffers for live transmission. Retention rules for separately enabled motion recordings are independent of the live session. Temporary connection signals are normally removed at session end, or by expiry cleanup for interrupted sessions. The user can disconnect Drive in app settings, stopping new automatic uploads.

User choices

  • Camera, location, background location, notification and Bluetooth permissions can be managed in Android settings.
  • Background GPS Recording can be disabled in app settings.
  • Google Drive integration can be disabled or disconnected in app settings.
  • Live faster-route monitoring starts only at the user’s request and can be ended with “Stop monitoring” in the persistent notification.
  • Video and GPS recordings can be deleted in the app or device storage.

Children’s privacy

goGPS is not specifically designed for children.

Policy changes

This privacy policy may be updated when app features, legal requirements or Google Play policies change. The current version is published on this page.

This promotional website

This site uses no forms, user accounts or analytics cookies. The hosting service may process connection information to serve pages and maintain security. External links such as Google Play are governed by the relevant service’s privacy terms.