Privacy Policy — GPS Simulator: Fake GPS

1. Overview

This policy explains how GPS Simulator: Fake GPS (“App”, “we” or “our”), published by Karam Mobile, processes information when you use mock GPS features, maps, routes, settings, diagnostics, optional problem reporting, and app analytics. The App is free and does not display advertisements or sell personal information.

You can use the main GPS simulator without creating a personal sign-in account. An anonymous Firebase account identifier may be created if you submit a problem report.

2. Location access and mock GPS

With Android's foreground location permission, the App reads your real location to show your position on the map, center the map when requested and provide GPS diagnostics. It may use Google Play services' fused location provider. It does not request the Android ACCESS_BACKGROUND_LOCATION permission.

When you enable Android's “Select mock location app” option and start simulation, your chosen simulated position is supplied to Android location providers through a foreground service. Other apps on your device may then receive that simulated position, subject to their own settings and policies. A foreground notification may display the simulated position while simulation is active.

Real and simulated location readings are used to operate GPS and map features. The App does not intentionally transmit raw real or simulated GPS coordinates as parameters of its custom Firebase Analytics screen-view events. It does not sell your location history. External services may receive location-related requests as described in Section 3.

3. Maps, place search and route services

Google Maps: Current signed Google Play releases use the Google Maps SDK for standard and satellite map display. Google may process network information, device information, map viewport and interactions to provide map imagery, according to Google's Privacy Policy. Experimental or older builds may use OpenFreeMap, CARTO, Esri or OpenStreetMap-related map sources, which can receive map-tile requests and your IP address.

Place search and geocoding: When you search for a place or ask the App to resolve a location to an address, the App may send the search text or relevant coordinates to the OpenStreetMap Nominatim service. Its server may receive your IP address and technical request information.

Route planning: To calculate road-following routes (for example walking, cycling or driving), the App may transmit route start points, destinations and intermediate waypoints to public OSRM routing services. Their operators can process these points and your IP address as part of the request.

These providers are separate from Firebase Analytics. We do not control their independent server logs or retention periods. Avoid searching for, selecting or routing to sensitive locations if you do not want relevant location details sent to the service used for that feature.

4. Firebase Analytics and app usage

App versions that include Firebase Analytics use Google Analytics for Firebase to understand aggregate app activity, diagnose feature usage and improve usability. The SDK may automatically process app opens and first launches, session statistics, engagement, app version, operating system, device model, an app-instance identifier and approximate geographic region (which can be inferred from network information such as an IP address).

We also send events for a fixed allowlist of screen names, such as Map, Search, Settings, and Routes. These custom events do not contain precise GPS coordinates, simulated positions, searched addresses, saved locations or routes.

The App disables advertising ID collection in Firebase Analytics and does not request the Android AD_ID permission. It also disables analytics ad-personalization signals. These restrictions do not mean Analytics collects no technical or installation identifiers.

Firebase Analytics data is processed by Google according to its applicable terms, privacy documentation and configured data-retention controls. See Firebase Privacy and Security and Firebase Analytics Data Collection.

5. Optional problem reports and Firebase services

If you voluntarily use the “Report a problem” feature, the App sends your written report, a problem category, app version, Android version, device manufacturer/model, report timestamp and a Firebase anonymous user identifier to Google Firebase Authentication and Cloud Firestore. This information is used to receive, investigate and resolve the reported issue. Please do not include sensitive information, passwords or precise locations in the free-text description.

Firebase App Check / Play Integrity may also process technical app and device integrity signals to protect these services against abuse. No personal sign-up is required to use the App's core GPS features.

Information entered into a support email or problem report is used for support, and is not sold to advertisers.

6. Data stored on your device

Depending on your preferences and use, local app storage can include map appearance and other settings, last map position, recent searches, saved places and favourites, route plans, geofences, mock-session details and history. These are not uploaded to Firebase Analytics by our custom screen-view tracking.

You can clear history, remove saved items or delete all local app data using the App's settings, or clear the App's storage through Android. Android's optional device-backup feature may include some locally stored app data in your Google account backup; Android and Google control those backups.

7. Purposes, security, retention and deletion

We use data to provide the map and GPS features you request, protect the App's backend against misuse, process reports you choose to submit, and understand aggregate app usage. Internet communications with the named services use encrypted HTTPS connections where supported.

Local information stays until you remove it, clear app data or uninstall the App, subject to any Android device backups. Problem reports and associated anonymous identifiers are kept in Firebase for support and issue resolution until they are no longer needed or are deleted following a valid request, subject to applicable obligations. Analytics information is retained under the Google Analytics property's configured retention settings and provider policies, and may be aggregated or deleted according to those controls.

To request access to or deletion of information held by the developer, including a report you submitted, email gps.simulator.support@gmail.com with sufficient details to locate the report. We may request reasonable verification before acting. Uninstalling the App stops future collection from that installation but does not by itself erase server-held support reports or already processed analytics information.

8. Choices and privacy rights

You may deny or revoke location permissions through Android settings, stop a mock location session, delete local data and refrain from submitting problem reports. If you live in the European Economic Area or another jurisdiction with data-protection rights, you may contact us to request information, access, correction, deletion, objection or other available rights, subject to applicable law.

Analytics collection and consent choices depend on the installed App version and implemented controls. Some versions may automatically collect analytics data on launch and may not provide a separate in-app Analytics opt-out switch. If you have questions about analytics collection or the handling of a request, contact the developer. Where applicable law requires consent for Analytics, appropriate consent controls must be implemented in the App separately from publishing this policy.

9. Permissions

• Precise / approximate location: show real position, diagnostics and map centering with your permission.
• Mock location: supply simulated positions when you select the App in Android Developer Options.
• Internet and network state: maps, searches, route planning, Firebase services and Analytics.
• Foreground service and notifications: keep active mock sessions operating and display status controls.

The App does not require camera, microphone, contacts or SMS access for its described core features.

10. Children

GPS Simulator is not designed or marketed specifically for children. If you believe that a child's personal information was submitted in a support report, contact us and we will review the request.

11. Updates and contact

We may update this Privacy Policy when the App's functionality, service providers or legal requirements change. Changes will be published at this same page with a revised “Last updated” date.

Developer / privacy contact: Karam Mobile — gps.simulator.support@gmail.com.