Privacy Policy

Location Simulator – Mock GPS Privacy Policy Last Updated: June 1, 2026

This Privacy Policy explains what data the Android app Location Simulator – Mock GPS ("the App") processes and how. The App is a developer tool designed for developers, testers, and users to test location-based scenarios on their device.

Developer / Data Controller: Abdulkadir ER Contact: akillisletme@gmail.com

1. Purpose of the App

Location Simulator – Mock GPS has been developed for the following legitimate use cases:

• Testing location-based applications • Trying different GPS scenarios during software development and quality assurance • Simulating map, route, location, and scheduling features on a device • Educational, experimental, and personal privacy awareness use

The App must not be used for the following purposes:

• Cheating in games, apps, or services • Fraud, deception, or identity concealment • Violating the terms of use of third-party apps or services • Any illegal, harmful, or unauthorized activity

The user is responsible for how the App is used. The App does not encourage illegal use or misuse.

2. Data We Process

A. Location and Simulation Data Stored on Device

The following data you create or save within the App may be stored locally on your device:

• Mock GPS coordinates • Favorite locations • Joystick starting positions • Saved routes • PRO route waypoints and route parameters • Human behavior simulation settings • Scheduled locations • Home widget and floating widget slot settings • Map and interface preferences • Language, theme, and consent preferences

This data is not uploaded by us to any external server, sold, or shared with third parties. The data is stored on your device, in Android's app data area.

B. Real Device Location

The App may request Android location permission for certain features. For example:

• Centering the map on your current location • Caching the current location locally to improve the map experience • Easing the selection of a starting point at the user's request

Your real device location is not sent to our servers. The App does not use your real location for advertising, analytics, profiling, or third-party marketing purposes.

If the user uses the current location feature, the last known location may only be cached locally on the device. This data can be deleted by clearing the app data from Android settings or by uninstalling the App.

C. Route Files and Sharing

The App may import route files such as GPX, KML, or TCX if selected by the user. These files are processed on the device and used to create a route.

The App may also initiate the following sharing actions at the user's explicit request:

• Sharing a Google Maps link • Sharing a route link • Exporting or sharing a GPX file

The sharing action is performed via Android's system share sheet or a third-party app chosen by the user. Once shared, the third-party app's own privacy policy applies.

D. Local Preferences

The App may store the following information locally on the device:

• Language selection • Theme preference • Map view settings • Usage/consent status • Favorites and saved routes • Scheduler settings • Widget and floating widget settings • Local flags related to setup guide and permission status

This information is not tied to a user account. The App does not require account creation, sign-in, or personal profile creation.

E. Photo Location Metadata (Photo GPS Editor)

The Photo GPS Editor feature edits the EXIF location (GPS) metadata of a photo you explicitly select, entirely on your device. The edited photo is saved as a new copy to your device gallery. This operation is fully local; your photos and their metadata are not sent to our servers. The App does not scan photos in the background; it only accesses the single file you select. This feature requires Android's ACCESS_MEDIA_LOCATION permission (see Section 4).

3. Third-Party Services and SDKs

The App uses the following third-party services:

A. Google Maps Platform

The Google Maps SDK is used for map display, coordinate selection, and map interaction.

According to Google's own policies, the Google Maps SDK may automatically process certain technical data such as IP address, device metadata, SDK/app information, crash metrics, unique identifiers, and map interactions.

The processing of this data is subject to Google's own privacy policies. We do not have access to the raw data sent to Google by the Google Maps SDK and do not store this data on our own servers.

Google Privacy Policy: https://policies.google.com/privacy

B. Firebase Remote Config

Firebase Remote Config is used to manage app configurations such as app version and forced updates.

For Firebase to function, Remote Config may process technical information such as country code, language code, time zone, platform/OS version, Firebase Android App ID, and app package name.

We do not use Remote Config for user tracking, advertising, behavioral analytics, or profiling.

C. Firebase Crashlytics

Firebase Crashlytics may be used to improve app stability and detect crashes.

Crashlytics may process technical crash data such as app version, package name, device model, operating system version, crash time, error logs, stack traces, and similar. This data is used to fix bugs and improve the security/stability of the App.

We do not knowingly collect personal content such as name, email, phone number, contacts, messages, payment information, or user-saved mock location lists through Crashlytics.

D. Internet Connectivity Check

The App may check whether the device is online to provide a smooth map experience. This check is used only to show the user an appropriate screen when offline. This process is not used to create a user profile or perform behavioral tracking.

E. Address Search (Geocoding)

When you search for a place name on the map, the text you type is resolved into coordinates through the device's Android system geocoder. This resolution happens over the internet and the backend provider may be Google; therefore only the search query you type leaves the device. We do not store your search queries, associate them with you, or use them for profiling. Your real location coordinates are not sent during this operation.

F. Cloud Firestore (Read-Only)

The App only reads the app_meta/changelog document from Cloud Firestore to display the "What's New" (changelog) text. This is one-way: the App reads data from this document, and no user data is written or uploaded to Firestore. During the read request, Firebase infrastructure may process standard connection metadata such as the IP address as a technical necessity of the request; this data is subject to Google's own policies. Your saved locations, routes, or other personal data are not associated with this operation.

4. Permissions and Their Purposes

The App may use the following Android permissions or system settings:

Location Permission: Used to center the map on the current location and to ease location selection at the user's request.

Mock Location / Developer Options: Required for the App to be selectable as a mock location provider in the Android system. This is done by the user via Android's developer settings.

Notification Permission: On Android 13 and above, the notification permission may be required to show the status of foreground service operations such as mock location or the floating widget.

Display Over Other Apps / Overlay Permission: Used for the floating widget feature. This permission is requested only if the user enables this feature.

Exact Alarm / Scheduling Permission: Android's alarm permissions may be required for the scheduled location feature to run at the specified time.

File Picker: Used to import GPX, KML, or TCX route files if the user selects them. The App does not scan all files on the device; it only accesses the file selected by the user.

Media Location Permission (ACCESS_MEDIA_LOCATION): Used so the Photo GPS Editor can read the original EXIF location data of the photo you select. From Android 10 onward, EXIF GPS data is stripped without this permission. It is only needed when you use this feature.

5. About the Smart Shield Feature

The Smart Shield feature uses the Android Accessibility Service API (SmartShieldService) solely to detect when a user-configured application comes to the foreground. This allows the App to automatically switch location profiles and simulate the configured coordinates for that specific application, and automatically stop when the user leaves the application.

This service operates strictly locally. For detailed information regarding data processing, privacy boundaries, and user controls for this feature, please review our standalone Accessibility Service Disclosure page.

6. Data We Do Not Collect

The App, on its own behalf, does not collect, sell, or share the following data with third parties for marketing purposes:

• Name, email address, phone number • User account or login information • Contacts, SMS, call logs • Camera or microphone data • Financial or payment information • Advertising profile via advertising identifier • User behavior profile • A centralized server database containing your saved mock locations

How third-party SDKs process technical data is subject to the policies of the respective services.

7. Data Sharing

We do not sell user data.

App data is not shared with third parties except in the following cases:

• The user explicitly initiates a sharing action • Technical operation of integrated third-party services such as Google Maps SDK, Firebase Remote Config, or Firebase Crashlytics • Legally mandated requests or legal obligations

Your saved favorites, routes, and simulation settings are not automatically shared by us.

8. Data Retention

Data stored on the device may remain on the device until deleted by the user.

To delete this data, you can:

• Use the delete/reset features within the App • Clear app data from Android Settings > Apps • Uninstall the App from the device

Technical data processed by Firebase or Google services is managed according to those services' own retention and deletion policies.

9. Data Security

App data is stored in Android's app data area. This area is isolated from other apps by the Android app sandbox mechanism.

That said, no storage or transmission method is 100% secure. Device security, screen lock, operating system updates, and device access controls are the user's responsibility.

10. Children's Privacy

The App is not directed at children under 13. The App is a technical tool that requires familiarity with Android Developer Options and the concept of mock locations.

We do not knowingly collect personal data from children. If you believe a child's personal data has been processed, please contact us.

11. International Users

The App can be used worldwide. App data stored on the device remains on your device.

Google Maps and Firebase services may process technical data over Google's global infrastructure. This processing is subject to Google's privacy policies and terms of service.

12. Your Rights

Under applicable laws, you may have the following rights:

• Delete your local data • Revoke Android permissions at any time • Clear local data by uninstalling the App • Request information about our privacy practices • Request correction of incorrect or missing information • Object to data processing activities to the extent permitted by law

You can contact us at the following address for your requests: akillisletme@gmail.com

13. Policy Changes

This Privacy Policy may be updated from time to time. Changes are reflected in the "Last Updated" date on this page.

For significant changes, users will be notified, where possible, through in-app notification or a Play Store description.

14. Contact

For questions about privacy, data processing, or the App's permissions:

Email: akillisletme@gmail.com Developer: Abdulkadir ER

15. Governing Law

This Privacy Policy has been prepared with reference to the laws of the Republic of Turkey, in particular the Law No. 6698 on the Protection of Personal Data (KVKK). If the App is used in other countries, the relevant local data protection regulations may also apply.

— Change Note (June 1, 2026): Updated for the v1.7.0 release. The read-only use of Cloud Firestore (app_meta/changelog "What's New" text) and the Photo GPS Editor feature were explicitly added; the ACCESS_MEDIA_LOCATION permission was noted in the permissions section.